bzm-triage-failure

Analyze a BlazeMeter execution to identify and prioritize root causes of failures.

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/benjithompson/blazemeter-perfecto-skills --skill bzm-triage-failure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bzm-triage-failure
Source: https://github.com/benjithompson/blazemeter-perfecto-skills/tree/main/skills/bzm-triage-failure
Command: npx skills add https://github.com/benjithompson/blazemeter-perfecto-skills --skill bzm-triage-failure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides deep analysis of a single failed or regressed BlazeMeter execution, helping users identify the root cause of failures and prioritize next steps for resolution.

Core Features & Use Cases

  • Error Breakdown: Analyze errors by type and endpoint to identify specific failure points.
  • Endpoint Hot Spots: Rank endpoints by latency and error contribution to find the most critical issues.
  • Anomaly Detection: Identify anomalies in the execution data that may indicate underlying problems.
  • Systemic vs. Noise: Differentiate between systemic issues and transient noise to prioritize fixes.
  • Prioritized Next Steps: Provide actionable recommendations for resolving identified issues.

Quick Start

Run the bzm-triage-failure skill for the execution with ID <execution_id>.

Frequently Asked Questions about bzm-triage-failure

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

FAQPage Schema
How do I identify the root cause of a failed BlazeMeter performance test execution?

To identify the root cause of a failed BlazeMeter execution, you can analyze the execution details to break down errors by type and endpoint, detect anomalies, and differentiate systemic issues from transient noise.

What is the best way to prioritize fixing performance testing errors by endpoint latency?

Prioritizing performance testing errors involves ranking endpoint hot spots by their latency and error contribution, which helps identify specific failure points and focus on the most critical issues first.

Can I analyze a single BlazeMeter execution to differentiate systemic issues from transient noise?

Yes, you can analyze a single BlazeMeter execution to differentiate systemic issues from transient noise, allowing you to distinguish underlying problems from random anomalies and prioritize fixes accordingly.

Do I need access to the BlazeMeter API to fetch execution details for error triage?

Yes, you need access to the BlazeMeter API to fetch execution details including errors, statistics, and anomalies, which are required to generate a structured report with insights and recommendations.

How do I get actionable recommendations for resolving BlazeMeter test regressions?

To get actionable recommendations for resolving BlazeMeter test regressions, analyze the execution data to produce a structured report that provides prioritized next steps based on identified anomalies and error breakdowns.