telemetry

Parse natural language queries to investigate telemetry data from Sentry and App Insights.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/knowz-io/knowzcode --skill telemetry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: telemetry
Source: https://github.com/knowz-io/knowzcode/tree/main/skills/telemetry
Command: npx skills add https://github.com/knowz-io/knowzcode --skill telemetry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose and resolve production errors by investigating telemetry data from various sources like Sentry and App Insights, reducing downtime and improving application stability.

Core Features & Use Cases

  • Error Investigation: Trace exceptions and pinpoint root causes of production issues.
  • Rate Monitoring: Check error rates and identify performance bottlenecks.
  • Diagnose Monitoring Issues: Understand why monitoring alerts are firing or not firing.
  • Use Case: When users report intermittent 500 errors in the checkout service, use this Skill to analyze Sentry and App Insights data from the last hour to identify the specific error and its origin.

Quick Start

Investigate telemetry for a 500 error in production over the last 20 minutes.

Frequently Asked Questions about telemetry

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

FAQPage Schema
How do I debug production errors using telemetry data from Sentry and App Insights?

Debug production errors by investigating telemetry data from Sentry and App Insights. This Skill parses natural language queries to extract timeframes and environments, queries sources using CLI tools, and synthesizes findings into a unified timeline with a root cause hypothesis.

Can I check error rates and trace exceptions for intermittent 500 errors?

Yes, you can check error rates and trace exceptions for intermittent 500 errors. The Skill investigates telemetry data to pinpoint root causes of production issues, identify performance bottlenecks, and diagnose why monitoring alerts are firing.

What is the best way to diagnose monitoring issues and alert failures in production?

The best way to diagnose monitoring issues is to investigate telemetry data from Sentry and App Insights. It parses natural language queries to extract search terms, queries available sources using CLI tools, and synthesizes findings into a unified timeline with a root cause hypothesis.

Does this telemetry investigation tool require any specific dependencies or components?

No specific dependencies are required to use this telemetry investigation tool. It operates using internal references to parse natural language queries and queries available sources using CLI tools to synthesize findings into a unified timeline.

How do I investigate telemetry for a specific production error over the last 20 minutes?

To investigate telemetry for a specific production error over the last 20 minutes, provide a natural language query. The Skill extracts the environment, timeframe, and search terms, queries sources like Sentry and App Insights, and generates a root cause hypothesis.