Daniel Cherrett
Daniel Cherrett
### 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...
In Cosmos and Substrate Node monitoring, we are retrieving historical/archive blocks to be used for slashing alerting. Currently, if a block retrieval fails during this process, the process will stop...
API routes should be separated into different files. An example of this can be seen in the substrate API. This change will improve readability and maintainability.
We must investigate if the latest node exporter version works with PANIC. [This is the change log](https://github.com/prometheus/node_exporter/blob/master/CHANGELOG.md) of node exporter. It only has a few breaking changes from the `0.18.1`...
When tackling #136, it was noted that we are sharing rabbitMQ connections between threads. This is not correct and each thread should have its own connection.
Some packages used by the API are outdated and latest major versions should be used. The following should be done in this ticket: - Investigate which packages need to be...
Currently the ENV variables are not very user friendly since they need to be changed from the .env file without any validation. These can be exposed through the UI as...
Currently, alerts which show some sort of timestamp do not follow a standard. Some are outputted as timestamps while some use the python DateTime default string output. An ENV variable...
The info severity count outputted by the `redis/alertsOverview` endpoint is not valid since currently there is no logic to distinguish between node types. This means that for every node inputted...
Currently, the node configs for cosmos and substrate chains hold a field whether to monitor the node's system. On the other hand, chainlink chains have separate configs for nodes and...