-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
expose managedLedgerCache, managedLedger, loadBalance metrics to prometheus #6705
Conversation
@@ -20,10 +20,14 @@ | |||
|
|||
import java.io.IOException; | |||
import java.io.OutputStream; | |||
import java.util.Enumeration; | |||
import java.util.*; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hangc0276 can we avoid wildcard import?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok,i will update in next commit with metric document.
@hangc0276 You'd better rebase the branch with master since there are some fixes related to integration tests. |
5f58876
to
68381c9
Compare
I have updated the document and rebase the master branch, but it still run test case failed. Please help take a look @codelipenghui @sijie |
/pulsarbot run-failure-checks |
1 similar comment
/pulsarbot run-failure-checks |
@hangc0276 Could you please rebase the branch? |
68381c9
to
81c2a79
Compare
I have rebase the master branch. |
/pulsarbot run-failure-checks |
1 similar comment
/pulsarbot run-failure-checks |
…etheus (apache#6705) ## Motivation The managed ledger read cache monitor metric is export via /admin/broker-stats/metrics with json format, it is hard to parse, collect and display, what's more the read cache is a very import module for message consuming throughput and latency. So collect and display the read cache metrics is extremely urgent for pulsar in production. ## Changes I parse the json format metric to prometheus message type and export to prometheus monitor port, so those metrics can be displayed in grafana. Please help check those changes, if it's ok, i will update the metric document.
…etheus (apache#6705) ## Motivation The managed ledger read cache monitor metric is export via /admin/broker-stats/metrics with json format, it is hard to parse, collect and display, what's more the read cache is a very import module for message consuming throughput and latency. So collect and display the read cache metrics is extremely urgent for pulsar in production. ## Changes I parse the json format metric to prometheus message type and export to prometheus monitor port, so those metrics can be displayed in grafana. Please help check those changes, if it's ok, i will update the metric document.
…etheus (apache#6705) ## Motivation The managed ledger read cache monitor metric is export via /admin/broker-stats/metrics with json format, it is hard to parse, collect and display, what's more the read cache is a very import module for message consuming throughput and latency. So collect and display the read cache metrics is extremely urgent for pulsar in production. ## Changes I parse the json format metric to prometheus message type and export to prometheus monitor port, so those metrics can be displayed in grafana. Please help check those changes, if it's ok, i will update the metric document.
…etheus (apache#6705) ## Motivation The managed ledger read cache monitor metric is export via /admin/broker-stats/metrics with json format, it is hard to parse, collect and display, what's more the read cache is a very import module for message consuming throughput and latency. So collect and display the read cache metrics is extremely urgent for pulsar in production. ## Changes I parse the json format metric to prometheus message type and export to prometheus monitor port, so those metrics can be displayed in grafana. Please help check those changes, if it's ok, i will update the metric document.
… to prometheus (apache#6705)" This reverts commit a9ed984.
Motivation
The managed ledger read cache monitor metric is export via /admin/broker-stats/metrics with json format, it is hard to parse, collect and display, what's more the read cache is a very import module for message consuming throughput and latency. So collect and display the read cache metrics is extremely urgent for pulsar in production.
Changes
I parse the json format metric to prometheus message type and export to prometheus monitor port, so those metrics can be displayed in grafana.
Please help check those changes, if it's ok, i will update the metric document.