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

Ensure errors are being communicated to alerting services correctly #3609

Open
tsachiherman opened this issue Dec 18, 2024 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@tsachiherman
Copy link
Contributor

** What ? **

Ensure that fatal/error/panic log from AvalancheGo and coreeth trigger our log based alerting.

** Why ? **

One of the index pods in data-dev account produced errors that were believed to be related to a corrupted backup process for leveldb.

While the cause for the issue is not known, detecting the issue earlier would have improve our reaction and handling time line.

** Goal **

Make the required changes in avalanchego, coreeth and other components, and make sure that fatal/error/panic log entries correctly trigger our log based alerting.

@tsachiherman tsachiherman added the bug Something isn't working label Dec 18, 2024
@tsachiherman tsachiherman self-assigned this Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant