Skip to content
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

Metrics (signer_sentry_connect_tries/signer_total_sentry_connect_tries) #193

Open
activenodes opened this issue Aug 24, 2023 · 1 comment

Comments

@activenodes
Copy link

  "version": "3.1.0",
  "commit": "03f565d67bb5394a4b3017a1adb00561d5297724",

I simulated a sentry down for a few minutes (first one and then two), and then restored, but after hours the result is still this:

# curl -sS localhost:6011/metrics | grep sentry

# HELP signer_sentry_connect_tries Consecutive Number of times sentry TCP connect has been tried (High count may indicate validator restarts)
# TYPE signer_sentry_connect_tries gauge
signer_sentry_connect_tries 124
# HELP signer_total_sentry_connect_tries Total Number of times sentry TCP connect has been tried (High count may indicate validator restarts)
# TYPE signer_total_sentry_connect_tries counter
signer_total_sentry_connect_tries 124

What is the difference between signer_sentry_connect_tries and signer_total_sentry_connect_tries?
Is it a bug?

Thanks

@activenodes
Copy link
Author

Update. I’ve noticed that maybe the value signer_sentry_connect_tries is reset only if the signer is "used" by sentry and not just after restored connection.
Could be this the reason and in case fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant