-
Notifications
You must be signed in to change notification settings - Fork 65
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
Prometheus Alertmanager config for PagerDuty #5290
Conversation
Send alerts to PagerDuty when jupyterhub-home-nfs disk usage is above 90%
Merging this PR will trigger the following deployment actions. Support and Staging deployments
Production deployments
|
This is the file to change the structure of https://github.com/2i2c-org/infrastructure/blob/main/helm-charts/support/enc-support.secret.values.yaml |
I have committed those changes to this PR! |
The name of the rulegroup doesn't get sent to PagerDuty unfortunately
Documentation requirements for this:
|
@sgibson91 I've added documentation on how to enable alerts through Prometheus Alertmanager and how to resize the EBS volume used by the NFS server. I created and merged #5297 to test the workflow for increasing EBS volume size. But weirdly, that didn't start any deployments at all. Can we look into that if you have time today? |
We don't automatically do anything when terraform config is changed, because we don't fully trust it not to delete something if the plan isn't inspected. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is good to merge once you've update that the terraform changes need to be applied locally (we don't automatically deploy terraform changes in CI/CD)
should be applied locally
Thanks @sgibson91! I've updated the PR accordingly. |
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/12412069094 |
Send alerts to PagerDuty when jupyterhub-home-nfs disk usage is above 90%. Related to #5062.
In addition to these changes, we need to store the Pagerduty key in a structure like this in
helm-charts/support/support.secret.values.yaml
:cc @sgibson91