Associate alerts with configuration entries

[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 alerts configurations accordingly since currently, some alerts might be a bit ambiguous.

Description

Currently, we have the following in the alerts-overview section within the UI:

To cater for the user story above, we would add a column with the alert metric code for each alert. As an example, a system is down alert would be associated with the system_is_down alert metric code. This can also be added for the dashboard-overview section, but this should be discussed beforehand.

From the backend perspective, we might need to update the alert store to also store the alert metric code. This would result in exposing this value from the mongo/alerts API endpoint. Currently, we return a list of alerts such as:

[{
    severity: 'WARNING',
    message: 'test alert 1',
    timestamp: 1609459200,
    origin: 'test_system_id'
}]

So this must be changed to also return an alert_metric_code field or something along these lines.

For ticket closure (acceptance criteria)

This is a set of rules which the update/feature must satisfy for the ticket to be closed.

Scenario: The alerter, API and the UI are started Given: The alerter, API and the UI started When: An alert is raised and checking the UI Then: You can see the alert metric code for the given alert

The above should be carried out for various alerts on different basechains so we make sure that there are no bugs.