Create new IA for observability docs (#4134)

* Create new IA for observability docs

* Try making the nav titles shorter

* Align TOC with latest outline

* Fix link text and rename analyze-metrics file

* Add redirect page for observability tutorials

* Add content to start here topic

* Add content to overview topic about monitoring applications and services

* Add content to overview topic about incident management

* Remove old tutorial container topic

* Apply changes from colleenmcginnis

* Apply feedback from alaudazzi

* More K8s tutorial to infra/hosts monitoring section

* Add getting started change and other changes requested by obs docs

* Fix broken apm links

* Apply more link fixes

* Reorganize getting started/quick start section

* Resolve or remove related TODOs

* Update docs/en/observability/splunk-get-started.asciidoc

* Make changes to getting started section

* Move universal profiling to section about infra monitoring

* Move troubleshooting up a level in the nav

* Delete old APM tutorial

* Fix jump tables

Author: dedemorton

docs/en/apm-server/redirects.asciidoc

@@ -428,7 +428,7 @@ Refer to {observability-guide}/apm.html[Application Performance Monitoring (APM)
 
 {move-notice}
 
-Refer to {observability-guide}/traces-get-started.html[Quick start with Elastic Cloud].
+Refer to {observability-guide}/get-started-with-fleet-apm-server.html[Quick start with Elastic Cloud].
 
 [role="exclude",id="getting-started-apm-server"]
 === Self manage APM Server
@@ -491,7 +491,7 @@ Refer to {observability-guide}/apm-running-on-docker.html[Run APM Server on Dock
 
 {move-notice}
 
-Refer to {observability-guide}/_fleet_managed_apm_server.html[Fleet-managed APM Server].
+Refer to {observability-guide}/get-started-with-fleet-apm-server.html[Fleet-managed APM Server].
 
 [role="exclude",id="_step_1_set_up_fleet"]
 === Step 1: Set up Fleet
@@ -505,7 +505,7 @@ Refer to {observability-guide}/_step_1_set_up_fleet.html[Step 1: Set up Fleet].
 
 {move-notice}
 
-Refer to {observability-guide}/_step_2_add_and_configure_the_apm_integration.html[Step 2: Add and configure the APM integration].
+Refer to {observability-guide}/add-apm-integration.html[Step 2: Add and configure the APM integration].
 
 [role="exclude",id="_step_3_install_apm_agents"]
 === Step 3: Install APM agents

docs/en/observability/apm-ui/new-experience-services.asciidoc

@@ -47,5 +47,5 @@ which means that other users need to turn on the new experience if they want to
 To add services to the inventory, use one of the following approaches:
 
 * Instrument your services with APM or OpenTelemetry.
-To learn how, refer to <<traces-get-started>>.
+To learn how, refer to <<get-started-with-fleet-apm-server>>.
 * Declare `service.name` in your logs. To learn how, <<add-logs-service-name>>.

docs/en/observability/apm.asciidoc

@@ -43,7 +43,7 @@ like JVM metrics in the Java Agent, and Go runtime metrics in the Go Agent.
 [float]
 === Give Elastic APM a try
 
-Use <<traces-get-started,Get started with application traces and APM>> to quickly spin up an APM deployment.
+Use <<get-started-with-fleet-apm-server,Get started with application traces and APM>> to quickly spin up an APM deployment.
 Want to host everything yourself instead? See <<apm-getting-started-apm-server>>.
 
 include::{observability-docs-root}/docs/en/observability/apm/getting-started-apm-server.asciidoc[]

docs/en/observability/apm/apm-quick-start.asciidoc

@@ -1,6 +1,8 @@
 [[apm-quick-start]]
 == Quick start with {ecloud}
 
+TODO: Ask Colleen if this file should be deleted.
+
 The easiest way to get started with Elastic APM is by using our
 {ess-product}[hosted {es} Service] on {ecloud}.
 The {es} Service is available on AWS, GCP, and Azure.

docs/en/observability/apm/getting-started-apm-server.asciidoc

@@ -8,7 +8,7 @@
 TIP: The easiest way to get started with Elastic APM is by using our
 {ess-product}[hosted {es} Service] on {ecloud}.
 The {es} Service is available on AWS, GCP, and Azure.
-See <<traces-get-started,getting started documentation>> to get started in minutes.
+See <<get-started-with-fleet-apm-server,getting started documentation>> to get started in minutes.
 
 
 // TODO: MOVE THIS
@@ -475,7 +475,7 @@ include::{observability-docs-root}/docs/en/observability/apm/repositories.asciid
 // Shared docker
 include::{observability-docs-root}/docs/en/observability/apm/shared-docker.asciidoc[]
 
-
+[[get-started-with-fleet-apm-server]]
 === Fleet-managed APM Server
 
 This guide will explain how to set up and configure a Fleet-managed APM Server.
@@ -498,6 +498,7 @@ include::{ingest-docs-root}/docs/en/ingest-management/tab-widgets/add-fleet-serv
 
 For more information, refer to {fleet-guide}/fleet-server.html[{fleet-server}].
 
+[[add-apm-integration]]
 ==== Step 2: Add and configure the APM integration
 
 include::{observability-docs-root}/docs/en/observability/tab-widgets/add-apm-integration/content.asciidoc[tag=self-managed]

docs/en/observability/apm/setting-up-and-running.asciidoc

@@ -6,7 +6,7 @@
 <titleabbrev>Advanced setup</titleabbrev>
 ++++
 
-Before reading this section, see the <<traces-get-started,getting started documentation>>
+Before reading this section, see the <<get-started-with-fleet-apm-server,getting started documentation>>
 for basic installation and running instructions.
 
 This section includes additional information on how to set up and run APM Server, including:

docs/en/observability/application-and-service-monitoring.asciidoc

@@ -0,0 +1,27 @@
+[[application-and-service-monitoring]]
+= Application and service monitoring
+
+++++
+<titleabbrev>Applications and services</titleabbrev>
+++++
+
+Explore the topics in this section to learn how to observe and monitor software applications and services running in your environment.
+
+[cols="1,1"]
+|===
+|<<apm>>
+|Monitor software services and applications in real time, by collecting detailed performance information on response time for incoming requests, database queries, calls to caches, external HTTP requests, and more.
+
+|<<monitor-uptime-synthetics>>
+|Monitor the availability of network endpoints and services.
+
+|<<user-experience>>
+|Quantify and analyze the perceived performance of your web application using real-world user experiences.
+
+|<<uptime-intro>>
+|Periodically check the status of your services and applications.
+
+|<<monitor-java-app>>
+|Monitor a Java application using Elastic Observability: Logs, Infrastructure metrics, APM, and Uptime.
+
+|===

docs/en/observability/ci-cd-observability.asciidoc

@@ -1,7 +1,11 @@
 [[ci-cd-observability]]
-= CI/CD observability
+= Continuous Integration and Continuous Delivery (CI/CD) monitoring
 :figure-caption!:
 
+++++
+<titleabbrev>CI/CD</titleabbrev>
+++++
+
 To help administrators monitor and troubleshoot their CI/CD platform and help developers
 increase the speed and reliability of their CI/CD pipelines, Elastic {observability}
 provides visibility in Continuous Integration and Continuous Delivery (CI/CD) processes.

docs/en/observability/cloud-monitoring.asciidoc

@@ -0,0 +1,23 @@
+[[cloud-monitoring]]
+= Cloud monitoring
+
+++++
+<titleabbrev>Cloud</titleabbrev>
+++++
+
+Explore the topics in this section to learn how to observe and monitor a broad range of resources and applications running in your cloud ecosystem.
+
+[cols="1,1"]
+|===
+|<<monitor-amazon-web-services>>
+|Monitor AWS services and resources, including EC2, Kinesis data streams, S3 buckets, SQS, VPC Flow Logs, CloudTrail logs, network firewall logs, WAF logs, and CloudWatch logs.
+
+|<<monitor-azure-web-services>>
+|Get visibility into your key Azure services including through secure native integration within the Azure console.
+
+|<<monitor-gcp>>
+|Track performance of your Google Cloud services, including through agentless data ingestion with Google Pub/Sub.
+|===
+
+
+

docs/en/observability/cloud-monitoring/aws/monitor-amazon-ec2.asciidoc

@@ -2,7 +2,7 @@
 = Monitor Amazon Cloud Compute (EC2)
 
 ++++
-<titleabbrev>Monitor EC2</titleabbrev>
+<titleabbrev>EC2</titleabbrev>
 ++++
 
 https://aws.amazon.com/ec2[Elastic Compute Cloud (Amazon EC2)] enables
@@ -115,7 +115,7 @@ workloads.
 A burstable performance instance configured as unlimited can sustain high CPU
 utilization for any period of time whenever required. T4g, T3a, and T3 instances
 launch as unlimited by default. If the average CPU usage over a 24-hour period
-exceeds the baseline, you incur charges for surplus credits. 
+exceeds the baseline, you incur charges for surplus credits.
 +
 The CPU surplus credit balance metric tracks the accumulated balance. The CPU
 surplus credit charged measures extra credits that will result in additional
@@ -227,7 +227,7 @@ of related EC2 instances.
 +
 The Elastic EC2 integration comes with a default dashboard that shows key
 metrics like status check, CPU utilization, Disk I/O, and network throughput. It
-also provides filtering for region, availability zone, and machine type. 
+also provides filtering for region, availability zone, and machine type.
 
 `aws.ec2.metrics.StatusCheckFailed_Instance.avg`::
 This check monitors the software and network configuration of the instance.
@@ -236,7 +236,7 @@ networking or startup configuration, exhausted memory, corrupted file system,
 incompatible kernel, and so on. When an instance status check fails, you
 typically must address the problem yourself. You may need to reboot the instance
 or make instance configuration changes. To troubleshoot instances with failed
-status checks, refer to the 
+status checks, refer to the
 https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html[Amazon EC2 documentation].
 +
 This check returns 0 (passed) if an instance passes the system status check or 1