tsuga-smoke-test

Name: tsuga-smoke-test
Availability: InStock
Author: Tsuga

Verify OpenTelemetry metrics, traces, and logs arrive in Tsuga for a service.

2|Updated May 28, 2026

Search Tags:#logs #metrics #telemetry #traces #correlation #openTelemetry #tsuga

Ready to run

npx skills add https://github.com/tsuga-dev/agent-plugins --skill tsuga-smoke-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tsuga-smoke-test
Source: https://github.com/tsuga-dev/agent-plugins/tree/main/plugins/telemetry/skills/tsuga-smoke-test
Command: npx skills add https://github.com/tsuga-dev/agent-plugins --skill tsuga-smoke-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you confirm that OpenTelemetry signals (metrics, traces, and logs) from a given service are actually arriving and can be correlated after a deployment.

Core Features & Use Cases

Signal presence validation: Checks that metrics, traces, and logs are observed within a recent time window for the specified service.
Post-deploy verification: Uses a default -15m window to quickly detect whether new instrumentation is producing data.
Cross-signal correlation: Verifies trace-log correlation by checking that logs include a non-empty trace_id (and trace_flags presence).
Actionable diagnostics: Produces targeted failure guidance when a signal is missing in the selected window.

Quick Start

Tell your AI to run a recent telemetry smoke test for your service by name and verify metrics, traces, and logs in Tsuga.

Frequently Asked Questions about tsuga-smoke-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify OpenTelemetry metrics, traces, and logs are arriving after a deployment?▼

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.

What is the best way to check trace-log correlation in OpenTelemetry?▼

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.

How do I investigate missing OpenTelemetry signals for a specific 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.

Does the telemetry smoke test work with a custom time window?▼

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.

Why are my OpenTelemetry logs not correlating with traces in Tsuga?▼

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.

Can I use this smoke test to check if a specific metric is being emitted?▼

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.