panic
panic copied to clipboard
PANIC Monitoring and Alerting For Blockchains
After chain update to cosmos sdk 46.x panic stops working with error "Could not retrieve cosmos-rest data for local ignite: Cosmos Network Monitor (local ignite) could not access any synced...
I'm still using the panic v1.2.1 because i'm not confident to upgrade to a newer version yet and first of all i'd like to have a backup of my db....
### Rationale The unit tests are taking too long to run. It is because of the latest change related to replica sets. Ideally, for testing we still use the old...
### User Story As it is, there are limitations as to how many github repos you can add for monitoring, because the GitHub API accepts only 60 requests per hour....
### Description The delay on every update in the alerts page is too quick, causing many API calls. Update: It has been decided to overhaul this page by implementing a...
### User Story When having data in field, then disabling the field, then removing it, It is not updating in DB side. The problem is that the 'field_name' key is...
### Summary of bug Timo reported that we have the following issues on PANIC Prod: - Arbitrum, Avalanche (evm node monitors), Tgrade and E-money (cosmos node monitors), zeitgeist (substrate system...
### Technical Story As any installer component, I want to prepare a request body that eventually gets sent to the API. ### Description Currently, the functions that prepare the request...
### Rationale When running API tests on the UI Iteration 2 branch, we are getting the following warning:  In this ticket, we should investigate and fix these leaks. Please...
### Summary of bug The Cosmos REST API returned a proposal with invalid `voting_start_time` and `voting_end_time` fields while the proposal was in voting stage. For this reason, the Cosmos Network...