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

Connection lost alert #57

Open
andreabadesso opened this issue Jul 6, 2022 · 0 comments
Open

Connection lost alert #57

andreabadesso opened this issue Jul 6, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@andreabadesso
Copy link
Collaborator

Currently, we don't alert when the websocket connection to the fullnode has been lost, we usually only find out the connection has been lost when we get a CPU spike alert or when the daemon gets a 504 from the fullnode

It is normal that the connection gets broken from time to time, so we shouldn't alert as soon as the connection gets lost, but we should alert after some time thresholds, similar to what we have on the network-monitor

We should also create a major alert when the connection is lost for more than X seconds, as it would indicate that the daemon is not syncing transactions

@andreabadesso andreabadesso added the enhancement New feature or request label Jul 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant