Bug: facing challenges with recently changed prometheus metrics naming convention

[tayalrishabh96]

📜 Description

Not receiving any alerts due to recent change in prometheus metrics naming convention.
earlier : nats_event_consumption_time_count
now : Nats_Event_Consumption_Time_count
Due to this change we are not receiving any alerts and also this is changed only for all streams except image-scanner due to which we will need to create segregated alerts for image-scanner NATS metrics.

Affected areas

Other CRITICAL functionality

Additional affected areas

Other CRITICAL functionality

Prod/Non-prod environments?

Prod

Is User unblocked?

No

How was the user un-blocked?

None

Impact on Enterprise

Unable to track anomalies in NATS like nats event consumption time etc.

👟 Steps to replicate the Issue

if you plot a graph in grafana over nats_event_consumption_time_count then you will see the data stopped coming after a certain time duration.

👍 Expected behavior

metrics naming convention should be same across all exposed metrics.

👎 Actual Behavior

Currently all metrics naming convention is lower case except for NATs which is camel case.

☸ Kubernetes version

EKS 1.30

Cloud provider

AWS

🌍 Browser

Chrome

✅ Proposed Solution

NA

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[github-actions]

Final Score: 240