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

[REQUEST]: New Observability threshold rule #3031

Closed
lcawl opened this issue Jun 22, 2023 · 2 comments · Fixed by #3314
Closed

[REQUEST]: New Observability threshold rule #3031

lcawl opened this issue Jun 22, 2023 · 2 comments · Fixed by #3314
Assignees
Labels
Request:8.11 Team:Docs Label for the Observability docs team

Comments

@lcawl
Copy link
Contributor

lcawl commented Jun 22, 2023

Description

Per https://github.com/elastic/actionable-observability/issues/36 there's a new rule that will combine three previous (logs threshold, infrastructure threshold, and metrics threshold) Observability rules, though I think all four will continue to exist in parallel for a little while.

Per @katrin-freihofner she has discussed with @mdbirnstiehl and they have added a link from the new rule to the docs (currently just a stub file), but will ultimately be similar to the existing rule-specific pages in this section: https://www.elastic.co/guide/en/observability/master/create-alerts.html

Resources

Collaboration

TBD. The docs and product team will work together to determine the best path forward.

Point of contact.

Main contact:

Stakeholders:
@katrin-freihofner

@lcawl lcawl added Team:Docs Label for the Observability docs team Request:8.9 labels Jun 22, 2023
@katrin-freihofner
Copy link

This rule is behind a feature flag - we can postpone the documentation for it to 8.10

@mdbirnstiehl
Copy link
Contributor

Due to a privilege issue, this has been pushed to 8.11.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Request:8.11 Team:Docs Label for the Observability docs team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants