# didi/KnowStreaming

一站式云原生实时流数据平台，通过0侵入、插件化构建企业级Kafka服务，极大降低操作、存储和管理实时流数据门槛

Repository: https://github.com/didi/KnowStreaming
Canonical: https://ross.abutalabs.com/products/knowstreaming
Homepage: https://knowstreaming.com
Language: Java
License: AGPL-3.0
License Family: copyleft
Topics: kafka, kafkamonitor, kafkamanager, logikm, cluster-manager, multi-cluster, clustermanager, multi-cluster-management, knowstreaming
Last push: 2026-08-18T06:34:29+00:00

## Health v2 (maintenance only)
Score: 87/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 98, release rhythm 66, longevity 100
- inputs: {"age_days": 2358, "days_push": 15, "days_rel": 15, "gap_med": null, "n_releases_24m": 1}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 7177, forks 1297 (observed 2026-08-28T04:09:56.435016+00:00)

## What it is
Know Streaming is a cloud-native Kafka management and control platform built from years of operational experience at Didi. It provides zero-intrusion, plugin-based management of Apache Kafka clusters (0.10.x to 3.x.x, ZK and Raft modes) with GUI-based operations, monitoring dashboards, health inspections, and resource governance.

## Use cases
- manage multiple kafka clusters from a single web ui
- monitor kafka broker and topic metrics with dashboards
- run health inspections and get cluster health scores for kafka
- rebalance kafka cluster load and migrate topic replicas
- manage kafka topics, consumer groups, ACLs and Connect via GUI
- get alerts on kafka cluster anomalies
- onboard existing kafka clusters without any code changes

## When to choose
- you operate multiple Kafka clusters and want a unified, visual management platform
- you need zero-intrusion monitoring and health checks for Kafka versions 0.10.x through 3.x
- your ops team wants GUI-based topic, consumer group, and ACL management instead of CLI
- you need enterprise features like load balancing, replica migration, and multi-cluster disaster recovery

## When to avoid
- you use message queues other than Kafka (e.g. Pulsar, RabbitMQ)
- you only need a lightweight single-cluster Kafka UI without enterprise ops features
- you cannot deploy a Java-based self-hosted service with a database dependency
- you require a fully managed cloud service rather than self-hosted infrastructure

## Facets
- artifact type: application
- maturity: active
- function: monitoring, alerting, analytics, web-framework, developer-tools
- domain: monitoring, big-data, self-hosted
- platform: jvm, self-hosted
- tags: kafka, kafka-management, cluster-management, multi-cluster, kafka-monitoring, kafka-ui, streaming, ops-platform, devops, messaging, web-server, docker, linux

## Member repositories
- didi/KnowStreaming (main) score 87

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:09:56.435016+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:39:55.926336+00:00, confidence not recorded.
  - readme: https://github.com/didi/KnowStreaming (fetched 2026-08-28T04:09:56.435016+00:00, sha 58acf497cdb8)
- Data as of 2026-08-30T08:39:29.467469+00:00.