Yes, or is a Prometheus operator. See the docs.
Prometheus
prometheus.io › docs › prometheus › latest › configuration › alerting_rules
Alerting rules | Prometheus
Elements that are active, but not firing yet, are in the pending state. Alerting rules without the for clause will become active on the first evaluation. There is also an optional keep_firing_for clause that tells Prometheus to keep this alert firing for the specified duration after the firing condition was last met.
Robust Perception
robustperception.io › combining-alert-conditions
Combining alert conditions – Robust Perception | Prometheus Monitoring Experts
It's easy to produce alerts in Prometheus to cover cases like latency is too high. What if you wanted to also restrict the alert to a minimum amount of traffic or a time of day? The answer is the and logical binary operator combined with vector matching: groups: - name: test.rules rules: - alert: LatencyTooHigh expr: job:request_latency_seconds:mean5m{job="myjob"} > 0.5 and ON(job) job:requests:rate5m{job="myjob"} > 100
How to filter Alert Processing Rule based on Name of Rule from Prometheus Rule Group?
We are using multiple rules defined in a Prometheus Rule Group to create alerts based on Prometheus metrics. An alert processing rule is used to trigger an action group based on alerts. We want to add a filter condition so that certain alerts do not lead… More on learn.microsoft.com
1
0
trying to activate a single alert if multiple conditions are true for different datapoints
its seems to me that prometheus is unable to perform the logic where it checks the status on multiple different datapoints in order to trigger a single alert for example: i am monitoring a series o... More on github.com
1
February 18, 2017Prometheus rule with multi expressions
If you want to label rules with different severity levels, you typically create the same alert name with different labels. For example, we have a [pair of rules]) https://gitlab.com/gitlab-com/runbooks/blob/master/rules/ssl-certificate-expirations.yml ) to change thresholds and routing for if we want an issue opened vs paging. It is also possible to create thresholds with recording rules. I think something like this should work: groups: - name: SSL Certs rules: - record: ssl_cert_expiry_threshold expr: 7 * 86400 labels: pager: issue - record: ssl_cert_expiry_threshold expr: 1 * 86400 labels: pager: pagerduty - alert: SSLCertExpiresSoon expr: probe_ssl_earliest_cert_expiry - time() < on () group_left (pager) ssl_cert_expiry_threshold for: 30m labels: severity: s1 annotations: description: Check SSL for specified nodes and consider reissuing certificate. runbook: troubleshooting/ssl_cert.md title: SSL certificate for {{ $labels.instance }} expires in {{ $value | humanizeDuration }} More on reddit.com
1
5
September 18, 2019Alert rules, {{value}} and mixed conditions
Two separate alerts are the way to go, as the units don't line up currently as one in a % and the other is in MB. You can make the value more readable using {{$value | printf "%.2f" }} or {{ $ value | humanize1024 }} More on reddit.com
2
3
April 24, 2017 Top answer 1 of 2
5
Yes, or is a Prometheus operator. See the docs.
2 of 2
1
Prometheus supports or operation as already pointed in this answer. The following query must be used for alerting when a time series foo exceeds the given threshold or if a time series foo is absent for the duration d:
foo > threshold or absent_over_time(foo[d])
See absent_over_time() docs. Note that the absent_over_time() doesn't work as expected, e.g. doesn't return non-empty result if there are multiple time series with foo name and only a single time series has no new samples during the duration d. Basically, it works as expected only if there is only a single matching time series.
Prometheus doesn't provide functionality for creating universal alerts, which could detect time series without new samples over the given duration across multiple matching time series. However, such function exists in VictoriaMetrics - see lag(). For example, the following query alerts (e.g. returns non-empty result) for time series with foo name, which exceeded the given threshold or which didn't have new samples during the last 5 minutes, while they had at least a single sample during the last hour:
foo > threshold or lag(foo[1h]) > 5m
Cloudcover
blog.cloudcover.ch › posts › prometheus-metric-alerting-rule-with-multiple-conditions
Prometheus Metric Alerting Rule with Multiple Conditions
March 27, 2022 - We could add another condition to the rule to avoid a false positive, ensuring that the pod is at least 15 minutes old before triggering an alert. To evaluate multiple Prometheus metrics in a single Alerting rule, and on or or on can be used.
Squadcast
squadcast.com › blog › prometheus-sample-alert-rules
Prometheus Alert Rules: Comprehensive Guide with Best Practices & Samples | Squadcast
April 17, 2023 - A single alert condition in a group triggers all alerts in the same group. Prometheus uses the PromQL (Prometheus Query Language) to create alerting rules. The alert expression is the core of a Prometheus alert.
DoHost
dohost.us › home › 2025 › september › 27 › writing prometheus alerting rules for critical conditions
Writing Prometheus Alerting Rules for Critical Conditions - DoHost
September 27, 2025 - Step 1: Understand the Alerting Rule Structure: Prometheus alerting rules are defined using YAML syntax. A basic rule consists of the alert name, the expr (expression) that triggers the alert, and optional annotations and labels. Step 2: Choose the Right Metric: Identify the metric that best reflects the critical condition you want to monitor.
Last9
last9.io › blog › prometheus-alerting-examples
Prometheus Alerting Examples for Developers | Last9
June 2, 2025 - Each rule says: “If this thing is true for this long, send an alert.” ... If your alerts need to work across multiple metrics, this guide on querying multiple metrics in Prometheus can help you structure those expressions better.
Microsoft Learn
learn.microsoft.com › en-us › answers › questions › 2123615 › how-to-filter-alert-processing-rule-based-on-name
How to filter Alert Processing Rule based on Name of Rule from Prometheus Rule Group? - Microsoft Q&A
The approach of full text matching against the alertContext field seemed rather fuzzy to our team, so we now chose a different approach. We split the PrometheusRuleGroup into multiple PrometheusRuleGroups, each containing only exactly one rule. We then used the IDs of the complete PrometheusRuleGroups as a filter condition on the alert_rule_id field.
OpsRamp
opsramp.com › guides › prometheus-monitoring › prometheus-alerting
Enterprise IT Glossary | HPE | HPE
Explore HPE's enterprise IT glossary for clear definitions of key technology terms across AI, hybrid cloud, compute, networking, storage, security, and more.
OneUptime
oneuptime.com › home › blog › how to implement prometheus alert rule design
How to Implement Prometheus Alert Rule Design
January 30, 2026 - This guide walks through the principles, patterns, and practical examples you need to build alert rules that actually work. ... Prometheus evaluates alert rules at regular intervals.
Alibaba Cloud
alibabacloud.com › help › en › arms › prometheus-monitoring › create-an-alert-rule-for-a-prometheus-instance
Set Up Prometheus Alert Rules with DingTalk Notifications - ARMS - Alibaba Cloud
... After you select a notification policy, alert events from this rule may also be matched by other notification policies that use fuzzy match. One alert event can be matched by multiple notification policies. Click Save.
GitHub
github.com › prometheus › alertmanager › issues › 629
trying to activate a single alert if multiple conditions are true for different datapoints · Issue #629 · prometheus/alertmanager
February 18, 2017 - this way it checks for 3 "seperate" datapoints instead of trying to qualify all of these conditions as true for only "one" device. this is the alert rule that im using: ALERT SERVER3_DOWN IF ipSlaUpStatus{rttMonCtrlAdminLongTag="'from_router_to_server1'"} == 1 AND ipSlaUpStatus{rttMonCtrlAdminLongTag="'from_router_to_server2"} == 1 AND ipSlaUpStatus{rttMonCtrlAdminLongTag="'from_router_to_server3'"} == 0 FOR 1m LABELS { severity = "critical" } ANNOTATIONS { summary = "Server 3 has gone down but not Server 1 & 2", description = "Server 3 has gone down but not Server 1 & 2.
Author: prometheus
Sysdig Docs
docs.sysdig.com › en › sysdig-monitor › prometheus-alerts
Prometheus Alerts | Sysdig Docs
This is because the No Data state in Prometheus is indistinguishable from a resolved state. Strategies for dealing with this can be found in the No Data and Multiple Thresholds. Duration: The duration is how long an alert condition must remain true before triggering an alert.
VictoriaMetrics
victoriametrics.com › blog › prometheus alerting 101: rules, recording rules, and alertmanager
Prometheus Alerting 101: Rules, Recording Rules, and Alertmanager
March 18, 2025 - Any alert that doesn’t match these conditions lands in team-email as a fallback. A key thing to notice is the continue: true line. Without it, high-priority critical alerts wouldn’t reach the team leader because the first rule would already capture them.
Google Groups
groups.google.com › g › prometheus-users › c › mYf6WxptMiw
alert rules: multiple rules for general & special cases
January 18, 2023 - To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/5fe28eec-a91c-4619-af41-128966ad08d9n@googlegroups.com. ... Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message ... The 'special cases' alert1 and alert2 have particular rules; alert3 has the generic catch-all rule with 'unless' blocks to suppress the alert1 and alert2 cases, but using identical expressions.
Nais Documentation
doc.nais.io › observability › alerting › reference › prometheusrule
Prometheus Alerting Rule Reference - Nais
A PrometheusRule can contain multiple groups of rules. Each group can contain multiple alert rules.
DrDroid
drdroid.io › engineering-tools › guide-for-creating-alerts-in-prometheus-alert-manager
Guide for creating alerts in Prometheus Alert Manager | Engineering Tools
Reduces notification noise by triggering alerts only when multiple critical conditions are met. These advanced features make Prometheus Alert Manager a robust tool for precise and efficient alerting.
Cloudflare
blog.cloudflare.com › monitoring-our-monitoring
Monitoring our monitoring: how we validate our Prometheus alert rules | Cloudflare Blog
May 19, 2022 - Knowing a bit more about how queries work in Prometheus we can go back to our alerting rules and spot a potential problem: queries that don’t return anything. If our query doesn’t match any time series or if they’re considered stale then Prometheus will return an empty result. This might be because we’ve made a typo in the metric name or label filter, the metric we ask for is no longer being exported, or it was never there in the first place, or we’ve added some condition that wasn’t satisfied, like value of being non-zero in our http_requests_total{status=”500”} > 0 example.
AWS
docs.aws.amazon.com › amazon managed service for prometheus › user guide › using rules to modify or monitor metrics as they are received
Using rules to modify or monitor metrics as they are received - Amazon Managed Service for Prometheus
Amazon Managed Service for Prometheus supports two types of rules that it evaluates at regular intervals: Recording rules allow you to precompute frequently needed or computationally expensive expressions and save their results as a new set of time series. Querying the precomputed result is often much faster than running the original expression every time it is needed. Alerting rules allow you to define alert conditions ...