[Investigate] [Incidents] Render Relevant Visualizations from Dashboards attached to the rule or alert on the Incident Details page

[dominiqueclarke]

Prerequisites

• [Investigate] Discover relevant lens visualizations within dashboards attached to a rule #209123
• [Investigate] [Incidents] Incident Details Page #209390

Overview

When SREs are responding to alerts, we want to surface the most helpful, relevant information as quickly as possible to reduce the time to resolution.

Often, our customers have already brought useful information together as part of a dashboard.

To aid in the investigation of the root cause of an alert, we will embed relevant lens visualizations from dashboards attached to the rule/alerts directly into the incident details page.

Scope

These relevant visualizations will only be applied to the custom threshold rule. This is to provide focused learning from one rule before moving onto enabling this for all rules.

Technical detail

1. The visualizations to render will be provided by the APIs defined in [Investigate] Discover relevant lens visualizations within dashboards attached to a rule #209123
2. These visualizations can then be rendered via the ReactEmbeddableRenderer component. An overview of the technical details of this is captured in a video between our team and dashboards. Reach out if you'd like the link.

Feature detail

1. Only the top 3 visualizations should be shown. The scope of this ticket does not include determining a heuristic for what is most valuable. Simply return the first 3 visualizations found at this time
2. It should be clear that the visualization originates from a dashboard, and which one. We should also include links back to the dashboard close to those visualizations
3. The visualizations should be scoped to the time range of the incident details page

Feature Flag consideration

It's difficult to know how helpful these additional visualizations will be, and we'll be modifying our heuristic for our we pick out these visualizations over time. For that reason, I would prefer to initially hide this behind a feature flag until we feel more confident in the feature.

Open questions

1. How do we determine which rules are most important within the incident to hierarchically display the relevant visualizations? Perhaps we also take into account if a visualization is relevant for multiple rules within an incident and show that.

[elasticmachine]

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)