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.x](backport #4418) Document no data settings for custom threshold rule #4430

Merged
merged 1 commit into from
Oct 24, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 24, 2024

Description

Adds documentation that explain new setting "no data" setting for the custom threshold rule.

Link to preview: https://observability-docs_bk_4418.docs-preview.app.elstc.co/guide/en/observability/master/custom-threshold-alert.html#trigger-alert-when-no-data

Documentation sets edited in this PR

Check all that apply.

  • Stateful (docs/en/observability/*)
  • Serverless (docs/en/serverless/*)
  • Integrations Developer Guide (docs/en/integrations/*)
  • None of the above

Related issue

Closes #4068

Checklist

  • Product/Engineering Review
  • Writer Review

Follow-up tasks

Select one.

  • This PR does not need to be ported to another doc set because:
    • The concepts in this PR only apply to one doc set (serverless or stateful)
    • The PR contains edits to both doc sets (serverless and stateful)
  • This PR needs to be ported to another doc set:
    • Port to stateful docs: <link to PR or tracking issue>
    • Port to serverless docs: ADD ISSUE LINK BEFORE MERGING

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

@mergify mergify bot requested a review from a team as a code owner October 24, 2024 18:10
@mergify mergify bot added the backport label Oct 24, 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.

@dedemorton dedemorton merged commit 3bd5914 into 8.x Oct 24, 2024
8 checks passed
@dedemorton dedemorton deleted the mergify/bp/8.x/pr-4418 branch October 24, 2024 22:04
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.

1 participant