Troubleshooting
No Traces Appearing
Use this guide when requests are reaching your application but Vight does not show traces for the expected service.
Symptom
Use this guide when requests are reaching your application but Vight does not show traces for the expected service.
The Traces page is empty for the selected service or environment. Services may appear, but request examples are missing. Logs may appear without trace links.
Likely causes
- SDK starts too late
- Requests handled before instrumentation starts can run normally without producing trace examples.
- Route excluded
- An exclusion rule may hide the exact path used for validation.
- Filters too narrow
- A selected service, status, environment, version, or short time range can make valid traces look absent.
Checks
Start with the broadest possible evidence window, then narrow the cause once you know where data is landing.
- 1
Confirm the SDK starts before the application handles requests.
- 2
Generate a fresh inbound request after deployment.
- 3
Check time range, service, environment, status, and error filters.
- 4
Confirm the request path is not excluded by SDK configuration.
Resolution
The fix should make new telemetry appear in the expected Vight page, under the expected service and environment, without relying on stale data.
Move SDK startup earlier in application boot. Set a stable service name and environment before instrumentation starts. Remove overly broad route exclusions and test with a normal user-facing request. Use the SDK-specific docs for the runtime you installed.
After applying the fix, validate it this way: Send a normal user-facing request, not only a health check. Open Traces with the current service and a broad time range. Confirm the trace shows route, status, duration, service, and environment. Open trace detail and verify at least one inbound span is present.