Check your OTLP endpoint before you redeploy.
Pick a signal, then paste the exporter's URL and headers. The tester checks the scheme, the /v1 path, the auth header, and the content type, and sends nothing.
Free plan. No credit card required.
OTLP endpoint tester
In your browserOne per line, as in your exporter or Collector config. Use a redacted key. Results update as you type.
| Result | Check |
|---|---|
| Pass | Endpoint URLParsed https://ingest.squasher.ai/v1/traces. |
| Pass | ProtocolThe endpoint uses HTTPS or a local development HTTP host. |
| Pass | Signal pathThe endpoint targets /v1/traces. |
| Pass | Authentication headerThe header shape matches x-squasher-key or Authorization: Bearer. |
| Pass | OTLP content typeThe headers mention protobuf or JSON OTLP/HTTP payloads. |
This is a dry-run checker. It does not send telemetry, store headers, or make network calls with pasted credentials.
Five checks for an OTLP/HTTP exporter.
Most failed exports come down to a path, a scheme, or a header. These are the ones the tester reads.
Endpoint URL
- Passes when
- The text is a full URL.
- Flags
- Fail
- Usual cause
- A missing https://, or a quote left over from a YAML or .env file.
Protocol
- Passes when
- https, or http to localhost or 127.0.0.1.
- Flags
- Fail
- Usual cause
- An http:// URL copied from a local Collector config.
Signal path
- Passes when
- The path ends with /v1/traces, /v1/logs, or /v1/metrics for the signal you picked.
- Flags
- Warn for a bare base URL. Fail for any other path.
- Usual cause
- A base URL in a per-signal setting, a signal path given twice, or the traces path used for logs.
Authentication header
- Passes when
- x-squasher-key, or Authorization with Bearer.
- Flags
- Warn
- Usual cause
- Headers set on one exporter but not the other, or a variable the service never loads.
OTLP content type
- Passes when
- application/x-protobuf or application/json is set.
- Flags
- Warn
- Usual cause
- A hand-written HTTP client. OpenTelemetry SDKs and the Collector set it for you.
Squasher finds the errors in your telemetry.
Point the exporter at Squasher once. It pulls the errors out of your traces and logs and keeps the rest as context.
- Exception events and spans with an error status become errors.
- Error and fatal log records do too. Other logs stay as context.
- Logs and spans share trace IDs, so one error opens its whole request.
- A managed connector key records its last export and last rejection.
acmecheckout-apiExplore
Search⌘ KLogs
Live| Level | Timestamp | Message |
|---|---|---|
| info | 14:06:13.251 | POST /api/checkout 500 in 2.31 s |
| error | 14:06:13.246 | TypeError: Cannot read properties of undefined (reading 'amount') |
| warn | 14:06:13.244 | pricing: price still pending at render |
| info | 14:06:12.988 | order 7f13 received, currency EUR |
| info | 14:06:12.730 | GET /api/cart 200 in 84 ms |
| info | 14:06:12.114 | cart.load cart=8f21 items=3 |
Example project and data
Questions, answered.
What is an OTLP endpoint?
The URL an OpenTelemetry SDK or Collector exports to. Over OTLP/HTTP each signal has its own path: /v1/traces, /v1/logs, and /v1/metrics.
Should my OTLP endpoint include /v1/traces?
It depends on the setting. OTEL_EXPORTER_OTLP_ENDPOINT and a Collector exporter's endpoint take the base URL and add the path for you. Per-signal settings such as OTEL_EXPORTER_OTLP_TRACES_ENDPOINT take the full URL, path included.
What is Squasher's OTLP endpoint?
https://ingest.squasher.ai, with /v1/traces, /v1/logs, and /v1/metrics. Send your key in the x-squasher-key header or as Authorization: Bearer. Bodies can be protobuf or JSON, and gzip is accepted.
Does Squasher accept OTLP over gRPC?
No. Squasher accepts OTLP over HTTP only. Set the exporter protocol to http/protobuf or http/json, and don't send to the gRPC port 4317.
How do I test the endpoint for real?
Send one span or log from your service and read the response status. 401 means the key is missing or wrong, 404 means the path is wrong, and 415 means the content type is not protobuf or JSON.
Does the tester send my key anywhere?
No. It is a dry run in your browser: it makes no network calls and stores nothing. The tool is also left out of this site's session replay, so what you paste is not recorded.
Keep exploring.
Point your exporter here.
Send traces, logs, and metrics over OTLP/HTTP. Squasher finds the errors in them.
Free plan. No credit card required.