offsets

DE//AGENT currently lists 3 resources under offsets: 2 tutorials, 1 skill. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.

Documented learning objectives across these resources:

• Explain how consumer groups and offsets decide who reads what — via Own the consumer side — offsets, rebalances, and the KIP-848 protocol
• Detect a rebalance loop from consumer-group state history — via Own the consumer side — offsets, rebalances, and the KIP-848 protocol
• Know what the KIP-848 protocol changes about rebalancing — via Own the consumer side — offsets, rebalances, and the KIP-848 protocol
• Read per-partition lag to separate skew from throughput — via Triage Kafka consumer lag from per-partition offsets
• Detect a rebalance loop from consumer-group state — via Triage Kafka consumer lag from per-partition offsets
• Find the poison message from retry counts — via Triage Kafka consumer lag from per-partition offsets

These resources map to stage: Streaming (3). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.

Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.

How scores are computed: source quality score.

Highest composite score first:

1. Own the consumer side — offsets, rebalances, and the KIP-848 protocol score 34.15 — intermediate
2. Triage Kafka consumer lag from per-partition offsets score 34.15 — intermediate
3. Kafka Consumer Lag Triage score 33.5 — advanced

Scores rank provenance, completeness and trust — read how verification works before adopting anything.

Reach for these with production experience: Kafka Consumer Lag Triage.

Security-flagged entries: Kafka Consumer Lag Triage (3 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

• Own the consumer side — offsets, rebalances, and the KIP-848 protocol — Consumer reliability is where streams quietly break: a rebalance loop looks like slowness, consumers past the partition count buy nothing, and stop-the-world rebalances pause consu… details
• Triage Kafka consumer lag from per-partition offsets — Combine the lag-triage skill's three questions with the lagging-consumer runbook: read per-partition lag to separate capacity from key skew, check the group state history for a reb… details
• Kafka Consumer Lag Triage — Triages consumer lag from the consumer-group offsets: distinguishing a slow consumer, a partitioned hot key, a rebalance storm, and a poison-pill retry loop. details

Real install commands from the registry — read the source before running any of them:

npx de-agent-platform add kafka-consumer-lag-triage

Kafka Consumer Lag Triage — review first

Adjacent topics: consumer-group (3 shared), tutorial (2 shared), lag (2 shared), incidents (2 shared).

Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.