Skip to content

Add managed platforms and serverless OTLP ingest docs#37395

Draft
brett0000FF wants to merge 4 commits into
masterfrom
brett.blue/otlp-ingest-serverless-managed-platforms
Draft

Add managed platforms and serverless OTLP ingest docs#37395
brett0000FF wants to merge 4 commits into
masterfrom
brett.blue/otlp-ingest-serverless-managed-platforms

Conversation

@brett0000FF

@brett0000FF brett0000FF commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

What does this PR do? What is the motivation?

Adds two new pages under Direct OTLP Ingest and updates the section's information architecture:

  • Managed Platforms: Dedicated OTLP endpoints for 27 third-party platforms (Cloudflare, Vercel, Heroku, etc.). Covers all signals (traces, metrics, logs).
  • Serverless: Traces from AWS (Lambda, ECS Fargate), Azure (Container Apps, Web Apps, Functions), and GCP (Cloud Run, Cloud Run Functions, GKE) environments.

Also restructures the landing page with an environment-first routing table, and adds cross-reference notes to the logs and metrics pages pointing to managed platforms.

Open items — blocks merge

  • Preview/GA framing: The serverless page documents the traces endpoint, which the landing page gates behind Preview/"contact your CSM." These need to agree before publish.
  • GCP endpoint ambiguity: The managed platforms table lists gcp and gae subdomains, but the serverless page says Cloud Run/Functions/GKE use the generic traces endpoint. A Cloud Run user could pick either path and get a different endpoint. Need to clarify what the gcp managed platform endpoint covers.
  • AWS resource attributes: Unconfirmed. Need eng to verify cloud.provider/cloud.platform values for Lambda and ECS Fargate.

Open items — needs decision

  • Span-mapping section (dd-otlp-span-mapping): Eng raised concern about documenting this header while operation name v2 is stabilizing. Keep or remove?
  • Azure cloud.platform values: Draft uses underscores (azure_app_service, azure_functions). OTel semantic conventions may use dots. Need to verify.
  • GKE scope: GKE is not serverless. Either broaden the page framing or move GKE elsewhere.
  • Serverless signal scope: Page is traces-only per draft. Resource attributes apply to all signals. Should this page cover metrics/logs config too?

Open items — missing content

  • Sign-up form link for the traces Preview on the landing page
  • Hostname configuration guidance
  • Traces page fixes (separate PR): Fix header typo and add routing notes before unprivating

Merge instructions

Merge readiness:

  • Ready for merge

Additional notes

All open items are marked with <!-- TODO --> comments inline. Strip before merge.

Add two new pages under Direct OTLP Ingest:
- Managed Platforms: dedicated OTLP endpoints for 27 platforms
- Serverless: traces from AWS, Azure, and GCP environments

Update the landing page with a routing table and add cross-reference
notes to the logs and metrics pages.
@github-actions github-actions Bot added the Architecture Everything related to the Doc backend label Jun 9, 2026
Mark open items inline: Preview framing, GCP endpoint ambiguity,
Azure semconv verification, AWS attributes, span-mapping decision,
GKE scope, and signal scope. Add GKE to routing table.
Lambda: cloud.provider + faas.id (ARN) required, cloud.platform
conditional. ECS Fargate: aws.ecs.task.arn + aws.ecs.launchtype
required, cloud.provider/cloud.platform optional.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Architecture Everything related to the Doc backend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant