We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is a follow up on #498 , currently api-server /metrics implementation doesn't allow to properly monitor targets up/down.
api-server
/metrics
api-server: address: :7890 enable-metrics: true
Once the target becomes gnmi unreachable, the current metric gnmic_subscribe_number_of_received_subscribe_response_messages_total disappears.
gnmic_subscribe_number_of_received_subscribe_response_messages_total
There should be a deterministic way in /metrics to tell whether a target up or down.
The text was updated successfully, but these errors were encountered:
Should be added in v0.39.0, please give it a try.
Sorry, something went wrong.
I'm not the initial requester but we've been waiting for it as well :) Tested and works well for us. Thank you for implementing it ! Quick dashboard.
oh, wow, Wikimedia uses gnmic then, @XioNoX ?
Yep, we're only at the beginning, but it has been working very well for us so far. Thanks for the tool! You can find more doc on https://wikitech.wikimedia.org/wiki/Network_telemetry
Nice, thank you!
No branches or pull requests
This is a follow up on #498 , currently
api-server
/metrics
implementation doesn't allow to properly monitor targets up/down.Once the target becomes gnmi unreachable, the current metric
gnmic_subscribe_number_of_received_subscribe_response_messages_total
disappears.There should be a deterministic way in
/metrics
to tell whether a target up or down.The text was updated successfully, but these errors were encountered: