qa-monitoring

Detect and triage application monitoring signals for new software defects.

2|1|Updated May 27, 2025
One-click install
npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill qa-monitoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-monitoring
Source: https://github.com/VirtoCommerce/vc-mcp-testing-module/tree/main/skills/qa-monitoring
Command: npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill qa-monitoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps QA teams detect overlooked application defects by continuously monitoring Application Insights signals, filtering noise, and surfacing actionable bug candidates without automatically filing issues or changing code.

Core Features & Use Cases

  • Application Monitoring Queries: Analyzes frontend and backend telemetry using targeted KQL probes for exceptions, failed requests, and failed dependencies.
  • Intelligent Triage and Deduplication: Fingerprints recurring signals, identifies new or spiking failures, classifies issues, and applies confidence-based reproduction rules.
  • Use Case: A QA team can use this Skill to monitor a test environment, confirm high-confidence defects, and generate reports for human review before bug fixing workflows begin.

Quick Start

Use the qa-monitoring skill to scan frontend and backend application telemetry for new high-confidence bugs from the selected environment.

Frequently Asked Questions about qa-monitoring

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

FAQPage Schema
How do I detect production-like bugs using Application Insights telemetry?

Application Insights telemetry detects production-like bugs by running targeted KQL probes for frontend exceptions and backend failures, then surfacing actionable bug candidates for human review.

What is the best way to triage and deduplicate recurring application monitoring signals?

Triage and deduplicate recurring application monitoring signals by applying fingerprint-based identification to recurring exceptions, filtering noise, and classifying new or spiking software defects.

How do I write KQL queries to find failed requests and dependencies in my test environment?

KQL queries find failed requests and dependencies by analyzing frontend and backend telemetry through targeted probes, applying environment-aware configuration to validate production-like environments.

Does this application monitoring approach automatically file bug reports or fix code?

This application monitoring approach does not automatically file bug reports or fix code, operating under controlled reporting workflows that surface high-confidence defects strictly for human review.

Can I use telemetry analysis to confirm high-confidence defects before starting bug fixing workflows?

Telemetry analysis confirms high-confidence defects by applying confidence-based reproduction rules to classified exceptions and failures, generating actionable reports for QA teams before bug fixing begins.