Check OTLP endpoint shape before changing your collector
Review an OTLP/HTTP exporter endpoint, signal path, and auth header shape without sending private telemetry from the browser.
This is a dry-run checker. It does not send telemetry, store headers, or make network calls with pasted credentials.
Dry-run OTLP exporter config
Endpoint shape is ready for OTLP/HTTP traces.
Parsed https://ingest.squasher.ai/v1/traces.
The endpoint uses HTTPS or a local development HTTP host.
The endpoint targets /v1/traces.
The header shape matches x-squasher-key or Authorization: Bearer.
The headers mention protobuf or JSON OTLP/HTTP payloads.
Useful enough for the immediate debugging job.
Each utility is product-adjacent by design: it solves a concrete setup or debugging problem, then links to the Squasher workflow that monitors it continuously.
Checks HTTPS endpoint shape and the expected /v1/traces, /v1/logs, or /v1/metrics path.
Accepts x-squasher-key or Authorization: Bearer header formats.
Calls out collector defaults that often hide path or protocol mistakes.
Route OTLP telemetry into the debugging workflow.
Use Squasher as an OTLP destination when logs, traces, metrics, errors, and AI triage should explain the same incident.