Update DD receiver doc (#1071)

docs/sources/tasks/configure-alloy-to-use-datadog-receiver.md

@@ -2,26 +2,26 @@
 canonical: https://grafana.com/docs/alloy/latest/tasks/configure-alloy-datadog-receiver/
 description: Learn how to configure Grafana Alloy to use the Datadog receiver
 menuTitle: Configure Alloy with the Datadog Receiver
-title: Configure Grafana Alloy with the Datadog Receiver
+title: Receive traces and metrics from Datadog-instrumented applications
 weight: 550
 ---
 
 # Receive traces and metrics from Datadog-instrumented applications
 
-You can configure {{< param "PRODUCT_NAME" >}} to collect [Datadog][] metrics and forward them to any OpenTelemetry-compatible database.
+You can configure {{< param "PRODUCT_NAME" >}} to collect [Datadog][] traces and metrics and forward them to any OpenTelemetry-compatible database.
 
 This topic describes how to:
 
 * Configure metrics and traces delivery.
-* Configure Alloy's Datadog Receiver.
-* Configure the Datadog Agent to forward metrics to Alloy's Datadog Receiver.
+* Configure the {{< param "PRODUCT_NAME" >}} Datadog Receiver.
+* Configure the Datadog Agent to forward metrics to the {{< param "PRODUCT_NAME" >}} Datadog Receiver.
 
 ## Before you begin
 
-* Ensure that you have at least one instance of the [Datadog Agent]() collecting metrics and/or traces.
+* Ensure that at least one instance of the [Datadog Agent][] is collecting metrics and/or traces.
 * Identify where you will write collected metrics.
   Metrics can be written to [Prometheus]() or any other OTel-compatible database such as Grafana Mimir, Grafana Cloud, or Grafana Enterprise Metrics.
-  Traces can be writtten to Grafana Tempo, Grafana Cloud, or Grafana Enterprise Traces.
+  Traces can be written to Grafana Tempo, Grafana Cloud, or Grafana Enterprise Traces.
 * Be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
 
 ## Configure metrics delivery
@@ -43,7 +43,7 @@ The [otelcol.exporter.otlp][] component is responsible for delivering OTLP data
 
    Replace the following:
 
-    - _`<OTLP_ENDPOINT_URL>`_ The full URL of the OTel-compatible endpoint where metrics and traces will be sent, such as `https://otlp-gateway-prod-eu-west-2.grafana.net/otlp`.
+    - _`<OTLP_ENDPOINT_URL>`_: The full URL of the OTel-compatible endpoint where metrics and traces will be sent, such as `https://otlp-gateway-prod-eu-west-2.grafana.net/otlp`.
 
 1. If your endpoint requires basic authentication, paste the following inside the `endpoint` block.
 
@@ -61,38 +61,48 @@ The [otelcol.exporter.otlp][] component is responsible for delivering OTLP data
 
 ## Configure Datadog Receiver
 
+1. Add the following `otelcol.processor.batch` component to your configuration file.
+
+   ```alloy
+   otelcol.processor.batch “example” {
+     output {
+       metrics = [otelcol.exporter.otlp.default.input]
+     }
+   }
+   ```
+
 1. Add the following `otelcol.processor.deltatocumulative` component to your configuration file.
 
    ```alloy
    otelcol.processor.deltatocumulative “example” {
      max_stale = “<MAX_STALE>”
      max_streams = <MAX_STREAMS>
      output {
-       metrics = [otelcol.exporter.otlp.default.input]
+       metrics = [otelcol.processor.batch.default.input]
      }
    }
    ```
 
    Replace the following:
 
-        - _`<MAX_STALE>`_ How long until a series not receiving new samples is removed, such as "5m".
-        - _`<MAX_STREAMS>`_ The upper limit of streams to track. new streams exceeding this limit will be dropped. For example 10000.
+    - _`<MAX_STALE>`_: How long until a series not receiving new samples is removed, such as "5m".
+    - _`<MAX_STREAMS>`_: The upper limit of streams to track. New streams exceeding this limit are dropped.
 
 1. Add the following `otelcol.receiver.datadog` component to your configuration file.
 
    ```alloy
    otelcol.receiver.datadog “example” {
      endpoint = “<HOST>:<PORT>”
      output {
-       metrics = [otelcol.processor.batch.example.input]
+       metrics = [otelcol.processor.deltatocumulative.example.input]
      }
    }
    ```
 
-   Replace the following:
+    Replace the following:
 
-        - _`<HOST>`_ The host address where the receiver will listen, such as localhost.
-        - _`<PORT>`_ The port where the receiver will listen, such as 4444.
+    - _`<HOST>`_: The host address where the receiver will listen.
+    - _`<PORT>`_: The port where the receiver will listen.
 
 1. If your endpoint requires basic authentication, paste the following inside the `endpoint` block.
 
@@ -103,16 +113,16 @@ The [otelcol.exporter.otlp][] component is responsible for delivering OTLP data
    }
    ```
 
-   Replace the following:
+    Replace the following:
 
     - _`<USERNAME>`_: The basic authentication username.
     - _`<PASSWORD>`_: The basic authentication password or API key.
 
 ## Configure Datadog Agent to forward metrics to the Datadog Receiver
 
-You can set up your Datadog Agent to forward Datadog metrics simultaneously to Alloy and Datadog.
+You can set up your Datadog Agent to forward Datadog metrics simultaneously to {{< param "PRODUCT_NAME" >}} and Datadog.
 
-We recommend this approach for current Datadog users who want to try using Alloy.
+We recommend this approach for current Datadog users who want to try using {{< param "PRODUCT_NAME" >}}.
 
 1. Add the following environment variable to your datadog-agent installation.
 
@@ -122,28 +132,27 @@ We recommend this approach for current Datadog users who want to try using Alloy
 
    Replace the following:
 
-    - _`<DATADOG_RECEIVER_HOST>`_: The hostname where Alloy's receiver can be found.
-    - _`<DATADOG_RECEIVER_PORT>`_: The port where Alloy's receiver is exposed.
+    - _`<DATADOG_RECEIVER_HOST>`_: The hostname where the {{< param "PRODUCT_NAME" >}} receiver is found.
+    - _`<DATADOG_RECEIVER_PORT>`_: The port where the {{< param "PRODUCT_NAME" >}} receiver is exposed.
 
-Alternatively, you might want your Datadog Agent to send metrics only to Alloy,
+Alternatively, you might want your Datadog Agent to send metrics only to {{< param "PRODUCT_NAME" >}}. 
 You can do this by setting up your Datadog Agent in the following way:
 
-1. Replace the DD_URL in the configuration yaml:
+1. Replace the DD_URL in the configuration YAML:
 
    ```yaml
     dd_url: http://<DATADOG_RECEIVER_HOST>:<DATADOG_RECEIVER_PORT>
    ```
-
 Or by setting an environment variable:
 
 
    ```bash
    DD_DD_URL='{"http://<DATADOG_RECEIVER_HOST>:<DATADOG_RECEIVER_HOST>": ["datadog-receiver"]}'
    ```
 
-## Running Alloy with the Datadog Receiver
+## Run {{% param "PRODUCT_NAME" %}} with the Datadog Receiver
 
-Some of the components used here are experimental. In order to run them, you need to start Alloy with additional command line flags:
+Some of the components used here are experimental. In order to run them, you need to start {{< param "PRODUCT_NAME" >}} with additional command line flags:
 
    ```bash
    alloy run config.alloy --stability.level=experimental
@@ -153,3 +162,5 @@ Some of the components used here are experimental. In order to run them, you nee
 [Datadog Agent]: https://docs.datadoghq.com/agent/
 [Prometheus]: https://prometheus.io
 [OTLP]: https://opentelemetry.io/docs/specs/otlp/
+[otelcol.exporter.otlp]: ../../reference/components/otelcol.exporter.otlp
+[Components]: ../../reference/components/