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.
61
77%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/confluent-skill-reviewer/evals/mock-skills/inlined-refs/SKILL.mdinlined-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=:9308Confluent 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.
- Repository
- confluentinc/agent-skills
- Commit
db79f9e
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.