From 0b51015dc9d2c1b1a758010b12dbd8668cd4e1e9 Mon Sep 17 00:00:00 2001 From: Jack Baldry Date: Thu, 28 Sep 2023 09:06:03 +0100 Subject: [PATCH] fix links (#75524) (#75607) Co-authored-by: brendamuir <100768211+brendamuir@users.noreply.github.com> --- docs/sources/alerting/manage-notifications/mute-timings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/alerting/manage-notifications/mute-timings.md b/docs/sources/alerting/manage-notifications/mute-timings.md index 084356169f2..983af85dd02 100644 --- a/docs/sources/alerting/manage-notifications/mute-timings.md +++ b/docs/sources/alerting/manage-notifications/mute-timings.md @@ -20,7 +20,7 @@ A mute timing is a recurring interval of time when no new notifications for a po Similar to silences, mute timings do not prevent alert rules from being evaluated, nor do they stop alert instances from being shown in the user interface. They only prevent notifications from being created. -You can configure Grafana managed mute timings as well as mute timings for an [external Alertmanager data source]({{< relref "/docs/grafana/latest/datasources/alertmanager" >}}). For more information, refer to [Alertmanager documentation]({{< relref "/docs/grafana/latest/alerting/manage-notifications/alertmanager" >}}). +You can configure Grafana managed mute timings as well as mute timings for an external Alertmanager. ## Mute timings vs silences