you can consider this solution to resolve your issue i hope it prove helpful for u
Step :1. Mute Timing Split Over Midnight – Combine into One
You mentioned:
23:00 → 00:00 00:00 → 06:00
This split across midnight can confuse the evaluation. Grafana doesn’t currently handle split timings gracefully unless the ranges are continuous and part of the same time interval object.
Create one single time interval with:
Start: 23:00
End: 06:00
Days: every day
Grafana interprets this as from 11 PM until 6 AM the next day.
Step: 2. Assign the Mute Timing to the Correct Notification Policy
You mentioned selecting alertname — make sure you’re assigning the mute timing in the right Notification Policy, not just a matching label.
Steps:
Alerting > Notification Policies
Check your policy list
Find the one matching your alertname or other labels
Edit it and scroll to Mute timings
Select the new combined time interval
ensure that no fallback policy lower in the tree is sending to Telegram without mute timings — Grafana processes policies top-down until one matches.
Step 3. Check Alert Rules are Using the Right Policy Tree
Make sure the alert rules are routed via the notification policy you configured:
Alerting > Alert Rules
Find the rule in question
Confirm the labels on the alert (e.g. alertname, severity, etc.)
Those labels must match the Notification Policy routing rule
If the alert doesn’t match any policy, it may fall back to the default policy, which sends alerts unmuted.
Step: 4. Validate the Mute Timing is Active
In Grafana v11.4.0, you can check:
Alerting > Notification Policies
On the relevant policy, check the Mute Timing status hover or view tooltip — it may say Active now or Not active
Try testing it manually by triggering an alert and observing behavior
Step: 5. Restart Grafana or Check for Sync Delay
