panic
panic copied to clipboard
SimplyStaking
PANIC Monitoring and Alerting For Blockchains
The following error log was spotted: ``` 04/05/2022 07:22:35 AM - ChainlinkContractStore.MongoApi - ERROR - Mongo error in : Resulting document after update is larger than 16777216, full error: {'index':...
### Technical stories If the `self.process_and_send_monitorable_data` function from the Monitor managers fails we cannot store the configurations. Therefore we might run into a scenario where a monitor has a process...
### User story As a user, I want to be able to figure out which configuration entries are associated with raised alerts. This would allow the user to adjust the...
### Story As a node operator, when I'm done with alerts setup, I want the ability to review my sub-chain configuration, so that any errors can be spotted before the...
As a node operator, I would like to see a page showing a summary of my sub-chain configuration, so I can review and approve it. Requirements - A page must...
### Story As a node operator, I want to be able to update threshold values and alerts across a number of sub-chains in batch, so threshold and alerts management is...
### User Story As a node operator, I want the ability to run PANIC's UI on a variety of browsers so that I don't need to move away from my...
In the UI, the following was noted: `The Chainlink chainlink-polygon-ocr node's missed observations have increased above CRITICAL threshold to -9 missed observations for price feed BCH / USD.` I can...
The factory class implementations for alerting where done after the `GitHubAlerter` was implemented, therefore they were not integrated. In this ticket we should do the following: - [ ] Implement...
The factory class implementations for alerting where done after the `DockerHubAlerter` was implemented, therefore they were not integrated. In this ticket we should do the following: - [ ] Implement...
Metadata
Owner
Metadata
PANIC Monitoring and Alerting For Blockchains