-
Notifications
You must be signed in to change notification settings - Fork 9.1k
HDDS-1811. Prometheus metrics are broken #1118
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
Conversation
/label ozone |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
@lokeshj1703 @mukul1987 please review |
💔 -1 overall
This message was automatically generated. |
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.
+1, LGTM
Thank you for your contribution. I have committed this patch to trunk and 0.4.1 branch. |
…ache#1118) This reverts commit ec536e1. PR 1116 included some issues, which will be fixed in PR 1117: 1) semantic change to return values of IncomingMessageEnvelope.getEventTime and IncomingMessageEnvelope.getArrivalTime (changed from millis to nanos) which are public API methods, and it will be hard to find existing usages to make sure they are updated properly, 2) usages of constructor of IncomingMessageEnvelope was not updated to handle nanos correctly in certain places (e.g. KafkaConsumerProxy)
What changes were proposed in this pull request?
Fix invalid metric type errors:
and
.
in record name by using simple class name-
with_
. Also properly convertALL_CAPS
names, eg.RATIS_THREE
toratis_three
instead of_rati_s-_thre_e
.https://issues.apache.org/jira/browse/HDDS-1811
How was this patch tested?
Updated unit test.
Checked metrics in
ozoneperf
pseudo-cluster.