From 3ecd4bb8d41380992739fa7721e88ec896728933 Mon Sep 17 00:00:00 2001
From: vishakha <54327666+vishakhanihore@users.noreply.github.com>
Date: Mon, 14 Oct 2019 11:52:36 +0530
Subject: [PATCH] Fixing links in markdown for `logs` and `metrics` (#16843)

---
 .../tasks/debug-application-cluster/events-stackdriver.md     | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/content/en/docs/tasks/debug-application-cluster/events-stackdriver.md b/content/en/docs/tasks/debug-application-cluster/events-stackdriver.md
index e3e9150f33..d852ed3cf9 100644
--- a/content/en/docs/tasks/debug-application-cluster/events-stackdriver.md
+++ b/content/en/docs/tasks/debug-application-cluster/events-stackdriver.md
@@ -29,12 +29,10 @@ It is not guaranteed that all events happening in a cluster will be
 exported to Stackdriver. One possible scenario when events will not be
 exported is when event exporter is not running (e.g. during restart or
 upgrade). In most cases it's fine to use events for purposes like setting up
-[metrics][sdLogMetrics] and [alerts][sdAlerts], but you should be aware
+[metrics](https://cloud.google.com/logging/docs/logs-based-metrics/) and [alerts](https://cloud.google.com/logging/docs/logs-based-metrics/charts-and-alerts), but you should be aware
 of the potential inaccuracy.
 {{< /note >}}
 
-[sdLogMetrics]: https://cloud.google.com/logging/docs/view/logs_based_metrics
-[sdAlerts]: https://cloud.google.com/logging/docs/view/logs_based_metrics#creating_an_alerting_policy
 
 {{% /capture %}}