tsuga-smoke-test

Verify OpenTelemetry metrics, traces, and logs by running a post-deploy smoke test that checks a specified service within a recent time window. It uses the tsuga CLI to search signals by service.name and confirms data presence for newly deployed instrumentation.

Check trace-log correlation in OpenTelemetry by verifying that logs include a populated trace_id and trace_flags. This confirms that logs and traces can be correlated, ensuring end-to-end visibility for the specified service.

Investigate missing OpenTelemetry signals by running time-bounded aggregations for metric counts and searching by service.name. The smoke test produces targeted failure guidance to diagnose why a specific metric, span, or log field is not being emitted.

Yes, the telemetry smoke test works with a custom time window, although it defaults to a -15m window for quick post-deploy checks. You can specify a different time range to validate metric counts and signal presence over a longer or shorter period.

OpenTelemetry logs may not correlate with traces if the log payload lacks a non-empty trace_id or trace_flags. The smoke test verifies this cross-signal correlation to ensure your logs and traces are properly linked for the specified service.

Yes, you can use this smoke test to check if a specific metric is being emitted by running time-bounded aggregations for metric counts. It validates signal presence for the specified service and provides actionable diagnostics if the metric is missing.