[Actionable Observability] Add context.alertDetailsUrl variable to action connector template for APM rule types#144791
Conversation
|
Pinging @elastic/apm-ui (Team:APM) |
c1aeca3 to
73e2053
Compare
73e2053 to
f11a5ad
Compare
…-context-alertdetailsurl-to-apm-latency-threshold-rule
f11a5ad to
93a0ee8
Compare
…saction Rate Threshold rule
…-context-alertdetailsurl-to-apm-latency-threshold-rule
x-pack/plugins/rule_registry/server/utils/create_lifecycle_executor.ts
Outdated
Show resolved
Hide resolved
…-context-alertdetailsurl-to-apm-latency-threshold-rule
…threshold-rule' of github.com:CoenWarmer/kibana into feat/144439-add-context-alertdetailsurl-to-apm-latency-threshold-rule
sorenlouv
left a comment
There was a problem hiding this comment.
Overall lgtm but re-orderings make it quite a bit harder to review
…threshold-rule' of github.com:CoenWarmer/kibana into feat/144439-add-context-alertdetailsurl-to-apm-latency-threshold-rule
…-context-alertdetailsurl-to-apm-latency-threshold-rule
Thanks for the feedback. Main objective was to lower the noise and improve legibility in the files. As a consequence the noise in the PR goes up a bit. Apologies for that. Will refrain from doing it in the future. |
…set by lifecycle executor
…-context-alertdetailsurl-to-apm-latency-threshold-rule
0995e90 to
a1cfd27
Compare
No worries. I think the re-orderings look good. I'd just prefer them done in a separate PR. |
|
Pinging @elastic/uptime (Team:uptime) |
…-context-alertdetailsurl-to-apm-latency-threshold-rule
…threshold-rule' of github.com:CoenWarmer/kibana into feat/144439-add-context-alertdetailsurl-to-apm-latency-threshold-rule
…ed in a specific way
…-context-alertdetailsurl-to-apm-latency-threshold-rule
💚 Build Succeeded
Metrics [docs]Unknown metric groupsESLint disabled in files
ESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
pmuellr
left a comment
There was a problem hiding this comment.
Alerting-related changes in rule_registry LGTM.
I guess the typing change of AlertTypeWithExecutor got the services in the executor to be typed the way you wanted.
* main: (65 commits) Migrate server-side `Root` and `Server` to packages (elastic#144990) [Discover] Handle no data views state for `esQuery` alert (elastic#145052) [ML] Allow updates for number of allocations and priority for trained model deployments (elastic#144704) [api-docs] 2022-11-15 Daily api_docs build (elastic#145203) [Security solution] remove guided onboarding feature flag (elastic#144247) [DOCS] Automate final case APIs (elastic#145007) [Enterprise Search] Name and description flyout for connectors (elastic#143827) [Guided onboarding] Update header button logic (elastic#144634) [Lens] Multi metric partition charts (elastic#143966) [Dashboard] [Controls] Add unmapped runtime field support to options list (elastic#144947) [Security Solution] Add Task Metric Collection to New Tasks (elastic#145181) [TriggersActionsUi] disable jest config in CI (elastic#145186) [TableListView] Enhance tag filtering (elastic#142108) [Cloud Posture] Compliance by CIS section table (elastic#145114) [8.6][Session View] Fix hidden alert flyout in session view (elastic#145141) [customIntegrations] async load all components (elastic#145166) Fix time for logs smoke tests in integration test (elastic#145130) [RAM] Update rule status (elastic#140882) Update babel (main) (elastic#145060) [Actionable Observability] Add context.alertDetailsUrl variable to action connector template for APM rule types (elastic#144791) ...

Closes #144439, closes #144438, closes #144436, closes #144434.
Summary
This PR adds the
context.alertDetailsUrlaction template variable for the following APM rule types:What it looks like
Configure a rule, with

{{context.alertDetailsUrl}}variable:Leads to output: (chosen server output in screenshot):

Checklist
xpack.observability.unsafe.alertDetails.apm.enabledis set tofalsecontext.viewInAppUrlvariable Space-aware.