jmeter-debugging

Debug JMeter scripts through iterative smoke tests and log analysis.

4|1|Updated Aug 22, 2025
One-click install
npx skills add https://github.com/canyonlabz/mcp-perf-suite --skill jmeter-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jmeter-debugging
Source: https://github.com/canyonlabz/mcp-perf-suite/tree/main/.cursor/skills/jmeter-debugging
Command: npx skills add https://github.com/canyonlabz/mcp-perf-suite --skill jmeter-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iterative AI-driven JMeter script debugging via smoke tests, log analysis, and targeted fixes. Use when the user asks to debug, troubleshoot, fix errors in, or validate a JMeter script, or mentions JMeter smoke testing failures.

Core Features & Use Cases

  • AI-assisted diagnosis across smoke-test failures and log anomalies
  • Targeted fixes with minimal changes and controlled iteration
  • Real-world scenario: diagnose and fix a flaky JMeter script used in performance tests

Quick Start

Provide a concise JMeter script debugging request to initiate the iterative workflow.

Frequently Asked Questions about jmeter-debugging

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

FAQPage Schema
How do I debug a flaky JMeter script that fails during a smoke test?

To debug a flaky JMeter script, this Skill automates iterative smoke tests and log analysis to diagnose anomalies. It applies targeted minimal fixes across up to five iterations to stabilize your performance pipeline using a debug post-processor.

What is the best way to troubleshoot JMeter log anomalies in a performance pipeline?

Troubleshooting JMeter log anomalies is handled by an AI-driven workflow that analyzes logs during smoke-test failures. It uses a verbose debug post-processor to capture detailed data and records iterative fixes in a debug manifest.

How do I fix errors in a JMeter test plan automatically?

Fixing JMeter test plan errors is automated through controlled iteration with 1/1/1 smoke tests. The Skill diagnoses failures, applies minimal targeted fixes, and validates results up to five times to stabilize the script.

Can I use a JMeter debug post-processor to capture more details for script diagnosis?

Yes, a verbose debug post-processor is integrated directly into the debugging workflow. It captures detailed diagnostic information during smoke tests, enabling the AI to analyze log anomalies and apply targeted fixes to your script.

What are the limitations of iterative JMeter script debugging?

Iterative JMeter script debugging is limited to a maximum of five stabilization iterations. If smoke test failures or log anomalies remain unresolved after five attempts, the workflow concludes and records the state in a debug manifest.