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

(WIP)add slos field saas file #774

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

(WIP)add slos field saas file #774

wants to merge 1 commit into from

Conversation

mehfuz
Copy link
Contributor

@mehfuz mehfuz commented Feb 25, 2025

No description provided.

@gwenneg
Copy link

gwenneg commented Mar 6, 2025

Hey @mehfuz! I just saw this PR while I was looking for something else in the repo. I'm curious about something: how will the namespace/cluster where the SLO expression is evaluated be determined? For instance, if a team depends on Kafka in AWS (MSK), they might build an SLO on top of metrics that are only available in the appsre[s|p]11ue1 cluster which is different from the cluster their service is deployed to. Do slo-documents support multi-clusters/namespaces SLOs?

@gwenneg
Copy link

gwenneg commented Mar 6, 2025

One way to solve that could just consist in adding an optional cluster or namespace field (I'm not sure which word is most relevant) to https://github.com/app-sre/qontract-schemas/blob/main/schemas/app-sre/slo-document-1.yml to specify where the expression should be evaluated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants