tsuga-audit-logs

Audit structured logging and trace correlation coverage using tsuga CLI queries.

2|Updated May 28, 2026
One-click install
npx skills add https://github.com/tsuga-dev/agent-plugins --skill tsuga-audit-logs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tsuga-audit-logs
Source: https://github.com/tsuga-dev/agent-plugins/tree/main/plugins/telemetry/skills/tsuga-audit-logs
Command: npx skills add https://github.com/tsuga-dev/agent-plugins --skill tsuga-audit-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you quickly determine whether your service logs are structured, searchable, and correctly correlated with traces so you can debug faster instead of guessing.

Core Features & Use Cases

  • Trace-log correlation audit: Verifies whether trace_id (and related trace context fields) appear in sampled logs when the service emits traces.
  • Log structure and severity consistency checks: Detects unstructured message blobs, inconsistent severity values (ERROR/WARN/INFO/DEBUG), and top-pattern dominance that can hide signals.
  • Error logging quality and regression detection: Reviews error log structure (e.g., stack/stack-context fields) and flags growing error patterns over a time window.

Quick Start

Use this skill to audit log quality for service "checkout-api" over the last hour and verify trace correlation exists in the logs.

Frequently Asked Questions about tsuga-audit-logs

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

FAQPage Schema
How do I verify trace_id correlation in my service logs?

Verify trace-log correlation by sampling log records to detect missing trace context fields like trace_id. This audit checks whether your service logs contain trace context and flags logs lacking proper trace correlation.

How do I check structured logging consistency for error patterns?

Check structured logging consistency by inspecting log field structure, severity discipline, and dominant patterns. This audit detects unstructured message blobs, inconsistent severity values, and flags growing error patterns over a specific time window.

What is the best way to audit observability logging during an incident?

Audit observability logging during an incident by inspecting log field structure and trace correlation coverage within a time window. This validates whether logs are queryable and properly linkable to traces for faster incident debugging.

Does this log audit require a live connection to query service emitters?

Yes, this log audit requires a live connection to confirm service emitters. It uses CLI queries to sample log records, detect missing trace fields, and summarize routing and pattern evidence for instrumentation validation.

How do I detect missing OTel trace fields in my application logs?

Detect missing OTel trace fields by sampling log records and checking for absent trace context fields when the service emits traces. The audit flags logs lacking trace correlation and summarizes dominant error patterns.