No data is appearing

Work through these checks in order. Changing sampling, batching, and transport at the same time makes the failure harder to isolate.

1. Check the dashboard scope

Confirm the selected organization, project, environment, and time range. Development traffic does not appear while the environment filter is production.

2. Check the credential

• The key begins with tm_ and has not been revoked.
• The key belongs to the intended organization and project.
• The application actually receives the environment variable at runtime.

Match the failing signal to its permission:

Signal	Required scope
OTLP traces, logs, metrics, and captured errors	ingest:write
Identify, group, screen, and diagnostic events sent to /api/v1/capture	analytics:write
Session replay chunks	replay:write
Feature-flag decisions from /api/v1/decide	flags:read

An SDK that sends both telemetry and identity normally needs ingest:write and analytics:write. The Ingest only access preset does not include capture, replay, or feature-flag permission.

Do not print the complete key while debugging.

3. Check the endpoint

The managed endpoint is https://api.teml.io. OTLP HTTP exporters use /v1/traces, /v1/logs, and /v1/metrics. Diagnostic events use /api/v1/capture.

Check proxy and firewall logs for DNS, TLS, 401, 403, 413, and 429 failures.

4. Force one recognizable signal

Create one manual span or captured error with a unique name. Avoid relying on framework auto-instrumentation until the manual signal works.

5. Flush a short-lived process

SDKs batch telemetry. Call the documented stop, shutdown, or flush method before a command, job, or test process exits.

6. Enable debug output briefly

Turn on SDK debug logging, reproduce once, and look for exporter or authentication errors. Turn it off after diagnosis.

7. Separate ingestion from identity

If the signal appears in Logs, Traces, or Issues but not in Customers, ingestion works. Continue with Customer activity is not connecting.