Skip to content
Snippets Groups Projects
Select Git revision
  • test-2
  • test
  • gitaly-troubleshoot-update
  • master default protected
  • update-tweet-guidelines
  • mk-alerting-update
  • ci-introduction
  • mk-db-locks-alert
  • pc-backups
  • mk-drop-vm-checklist
10 results

machines-operation-rates.rules

  • Julius Volz's avatar
    bfcc3b49
    Various alerting rule cleanups/fixes etc. · bfcc3b49
    Julius Volz authored 
    - Changed all alert names to CamelCase (@bjk-gitlab asked for this)
- Improved/fixed some alert conditions and messages
- Try to preserve a tad more labels in expressions (when possible)

Unfortunately the Slack notification templates in Alertmanager rely on
there being only one "title" and "description" value, because they use
the title/description from CommonAnnotations (so those are only present
if they are the same between all alerts resulting from one alerting
rule). So I kept appropriate aggregations and topk-ing in some of the
alerts to not break that assumption.
    bfcc3b49
    History
    Various alerting rule cleanups/fixes etc.
    Julius Volz authored 
    - Changed all alert names to CamelCase (@bjk-gitlab asked for this)
- Improved/fixed some alert conditions and messages
- Try to preserve a tad more labels in expressions (when possible)

Unfortunately the Slack notification templates in Alertmanager rely on
there being only one "title" and "description" value, because they use
the title/description from CommonAnnotations (so those are only present
if they are the same between all alerts resulting from one alerting
rule). So I kept appropriate aggregations and topk-ing in some of the
alerts to not break that assumption.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.