Monitoring-Related
Last updated: 2025-09-28 16:19:49
Why No Monitoring Data for Topic
The client may not have production consumption
Check whether the client has production and consumption behavior. You can test with native production and consumption commands, then view monitoring data. For specific operations, refer to running the Kafka client.
The monitoring collection system has a failure
Why Does Message Queue Depth Persist in Specific Partitions during Monitoring?
The consumer does not consume messages from this partition, while message production continues, leading to persistent aggregated data.
If you encounter a situation where specific partitions are not being consumed, you can attempt to resolve the issue by restarting the client. If restarting resolves the problem, first troubleshoot the client log. You can also submit a ticket to request assistance.
Insufficient consumer count in the consumer group or consumption speed too slow causes data accumulation.
You can try increasing the number of consumers to improve consumption speed.
The consumer program may contain bugs, which may lead to not consuming specific partitions.
At this point, check the local log at the consumer end to see if there is any exception info.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback