You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
Given the introduction of Request Tracing Framework (RTF) using OpenTelemetry (OTel), metrics (histogram/counter) can now be published and used to track failures.
This issue tracks the instrumentation for introducing following 2 counter metrics to identify node drops/health check failures for both the leader and follower nodes:
Leader Check Failures-> Health check failure for ClusterManager Node (leader) performed by follower nodes.
Follower Check Failures -> Health check failures for follower nodes performed by ClusterManager Node (leader).
Describe the solution you'd like
OTel Counter Metrics: Support for Counter type metrics, which was added as part of #10241, can be utilised to publish the metrics.
Related component
Cluster Manager
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
gargharsh3134
changed the title
[Feature Request] Counter Metrics to detect leader and follower checks.
[Feature Request] Counter Metrics to detect leader and follower check failures.
Mar 18, 2024
Is your feature request related to a problem? Please describe
Given the introduction of Request Tracing Framework (RTF) using OpenTelemetry (OTel), metrics (histogram/counter) can now be published and used to track failures.
This issue tracks the instrumentation for introducing following 2 counter metrics to identify node drops/health check failures for both the leader and follower nodes:
Describe the solution you'd like
OTel Counter Metrics: Support for Counter type metrics, which was added as part of #10241, can be utilised to publish the metrics.
Related component
Cluster Manager
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: