Support
Use the right support path for product questions, docs gaps, and operational details so customer details stay protected and support gets enough context to act.
Route by report type
Start with the feedback intake when you need to report a docs gap, handle sensitive operational details, or separate product-support questions from docs corrections.
Choose the approved path for assigned support, redaction guidance, or customer-safe diagnostic context.
Open guidanceUse your assigned channel
Route account-specific, product-behavior, or pilot-blocking questions through the support path provided with the private beta invitation.
Include the product, route, readiness label, observed behavior, impact, and sanitized details.
Issue-first docs intake
Use the assigned feedback or support path when a page is missing, unclear, stale, or inconsistent with observed product behavior.
Start from the public route and the smallest reproducible gap.
Open guidanceRedaction required
Use the support bundle and privacy guidance before sharing logs, traces, diagnostics, configuration, or troubleshooting output.
Remove credentials, identifiers, payloads, and private topology.
Open guidanceName one product, one route or workflow, and the smallest reproducible symptom before attaching broad logs or command output.
Use status codes, reason codes, route names, timestamps, counters, and shape-only examples before payloads or customer-specific values.
Include the docs route, relevant status or limits page, and the runbook link that framed the question.
S3 Core health checks, platform capabilities, unsupported behavior triage, and support-safe diagnostics.
Stream, queue, audit, metrics, diagnostics, quota, replication, and support-safe boundaries.
OTLP admission, WAL, segment bundle, query, S3 query-read, BYOC, and support-safe workflows.