[DOCS-7217/7054] Add OP landing and setup docs

config/_default/menus/menus.en.yaml

@@ -3352,6 +3352,136 @@ main:
     identifier: observability_pipelines
     parent: log_management_heading
     weight: 10000
+  - name: Log Volume Control
+    url: observability_pipelines/log_volume_control/
+    parent: observability_pipelines
+    identifier: observability_pipelines_log_volume_control
+    weight: 1
+  - name: Splunk HTTP Event Collector
+    url: observability_pipelines/log_volume_control/splunk_hec/
+    parent: observability_pipelines_log_volume_control
+    identifier: observability_pipelines_log_volume_control_splunk_hec
+    weight: 1001
+  - name: Splunk Forwarders (TCP)
+    url: observability_pipelines/log_volume_control/splunk_tcp/
+    parent: observability_pipelines_log_volume_control
+    identifier: observability_pipelines_log_volume_control_splunk_tcp
+    weight: 1002
+  - name: Sumo Logic Hosted Collector
+    url: observability_pipelines/log_volume_control/sumo_logic_hosted_collector/
+    parent: observability_pipelines_log_volume_control
+    identifier: observability_pipelines_log_volume_control_sumo_logic_hosted_collector
+    weight: 1003
+  - name: Dual Ship Logs
+    url: observability_pipelines/dual_ship_logs/
+    parent: observability_pipelines
+    identifier: observability_pipelines_dual_ship_logs
+    weight: 2
+  - name: Datadog Agent
+    url: observability_pipelines/dual_ship_logs/datadog_agent/
+    parent: observability_pipelines_dual_ship_logs
+    identifier: observability_pipelines_dual_ship_logs_datadog_agent
+    weight: 2001
+  - name: Splunk HTTP Event Collector
+    url: observability_pipelines/dual_ship_logs/splunk_hec/
+    parent: observability_pipelines_dual_ship_logs
+    identifier: observability_pipelines_dual_ship_logs_splunk_hec
+    weight: 2002
+  - name: Splunk Forwarders (TCP)
+    url: observability_pipelines/dual_ship_logs/splunk_tcp/
+    parent: observability_pipelines_dual_ship_logs
+    identifier: observability_pipelines_dual_ship_logs_splunk_tcp
+    weight: 2003
+  - name: Sumo Logic Hosted Collector
+    url: observability_pipelines/dual_ship_logs/sumo_logic_hosted_collector/
+    parent: observability_pipelines_dual_ship_logs
+    identifier: observability_pipelines_dual_ship_logs_sumo_logic_hosted_collector
+    weight: 2004
+  - name: Archive Logs
+    url: observability_pipelines/archive_logs/
+    parent: observability_pipelines
+    identifier: observability_pipelines_archive_logs
+    weight: 3
+  - name: Datadog Agent
+    url: observability_pipelines/archive_logs/datadog_agent/
+    parent: observability_pipelines_archive_logs
+    identifier: observability_pipelines_archive_logs_datadog_agent
+    weight: 3001
+  - name: Splunk HTTP Event Collector
+    url: observability_pipelines/archive_logs/splunk_hec/
+    parent: observability_pipelines_archive_logs
+    identifier: observability_pipelines_archive_logs_splunk_hec
+    weight: 3002
+  - name: Splunk Forwarders (TCP)
+    url: observability_pipelines/archive_logs/splunk_tcp/
+    parent: observability_pipelines_archive_logs
+    identifier: observability_pipelines_archive_logs_splunk_tcp
+    weight: 3003
+  - name: Sumo Logic Hosted Collector
+    url: observability_pipelines/archive_logs/sumo_logic_hosted_collector/
+    parent: observability_pipelines_archive_logs
+    identifier: observability_pipelines_archive_logs_sumo_logic_hosted_collector
+    weight: 3004
+  - name: Split Logs
+    url: observability_pipelines/split_logs/
+    parent: observability_pipelines
+    identifier: observability_pipelines_split_logs
+    weight: 4
+  - name: Datadog Agent
+    url: observability_pipelines/split_logs/datadog_agent/
+    parent: observability_pipelines_split_logs
+    identifier: observability_pipelines_split_logs_datadog_agent
+    weight: 4001
+  - name: Splunk HTTP Event Collector
+    url: observability_pipelines/split_logs/splunk_hec/
+    parent: observability_pipelines_split_logs
+    identifier: observability_pipelines_split_logs_splunk_hec
+    weight: 4002
+  - name: Splunk Forwarders (TCP)
+    url: observability_pipelines/split_logs/splunk_tcp/
+    parent: observability_pipelines_split_logs
+    identifier: observability_pipelines_split_logs_splunk_tcp
+    weight: 4003
+  - name: Sumo Logic Hosted Collector
+    url: observability_pipelines/split_logs/sumo_logic_hosted_collector/
+    parent: observability_pipelines_split_logs
+    identifier: observability_pipelines_split_logs_sumo_logic_hosted_collector
+    weight: 4004
+  - name: Sensitive Data Redaction
+    url: observability_pipelines/sensitive_data_redaction/
+    parent: observability_pipelines
+    identifier: observability_pipelines_sensitive_data_redaction
+    weight: 5
+  - name: Datadog Agent
+    url: observability_pipelines/sensitive_data_redaction/datadog_agent/
+    parent: observability_pipelines_sensitive_data_redaction
+    identifier: observability_pipelines_sensitive_data_redaction_datadog_agent
+    weight: 5001
+  - name: Splunk HTTP Event Collector
+    url: observability_pipelines/sensitive_data_redaction/splunk_hec/
+    parent: observability_pipelines_sensitive_data_redaction
+    identifier: observability_pipelines_sensitive_data_redaction_splunk_hec
+    weight: 5002
+  - name: Splunk Forwarders (TCP)
+    url: observability_pipelines/sensitive_data_redaction/splunk_tcp/
+    parent: observability_pipelines_sensitive_data_redaction
+    identifier: observability_pipelines_sensitive_data_redaction_splunk_tcp
+    weight: 5003
+  - name: Sumo Logic Hosted Collector
+    url: observability_pipelines/sensitive_data_redaction/sumo_logic_hosted_collector/
+    parent: observability_pipelines_sensitive_data_redaction
+    identifier: observability_pipelines_sensitive_data_redaction_sumo_logic_hosted_collector
+    weight: 5004
+  - name: Configure Existing Pipelines
+    url: observability_pipelines/configure_existing_pipelines/
+    parent: observability_pipelines
+    identifier: observability_pipelines_configure_existing_pipelines
+    weight: 6
+  - name: Architecture
+    url: observability_pipelines/architecture/
+    parent: observability_pipelines
+    identifier: observability_pipelines_architecture
+    weight: 7
   - name: Log Management
     url: logs/
     pre: log

content/en/agent/remote_config/_index.md

@@ -77,7 +77,7 @@ The following products and features are supported with Remote Configuration:
 - **Automatic deployment of custom Agent rules**: Automatically deploy your custom Agent rules to designated hosts (all hosts or a defined subset of hosts).
 
 ### Observability Pipelines
-<div class="alert alert-info">This feature is in private beta.</div>
+<div class="alert alert-info">This feature is in public beta.</div>
 
 - **Remotely deploy and update [Observability Pipelines Workers][4] (OPW)**: Build and edit pipelines in the Datadog UI, rolling out your configuration changes to OPW instances running in your environment.
 

content/en/observability_pipelines/_index.md

@@ -0,0 +1,52 @@
+---
+title: Observability Pipelines
+kind: documentation
+disable_toc: false
+---
+
+{{< site-region region="gov" >}}
+<div class="alert alert-warning">Observability Pipelines is not available on the US1-FED Datadog site.</div>
+{{< /site-region >}}
+
+<div class="alert alert-info">
+Datadog recommends you update Observability Pipelines Worker (OPW) with every minor and patch release, or, at a minimum, monthly. <br><br> Upgrading to a major OPW version and keeping it updated is the only supported way to get the latest OPW functionality, fixes, and security updates.
+</div>
+
+## Overview
+
+Observability Pipelines allows you to collect, process, and route logs in your own infrastructure. It comes with out-of-the-box templates so that you can easily build and deploy pipelines. The templates are purpose-built for the following use cases:
+
+- Log volume control: Cut down on your log volume before it leaves your infrastructure or network.
+- Dual ship logs: Send copies of your logs to multiple destinations.
+- Split logs: Send your logs to different destinations based on your use case. For example, you can send DevOps logs to Datadog and security logs to a security vendor.
+- Archive logs: Send logs to a log vendor and to an archive in Datadog rehydratable format.
+- Sensitive data redaction: Redact sensitive data in your logs before they are routed outside of your infrastructure.
+
+The Observability Pipelines Worker is the software that runs in your infrastructure. It aggregates and centrally processes and routes your logs based on the selected use case.
+
+The Datadog UI provides a control plane to manage your Observability Pipelines Workers. You can build and edit pipelines, deploy pipeline changes to your Workers, and monitor your pipelines to evaluate the health of your pipelines.
+
+The following sources are available:
+
+- Datadog Agent
+- Splunk HTTP Event Collector (HEC)
+- Splunk Heavy and Universal Forwarders (TCP)
+- Sumo Logic Hosted Collector
+
+## Get started
+
+1. Navigate to [Observability Pipelines][1].
+1. Select a use case:
+    - [Log volume control][2]
+    - [Dual ship logs][3]
+    - [Split logs][4]
+    - [Archive logs to Datadog Archives][5]
+    - [Sensitive data redaction][6]
+1. Enable monitors.
+
+[1]: https://app.datadoghq.com/observability-pipelines
+[2]: /observability_pipelines/log_volume_control/
+[3]: /observability_pipelines/dual_ship_logs/
+[4]: /observability_pipelines/split_logs/
+[5]: /observability_pipelines/archive_logs/
+[6]: /observability_pipelines/sensitive_data_redaction/