inlined-refs
Generate a Kafka consumer group lag dashboard. Use when the user asks to monitor lag, build a dashboard for consumer lag, or wire up Prometheus exporters for Kafka. Do NOT trigger for producer metrics, broker JMX, or Streams-specific monitoring.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-27
- Stars
- ★ 64
- Forks
- 11
01 前言 Front Matter
- name
- inlined-refs
- description
- Generate a Kafka consumer group lag dashboard. Use when the user asks to monitor lag, build a dashboard for consumer lag, or wire up Prometheus exporters for Kafka. Do NOT trigger for producer metrics, broker JMX, or Streams-specific monitoring.
02 资源文件 3
- 参考文档evals/evals.json366 B
- 参考文档index.json650 B
- 参考文档references/exporters.md571 B
03 SKILL.md 正文
inlined-refs — consumer lag dashboarding
Step 1 — pick the exporter
We support two exporters. Read the comparison below before recommending.
Exporter comparison (from references/exporters.md)
kafka-exporter (Danielqsj)
Pros: lightweight, single binary, exposes per-group lag directly.
Cons: stateful (consumes __consumer_offsets internally), can lag on large clusters.
Best for: clusters < 100 brokers, < 1000 consumer groups.
Config snippet:
kafka-exporter \
--kafka.server=localhost:9092 \
--kafka.version=3.5.0 \
--web.listen-address=:9308
Confluent Control Center
Pros: official, covers full Confluent Platform metrics. Cons: paid licensing, heavier footprint.
Best for: enterprise Confluent Platform users.
Step 2 — Grafana dashboard
Use Grafana dashboard 7589 for kafka-exporter. Filter by consumer group, plot kafka_consumergroup_lag over a 5-minute window.
Step 3 — alerts
Set lag > 10,000 messages for 5 minutes as the default alert. Adjust per topic SLA.
04 同仓库更多 Skills
msk-migration
Use this skill to assess and plan a migration from AWS MSK (Managed Streaming for Apache Kafka) to Confluent Cloud. Triggers on user intent like "migrate MSK to Confluent Cloud", "move off MSK", "MSK to CC cutover", "Zero-Cut migration from MSK", "kcp scan my MSK", or any discussion of MSK-to-CC assessment, planning, cluster sizing, Cluster Linking setup, Gateway-based switchover, or post-cutover validation. Do NOT trigger for non-MSK Kafka sources (open-source Kafka, Aiven, Confluent Platform, Redpanda) — this skill is MSK-only. Do NOT trigger for greenfield Confluent Cloud projects with no existing Kafka source. Do NOT trigger for general Kafka programming questions (producer/consumer code, Kafka Streams) unrelated to migration.
kafka-streams-programming
Architect, build, and debug Kafka Streams apps (JVM-embedded stream processing). Use when user mentions KStream, KTable, topology, TopologyTestDriver, StreamsBuilder, interactive queries, GlobalKTable, joins/windows/aggregations, or debugging issues (rebalancing, state stores, lag, deserialization errors). Also use when user wants to optimize Kafka Streams for WarpStream or tune Kafka Streams client configuration for WarpStream. Do NOT trigger for Flink, connectors, CDC, or plain producer/consumer.
kafka-schema-registry
Scan a project to identify Kafka applications, extract schemas from data models, tag PII fields, generate Terraform for Confluent Schema Registry registration, and produce a migration report with rollout ordering. Use this skill when a user asks to analyze a folder or repo for Kafka usage, extract schemas, audit producer/consumer configurations, or generate Terraform for Schema Registry.
flink-udf
Build and deploy Apache Flink user-defined functions (UDFs) in Java for stream processing over Kafka. Use this skill when users want to create scalar UDFs, user-defined table functions (UDTFs), or process table functions (PTFs) in Java, deploy them to Confluent Cloud or local Docker environments, and invoke them from Flink SQL or the Table API. Trigger on: Flink UDF, custom Flink function, process table function, PTF, UDTF, Flink user defined, extend Flink SQL, stateful stream processing with Flink. Do NOT trigger for: Kafka Streams UDFs (use kafka-streams-programming skill), general Flink job development without custom functions, CDC streaming data piplines that include Flink (prefer the confluent-cloud-cdc-tableflow skill), Flink connector setup, or Kafka producer/consumer code.
developing-kafka-python-client
Use when the user wants to build a Python Kafka producer or consumer, add Schema Registry to existing Python code, migrate from raw JSON to schema-backed serialization, or scaffold a confluent-kafka-python project for Confluent Cloud, local Docker, or WarpStream. Also use when user wants to optimize Python Kafka client configuration for WarpStream.
developing-kafka-java-client
Use when the user wants to integrate a Kafka client into an existing application or scaffold a Java Kafka client project (Maven or Gradle based) for Confluent Cloud, local Docker, or WarpStream. Covers the Apache Kafka Java clients (KafkaProducer/KafkaConsumer/KafkaShareConsumer) with Avro, JSON Schema, or Protobuf serializers. Also use when the user wants to optimize Java Kafka client configuration for WarpStream. Do NOT trigger for Kafka Streams apps (use kafka-streams-programming), Flink, connectors, or Kafka Python client (use developing-kafka-python-client).