Prometheus
prometheus.io › docs › prometheus › latest › configuration › alerting_rules
Alerting rules | Prometheus
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
Prometheus
prometheus.io › docs › alerting › latest › overview
Alerting overview | Prometheus
Join PromCon EU 2026 , the Prometheus users conference, on October 7–8, 2026 in Munich. PromCon EU 2026 — Oct 7–8, Munich. ... Alerting with Prometheus is separated into two parts. Alerting rules in Prometheus servers send alerts to an Alertmanager.
Best practice for using Prometheus with Alloy
I use: count(count_over_time(up[1h])) by (instance) unless count(count_over_time(up[5m])) by (instance) This looks for the up metric over the last 5 mins and compares it to the last hour. If there were up metrics in the last hour BUT there were no recent metrics in the last 5 mins, then the alert triggers. After one hour the up metric no longer exists for the instance, so the no data setting needs to be set to normal so it will place the alert back from 'triggering' to 'normal' state. What this means is that if a node goes offline and stops sending the 'up' metric, we'll get alerted. If we choose to ignore it, the assumption has to be that this is "expected" and the alert goes back to normal. You can play with the time values in the search if you want the alert to remain in 'triggering' mode longer or shorter. But, because Grafana can't differentiate between "oops it's down" versus "this is being retired", the alert has to switch back to normal after some time on its own. More on reddit.com
oauth2-proxy for Prometheus Operator with Google SSO deployed with helm
Without the actual log entries in the oauth2proxy and it's idp's logs hard to say anything. More on reddit.com
Zabbix or promethes/Grafana/AlertManager for on-prem VM monitoring?
Zabbix is a tool for sysadmins. Grafana/prometheus is a tool stack for DevOps engineers. You cannot effectively monitor dynamic environments with zabbix. More on reddit.com
Is there a WebUI for Alertmanager that allows managing silences and scheduling downtimes via a browser?
Check out https://github.com/prymitive/karma/ in addition to AM's native UI More on reddit.com
41:05
Alerts using Prometheus & Grafana - YouTube
31:50
How to send Alerts in Prometheus - Alertmanager - YouTube
Ep4 Prometheus Alerts to Slack | Real-Time Alertmanager ...
13:55
Prometheus Alertmanager - YouTube
10:41
PROMETHEUS - 22. Alert Manager : installation - YouTube
27:44
How to setup alerting using Prometheus Alerts Manager #aws ...
Samber
samber.github.io › home › rules
1162 Prometheus Alerting Rules for 94 Services | Awesome Prometheus Alerts
Browse 1162 Prometheus alerting rules across 94 services. Organized by category: databases, Kubernetes, cloud providers, message brokers, and more.
Prometheus
prometheus.io › docs › alerting › latest › alertmanager
Alertmanager | Prometheus
Example: Dozens or hundreds of ... reach the database. Alerting rules in Prometheus were configured to send an alert for each service instance if it cannot communicate with the database....
Microsoft Learn
learn.microsoft.com › en-us › azure › azure-monitor › alerts › prometheus-alerts
Prometheus metric alerts in Azure Monitor - Azure Monitor | Microsoft Learn
The rule queries are applied on Prometheus metrics stored in an Azure Monitor workspace. Whenever the alert query results in one or more time series meeting the condition, the alert counts as pending for these metric and label sets. A pending alert becomes active after a user-defined period of time during which all the consecutive query evaluations for the respective time series meet the alert condition.
Prometheus
prometheus.io › docs › practices › alerting
Alerting | Prometheus
Typically alert on high latency and error rates as high up in the stack as possible. Only page on latency at one point in a stack. If a lower-level component is slower than it should be, but the overall user latency is fine, then there is no need to page. For error rates, page on user-visible ...
Sysdig Docs
docs.sysdig.com › en › sysdig-monitor › prometheus-alerts
Prometheus Alerts | Sysdig Docs
Click Add Alert and choose Prometheus. Condition: Enter a valid PromQL expression. Unlike Threshold Alerts, PromQL queries only return time series that meet the specified condition. For example, if you enter sysdig_host_cpu_used_percent > 80, only the hosts with CPU usage above 80% will be included in the query results.
Doks
prometheus-operator.dev › home › docs › developer › alerting routes
Alerting Routes - Prometheus Operator
The AlertmanagerConfig resource named example-config in namespace default will be a global AlertmanagerConfig. When the operator generates the Alertmanager configuration from it, the namespace label will not be enforced for routes and inhibition rules. The PrometheusRule CRD allows to define alerting and recording rules.
Samber
samber.github.io › awesome-prometheus-alerts › rules.html
Awesome Prometheus alerts | Collection of alerting rules
Redirecting to /awesome-prometheus-alerts/rules/…
GitHub
github.com › bdossantos › prometheus-alert-rules
GitHub - bdossantos/prometheus-alert-rules: Collection of Prometheus Alert Rules · GitHub
Docker — used to run promtool for rule validation ... This runs promtool check rules on all files in rules/ inside a Docker container. ... Add or edit the appropriate YAML file in rules/. Run make test to validate the rule syntax. ... --- groups: - name: <group-name> rules: - alert: <AlertName> expr: > (<PromQL expression>) * on(instance) group_left (nodename) node_uname_info{nodename=~".+"} for: <duration> labels: severity: <page|warning|info> annotations: summary: <Human readable description> (instance {{ $labels.instance }}) description: "<detailed description>\n VALUE = {{ $value }}\n LABELS = {{ $labels }}"
Author: bdossantos