Troubleshooting
Missing Runtime Metrics
Use this guide when a service has traces but Runtime does not show expected pressure signals.
Symptom
Use this guide when a service has traces but Runtime does not show expected pressure signals.
Runtime charts are empty for a service that has traces. Only request data appears, not process or runtime signals. The service appears in filters but has no recent runtime samples.
Likely causes
- Unsupported signal
- Not every SDK and runtime combination reports the same process or runtime metrics.
- Short-lived process
- A process that exits quickly may send request traces without enough time to report runtime samples.
- Label mismatch
- Runtime charts can look empty when the selected service or environment differs from trace identity.
Checks
Start with the broadest possible evidence window, then narrow the cause once you know where data is landing.
- 1
Confirm the selected SDK and runtime support the metric you expect.
- 2
Check service, environment, and time range filters.
- 3
Confirm the service process stays alive long enough to report runtime samples.
- 4
Compare Runtime with service detail to ensure you selected the same service label.
Resolution
The fix should make new telemetry appear in the expected Vight page, under the expected service and environment, without relying on stale data.
Use an SDK/runtime combination that emits runtime metrics. Set service and environment values before SDK startup. Generate sustained traffic or keep the service running while validating charts. Use traces and logs for request evidence while runtime metrics are being fixed.
After applying the fix, validate it this way: Keep the service running long enough to emit runtime samples. Open Runtime with the same service and environment that appear in Traces. Generate sustained traffic and refresh the selected time range. Use traces and logs for incident evidence while runtime setup is being corrected.