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

[SLO] Add support for group by to SLO burn rate rule #163434

Conversation

simianhacker
Copy link
Member

@simianhacker simianhacker commented Aug 8, 2023

Summary

This PR fixes #163120 by adding support for group by's to the SLO Burn Rate rule. I refactored the rule to push all the executions down to Elasticsearch, it uses the same technique as the Metric Threshold rule. I also added a callout to the rule form to let the user know when they've selected an SLO with a group by so it's clear what the behavior will be.

image image

@apmmachine
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
  • /oblt-deploy-serverless : Deploy a serverless Kibana instance using the Observability test environments.
  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@simianhacker simianhacker marked this pull request as ready for review August 8, 2023 23:13
@simianhacker simianhacker requested review from a team as code owners August 8, 2023 23:13
@kdelemme
Copy link
Contributor

kdelemme commented Aug 9, 2023

I have created an SLO with a groupBy and a rule on it which seems to trigger, but in the SLO details page, under the Alerts tab, I see nothing (notice the [1] notifcation badge))

Screenshot
image
image

@simianhacker simianhacker added release_note:enhancement Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge" v8.11.0 labels Aug 9, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/actionable-observability (Team: Actionable Observability)

Copy link
Contributor

@kdelemme kdelemme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Impressive work with The Query™️.
I just have a question about the kibana.alert.rule.parameters prefix that you removed.
Otherwise tested locally, and it works as expected:

screencapture-localhost-5601-kibana-app-observability-slos-2023-08-09-15_56_57

Copy link
Contributor

@kdelemme kdelemme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the refactoring, LGTM!

import { useKibana } from '../../utils/kibana_react';
import { sloKeys } from './query_key_factory';

type SLO = Pick<SLOResponse, 'id' | 'instanceId'>;

export class ActiveAlerts {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏻 Nice abstraction

Copy link
Contributor

@ymao1 ymao1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

response ops changes lgtm

@simianhacker simianhacker enabled auto-merge (squash) August 10, 2023 14:58
@simianhacker simianhacker merged commit 96e9c37 into elastic:main Aug 10, 2023
24 checks passed
@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
observability 420 421 +1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
observability 1.0MB 1.0MB +321.0B
Unknown metric groups

References to deprecated APIs

id before after diff
observability 43 45 +2

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@kibanamachine kibanamachine added the backport:skip This commit does not require backporting label Aug 10, 2023
@simianhacker simianhacker deleted the issue-163120-add-support-for-group-by-to-burn-rate-rule branch April 17, 2024 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting release_note:enhancement Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge" v8.10.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[SLO][Group By] Add support for group by feature to Burn Rate Rule
7 participants