Update Service Management to Incident Response

content/en/account_management/billing/incident_response.md

@@ -1,13 +1,13 @@
 ---
 title: Incident Response Billing
 further_reading:
-- link: "/service_management/incident_management/"
+- link: "/incident_response/incident_management/"
   tag: "Documentation"
   text: "Incident Management"
-- link: "/service_management/on-call/"
+- link: "/incident_response/on-call/"
   tag: "Documentation"
   text: "On-Call"
-- link: "/service_management/status_pages/"
+- link: "/incident_response/status_pages/"
   tag: "Documentation"
   text: "Status Pages"
 ---
@@ -132,12 +132,12 @@ Your monthly bill contains the following:
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: /service_management/incident_management/
-[2]: /service_management/on-call/
+[1]: /incident_response/incident_management/
+[2]: /incident_response/on-call/
 [3]: https://www.datadoghq.com/pricing/?product=incident-response#products
 [4]: https://app.datadoghq.com/billing/seats
-[5]: /service_management/on-call/schedules/
-[6]: /service_management/on-call/escalation_policies/
-[7]: /service_management/on-call/profile_settings/#notification-preferences
-[8]: /service_management/incident_management/investigate/timeline
+[5]: /incident_response/on-call/schedules/
+[6]: /incident_response/on-call/escalation_policies/
+[7]: /incident_response/on-call/profile_settings/#notification-preferences
+[8]: /incident_response/incident_management/investigate/timeline
 [9]: https://app.datadoghq.com/on-call/settings/notifications-preferences-admin

content/en/account_management/billing/workflow_automation.md

@@ -73,8 +73,8 @@ This means that if your automation originates from one of these services, those
 [6]: https://www.datadoghq.com/pricing/?product=infrastructure-monitoring#products
 [7]: /api/latest/workflow-automation/
 [8]: /actions/workflows/
-[9]: /service_management/incident_management/
-[10]: /service_management/on-call/
+[9]: /incident_response/incident_management/
+[10]: /incident_response/on-call/
 [11]: /actions/app_builder/
 [12]: /api/latest/workflow-automation/#list-workflow-instances
 [13]: https://www.datadoghq.com/pricing/?product=workflow-automation#products

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/account_management/rbac/granular_access.md

@@ -52,9 +52,9 @@ A user with the `user_access_manage` permission can elevate their access to any
 [5]: /dashboards/widgets/powerpack/#powerpack-permissions
 [6]: /security/detection_rules/#restrict-edit-permissions
 [7]: /security/suppressions/#restrict-edit-permissions
-[8]: /service_management/service_level_objectives/#permissions
+[8]: /service_level_objectives/#permissions
 [9]: /synthetics/browser_tests/#permissions
-[10]: /service_management/case_management/settings#granular-access-control
+[10]: /incident_response/case_management/settings#granular-access-control
 [11]: /getting_started/integrations/#granular-access-control
 [12]: /reference_tables/#permissions
 [13]: /actions/app_builder/access_and_auth/#restrict-access-to-a-specific-app
@@ -66,6 +66,6 @@ A user with the `user_access_manage` permission can elevate their access to any
 [19]: /real_user_monitoring
 [20]: /account_management/org_settings/cross_org_visibility/#permissions
 [21]: /sheets/#permissions
-[22]: /service_management/on-call/#granular-access-control
+[22]: /incident_response/on-call/#granular-access-control
 [23]: /observability_pipelines/configuration/access_control/
 [24]: /logs/log_configuration/pipelines/#pipeline-permissions

content/en/account_management/teams/_index.md

@@ -20,7 +20,7 @@ Team membership is flexible. Users can join teams, be added by other members, or
 
 ### Navigation
 
-Access the team directory page from [Organization Settings][1] or by navigating to [**Service Management > Teams**][2]. The [team directory page][1] lists all teams within your organization.
+Access the team directory page from [Organization Settings][1] or by navigating to [**Teams**][2]. The [team directory page][1] lists all teams within your organization.
 
 ### Create team
 
@@ -161,11 +161,11 @@ To customize your team, see [Team Management][3].
 [3]: /account_management/teams/manage/
 [4]: /account_management/saml/mapping/#map-saml-attributes-to-teams
 [5]: /dashboards/#dashboard-details
-[6]: /service_management/incident_management/
+[6]: /incident_response/incident_management/
 [7]: /monitors/configuration/?tab=thresholdalert#add-metadata
 [8]: /infrastructure/resource_catalog/
 [9]: /tracing/software_catalog/adding_metadata/#add-metadata-from-the-datadog-ui
-[10]: /service_management/service_level_objectives/#slo-tags
+[10]: /service_level_objectives/#slo-tags
 [11]: https://app.datadoghq.com/dashboard/lists
 [12]: https://app.datadoghq.com/services
 [13]: https://app.datadoghq.com/incidents

content/en/account_management/teams/manage.md

@@ -85,7 +85,7 @@ In some cases, a team's membership cannot be directly modified within Datadog by
 With subteams, you can nest teams within each other to mimic your company's hierarchy in Datadog, allowing for a more complete and accurate ownership model. Subteams also provide an enhanced filtering experience; select a larger team (like a director-level group) to find all the data connected to any of its subteams.
     {{< img src="account_management/teams/teams_filter_hierarchies.png" alt="Filter Hierarchical Teams" >}}
 
-On the **Subteams** tab, you can add and remove existing teams. For a clear view of a team's place in its hierarchy, go to [**Service Management** > **Teams** > **Map View**][4], then search for the team by name.
+On the **Subteams** tab, you can add and remove existing teams. For a clear view of a team's place in its hierarchy, go to [ **Teams** > **Map View**][4], then search for the team by name.
 To automate subteam management based on your organization’s hierarchical structure, use the [Teams APIs][5].
 
 ## Manage teams through an identity provider

content/en/actions/app_builder/components/_index.md

@@ -5,13 +5,13 @@ disable_toc: true
 aliases:
     - /service_management/app_builder/components
 further_reading:
-- link: "/service_management/app_builder/tables/"
+- link: "/actions/app_builder/tables/"
   tag: "Documentation"
   text: "Tables"
-- link: "/service_management/app_builder/build/"
+- link: "/actions/app_builder/build/"
   tag: "Documentation"
   text: "Build Apps"
-- link: "/service_management/app_builder/expressions/"
+- link: "/actions/app_builder/expressions/"
   tag: "Documentation"
   text: "JavaScript Expressions"
 - link: "https://learn.datadoghq.com/courses/app-builder-integration"

content/en/actions/app_builder/components/custom_charts.md

@@ -6,10 +6,10 @@ aliases:
 - /service_management/app_builder/custom_charts/
 - /service_management/app_builder/components/custom_charts
 further_reading:
-- link: "/service_management/app_builder/components/"
+- link: "/actions/app_builder/components/"
   tag: "Documentation"
   text: "Components"
-- link: "/service_management/workflows/build/"
+- link: "/incident_response/workflows/build/"
   tag: "Documentation"
   text: "Build Apps"
 ---

content/en/actions/app_builder/components/reusable_modules.md

@@ -3,13 +3,13 @@ title: Reusable Modules
 description: Save and reuse groups of components and queries across multiple App Builder applications as modular templates.
 disable_toc: false
 further_reading:
-- link: "/service_management/app_builder/components/"
+- link: "/actions/app_builder/components/"
   tag: "Documentation"
   text: "Components"
-- link: "/service_management/app_builder/build/"
+- link: "/actions/app_builder/build/"
   tag: "Documentation"
   text: "Build Apps"
-- link: "/service_management/app_builder/queries/"
+- link: "/actions/app_builder/queries/"
   tag: "Documentation"
   text: "Queries"
 ---

content/en/actions/app_builder/components/tables.md

@@ -6,10 +6,10 @@ aliases:
 - /service_management/app_builder/tables/
 - /service_management/app_builder/components/tables
 further_reading:
-- link: "/service_management/app_builder/components/"
+- link: "/actions/app_builder/components/"
   tag: "Documentation"
   text: "Components"
-- link: "/service_management/app_builder/build/"
+- link: "/actions/app_builder/build/"
   tag: "Documentation"
   text: "Build 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

@@ -21,8 +21,8 @@ Guides in the Datadog documentation are pages that provide background knowledge,
 {{< /whatsnext >}}
 
 {{< whatsnext desc="Service Management:">}}
-{{< nextlink href="/service_management/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="/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="/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/bits_ai/bits_ai_sre/configure.md

@@ -107,7 +107,7 @@ You can monitor user-initiated actions with [Audit Trail][11]. Events are sent w
 [2]: /monitors/notify
 [3]: https://docs.datadoghq.com/integrations/slack/?tab=datadogforslack
 [4]: https://app.datadoghq.com/bits-ai/settings/integrations
-[5]: /service_management/case_management/projects
+[5]: /incident_response/case_management/projects
 [6]: https://app.datadoghq.com/cases/settings
 [7]: https://app.datadoghq.com/integrations/confluence
 [8]: /account_management/rbac

content/en/bits_ai/bits_ai_sre/investigate_issues.md

@@ -136,6 +136,6 @@ The Reports tab enables you to track the number of investigations run over time
 [6]: https://app.datadoghq.com/monitors/manage
 [8]: /bits_ai/bits_ai_sre/configure#slack
 [9]: /bits_ai/bits_ai_sre/help_bits_learn/
-[10]: /service_management/on-call/pages/#page-from-notifications
-[14]: /service_management/case_management/notifications_integrations/#third-party-tickets
+[10]: /incident_response/on-call/pages/#page-from-notifications
+[14]: /incident_response/case_management/notifications_integrations/#third-party-tickets
 [15]: /account_management/rbac/permissions/#bits-ai

content/en/bits_ai/chat_with_bits_ai.md

@@ -5,7 +5,7 @@ further_reading:
 - link: "bits_ai/"
   tag: "Documentation"
   text: "Bits AI Overview"
-- link: "/service_management/incident_management/incident_ai"
+- link: "/incident_response/incident_management/incident_ai"
   tag: "Documentation"
   text: "Coordinate incidents with Incident AI"
 aliases:

content/en/containers/datadog_operator/crd_slo.md

@@ -68,11 +68,11 @@ To create a [Service Level Objective][1] (SLO), you can use the Datadog Operator
 ### Additional examples
 [Metric-based SLO with Universal Service Monitoring][8]
 
-[1]: /service_management/service_level_objectives/
+[1]: /service_level_objectives/
 [2]: https://helm.sh/
 [3]: https://kubernetes.io/docs/tasks/tools/install-kubectl/
 [4]: /api/latest/service-level-objectives/#create-an-slo-object
-[5]: /service_management/service_level_objectives/monitor/
-[6]: /service_management/service_level_objectives/metric/
+[5]: /service_level_objectives/monitor/
+[6]: /service_level_objectives/metric/
 [7]: /api/latest/service-level-objectives/#create-an-slo-object
 [8]: https://github.com/DataDog/datadog-operator/blob/main/examples/datadogslo/metric-usm-example.yaml

content/en/coscreen/_index.md

@@ -146,5 +146,5 @@ For all the details on how CoScreen enables secure collaboration, read the [CoSc
 [6]: https://www.datadoghq.com/legal/privacy/
 [7]: https://www.coscreen.co/security
 [8]: /security/sensitive_data_scanner/
-[9]: /service_management/incident_management/
+[9]: /incident_response/incident_management/
 [10]: https://app.datadoghq.com/incidents/settings#Integrations

content/en/coterm/_index.md

@@ -50,7 +50,7 @@ You can review your recorded terminal sessions and process data in Datadog:
 
 [1]: https://app.datadoghq.com/organization-settings/api-keys
 [2]: /security/sensitive_data_scanner/
-[3]: /service_management/case_management/
+[3]: /incident_response/case_management/
 [4]: http://app.datadoghq.com/event/explorer?query=source%3Acoterm_process_info
 [5]: https://app.datadoghq.com/logs?query=service%3Addcoterm
 [6]: https://app.datadoghq.com/terminal-streams

content/en/coterm/rules.md

@@ -126,4 +126,4 @@ All Lua snippets are executed inside a sandboxed [Luau][3] runtime. CoTerm injec
 [3]: https://luau.org/
 [4]: https://www.lua.org/pil/2.5.html
 [5]: https://www.lua.org/pil/2.1.html
-[6]: /service_management/incident_management/
+[6]: /incident_response/incident_management/

content/en/coterm/usage.md

@@ -130,10 +130,10 @@ COTERM_BREAK_GLASS=true kubectl delete foo
 {{< partial name="whats-next/whats-next.html" >}}
 
 [1]: /sensitive_data_scanner/
-[2]: /service_management/events/
-[3]: /service_management/case_management/
+[2]: /events/
+[3]: /incident_response/case_management/
 [4]: /coterm/rules
-[5]: /service_management/incident_management/
+[5]: /incident_response/incident_management/
 [6]: /coterm/install
 [7]: https://app.datadoghq.com/terminal-streams
-[8]: /service_management/case_management/automation_rules/
+[8]: /incident_response/case_management/automation_rules/

content/en/dashboards/_index.md

@@ -45,7 +45,7 @@ Dashboards provide real-time insights into the performance and health of systems
     {{< nextlink href="/dashboards/configure" >}}Configure: Overview of the configuration options for dashboards{{< /nextlink >}}
     {{< nextlink href="/dashboards/list" >}}Dashboard List: Search, view, or create dashboards and lists{{< /nextlink >}}
     {{< nextlink href="/dashboards/template_variables" >}}Template Variable: Dynamically filter widgets in a dashboard{{< /nextlink >}}
-    {{< nextlink href="/service_management/incident_management/datadog_clipboard/" >}}Datadog Clipboard{{< /nextlink >}}
+    {{< nextlink href="/incident_response/incident_management/datadog_clipboard/" >}}Datadog Clipboard{{< /nextlink >}}
     {{< nextlink href="/api/latest/dashboards" >}}API: Manage dashboards programmatically{{< /nextlink >}}
 {{< /whatsnext >}}
 

content/en/dashboards/guide/slo_data_source.md

@@ -2,7 +2,7 @@
 title: Graph historical SLO data on Dashboards
 description: Display historical SLO data on dashboards using SLO widgets and timeseries visualizations for performance tracking.
 further_reading:
-- link: "/service_management/service_level_objectives/"
+- link: "/service_level_objectives/"
   tag: "Documentation"
   text: "Learn more about Service Level Objectives"
 - link: "/dashboards/widgets/slo"
@@ -51,5 +51,5 @@ For SLOs that have [status corrections][2], you can enable or disable correction
 {{< partial name="whats-next/whats-next.html" >}}
 
 [1]: /dashboards/sharing/scheduled_reports/
-[2]: /service_management/service_level_objectives/#slo-status-corrections
-[3]: /service_management/service_level_objectives/#configuration
+[2]: /service_level_objectives/#slo-status-corrections
+[3]: /service_level_objectives/#configuration

content/en/dashboards/guide/slo_graph_query.md

@@ -50,5 +50,5 @@ The SLO widget filters the SLO metric queries by those additional tags for your
 {{< partial name="whats-next/whats-next.html" >}}
 
 [1]: /dashboards/widgets/slo/
-[2]: /service_management/service_level_objectives/metric/
+[2]: /service_level_objectives/metric/
 [3]: /dashboards/template_variables/

content/en/dashboards/widgets/configuration/_index.md

@@ -187,5 +187,5 @@ Click on the context menu (three vertical dots) of any dashboard graph to open a
 [6]: /tracing/services/service_page/
 [7]: /tracing/services/resource_page/
 [8]: /dashboards/guide/custom_time_frames/
-[9]: /service_management/incident_management/datadog_clipboard/
+[9]: /incident_response/incident_management/datadog_clipboard/
 [10]: /dashboards/widgets/split_graph/

content/en/dashboards/widgets/geomap.md

@@ -48,7 +48,7 @@ The geomap widget visualizes geographic data with shaded regions or points. It c
   [4]: /logs/logs_to_metrics/
   [5]: /dashboards/querying/
   [6]: /real_user_monitoring/explorer/search_syntax/
-  [7]: /service_management/service_level_objectives/#searching-slos
+  [7]: /service_level_objectives/#searching-slos
   {{% /tab %}}
 
   {{% tab "Points" %}}

content/en/dashboards/widgets/slo.md

@@ -80,7 +80,7 @@ This widget can be used with the **[Dashboards API][3]**. See the following tabl
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: /service_management/service_level_objectives/
+[1]: /service_level_objectives/
 [2]: /dashboards/template_variables/
 [3]: /api/latest/dashboards/
 [4]: /dashboards/graphing_json/widget_json/

content/en/dashboards/widgets/slo_list.md

@@ -41,6 +41,6 @@ This widget can be used with the **[Dashboards API][2]**. See the following tabl
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: /service_management/service_level_objectives/
+[1]: /service_level_objectives/
 [2]: /api/latest/dashboards/
 [3]: /dashboards/graphing_json/widget_json/

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
@@ -142,5 +142,5 @@ Using commit-level granularity provides a more accurate view of engineering perf
 [12]: /dora_metrics/deployments/#limitations
 [13]: https://www.datadoghq.com/blog/service-catalog-setup/
 [14]: https://app.datadoghq.com/incidents
-[15]: /service_management/incident_management/describe#attributes
+[15]: /incident_response/incident_management/describe#attributes
 [16]: /dora_metrics/

content/en/dora_metrics/setup/failures.md

@@ -56,7 +56,7 @@ If provided with incidents, the `Severity` tag is added to failure events.
 
 You can retroactively include incidents from the past two years by selecting **Backfill Data** in the [DORA settings][202], which creates failures from those incidents. Backfilling data can take up to an hour to complete.
 
-[201]: /service_management/incident_management/
+[201]: /incident_response/incident_management/
 [202]: https://app.datadoghq.com/ci/settings/dora
 [203]: https://app.datadoghq.com/incidents/settings?section=property-fields