Update events urls links

Author: estherk15

content/en/account_management/org_settings.md

@@ -168,7 +168,7 @@ Users with the `Org Management` permission can enable or disable the idle time s
 [9]: /account_management/rbac/
 [10]: /remote_configuration#how-it-works
 [11]: /account_management/api-app-keys/#client-tokens
-[12]: /service_management/events/guides/email/
+[12]: /events/guides/email/
 [13]: /synthetics/settings/?tab=specifyvalue#overview
 [14]: /account_management/safety_center
 [15]: /account_management/org_settings/oauth_apps

content/en/administrators_guide/plan.md

@@ -344,7 +344,7 @@ Create a detailed roll-out methodology in the [build][41] phase by focusing on t
 [28]: /integrations/network/
 [29]: /network_monitoring/cloud_network_monitoring/
 [30]: /software_catalog/
-[31]: /service_management/events/
+[31]: /events/
 [32]: /error_tracking/
 [33]: /software_catalog/endpoints/
 [34]: /agent/fleet_automation/

content/en/all_guides.md

@@ -22,7 +22,7 @@ Guides in the Datadog documentation are pages that provide background knowledge,
 
 {{< whatsnext desc="Service Management:">}}
 {{< nextlink href="/service_level_objectives/guide" >}}<i class="icon-slos" style="font-size:25px;color:#7c3eb9;vertical-align:middle"></i>&nbsp;&nbsp;&nbsp;&nbsp;SLOs{{< /nextlink >}}
-{{< nextlink href="/service_management/events/guides" >}}<i class="icon-events" style="font-size:25px;color:#7c3eb9;vertical-align:middle"></i>&nbsp;&nbsp;&nbsp;&nbsp;Events{{< /nextlink >}}
+{{< nextlink href="/events/guides" >}}<i class="icon-events" style="font-size:25px;color:#7c3eb9;vertical-align:middle"></i>&nbsp;&nbsp;&nbsp;&nbsp;Events{{< /nextlink >}}
 {{< /whatsnext >}}
 
 {{< whatsnext desc="Infrastructure:">}}

content/en/coterm/usage.md

@@ -130,7 +130,7 @@ COTERM_BREAK_GLASS=true kubectl delete foo
 {{< partial name="whats-next/whats-next.html" >}}
 
 [1]: /sensitive_data_scanner/
-[2]: /service_management/events/
+[2]: /events/
 [3]: /service_management/case_management/
 [4]: /coterm/rules
 [5]: /service_management/incident_management/

content/en/developers/dogstatsd/_index.md

@@ -602,7 +602,7 @@ DogStatsD and StatsD are broadly similar, however, DogStatsD contains advanced f
 
 {{< whatsnext desc="">}}
 {{< nextlink href="/metrics/custom_metrics/dogstatsd_metrics_submission/" >}}Send metrics to Datadog with DogStatsD.{{< /nextlink >}}
-{{< nextlink href="/service_management/events/guides/dogstatsd/" >}}Send events to Datadog with DogStatsD.{{< /nextlink >}}
+{{< nextlink href="/events/guides/dogstatsd/" >}}Send events to Datadog with DogStatsD.{{< /nextlink >}}
 {{< nextlink href="/developers/service_checks/dogstatsd_service_checks_submission/" >}}Send service checks to Datadog with DogStatsD.{{< /nextlink >}}
 {{< /whatsnext >}}
 
@@ -617,7 +617,7 @@ If you're interested in learning more about the datagram format used by DogStats
 [3]: https://hub.docker.com/r/datadog/dogstatsd
 [4]: https://gcr.io/datadoghq/dogstatsd
 [5]: /metrics/custom_metrics/
-[6]: /service_management/events/guides/dogstatsd/
+[6]: /events/guides/dogstatsd/
 [7]: /developers/service_checks/dogstatsd_service_checks_submission/
 [8]: /getting_started/tagging/unified_service_tagging
 [9]: /developers/dogstatsd/datagram_shell/

content/en/dora_metrics/_index.md

@@ -17,7 +17,7 @@ further_reading:
 - link: "/continuous_delivery/deployments"
   tag: "Documentation"
   text: "Learn about Deployment Visibility"
-- link: "/service_management/events"
+- link: "/events"
   tag: "Documentation"
   text: "Learn about Event Management"
 - link: "/monitors/types/metric"

content/en/dora_metrics/data_collected/_index.md

@@ -129,7 +129,7 @@ Using commit-level granularity provides a more accurate view of engineering perf
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: /service_management/events/explorer/
+[1]: /events/explorer/
 [2]: /api/latest/metrics/#query-timeseries-points
 [3]: /api/latest/metrics/#query-timeseries-data-across-multiple-products
 [5]: https://app.datadoghq.com/event/explorer?query=source%3Asoftware_delivery_insights

content/en/error_tracking/dynamic_sampling.md

@@ -48,7 +48,7 @@ When Dynamic Sampling is applied, the following steps are recommended:
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: /service_management/events/
+[1]: /events/
 [2]: https://app.datadoghq.com/error-tracking/settings/rate-limits
 [3]: /logs/error_tracking/manage_data_collection#add-a-rule
 [4]: https://app.datadoghq.com/error-tracking/settings

content/en/error_tracking/manage_data_collection.md

@@ -148,5 +148,5 @@ When Dynamic Sampling is applied, the following steps are recommended:
 
 [1]: https://app.datadoghq.com/error-tracking/settings/rules
 [2]: /error_tracking/troubleshooting/?tab=java#errors-are-not-found-in-error-tracking
-[4]: /service_management/events/
+[4]: /events/
 [5]: https://app.datadoghq.com/error-tracking/settings/rate-limits

content/en/events/_index.md

@@ -8,7 +8,7 @@ further_reading:
 - link: "/api/latest/events/"
   tag: "Documentation"
   text: "Datadog Events API"
-- link: "/service_management/events/guides/recommended_event_tags/"
+- link: "/events/guides/recommended_event_tags/"
   tag: "Documentation"
   text: "Best Practices for Tagging Events"
 - link: "https://www.datadoghq.com/blog/identify-sensitive-data-leakage-in-apm-rum-with-sensitive-data-scanner/"
@@ -40,12 +40,12 @@ More than 100 Datadog integrations support events collection, including [Kuberne
 ## Components
 
 {{< whatsnext desc="Event Management features:">}}
-    {{< nextlink href="/service_management/events/ingest/" >}}<u>Ingest events</u> - Learn how to send events to Datadog{{< /nextlink >}}
-     {{< nextlink href="/service_management/events/triage_inbox" >}}<u>Triage Inbox</u> - Triage, investigate, collaborate, and resolve incidents{{< /nextlink >}}
-     {{< nextlink href="/service_management/events/pipelines_and_processors/">}}<u>Pipelines and Processors</u> - Enrich and Normalize your events{{< /nextlink >}}
-    {{< nextlink href="/service_management/events/explorer/" >}}<u>Events Explorer</u> - View, search and send notifications from events coming into Datadog{{< /nextlink >}}
-    {{< nextlink href="/service_management/events/guides/usage/" >}}<u>Using events</u> - Analyze, investigate, and monitor events {{< /nextlink >}}
-    {{< nextlink href="/service_management/events/correlation/" >}}<u>Correlation</u> - reduce alert fatigue and the number of tickets/notifications you receive {{< /nextlink >}}
+    {{< nextlink href="/events/ingest/" >}}<u>Ingest events</u> - Learn how to send events to Datadog{{< /nextlink >}}
+     {{< nextlink href="/events/triage_inbox" >}}<u>Triage Inbox</u> - Triage, investigate, collaborate, and resolve incidents{{< /nextlink >}}
+     {{< nextlink href="/events/pipelines_and_processors/">}}<u>Pipelines and Processors</u> - Enrich and Normalize your events{{< /nextlink >}}
+    {{< nextlink href="/events/explorer/" >}}<u>Events Explorer</u> - View, search and send notifications from events coming into Datadog{{< /nextlink >}}
+    {{< nextlink href="/events/guides/usage/" >}}<u>Using events</u> - Analyze, investigate, and monitor events {{< /nextlink >}}
+    {{< nextlink href="/events/correlation/" >}}<u>Correlation</u> - reduce alert fatigue and the number of tickets/notifications you receive {{< /nextlink >}}
 
 {{< /whatsnext >}}