Description
This article provides insights into possible reasons why Consumer Lag details may not appear in the Confluent Cloud UI.
Applies To
Confluent Cloud
Consumer Lag
Cause
As part of our effort to improve the security posture and observability of the Confluent Cloud UI, the Consumer Lag UI is being adapted to use the Confluent Cloud Metrics API.
Resolution
The following UI elements may not be available anymore when using the Consumer Lag page within the Confluent Cloud Console (UI):
- Consumer offsets - as the Metrics API contains only the consumer lag
- Lag information for inactive consumer groups (consumer groups with no members)
- Lag information for consumers that use the
assign()method
Reference: Monitor Consumer Lag via the Metrics API
Additional considerations are required due to some differences in the data between the Metrics API and the previous UI backend. See: Permissions required for Consumer Lag details on Confluent Cloud UI
NOTE: Consumer Lag UI details may take up to 5 minutes to update due to Metric Data Latency.
To see more consumer group details, including offsets information, use the Kafka Admin API.
Reference: Monitor Offset Lag via Kafka Admin API