Notifications history

[cjcenizal]

Related to #8194

Overview

At one point, @uboness explored the idea of an app that was a log of notifications, which allows the user to review past notifications. This app should have the following functionality:

• You can filter by severity (info, success, error)
• You can filter by originator (Visualize, Reporting, Alerting, Monitoring, etc.)
• You can filter by date
• Each notification can surface deep-links to the relevant parts of Kibana, or quick contextual actions
• You can clear all notifications
• You can export all notifications (or copy to clipboard)

Examples of notifications

Unhandled ES query errors

If the UI can't gracefully handle an error and contextually surface it to the user in a helpful way, we should consider it a bug. We need to store these errors so we can help users (and ourselves) diagnose and fix these bugs.

Handled ES query errors

We may also want to consider storing all errors, even if they're handled. By keeping a log of user actions, we can make it easier to report and reproduce bugs.

Job status changes

For example, notifications of when a new Report is being generated or has been completed.

[marius-dr]

It would also be nice to have the ability for a weekly report to be sent to an admin user with all the notifications from each node.

[elasticmachine]

Pinging @elastic/es-ui (Team:Elasticsearch UI)

[cjcenizal]

This issue is too broad to be actionable.