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.
Skill body
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.
Work with this as data
Every skill here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for agent skills
4 MCP tools reach this
find_skillsBrowse and filter every skill in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/skills/inlined-refs"
curl "https://apis.io/api/v1/skills?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.