Troubleshooting
Missing Logs
Use this guide when traces or services appear but the Logs page does not show expected application events.
Symptom
Use this guide when traces or services appear but the Logs page does not show expected application events.
Services or traces appear, but Logs is empty for the same service and time range. Only some severity levels appear. Expected application events are not visible after deployment.
Likely causes
- Capture not enabled
- The SDK may be sending traces while application logs still use a logger path that Vight is not collecting.
- Different process
- Logs emitted by another process or command can miss the service identity used by the running application.
- Hidden by filters
- Severity, text, service, environment, version, and deployment filters are common reasons expected logs disappear.
Checks
Start with the broadest possible evidence window, then narrow the cause once you know where data is landing.
- 1
Confirm log capture is enabled for the SDK or logger integration you use.
- 2
Generate a fresh log event after deployment and use a short time range.
- 3
Check service, environment, severity, text, version, and deployment filters.
- 4
Confirm logs are emitted by the same process that has Vight 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.
Enable console or logger capture according to the SDK docs. Use consistent service and environment values for traces and logs. Remove narrow severity or text filters while validating setup. Add one explicit test log event during startup or a test request.
After applying the fix, validate it this way: Emit one explicit test log during a request or startup path. Open Logs with service and environment filters removed first. Confirm the event has the expected service, environment, severity, and timestamp. If the log happened during a traced request, confirm whether trace and span links are present.