You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Jonathan Poholarz (Jira)" <ji...@apache.org> on 2021/03/22 20:09:00 UTC
[jira] [Created] (STORM-3759) Additional Trident Kafka Spout
Metrics
Jonathan Poholarz created STORM-3759:
----------------------------------------
Summary: Additional Trident Kafka Spout Metrics
Key: STORM-3759
URL: https://issues.apache.org/jira/browse/STORM-3759
Project: Apache Storm
Issue Type: New Feature
Components: storm-kafka-client
Reporter: Jonathan Poholarz
The Trident Kafka Spout/Emitter does not seem to measure a couple metrics that my team has found useful over the years using the spout.
*Event emit rate*
Having a count of how many events are being emitted by the spout can track the rate at which the spout is consuming from the kafka topic(s). If this rate decreases, it signals performance issues to investigate. This metric has helped my team track the overall health of our Kafka spouts.
*Kafka Spout Max Lag*
This gauge value monitors the backlog of events. It helps determine if:
* a. the spout is not emitting fast enough to keep up with the incoming data, or
* b. the spout is current and Kafka topic delayed.
This metric can be used to distinguish between these two cases and determine the source of the slowdown. It has helped my team better understand delays.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)