Set both kibana.alert.url and context.alertDetailsUrl for observability alerts #158391
Labels
Feature:Alerting
Team: Actionable Observability - DEPRECATED
For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge"
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
v8.9.0
Milestone
📝 Summary
In
v8.8
, AO introduced the alert details page for APM Latency threshold and also addedcontext.alertDetailsUrl
to the action variables of that rule type here. (We are not using this variable in the default action message yet)Now we want to add the same parameters to the other observability rule types (#156534), but since we already have
kibana.alert.url
, the question is whether to move forward with addingcontext.alertDetailsUrl
to all the observability rule types or usekibana.alert.url
instead.After discussion with @XavierM , it seems providing
kibana.alert.url
as an action variable is complicated, and we might not be able to deliver it inv8.9
. On the other hand, we want to ensure that observability users can navigate to a page filtered for that alert sooner.@XavierM suggested that we continue using
context.alertDetailsUrl
until the work related to providing all alert fields in the action context is done and then think about a migration plan to update the existing action messages and replacecontext.alertDetailsUrl
withkibana.alert.url
. Also, we might need to consider to change thecontext
mapping to a flattened field so our user does need to know what we define here and it will be more an internal sauce for our application.The text was updated successfully, but these errors were encountered: