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

Updated cluster_release_version to support CAPI clusters #1402

Merged
merged 1 commit into from
Oct 25, 2024

Conversation

AverageMarcus
Copy link
Member

Before adding a new alerting rule into this repository you should consider creating an SLO rules instead.
SLO helps you both increase the quality of your monitoring and reduce the alert noise.


Towards: giantswarm/roadmap#3650

This PR updates the expression used by aggregation:giantswarm:cluster_release_version to support CAPI clusters by getting the release version from capi_cluster_info.

Checklist

…o support CAPI clusters

Signed-off-by: Marcus Noble <[email protected]>
@AverageMarcus AverageMarcus requested a review from a team October 25, 2024 10:20
@AverageMarcus AverageMarcus requested a review from a team as a code owner October 25, 2024 10:20
Copy link
Member

@njuettner njuettner left a comment

Choose a reason for hiding this comment

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

lgtm, but waiting for @giantswarm/team-atlas final call 🙂

@@ -121,7 +121,10 @@ spec:
{{- end }}
)
record: aggregation:giantswarm:cluster_info
- expr: sum(cluster_service_cluster_info) by (release_version, cluster_id, cluster_type, customer, installation, pipeline, provider, region) / 2 or sum(cluster_operator_cluster_status{release_version!=""}) by (release_version, cluster_id, cluster_type, customer, installation, pipeline, provider, region)
- expr: |-
Copy link
Contributor

Choose a reason for hiding this comment

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

LGTM if it was tested :)

Copy link
Member Author

Choose a reason for hiding this comment

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

I've tested the expression query itself manually on both vintage and capi instances. Is there a better way to test it as an aggregation itself? I'm a bit out of my comfort zone here 😅

Copy link
Contributor

Choose a reason for hiding this comment

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

Easy solution is to deploy the rule on a test mc and check out the metrics on grafana cloud I think :) you should sée thé clusters showing up on the cluster dashboard on grafana cloud

Copy link
Member Author

Choose a reason for hiding this comment

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

Confirmed! :D

Copy link
Contributor

Choose a reason for hiding this comment

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

Great work

@AverageMarcus AverageMarcus merged commit 014e7cc into main Oct 25, 2024
7 checks passed
@AverageMarcus AverageMarcus deleted the capi-cluster_release_version branch October 25, 2024 13:08
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.

3 participants