We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The consume mode currently is not exposing any status of how successful its remote_write requests.
Ideally it should expose metrics about the outcome of the remote_write requests in a similar way as the "produce" mode does.
The pulsar client itself registers some metrics about consume the messages from the bus.
Their metrics definition is here:
prometheus-pulsar-remote-write/pkg/app/metrics.go
Line 8 in ed7be59
Ideally the metric vector includes the tenant ID if set, so we can figure which tenant fails to deliver remote_write requests
The text was updated successfully, but these errors were encountered:
Currently the consume mode itself is not merged yet #34, but should be fairly soon
/cc @56quarters
Sorry, something went wrong.
Add metrics (writes and error counts, timing) for consumer mode
6a9bf83
Fixes #36
Add metrics (writes and error counts, timing) for consumer mode (#37)
aaf694b
Add metrics (writes and error counts, timing) for consumer mode Fixes #36
56quarters
Successfully merging a pull request may close this issue.
The consume mode currently is not exposing any status of how successful its remote_write requests.
Ideally it should expose metrics about the outcome of the remote_write requests in a similar way as the "produce" mode does.
The pulsar client itself registers some metrics about consume the messages from the bus.
Their metrics definition is here:
prometheus-pulsar-remote-write/pkg/app/metrics.go
Line 8 in ed7be59
Ideally the metric vector includes the tenant ID if set, so we can figure which tenant fails to deliver remote_write requests
The text was updated successfully, but these errors were encountered: