Troubleshooting
Fixes for the most common setup problems.
- Nothing arrives: check the key on Credentials (a server key on servers, a browser key that lists the site in web pages) and that the service can reach the endpoint on port 443; the SDK logs the exact reply, which names the problem. - Some spans or logs are missing: open Ingestion errors; each problem shows the setting that fixes it. - Hitting the daily quota: sample traces (see billing_and_limits); the quota resets at 00:00 UTC. - Services have odd names like unknown_service: set OTEL_SERVICE_NAME on every service. - The browser gets 403: the browser key doesn't list that website; add it on the key's details. - Deployments stays empty: set service.version from the build (tag or commit). - Behavior stays empty: send session.id and journey.step_name on frontend spans, or map existing names on Attribute mappings. - Health shows no uptime: add health.check.url to the resource attributes.