tsuga-audit-monitor-coverage

Name: tsuga-audit-monitor-coverage
Availability: InStock
Author: Tsuga

Audit Tsuna monitor coverage and notification routing gaps across services and teams.

2|Updated May 28, 2026

Search Tags:#monitoring #audit #reliability #alerting #configuration validation #tsuga #notification routing

Ready to run

npx skills add https://github.com/tsuga-dev/agent-plugins --skill tsuga-audit-monitor-coverage

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies missing monitor coverage, broken notification routing, and stale team references in Tsuga alerting configuration so teams can stop silent failures.

Core Features & Use Cases

Monitor coverage audit: compares service inventory against monitor filter exact matches to find services with no monitors, while separately reporting glob-pattern “possible coverage.”
Notification routing gap detection: flags monitor-owner teams that have monitors but no active notification rules, indicating alerts may not reach the right recipients.
Config hygiene checks: finds notification rules referencing non-existent team IDs and reports active silences affecting coverage scope.

Quick Start

Ask the AI to audit alerting monitor coverage for all services and show uncovered services, routing gaps, and active silences for remediation.

Frequently Asked Questions about tsuga-audit-monitor-coverage

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

FAQPage Schema

How do I audit alerting monitor coverage to find services with no monitors?▼

Auditing alerting monitor coverage involves comparing your service inventory against exact monitor filter matches to identify uncovered services, while separately reporting possible coverage from glob-pattern filters.

Why does broken notification routing cause silent failures in alerting systems?▼

Broken notification routing causes silent failures when monitor-owner teams have active monitors but lack active notification rules, meaning generated alerts fail to reach the intended recipients.

What is the best way to detect stale team references in notification rules?▼

Detecting stale team references requires cross-referencing active notification rules against your team inventory to flag any rules referencing non-existent team IDs for cleanup.

Can I check active notification silences affecting my alerting scope?▼

You can check active notification silences by querying your notification silences inventory and reporting them alongside coverage and routing gaps to understand the full alerting configuration snapshot.

What prerequisites are needed to audit Tsuga monitor coverage and routing gaps?▼

Auditing Tsuga monitor coverage requires running inventory queries for services, monitors, teams, notification rules, and silences, then building cross-reference mappings to report a configuration snapshot with a query timestamp.