fix(ckpt): update traces push path information (#4727)

Author: sfinet-scw

pages/cockpit/how-to/activate-push-traces.mdx

@@ -12,12 +12,12 @@ dates:
   posted: 2023-10-31
 ---
 
-This page shows you how to create [traces](/cockpit/concepts/#traces) from the Scaleway console, retrieve traces push paths, configure the OpenTelemetry HTTP agent, and push traces.
+This page shows you how to create [traces](/cockpit/concepts/#traces) from the Scaleway console, retrieve traces push path, configure the OpenTelemetry HTTP agent, and push traces.
 
 <Macro id="requirements" />
 
   - A Scaleway account logged into the [console](https://console.scaleway.com)
-  - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+  - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Project
 
 ## Create a trace
 
@@ -28,23 +28,22 @@ This page shows you how to create [traces](/cockpit/concepts/#traces) from the S
     - Enter a name
     - Choose the **Traces** data type
     - Select a region to create your trace in
+    - Choose your data retention duration (by default traces will be retained for 7 days)
 5. Check the estimated cost, then click **Create custom data source**.
 
-### Retrieve traces push paths
+### Retrieve traces push path
 
-<Message type="important">
- Only the [OpenTelemetry](https://opentelemetry.io/docs/what-is-opentelemetry/) HTTP push path is supported. Scaleway is working on implementing the [Open Telemetry gRPC](https://opentelemetry.io/docs/specs/semconv/rpc/grpc/), [Zipkin](https://zipkin.io/) and [Jaeger](https://www.jaegertracing.io/docs/1.50/) protocols.
-</Message>
+Scaleway supports the [OpenTelemetry](https://opentelemetry.io/docs/what-is-opentelemetry/) HTTP push path for traces: `/otlp/v1/traces`.
 
-Scaleway provides the following push path for the OpenTelemetry agent: `/otlp/v1/traces`.
-The complete endpoint is `https://traces.cockpit.fr-par.scw.cloud/otlp/v1/traces`.
+The complete endpoint is `https://<datasource_id>.traces.cockpit.<region>.scw.cloud/otlp/v1/traces`.
 
-Alternatively, you can retrieve your trace's push path from the Scaleway console:
+You can retrieve your trace's push path (and data source ID) from [Scaleway API](https://www.scaleway.com/en/developers/api/cockpit/regional-api/#path-data-sources-list-data-sources) or from the Scaleway console:
 
 1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
 2. Click the **Data sources** tab.
-3. Click the trace of which you want to retrieve the path. The trace's information displays.
-4. Retrieve the push path under the **URL** section.
+3. Click the trace data source of which you want to retrieve the path. The trace's information displays.
+4. Retrieve the data source's URL under the **URL** section. 
+5. Add the push path `/otlp/v1/traces` to the URL.
 
 ## Push traces