Diagnose an application with logs and traces
Correlate bounded telemetry with the project, release, region, and W3C trace ID.
Last updated 2026-08-07
What you'll achieve
- Find the affected release and region
- Follow one request by trace ID
- Understand retention, sampling, and usage state
Start with the incident boundary
Open the project's Logs or Analytics page and choose the smallest useful time window. Filter by release, region, operation, outcome, or trace ID. A no-data, delayed, sampled, or unavailable state is reported explicitly; BlinkHost does not invent zero traffic.
Correlate a request
Send a valid W3C traceparent header when an upstream client owns the trace. BlinkHost preserves the trace ID and creates the edge span. Use the returned trace, request, correlation, and release identifiers to move between telemetry views.
Protect customer data
Never log authorization headers, cookies, passwords, tokens, keys, connection strings, request or response bodies, raw database values, or personal information. Platform redaction is a backstop, not permission to emit sensitive data.
Telemetry retention, query windows, live-tail sessions, alerts, and exports are plan-governed and visible in Usage.
Help improve this page
Sign in to send page-specific feedback. For account-specific help, email support@blinkhost.me.