knowzcode-telemetry

Correlate Sentry and App Insights telemetry to diagnose production errors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the friction of switching between IDEs and external monitoring dashboards by bringing production telemetry directly into your development workflow.

Core Features & Use Cases

  • Unified Investigation: Correlate error logs and performance metrics from Sentry and App Insights in one place.
  • Root Cause Analysis: Automatically parse natural language queries to identify trends, timelines, and potential fixes for production bugs.
  • Use Case: When a user reports a recurring 500 error, use this skill to pull the relevant Sentry traces and App Insights logs to pinpoint the exact failing service call without leaving your terminal.

Quick Start

Use the knowzcode telemetry skill to investigate the recent production errors related to the user authentication service.

Frequently Asked Questions about knowzcode-telemetry

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

FAQPage Schema
How do I correlate Sentry error traces with App Insights logs for root cause analysis?

Correlating Sentry error traces with App Insights logs for root cause analysis involves parsing natural language queries to unify multi-source telemetry data, identify performance bottlenecks, and pinpoint failing service calls. This provides actionable remediation steps without leaving your development workflow.

What is the best way to diagnose production errors without switching between IDEs and monitoring dashboards?

Diagnosing production errors without switching dashboards is achieved by bringing live telemetry directly into your terminal. This approach investigates Sentry and App Insights data within your existing development workflow to provide root cause analysis for software bugs.

Can I investigate recurring 500 errors by pulling live telemetry data directly into my development workflow?

You can investigate recurring 500 errors by pulling live telemetry data directly into your development workflow. This process queries Sentry traces and App Insights logs to pinpoint the exact failing service call causing the production software errors.

Does this telemetry investigation approach work for both error tracking and system health monitoring tasks?

This telemetry investigation approach works for both error tracking and system health monitoring tasks. It operates within the context of production debugging to diagnose software errors and performance bottlenecks using Sentry and App Insights data.

How do I identify performance bottlenecks using multi-source telemetry logs?

Identifying performance bottlenecks using multi-source telemetry logs requires correlating error logs and performance metrics from Sentry and App Insights. This unified investigation automatically identifies trends and timelines to provide actionable remediation steps.