Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Prometheus Metrics Exporter #628

Merged
merged 2 commits into from
May 11, 2020
Merged

Add Prometheus Metrics Exporter #628

merged 2 commits into from
May 11, 2020

Conversation

mwain
Copy link
Contributor

@mwain mwain commented Apr 28, 2020

I was wanting to export Burrow lag stats too Prometheus as we us it as our metrics and alerting platform. Im aware of a few exporters but didn't really want to run another service along side.

I noticed the PR (#537) and Issue (#318) this uses the general concept from the PR but uses the official Prometheus go client.

@mwain mwain requested a review from bai as a code owner April 28, 2020 21:05
@bai bai merged commit ece489e into linkedin:master May 11, 2020
@bai
Copy link
Collaborator

bai commented May 11, 2020

Thanks for contributing!


if consumerStatus == nil ||
consumerStatus.Status == protocol.StatusNotFound ||
consumerStatus.Complete < 1.0 {
Copy link

@vazdauta vazdauta Jul 21, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am wondering what is the reason for this particular rule( consumerStatus.Complete < 1.0 ).
We have some partitions that have the completion percentage 0.1. The cause of this seems to be related to the fact that we have some partitions that are empty and eventually - their offset expires(although I'm not sure - it might be something else on our side). The consequence is that the completion percentage for the consumer is less than 1 and it is not included in prometheus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants