October 21, 2018 - PromQL (Prometheus Query Language) ... rules use PromQL expressions — for example, rate(http_requests_total[5m]) > 100 fires when request rate exceeds 100/s over a 5-minute window....

A curated collection of Prometheus alert rules and recording rules covering a wide range of systems and services.

1,155+ production-ready Prometheus alerting rules for 93+ services — copy-paste YAML for Kubernetes, MySQL, Redis, Kafka, and more.

Redirecting to /awesome-prometheus-alerts/rules/…

​ The goal of this repository is collect prometheus alert rules for everyone to use. We all want good alerting. But writing new rules for common things shouldn't be something everyone has to do from scratch. This is a place for people to share useful alerts they have written, and a place for people to find good alerts without having to re-invent the wheel every time. If anything this can serve as a great resource of examples for people to create their own rules.

- name: example · rules: · # Alert for any instance that is unreachable for >2 minutes. - alert: service_down · expr: up == 0 · for: 2m · labels: severity: page · annotations: summary: "Instance {{ ...

Alerting rules are configured in Prometheus in the same way as recording rules. ... groups: - name: example labels: team: myteam rules: - alert: HighRequestLatency expr: job:request_latency_seconds:mean5m{job="myjob"} > 0.5 for: 10m keep_firing_for: 5m labels: severity: page annotations: summary: High request latency

Awesome Prometheus AlertsAPA · ⌘K · Sponsored by · Search · 1162 alerting rules across 94 services and 13 categories. ⚠️ · Alert thresholds depend on the nature of your applications. Some queries may have arbitrary tolerance thresholds. Building an efficient monitoring platform takes time.

Alerts should be configured at two severity levels, warning and critical: warning should be used for alerts which will be read by a human, but do not require immediate action. They would, for example, trigger an email ...

rules: - alert: InstanceDown · expr: up{job="hello"} == 0 · for: 10s · labels: severity: page ·

October 6, 2016 - I.e. most common (critical and warning severity): disk usage memory usage CPU usage kubelet limit for pods per node etc.

Example alertmanager.yml receivers section with API Key · receivers: - name: "alerta" webhook_configs: - url: 'http://localhost:8080/webhooks/prometheus?api-key=QBPALlsFSkokm-XiOSupkbpK4SJdFBtStfrOjcdG' send_resolved: true · Prometheus rules define thresholds at which alerts should be triggered.

rules: - alert: monitor_service_down · expr: up == 0 · for: 30s · labels: severity: critical · annotations: summary: "Monitor service non-operational" description: "Service {{ $labels.instance }} is down." · - name: host ·

Example-of-prometheus-alerting-rules. GitHub Gist: instantly share code, notes, and snippets.

This repository serves as a centralized collection of Prometheus configurations for Giant Swarm's monitoring system. It includes: Alerting Rules: Definitions for monitoring and alerting across different teams and platforms

Prometheus Operator creates/configures/manages Prometheus clusters atop Kubernetes - prometheus-operator/example/user-guides/alerting/prometheus-example-rules.yaml at main · prometheus-operator/prometheus-operator

rules: · # heartbeat alert · - alert: Heartbeat · expr: vector(1) labels: event: "Heartbeat" instance: "prometheus" monitor: "prometheus" severity: "major" timeout: "120" annotations: summary: "Heartbeat from prometheus" description: "Heartbeat from from prometheus" ·

groups: - name: /var/www/monitor/prometheus/containers.rules rules: - alert: high_cpu_usage_on_container expr: sum(rate(container_cpu_usage_seconds_total{name=~".+"}[1m])) BY (name, host) * 100 > 70 for: 5m labels: severity: warning annotations: description: '{{ $labels.name }} is using a LOT ...

description: A Prometheus job does not have living target anymore. ... description: "Allow a job time to start up (10 minutes) before alerting that it's down."

This repository contains a collection of Prometheus alert templates for various systems and services. Each directory contains specific alert rules and documentation for monitoring different components of your infrastructure. Kubernetes: Alerts for Kubernetes cluster monitoring ... # values.yaml additionalPrometheusRulesMap: custom-alerts.yaml: groups: - name: custom_alerts rules: # Copy rules from respective alert template files - alert: ExampleAlert expr: up == 0 for: 5m labels: severity: critical annotations: summary: "Example alert" description: "Example description"