-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
ReliableTopic totalPublishes metric is always 0 #19555
Labels
Module: Metrics
Module: Ringbuffer
Source: Internal
PR or issue was opened by an employee
Team: Client
Team: Core
Type: Defect
Milestone
Comments
This was referenced Sep 28, 2021
promanenko
added a commit
that referenced
this issue
Sep 28, 2021
Previously ReliableTopic stats (published/received messages) were reported only when ReliableTopicProxy was used. No stats were reported If ClientReliableTopicProxy was used. Since ReliableTopic is always backed by a RingBuffer, we can report ReliableTopic stats from the RB operations if the RB name has a prefix "_hz_rb_" Fixes #19555
promanenko
added a commit
to promanenko/hazelcast
that referenced
this issue
Sep 28, 2021
Previously ReliableTopic stats (published/received messages) were reported only when ReliableTopicProxy was used. No stats were reported If ClientReliableTopicProxy was used. Since ReliableTopic is always backed by a RingBuffer, we can report ReliableTopic stats from the RB operations if the RB name has a prefix "_hz_rb_" Fixes hazelcast#19555
promanenko
added a commit
to promanenko/hazelcast
that referenced
this issue
Sep 28, 2021
Previously ReliableTopic stats (published/received messages) were reported only when ReliableTopicProxy was used. No stats were reported If ClientReliableTopicProxy was used. Since ReliableTopic is always backed by a RingBuffer, we can report ReliableTopic stats from the RB operations if the RB name has a prefix "_hz_rb_" Fixes hazelcast#19555
promanenko
added a commit
that referenced
this issue
Sep 29, 2021
Previously ReliableTopic stats (published/received messages) were reported only when ReliableTopicProxy was used. No stats were reported If ClientReliableTopicProxy was used. Since ReliableTopic is always backed by a RingBuffer, we can report ReliableTopic stats from the RB operations if the RB name has a prefix "_hz_rb_" Fixes #19555
promanenko
added a commit
that referenced
this issue
Sep 29, 2021
Previously ReliableTopic stats (published/received messages) were reported only when ReliableTopicProxy was used. No stats were reported If ClientReliableTopicProxy was used. Since ReliableTopic is always backed by a RingBuffer, we can report ReliableTopic stats from the RB operations if the RB name has a prefix "_hz_rb_" Fixes #19555
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Module: Metrics
Module: Ringbuffer
Source: Internal
PR or issue was opened by an employee
Team: Client
Team: Core
Type: Defect
This was reported by a community user at: https://groups.google.com/g/hazelcast/c/AaNdgDamGtc
Describe the bug
The
reliableTopic.totalPublishes
metric is always 0.Expected behavior
The
reliableTopic.totalPublishes
should be incremented on each publish, just liketopic.totalPublishes
To Reproduce
Steps to reproduce the behavior:
docker run -p 5701:5701 hazelcast/hazelcast:4.2.2
java -Dhazelcast.mc.prometheusExporter.enabled=true -Dhazelcast.mc.license='<any-valid-license>' -jar target/hazelcast-management-center-5.0-SNAPSHOT.jar
curl http://localhost:8080/metrics
Expected output: the
hz_reliableTopic_totalPublishes{mc_cluster="dev",mc_member="172.17.0.2:5701",name="myRB",unit="COUNT",}
metric has a value higher than 0Actual output:
hz_reliableTopic_totalPublishes{mc_cluster="dev",mc_member="172.17.0.2:5701",name="myRB",unit="COUNT",}
is0.0
in the metric dumpAdditional context
It is reproducible with
The text was updated successfully, but these errors were encountered: