Remove UI references to Service Management

Author: estherk15

config/_default/menus/main.en.yaml

@@ -1436,42 +1436,6 @@ menu:
       identifier: cloudcraft_api_users_info
       parent: cloudcraft_api_users
       weight: 1
-    - name: Watchdog
-      url: watchdog/
-      identifier: watchdog_top_level
-      pre: watchdog
-      parent: platform_heading
-      weight: 60000
-    - name: Alerts
-      url: watchdog/alerts
-      identifier: watchdog_alerts
-      parent: watchdog_top_level
-      weight: 1
-    - name: Impact Analysis
-      url: watchdog/impact_analysis/
-      identifier: watchdog_impact_analysis
-      parent: watchdog_top_level
-      weight: 2
-    - name: RCA
-      url: watchdog/rca/
-      identifier: watchdog_rca
-      parent: watchdog_top_level
-      weight: 3
-    - name: Insights
-      identifier: watchdog_insights
-      url: watchdog/insights
-      parent: watchdog_top_level
-      weight: 4
-    - name: Faulty Deployment Detection
-      url: watchdog/faulty_deployment_detection/
-      identifier: watchdog_faulty_deployment_detection
-      parent: watchdog_top_level
-      weight: 5
-    - name: Faulty Cloud & SaaS API Detection
-      url: watchdog/faulty_cloud_saas_api_detection
-      parent: watchdog_top_level
-      weight: 6
-      identifier: watchdog_faulty_cloud_saas_api_detection
     - name: Bits AI
       url: bits_ai/
       pre: bits-ai
@@ -2121,6 +2085,42 @@ menu:
       parent: metrics_top_level
       identifier: metrics_guide
       weight: 14
+    - name: Watchdog
+      url: watchdog/
+      identifier: watchdog_top_level
+      pre: watchdog
+      parent: platform_heading
+      weight: 90000
+    - name: Alerts
+      url: watchdog/alerts
+      identifier: watchdog_alerts
+      parent: watchdog_top_level
+      weight: 1
+    - name: Impact Analysis
+      url: watchdog/impact_analysis/
+      identifier: watchdog_impact_analysis
+      parent: watchdog_top_level
+      weight: 2
+    - name: RCA
+      url: watchdog/rca/
+      identifier: watchdog_rca
+      parent: watchdog_top_level
+      weight: 3
+    - name: Insights
+      identifier: watchdog_insights
+      url: watchdog/insights
+      parent: watchdog_top_level
+      weight: 4
+    - name: Faulty Deployment Detection
+      url: watchdog/faulty_deployment_detection/
+      identifier: watchdog_faulty_deployment_detection
+      parent: watchdog_top_level
+      weight: 5
+    - name: Faulty Cloud & SaaS API Detection
+      url: watchdog/faulty_cloud_saas_api_detection
+      parent: watchdog_top_level
+      weight: 6
+      identifier: watchdog_faulty_cloud_saas_api_detection
     - name: Internal Developer Portal
       url: internal_developer_portal/
       pre: internal-developer-portal-wui

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
 

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/events/triage_inbox.md

@@ -26,7 +26,7 @@ Case triage and investigation begins in the Triage Inbox, where you can sort, fi
 
 ## Getting Started
 
-1. Navigate to [**Service Management** > **Event Management** > **Triage Inbox**][4].
+1. Navigate to [**Event Management** > **Triage Inbox**][4].
 2. Select a project from the left-hand panel to display out-of-the-box status views such as **Open**, **In Progress**, **Closed**, and **Archived**.
 3. Use the display settings icon to choose between **split view** (for detailed case investigation) or **table view** (for bulk case review and column configuration). Customize your inbox ranking with the **Sort By** dropdown-options include **Priority**, **Created at**, or **Last Updated**. Click **Save** to re-use your customized inbox for future use.
 5. Update the status, priority, and assignment directly on case cards during triage.

content/en/incident_response/incident_management/analytics.md

@@ -64,7 +64,7 @@ To address this, organizations can enable **timestamp overrides**, which allow i
 
 Overrides only influence search and analytics. They do not change the history automatically recorded to the incident timeline. They do not apply to the analytic measures `Status Active Duration` or `Status Stable Duration`, which are driven by the cumulative length of status segments on incident timelines.
 
-To enable timestamp overrides, go to [**Service Management** > **Incidents** > **Settings** > **Information**][11].
+To enable timestamp overrides, go to [**Incidents** > **Settings** > **Information**][11].
 
 To create, update, or delete timestamp overrides, users must have the **Incidents Write** permission.
 

content/en/incident_response/incident_management/integrations/slack/_index.md

@@ -37,7 +37,7 @@ The Slack integration documentation is organized around the typical lifecycle of
 
 Install the integration through the [Slack Integration tile][1] with the proper [OAuth scopes][6]. For more information, see the [Slack integration][2] documentation.
 
-After the integration is installed, navigate to [**Service Management** > **Incidents** > **Settings** > **Integrations**][3] to enable Slack capabilities for Incident Management.
+After the integration is installed, navigate to [**Incidents** > **Settings** > **Integrations**][3] to enable Slack capabilities for Incident Management.
 
 ## Declaring incidents from Slack
 
@@ -201,5 +201,5 @@ You can view the full list of available Slack commands at any time by typing `/d
 [2]: /integrations/slack/?tab=datadogforslack
 [3]: https://app.datadoghq.com/incidents/settings#Integrations
 [4]: /integrations/jira/
-[5]: /service_management/incident_management/incident_settings/notification_rules/
+[5]: /incident_response/incident_management/incident_settings/notification_rules/
 [6]: /integrations/slack/?tab=datadogforslack#permissions

content/en/incident_response/incident_management/zoom_integration.md

@@ -16,7 +16,7 @@ By connecting Zoom and Datadog, you can quickly create Zoom meetings to collabor
 
 To install the Datadog for Zoom app:
 
-1. In Datadog, find the Incidents Settings page under **Service Management**.
+1. In Datadog, find the [**Incidents Settings**][3] page.
 2. Go to **Integrations** and enable the **Automatically create a meeting in Zoom for every incident** toggle. This setting replaces the **Add Video Call** button with a **Start Zoom Call** button for one-click Zoom meeting creation from Datadog's incident overview page.
 3. When you click the **Start Zoom Call** button, you are prompted to add the Datadog Zoom App. Be sure to allow it to view and manage information on Zoom's behalf.
 
@@ -48,3 +48,4 @@ Need help? Contact [Datadog support][1].
 
 [1]: /help/
 [2]: https://developers.zoom.us/docs/integrations/oauth-scopes/
+[3]: https://app.datadoghq.com/incidents/settings

content/en/incident_response/status_pages/_index.md

@@ -67,7 +67,7 @@ To create, update, or publish Status Pages, you must have `status_pages_settings
 
 ## Create a status page
 
-1. In Datadog, navigate to [**Service Management > Status Pages**][2].
+1. In Datadog, navigate to [**Status Pages**][2].
 1. Click **Create Status Page** and follow the onboarding flow:
 
    | Field             | Description |

content/en/internal_developer_portal/software_catalog/set_up/ownership.md

@@ -35,7 +35,7 @@ After creating a Team, you can add reference links, configure notifications, and
 
 To add or update an entity's owner in Datadog:
 
-1. Go to **Service Management** > **Software Catalog**, and open the entity.
+1. Go to **Software Catalog**, and open the entity.
 2. Click **Edit in UI** on the entity page.
 3. In the **Ownership** section, set the **Owner** and optionally add **Additional owners**.
    - Search by team name or paste a handle (for example, `team:example-team`).

content/en/service_level_objectives/time_slice.md

@@ -33,7 +33,7 @@ You can create a Time Slice SLO through the following ways:
 
 {{< img src="service_management/service_level_objectives/time_slice/time-slice-creation.png" alt="Configuration options to create a Time Slice SLO" style="width:90%;" >}}
 
-1. Navigate to [**Service Management > SLOs**][1].
+1. Navigate to [**SLOs**][1].
 2. Click **+ New SLO** to open up the Create SLO page.
 3. Select **By Time Slices** to define your SLO measurement. 
 4. Define your uptime condition by choosing a metric query, comparator and threshold. For example, to define uptime as whenever p95 latency is less than 1s. Alternatively, you can [import the uptime from a monitor](#import-from-a-monitor).