[DRAFT] Workers Tracing / Exporting OTel

src/content/docs/workers/observability/exporting-opentelemetry-data/axiom.mdx

@@ -0,0 +1,106 @@
+---
+pcx_content_type: how-to
+title: Export to Axiom
+sidebar:
+  order: 3
+---
+
+import {WranglerConfig} from "~/components";
+
+Axiom is a serverless log analytics platform that helps you store, search, and analyze massive amounts of data. By exporting your Cloudflare Workers application telemetry to Axiom, you can:
+- Store and query logs and traces at scale 
+- Create dashboards and alerts to monitor your Workers
+
+![Trace view with timing information displayed on a timeline](~/assets/images/workers-observability/axiom-example.png)
+
+This guide will walk you through exporting OpenTelemetry-compliant traces and logs to Axiom from your Cloudflare Worker application
+
+## Prerequisites
+
+Before you begin, ensure you have:
+
+- An active [Axiom account](https://app.axiom.co/register) (free tier available)
+- A deployed Worker that you want to monitor
+- An Axiom dataset to send data to
+
+## Step 1: Create a dataset
+
+If you don't already have a dataset to send data to:
+1. Log in to your [Axiom account](https://app.axiom.co/)
+2. Navigate to **Datasets** in the left sidebar
+3. Click **New Dataset**
+4. Enter a name (e.g. `cloudflare-workers-otel`)
+5. Click **Create Dataset**
+
+## Step 2: Get your Axiom API token and dataset
+
+1. Navigate to **Settings** in the left sidebar
+2. Click on **API Tokens**
+3. Click **Create API Token**
+4. Configure your API token:
+   - **Name**: Enter a descriptive name (e.g., `cloudflare-workers-otel`)
+   - **Permissions**: Select **Ingest** permission (required for sending telemetry data)
+   - **Datasets**: Choose which datasets this token can write to, or select **All Datasets**
+5. Click **Create**
+6. **Important**: Copy the API token immediately and store it securely - you won't be able to see it again
+
+The API token will look something like: `xaat-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`
+
+## Step 3: Configure Cloudflare destinations
+
+Now you'll create destinations in the Cloudflare dashboard that point to Axiom.
+
+### Axiom OTLP endpoints
+
+Axiom provides separate OTLP endpoints for traces and logs:
+- **Traces**: `https://api.axiom.co/v1/traces`
+- **Logs**: `https://api.axiom.co/v1/logs`
+
+### Configure trace or logs destination
+
+1. Navigate to your Cloudflare account's [Workers Observability](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/pipelines) section
+2. Click **Add destination**
+3. Configure your trace destination:
+   - **Destination Name**: `axiom-traces` (or any descriptive name)
+   - **Destination Type**: Select **Traces**
+   - **OTLP Endpoint**: `https://api.axiom.co/v1/traces` (or `/v1/logs`)
+   - **Custom Headers**: Add two required headers: 
+     -  Authentication header 
+        - Header name: `Authorization`
+        - Header value: `Bearer <your-api-token>` 
+     - Dataset header: 
+       - Header name: `X-Axiom-Dataset`
+       - Header value: Your dataset name (e.g., `cloudflare-workers-otel`) 
+4. Click **Save**
+
+## Step 3: Configure your Worker
+
+With your destinations created in the Cloudflare dashboard, update your Worker's configuration to enable telemetry export.
+
+<WranglerConfig>
+
+```json
+{
+  "observability": {
+    "traces": {
+      "enabled": true,
+      // Must match the destination name in the dashboard
+      "destinations": ["axiom-traces"]
+    },
+    "logs": {
+      "enabled": true,
+      // Must match the destination name in the dashboard
+      "destinations": ["axiom-logs"]
+    }
+  }
+}
+```
+
+</WranglerConfig>
+
+After updating your configuration, deploy your Worker for the changes to take effect.
+
+:::note
+It may take a few minutes after deployment for data to appear in Axiom. 
+:::
+

src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx

@@ -0,0 +1,74 @@
+---
+pcx_content_type: how-to
+title: Export to Grafana Cloud
+sidebar:
+  order: 2
+---
+import {WranglerConfig} from "~/components";
+
+Grafana Cloud is a fully managed observability platform that provides visualization, alerting, and analytics for your telemetry data. By exporting your Cloudflare Workers telemetry to Grafana Cloud, you can:
+- Visualize distributed traces in **Grafana Tempo** to understand request flows and performance bottlenecks
+- Query and analyze logs in **Grafana Loki** alongside your traces
+
+This guide will walk you through configuring Cloudflare Workers to export OpenTelemetry-compliant traces and logs to your Grafana Cloud stack.
+
+![Grafana Tempo trace view showing a distributed trace for a service with multiple spans including fetch requests, durable object subrequests, and queue operations, with timing information displayed on a timeline](~/assets/images/workers-observability/grafana-traces.png)
+
+## Prerequisites
+
+Before you begin, ensure you have:
+
+- An active [Grafana Cloud account](https://grafana.com/auth/sign-up/create-user) (free tier available)
+- A deployed Worker that you want to monitor
+
+## Step 1: Access the OpenTelemetry setup guide
+
+1. Log in to your [Grafana Cloud portal](https://grafana.com/)
+2. From your organization's home page, navigate to **Connections** → **Add new connection**
+3. Search for "OpenTelemetry" and select **OpenTelemetry (OTLP)**
+4. Select **Quickstart** then select **JavaScript**
+6. Click **Create a new token**
+7. Enter a name for your token (e.g., `cloudflare-workers-otel`) and click **create token**
+8. Click on **Close** without copying the token
+9. Copy and Save the value for `OTEL_EXPORTER_OTLP_ENDPOINT` and `OTEL_EXPORTER_OTLP_HEADERS` in the `Environment variables` code block as the OTel endpoint and as the Auth header value respectively
+
+
+## Step 2: Set up destination 
+1. Navigate to your Cloudflare account's [Workers Observability](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/pipelines) section
+2. Click **Add destination** and configure a destination name (e.g. `grafana-tracing`)
+3. From Grafana, copy your Otel endpoint, auth header, and auth value 
+  * Your OTEL endpoint will look like `https://otlp-gateway-prod-us-east-2.grafana.net/otlp` (append `/v1/traces` for traces and `/v1/logs` for logs) 
+  * Your custom header should include: 
+      * Your auth header name `Authorization`
+      * Your auth header value `Basic MTMxxx...`
+
+## Step 3: Configure your Worker
+
+With your destination created in the Cloudflare dashboard, update your Worker's configuration to enable telemetry export. 
+
+<WranglerConfig>
+
+```json
+{
+  "observability": {
+    "traces": {
+      "enabled": true,
+      // Must match the destination name in the dashboard
+      "destinations": ["grafana-traces"]
+    },
+    "logs": {
+      "enabled": true,
+      // Must match the destination name in the dashboard
+      "destinations": ["grafana-logs"]
+    }
+  }
+}
+```
+
+</WranglerConfig>
+
+After updating your configuration, deploy your Worker for the changes to take effect. 
+
+:::note
+It may take a few minutes after deployment for data to appear in Grafana Cloud. 
+:::

src/content/docs/workers/observability/exporting-opentelemetry-data/honeycomb.mdx

@@ -0,0 +1,108 @@
+---
+pcx_content_type: how-to
+title: Export to Honeycomb
+sidebar:
+  order: 1
+---
+
+import {WranglerConfig} from "~/components";
+
+Honeycomb is an observability platform built for high-cardinality data that helps you understand and debug your applications. By exporting your Cloudflare Workers application telemetry to Honeycomb, you can:
+- Visualize traces to understand request flows and identify performance bottlenecks
+- Query and analyze logs with unlimited dimensionality across any attribute
+- Create custom queries and dashboards to monitor your Workers
+
+![Trace view including POST request, fetch operations, durable object subrequest, and queue send, with timing information displayed on a timeline](~/assets/images/workers-observability/honeycomb-example.png)
+
+This guide will walk you through configuring your Cloudflare Worker application to export OpenTelemetry-compliant traces and logs to Honeycomb.
+
+## Prerequisites
+
+Before you begin, ensure you have:
+
+- An active [Honeycomb account](https://ui.honeycomb.io/signup) (free tier available)
+- A deployed Worker that you want to monitor
+
+## Step 1: Get your Honeycomb API key
+
+1. Log in to your [Honeycomb account](https://ui.honeycomb.io/)
+2. Navigate to your account settings by clicking on your profile icon in the top right
+3. Select **Team Settings**
+4. In the left sidebar, click **Environments** and click the gear icon
+5. Find your environment (e.g., `production`, `test`) or create a new one
+6. Under **API Keys**, click **Create Ingest API Key**
+7. Configure your API key:
+   - **Name**: Enter a descriptive name (e.g., `cloudflare-workers-otel`)
+   - **Permissions**: Select **Can create services/datasets** (required for OTLP ingestion)
+8. Click **Create**
+9. **Important**: Copy the API key immediately and store it securely - you won't be able to see it again
+
+The API key will look something like: `hcaik_01hq...`
+
+## Step 2: Configure Cloudflare destinations
+
+Now you'll create destinations in the Cloudflare dashboard that point to Honeycomb. 
+
+### Honeycomb OTLP endpoints
+
+Honeycomb provides separate OTLP endpoints for traces and logs:
+- **Traces**: `https://api.honeycomb.io/v1/traces`
+- **Logs**: `https://api.honeycomb.io/v1/logs`
+
+### Configure trace destination
+
+1. Navigate to your Cloudflare account's [Workers Observability](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/pipelines) section
+2. Click **Add destination**
+3. Configure your trace destination:
+   - **Destination Name**: `honeycomb-traces` (or any descriptive name)
+   - **Destination Type**: Select **Traces**
+   - **OTLP Endpoint**: `https://api.honeycomb.io/v1/traces`
+   - **Custom Headers**: Add the authentication header:
+     - Header name: `x-honeycomb-team`
+     - Header value: Your Honeycomb API key (e.g., `hcaik_01hq...`)
+4. Click **Save**
+
+### Configure logs destination
+
+Repeat the process for logs:
+
+1. Click **Add destination** again
+2. Configure your logs destination:
+   - **Destination Name**: `honeycomb-logs` (or any descriptive name)
+   - **Destination Type**: Select **Logs**
+   - **OTLP Endpoint**: `https://api.honeycomb.io/v1/logs`
+   - **Custom Headers**: Add the authentication header:
+     - Header name: `x-honeycomb-team`
+     - Header value: Your Honeycomb API key (same as above)
+3. Click **Save**
+
+## Step 3: Configure your Worker
+
+With your destinations created in the Cloudflare dashboard, update your Worker's configuration to enable telemetry export.
+
+<WranglerConfig>
+
+```json
+{
+  "observability": {
+    "traces": {
+      "enabled": true,
+      // Must match the destination name in the dashboard
+      "destinations": ["honeycomb-traces"]
+    },
+    "logs": {
+      "enabled": true,
+      // Must match the destination name in the dashboard
+      "destinations": ["honeycomb-logs"]
+    }
+  }
+}
+```
+
+</WranglerConfig>
+
+After updating your configuration, deploy your Worker for the changes to take effect.
+
+:::note
+It may take a few minutes after deployment for data to appear in Honeycomb. 
+:::