Infra/Logs rule types > Add alertDetailsUrl parameter to redirect user to the Alerts page filtered for that alert instance

[maryam-saeidi]

📝 Summary

At the moment, we only have alertDetailsUrl action variable for APM Latency:

Since it will take time to have alert details page for all the rule types, one idea is to add this context variable to all observability rules and then redirect the user to the Alerts page filtered for that specific alert instance, something like the following screenshot using URL query parameter:

In this case, we need to:

• Use a unique identifier for each alert to filter based on that
• Make sure that the time range covers the time that the alert was firing (To avoid not showing any alert if it was recovered)

This can be used to improve the user experience related to this request: #156498

✅ Acceptance Criteria

• Add alertDetailsUrl context variable for all the observability infra rule types

🛠️ Related tickets/PRs

• [ResponseOps] [Alerting] Add warning to Edit Rule Flyout when publicUrl is not configured #149832
• Add context.alertDetailsUrl to connector template when configuring a Rule #142854

[elasticmachine]

Pinging @elastic/actionable-observability (Team: Actionable Observability)

[maryam-saeidi]

@katrin-freihofner What should be the description of alertDetailsUrl context variable? (Same for viewInAppUrl)
The current one does not match the other two, and I want to know if it is clear enough.

[maryam-saeidi]

Based on @XavierM feedback: we should use kibana.alert.url instead of context.alertDetailsUrl

[katrin-freihofner]

Okay, so the context.alertDetailsUrl field will be removed?

[maryam-saeidi]

Yes, that's the idea