API Catalog -> Service Catalog Migration

config/_default/menus/main.en.yaml

@@ -1947,7 +1947,7 @@ menu:
       parent: service_catalog
       identifier: software_templates
       weight: 7
-    - name: APIs
+    - name: Definition APIs
       url: service_catalog/apis
       parent: service_catalog
       identifier: service_catalog_apis
@@ -1962,52 +1962,6 @@ menu:
       parent: service_catalog
       identifier: service_catalog_troubleshooting
       weight: 10
-    - name: API Catalog
-      url: /api_catalog/
-      pre: api-catalog
-      parent: platform_heading
-      identifier: api_catalog
-      weight: 120000
-    - name: Exploring APIs
-      url: /api_catalog/explore_apis/
-      identifier: api_catalog_explore
-      parent: api_catalog
-      weight: 1
-    - name: Assigning Owners
-      url: /api_catalog/owners_and_tags/
-      identifier: api_catalog_ownership
-      parent: api_catalog
-      weight: 2
-    - name: Monitoring APIs
-      url: /api_catalog/monitor_apis/
-      identifier: api_catalog_monitor
-      parent: api_catalog
-      weight: 3
-    - name: Adding Entries to API Catalog
-      url: /api_catalog/add_entries/
-      identifier: api_catalog_entries
-      parent: api_catalog
-      weight: 4
-    - name: Adding Metadata to APIs
-      url: /api_catalog/add_metadata/
-      identifier: api_catalog_metadata
-      parent: api_catalog
-      weight: 5
-    - name: API Catalog API
-      url: /api_catalog/api_catalog_api/
-      identifier: api_catalog_api
-      parent: api_catalog
-      weight: 6
-    - name: Endpoint Discovery from APM
-      url: /api_catalog/endpoint_discovery/
-      identifier: endpoint_discovery
-      parent: api_catalog
-      weight: 7
-    - name: Troubleshooting
-      url: /api_catalog/troubleshoot/
-      identifier: api_catalog_troubleshoot
-      parent: api_catalog
-      weight: 8
     - name: Error Tracking
       url: error_tracking/
       pre: error-tracking
@@ -3517,11 +3471,21 @@ menu:
       parent: tracing_services
       identifier: tracing_apm_monitors
       weight: 707
-    - name: API Catalog
-      url: /tracing/api_catalog/
-      identifier: api_catalog
+    - name: Endpoint Observability
+      url: /service_catalog/endpoints/
+      identifier: endpoint_observability
       parent: tracing
       weight: 8
+    - name: Explore Endpoints
+      url: /service_catalog/endpoints/explore_endpoints
+      identifier: explore_endpoints
+      parent: endpoint_observability
+      weight: 802
+    - name: Monitor Endpoints
+      url: /service_catalog/endpoints/monitor_endpoints
+      identifier: monitor_endpoints
+      parent: endpoint_observability
+      weight: 803
     - name: Dynamic Instrumentation
       url: dynamic_instrumentation/
       identifier: dyninst

content/en/administrators_guide/plan.md

@@ -215,7 +215,7 @@ Web servers are almost always inter-connected with other services through a netw
 
 ## Platform services
 
-Datadog infrastructure monitoring comes with  additional products that you can use to maximize observability of your environments.
+Datadog infrastructure monitoring comes with additional products that you can use to maximize observability of your environments.
 
 ### Service Catalog
 
@@ -225,7 +225,9 @@ Service Catalog also helps you evaluate the coverage of your observability setup
 
 {{< img src="/administrators_guide/service_catalog_2.png" alt="Service Catalog home screen" style="width:90%;">}}
 
-You can add components that you aren't planning on monitoring immediately, such as cron jobs or libraries, to create a comprehensive view of your system, and to mark team members who are responsible for these components ahead of the next phase of your Datadog rollout.  
+You can add components that you aren't planning on monitoring immediately, such as cron jobs or libraries, to create a comprehensive view of your system, and to mark team members who are responsible for these components ahead of the next phase of your Datadog rollout.
+
+Use the [API list][33] for resource endpoint-specific categorization, performance, reliability, and ownership of all your API endpoints in one place.
 
 ### Resource Catalog
 
@@ -238,10 +240,6 @@ You can use Resource Catalog in a variety of contexts, including:
 - Accessing configuration information and other metadata to speed up incident response.
 - Maintaining your security posture by finding and resolving misconfigurations and vulnerabilities.
 
-### API Catalog 
-
-Use [API Catalog][33] for resource endpoint-specific categorization, performance, reliability, and ownership of all your API endpoints in one place.
-
 ### Event Management 
 
 Without any additional setup, [Event management][31] can show third-party event statuses, events generated from the Agent and installed integrations. Datadog Event Management centralizes third-party events, such as alerts and change events. Datadog also automatically creates events from various products including monitors and Error Tracking. You can also use Event Management to send monitor alerts and notifications based on event queries.
@@ -348,7 +346,7 @@ Create a detailed roll-out methodology in the [build][41] phase by focusing on t
 [30]: /service_catalog/
 [31]: /service_management/events/
 [32]: /error_tracking/
-[33]: /api_catalog/
+[33]: /service_catalog/endpoints/
 [34]: /agent/fleet_automation/
 [35]: /agent/remote_config/
 [36]: /agent/remote_config/?tab=configurationyamlfile\#supported-products-and-feature-capabilities