search

confluentinc / ksql

The database purpose-built for stream processing applications.
https://ksqldb.io
Other
5.87k stars 1.04k forks source link

Keep track of lag for command topic consumer in KSQL Server #2353

Open hjafarpour opened 5 years ago

hjafarpour commented 5 years ago

One metric to keep track of for KSQL servers is the lag for the command topic consumer. This will help us detect if any of the servers lag behind in reading the commands. This can be a new JMX metric for each server.

blueedgenick commented 5 years ago

isn't this already available ? see mbeans under kafka.consumer/consumer-fetch-manager-metrics/consumer-1/

On Tue, Jan 15, 2019 at 10:57 AM Hojjat Jafarpour notifications@github.com wrote:

One metric to keep track of for KSQL servers is the lag for the command topic consumer. This will help us detect if any of the servers lag behind in reading the commands. This can be a new JMX metric for each server.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/confluentinc/ksql/issues/2353, or mute the thread https://github.com/notifications/unsubscribe-auth/AEV0oCK5qQXLIlR3vboS4lDDIeNdsQoIks5vDiStgaJpZM4aBmFs .