Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.13](backport #3693) [Alerting] Add list of action variables to Observability alerting docs #3702

Merged
merged 1 commit into from
Mar 22, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 22, 2024

This PR adds a list of valid action variables to the following alerting rules for stateful:

  • Custom threshold
  • Log threshold
  • Inventory threshold
  • Metric threshold
  • SLO burn rate

Adds changes to the stateful docs for issue #3658. These updates will need to be ported to the serverless docs, too.

In a follow-on PR, we should add examples to the variable descriptions, but that's out-of-scope for this PR. Tracked here: #3622

Notes

The following rules were not updated because they appear in the Uptime app, which is not visible in Kibana by default. Should we update these rules to include action variable lists or are the rules going away?

  • Monitor status
  • TLS certificate
  • Uptime duration anomaly

The following rules were not updated for this PR because they appear in other guides (not the Observability Guide). They will need to be updated in follow-on PRs. There is an unverified spreadsheet here that shows which variables are valid for each rule type:

For reference, here is the full list of rules that users see when they click Create rule in the Alerts UI.

image


This is an automatic backport of pull request #3693 done by [Mergify](https://mergify.com).

@mergify mergify bot requested a review from a team as a code owner March 22, 2024 18:00
@mergify mergify bot added the backport label Mar 22, 2024
Copy link
Contributor

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@bmorelli25 bmorelli25 merged commit 92d331b into 8.13 Mar 22, 2024
7 checks passed
@bmorelli25 bmorelli25 deleted the mergify/bp/8.13/pr-3693 branch March 22, 2024 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants