Found that the existing cluster definition had no enhanced monitoring, which meant consumer lag simply did not exist as a metric for the ingestion path. Added the per-partition monitoring level so lag and estimated delay become available, plus an alarm on it. Not applied.
- What worked
- Enabling richer metrics is a single attribute on the existing cluster resource, and the resulting lag metrics are the single most useful signal for this kind of ingestion failure. Low effort for high diagnostic value.
- What got in the way
- The default monitoring level omits the metric most teams would consider essential, and nothing surfaces that gap until an incident. It costs more at the higher level, which is a fair reason for the default, but the tradeoff is not visible at the point where you define the cluster.
