Kafka Resource Analyzer - Topics & ACLs offline visualisieren

Kafka Resource Analyzer

Verschaff dir einen Überblick über das Chaos in deinem Kafka-Cluster — ohne dich mit ihm zu verbinden.

Füge den Output deiner Topic- und ACL-Dumps ein und erhalte sofort eine Analyse: Topic-Hierarchie, Partitions- und Replication-Konsistenz, Config-Audit und ein interaktiver Zugriffsgraph deiner ACLs.

Alles läuft zu 100 % lokal in deinem Browser — deine Daten verlassen deinen Rechner nicht. Keine Cluster-Verbindung, kein Upload, keine Installation. Das vorgeladene Beispiel ist die (komplett fiktive) Kafka-Plattform eines Windpark-Betreibers — ersetze es einfach durch deine eigenen Dumps.

Topics leer

Rohe Namensliste, kafka-topics.sh --describe-Output oder Strimzi-KafkaTopic-YAML — wird automatisch erkannt.

Apache Kafka bin/kafka-topics.sh --bootstrap-server broker:9092 --describe

Strimzi kubectl get kafkatopics -n <namespace> -o yaml

Topic: windworks.telemetry.scada.raw	PartitionCount: 24	ReplicationFactor: 3	Configs: retention.ms=1209600000
Topic: windworks.telemetry.scada.validated	PartitionCount: 24	ReplicationFactor: 3	Configs: retention.ms=604800000
Topic: windworks.telemetry.vibration	PartitionCount: 12	ReplicationFactor: 3	Configs: retention.ms=1209600000
Topic: windworks.telemetry.power-output	PartitionCount: 12	ReplicationFactor: 3	Configs:
Topic: windworks.telemetry.scada.raw.archive	PartitionCount: 6	ReplicationFactor: 3	Configs: retention.ms=-1
Topic: windworks.telemetry.weather-correlated	PartitionCount: 6	ReplicationFactor: 3	Configs: segment.bytes=104857600,segment.ms=86400000
Topic: windworks.turbine.state	PartitionCount: 6	ReplicationFactor: 3	Configs: cleanup.policy=compact,min.compaction.lag.ms=0
Topic: windworks.turbine.status	PartitionCount: 6	ReplicationFactor: 3	Configs:
Topic: windworks_turbine_status	PartitionCount: 3	ReplicationFactor: 3	Configs:
Topic: windworks.turbine.firmware-updates	PartitionCount: 3	ReplicationFactor: 3	Configs: max.message.bytes=10485760
Topic: windworks.turbine.metadata	PartitionCount: 3	ReplicationFactor: 3	Configs: cleanup.policy=compact,delete.retention.ms=60000
Topic: windworks.commands.turbine-control	PartitionCount: 1	ReplicationFactor: 3	Configs:
Topic: windworks.alerts.critical	PartitionCount: 6	ReplicationFactor: 3	Configs: min.insync.replicas=3
Topic: windworks.alerts.notifications	PartitionCount: 6	ReplicationFactor: 3	Configs:
Topic: windworks.alerts.heartbeat	PartitionCount: 3	ReplicationFactor: 3	Configs: retention.ms=3600000
Topic: windworks.alerts.acknowledged	PartitionCount: 3	ReplicationFactor: 3	Configs: compression.type=gzip
Topic: turbine-maintenance-events	PartitionCount: 6	ReplicationFactor: 3	Configs: min.insync.replicas=1
Topic: turbine-maintenance-workorders	PartitionCount: 3	ReplicationFactor: 3	Configs: preallocate=true
Topic: turbine-maintenance-history	PartitionCount: 3	ReplicationFactor: 3	Configs: retention.bytes=536870912
Topic: windworks.settlement.meter-readings	PartitionCount: 12	ReplicationFactor: 3	Configs: min.insync.replicas=2
Topic: windworks.settlement.invoices	PartitionCount: 3	ReplicationFactor: 5	Configs: min.insync.replicas=3
Topic: windworks.settlement.corrections	PartitionCount: 3	ReplicationFactor: 3	Configs: unclean.leader.election.enable=true
Topic: windworks.settlement.audit-log	PartitionCount: 6	ReplicationFactor: 3	Configs: retention.ms=31536000000
Topic: weather_forecast_feed	PartitionCount: 3	ReplicationFactor: 3	Configs:
Topic: windworks.weather.observations	PartitionCount: 8	ReplicationFactor: 3	Configs:
Topic: anomaly-detector-1.2.0-turbine-window-store-changelog	PartitionCount: 6	ReplicationFactor: 3	Configs:
Topic: anomaly-detector-1.2.0-turbine-window-store-repartition	PartitionCount: 6	ReplicationFactor: 3	Configs:
Topic: anomaly-detector-1.1.0-turbine-window-store-changelog	PartitionCount: 6	ReplicationFactor: 3	Configs: cleanup.policy=compact
Topic: anomaly-detector-1.1.0-turbine-window-store-repartition	PartitionCount: 6	ReplicationFactor: 3	Configs:
Topic: power-forecast-2.0.1-forecast-store-changelog	PartitionCount: 3	ReplicationFactor: 3	Configs: cleanup.policy=compact,min.cleanable.dirty.ratio=0.1
Topic: windworks.reporting.daily-production	PartitionCount: 3	ReplicationFactor: 3	Configs: message.timestamp.type=LogAppendTime
Topic: windworks.reporting.kpi-dashboard	PartitionCount: 3	ReplicationFactor: 3	Configs:
Topic: windworks.erp.workorder-sync	PartitionCount: 3	ReplicationFactor: 3	Configs:
Topic: windworks.erp.asset-master	PartitionCount: 3	ReplicationFactor: 3	Configs: cleanup.policy=compact
Topic: test-turbine-data	PartitionCount: 3	ReplicationFactor: 2	Configs:
Topic: tmp.delete-me	PartitionCount: 1	ReplicationFactor: 3	Configs:
Topic: windworks.legacy.scada-bridge	PartitionCount: 3	ReplicationFactor: 3	Configs: flush.ms=1000
Topic: windworks.legacy.scada-bridge-dlq	PartitionCount: 3	ReplicationFactor: 3	Configs: retention.ms=604800000

ACLs leer

kafka-acls.sh --list-Output oder Strimzi-KafkaUser-YAML — wird automatisch erkannt.

Apache Kafka bin/kafka-acls.sh --bootstrap-server broker:9092 --list

Strimzi kubectl get kafkausers -n <namespace> -o yaml

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=windworks.telemetry., patternType=PREFIXED)`:
 	(principal=User:svc-scada-ingest, host=*, operation=WRITE, permissionType=ALLOW)
	(principal=User:svc-scada-ingest, host=*, operation=DESCRIBE, permissionType=ALLOW)
	(principal=User:svc-anomaly-detector, host=*, operation=READ, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=anomaly-detector-, patternType=PREFIXED)`:
 	(principal=User:svc-anomaly-detector, host=*, operation=ALL, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=GROUP, name=anomaly-detector, patternType=PREFIXED)`:
 	(principal=User:svc-anomaly-detector, host=*, operation=READ, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TRANSACTIONAL_ID, name=anomaly-detector-, patternType=PREFIXED)`:
 	(principal=User:svc-anomaly-detector, host=*, operation=WRITE, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=windworks.alerts.critical, patternType=LITERAL)`:
 	(principal=User:svc-anomaly-detector, host=*, operation=WRITE, permissionType=ALLOW)
	(principal=User:svc-alert-router, host=*, operation=READ, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=windworks.alerts.notifications, patternType=LITERAL)`:
 	(principal=User:svc-alert-router, host=*, operation=WRITE, permissionType=ALLOW)
	(principal=User:svc-mobile-push, host=*, operation=READ, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=power-forecast-, patternType=PREFIXED)`:
 	(principal=User:svc-power-forecast, host=*, operation=ALL, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=GROUP, name=power-forecast, patternType=PREFIXED)`:
 	(principal=User:svc-power-forecast, host=*, operation=READ, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TRANSACTIONAL_ID, name=power-forecast-, patternType=PREFIXED)`:
 	(principal=User:svc-power-forecast, host=*, operation=WRITE, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=windworks.weather.observations, patternType=LITERAL)`:
 	(principal=User:svc-power-forecast, host=*, operation=READ, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=windworks.reporting.daily-production, patternType=LITERAL)`:
 	(principal=User:svc-power-forecast, host=*, operation=WRITE, permissionType=ALLOW)
	(principal=User:svc-erp-sink, host=*, operation=READ, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=windworks., patternType=PREFIXED)`:
 	(principal=User:svc-grafana, host=*, operation=READ, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=GROUP, name=grafana-, patternType=PREFIXED)`:
 	(principal=User:svc-grafana, host=*, operation=READ, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=GROUP, name=*, patternType=LITERAL)`:
 	(principal=User:svc-legacy-scada, host=*, operation=ALL, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=CLUSTER, name=kafka-cluster, patternType=LITERAL)`:
 	(principal=User:svc-legacy-scada, host=*, operation=ALL, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=windworks.legacy., patternType=PREFIXED)`:
 	(principal=User:svc-legacy-scada, host=*, operation=ALL, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=windworks.turbine.firmware-updates, patternType=LITERAL)`:
 	(principal=User:svc-legacy-scada, host=*, operation=ALL, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=windworks.turbine.state, patternType=LITERAL)`:
 	(principal=User:svc-legacy-scada, host=*, operation=ALL, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=windworks.turbine.metadata, patternType=LITERAL)`:
 	(principal=User:svc-legacy-scada, host=*, operation=READ, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=windworks.settlement., patternType=PREFIXED)`:
 	(principal=User:svc-billing, host=*, operation=ALL, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=GROUP, name=billing-app, patternType=LITERAL)`:
 	(principal=User:svc-billing, host=*, operation=READ, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=turbine-maintenance-, patternType=PREFIXED)`:
 	(principal=User:svc-maintenance, host=*, operation=READ, permissionType=ALLOW)
	(principal=User:svc-maintenance, host=*, operation=WRITE, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=GROUP, name=maintenance-app, patternType=LITERAL)`:
 	(principal=User:svc-maintenance, host=*, operation=READ, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=windworks.erp., patternType=PREFIXED)`:
 	(principal=User:svc-erp-sink, host=*, operation=READ, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=GROUP, name=connect-erp, patternType=PREFIXED)`:
 	(principal=User:svc-erp-sink, host=*, operation=READ, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=windworks.telemetry.v1., patternType=PREFIXED)`:
 	(principal=User:svc-fleet-import, host=*, operation=ALL, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=windworks.turbine.blade-sensors, patternType=LITERAL)`:
 	(principal=User:svc-fleet-import, host=*, operation=READ, permissionType=ALLOW)

Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=win, patternType=PREFIXED)`:
 	(principal=User:svc-ops-dashboard, host=*, operation=READ, permissionType=ALLOW)

100 % lokal — deine Daten verlassen den Browser nicht

Was du siehst

Topic-Hierarchie — deine Topic-Namen, an ihren Trennzeichen zerlegt und als aufklappbarer Baum dargestellt. Namenskonventionen (und ihre Verletzungen) auf einen Blick.
Konsistenz — wie viele Topics mit wie vielen Partitionen und welche Replication Factors im Einsatz sind. Hoffentlich nur einer.
Config-Audit — jede gesetzte Topic-Config mit ihrer Werteverteilung. Zum Beispiel: cleanup.policy — 10× compact, 5× delete, 20× nicht gesetzt. Jeder Wert aufklappbar, damit du die Übeltäter siehst.
ACL-Analyse — wer darf was: pro Principal, pro Resource, Operations-Verteilung und ein interaktiver Zugriffsgraph.
Cross-Check — lade Topics und ACLs zusammen und finde Topics ohne ACL sowie ACL-Patterns, die ins Leere zeigen.

Über die Beispieldaten

Das vorgeladene Beispiel ist die komplett fiktive Kafka-Plattform eines Windpark-Betreibers: SCADA-Telemetrie fließt herein, Kafka-Streams-Anwendungen erkennen Anomalien und prognostizieren die Einspeisung, dahinter hängen Alerting, Wartung, Abrechnung und ERP-Integration. Drei Generationen von Teams haben ihre Spuren hinterlassen — mit Absicht: Fast jede Warnung, die der Analyzer kennt, hat hier ein Anschauungsexemplar. Vom test-turbine-data-Topic mit Replication Factor 2 bis zum Legacy-SCADA-Account mit Wildcard-ACLs.

Topics leer

ACLs leer

Was du siehst

Über die Beispieldaten

Kontakt

Adresse

E-Mail Adresse

Links