How application observability works
Understand tenant-scoped telemetry, retention, redaction and diagnostic evidence.
Last updated 2026-09-02
What you'll achieve
- Find production evidence
- Avoid sensitive logging
- Build a useful support report
Signals and scope
BlinkHost records bounded request, runtime, database-operation, outbound-call and policy-decision signals for the owning project. Logs, metrics and traces are scoped by workspace role and the project retention available on its plan.
Data minimisation
Platform telemetry is designed for operational evidence and excludes secret values and raw database rows. Application logs are still customer-controlled content: do not write credentials, payment-card data or unnecessary personal data to them.
Troubleshooting
Start with the release identifier, request identifier, UTC time, region and stable error category. Compare the affected release with a known baseline before changing production. A support bundle contains bounded environment and manifest facts and excludes source, tokens and repository URLs.
Help improve this page
Sign in to send page-specific feedback. For account-specific help, email support@blinkhost.me.