-
Notifications
You must be signed in to change notification settings - Fork 39
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
PromQL expression QOL #31
Comments
Hey @kedoodle, thanks for opening this issue. I understand the benefit of switching to the |
Hey @brennerm, appreciate the response! I'm thinking of a scenario for "generic" expressions where we want to alert on any and all AWS limits reaching a certain threshold (as opposed to a singular resource). TL;DR: it saves a Existing metrics:
Existing expression (same as original issue comment):
Existing metric names with additional
New expression with existing metric names with additional
It could also be nice for specific alerts where you want to use the resource as part of the alert details e.g. the alert could have a description (using metric labels) that we have reached 70% of the limit on
|
@kedoodle I agree with your point of view. I added a new label called I'll probably also switch to the proposed |
That's great to hear. The change has been released with version 1.10.0. I'll leave the ticket open until I switch to the breaking change scheme. |
Thanks @brennerm! I'm in the process of deploying Container logs, after which the pod is
EDIT:
This particular AWS account has ~35k EBS snapshots. I suspect pagination may be needed to reduce memory usage during any one particular check e.g. https://github.com/brennerm/aws-quota-checker/blob/1.10.0/aws_quota/check/ebs.py#L13 for my scenario. EDIT 2: |
Hello @kedoodle thanks for your work. Your expression doesn't work with this metric awsquota_elb_listeners_per_clb We are trying to find a new alert rule, we will get back to you ! Thanks ! |
Hopefully you can adapt the expression to something that works for your use case in leiu of the proposed |
We're updating our alerts to make use of the metrics exposed by the
prometheus-exporter
feature ofaws-quota-checker
. We have a generic expression which aims to alert whenever we've breached 70% of any limit.The expression is quite unweildly:
A couple suggestions which would aid in crafting PromQL expressions:
Feel free to disregard if this is too niche or opinionated in a direction you'd rather not take. A solution to those facing similar grievances could be through the use of recording rules.
The text was updated successfully, but these errors were encountered: