Support
Use the right support path for product questions, docs gaps, and operational evidence so customer details stay protected and reviewers get enough context to act.
Route by report type
Start with the feedback intake when you need to report a docs gap, route sensitive evidence, or separate product-support questions from docs corrections.
Choose the approved path for issue templates, assigned support, redaction guidance, or local page-health diagnostics.
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, maturity label, observed behavior, impact, and sanitized evidence.
Issue-first docs intake
Use the docs issue templates when a page is missing, unclear, stale, or stronger than the linked evidence supports.
Start from the public-safe template that matches the docs issue.
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 evidence or runbook link that framed the question.
S3 Core health checks, platform capabilities, unsupported behavior triage, and support evidence.
Stream, queue, audit, metrics, diagnostics, quota, replication, and support evidence boundaries.
OTLP admission, WAL, segment bundle, query, S3 query-read, BYOC, and support evidence workflows.
Cache, Gateway, Storage, Time Series, active compatibility, and validation evidence handoff.