BlazeMeter Troubleshooting
Comprehensive troubleshooting guide for resolving issues in BlazeMeter.
Overview
This skill covers troubleshooting for API Monitoring, Performance Testing, general issues, integrations, and security. It includes diagnostic steps, common solutions, and support resources. Effective troubleshooting requires systematic diagnosis and understanding of common issues and their solutions.
Quick Start
- Identify the issue: Determine if it's API Monitoring, Performance Testing, or general
- Check relevant reference: Review the appropriate troubleshooting guide
- Apply solutions: Follow diagnostic steps and solutions
- Contact support: If issues persist, use support resources
MCP Tools Integration
While troubleshooting is primarily done through UI and logs, you can use BlazeMeter MCP tools to access test execution information and results that may help diagnose issues:
Available MCP Tools
When to Use MCP Tools
- Execution Analysis: Use MCP tools to programmatically retrieve execution details and errors
- Automation: Integrate troubleshooting information into automation scripts
- Monitoring: Monitor test execution status and errors programmatically
Example Workflow
Getting Execution Details for Troubleshooting:
- Use
blazemeter_execution with action list to get execution IDs for a test
- Use
blazemeter_execution with action read to get detailed execution information
- Review execution status, errors, and results to identify issues
- Use this information to diagnose and resolve problems
Reference Files
API Monitoring
- api-monitoring.md: Radar Agent Auth Fail, SSL Certificate, Debug Test
Performance
- performance.md: High Response Time, 500 Response, Debug Test Multiple Scenarios, Partial Load, Selenium vs JMeter Load Testing, Test Works Locally but Not in BlazeMeter, Taurus Test Works Locally but Not in BlazeMeter, Test Won't Start
General
- general.md: Delete Non-Empty Project, Forbidden Domains, Chrome Extension Export JMX Failed, Support Feature Requests Submit, Support Feature Requests Track, Support Ticket Management
Integrations
- integrations.md: Integration New Relic Reporting
Security
- security.md: Apache Log4j2 Vulnerability
When to Use Each Reference
- API Monitoring: When troubleshooting API Monitoring test failures, Radar Agent issues, or SSL certificate problems
- Performance: When troubleshooting Performance test failures, high response times, or execution issues
- General: When troubleshooting general issues, project deletion, or support requests
- Integrations: When troubleshooting integration issues
- Security: When addressing security vulnerabilities
1---2name: blazemeter-troubleshooting3description: Comprehensive troubleshooting guide for BlazeMeter, covering API Monitoring, Performance Testing, general issues, integrations, and security. Use when troubleshooting for (1) API Monitoring issues (Radar Agent auth, SSL certificates, debug tests), (2) Performance Testing issues (high response time, 500 errors, partial load, tests not starting), (3) General issues (delete non-empty project, forbidden domains, Chrome Extension export failures), (4) Integration issues (New Relic reporting), (5) Security issues (Apache Log4j2 vulnerability), (6) Support requests and tickets, or any other troubleshooting tasks.4metadata:5 source: https://skillmd.com/skills/blazemeter/blazemeter-troubleshooting6---78# BlazeMeter Troubleshooting910Comprehensive troubleshooting guide for resolving issues in BlazeMeter.1112## Overview1314This skill covers troubleshooting for API Monitoring, Performance Testing, general issues, integrations, and security. It includes diagnostic steps, common solutions, and support resources. Effective troubleshooting requires systematic diagnosis and understanding of common issues and their solutions.1516## Quick Start17181. **Identify the issue**: Determine if it's API Monitoring, Performance Testing, or general192. **Check relevant reference**: Review the appropriate troubleshooting guide203. **Apply solutions**: Follow diagnostic steps and solutions214. **Contact support**: If issues persist, use support resources2223## MCP Tools Integration2425While troubleshooting is primarily done through UI and logs, you can use BlazeMeter MCP tools to access test execution information and results that may help diagnose issues:2627### Available MCP Tools2829- **Test Execution Information**: 30 - `blazemeter_execution` with action `read` - Read test execution details and status31 - `blazemeter_execution` with action `list` - List all executions for a test32 - Required args: `execution_id` (integer) or `test_id` (integer)33 - Returns: Execution details including status, errors, and results3435- **Test Information**:36 - `blazemeter_tests` with action `read` - Read test details and configuration37 - Required args: `test_id` (integer)38 - Returns: Test details including configuration that may help identify issues3940### When to Use MCP Tools4142- **Execution Analysis**: Use MCP tools to programmatically retrieve execution details and errors43- **Automation**: Integrate troubleshooting information into automation scripts44- **Monitoring**: Monitor test execution status and errors programmatically4546### Example Workflow4748**Getting Execution Details for Troubleshooting**:491. Use `blazemeter_execution` with action `list` to get execution IDs for a test502. Use `blazemeter_execution` with action `read` to get detailed execution information513. Review execution status, errors, and results to identify issues524. Use this information to diagnose and resolve problems5354## Reference Files5556### API Monitoring57- **[api-monitoring.md](skill-blazemeter-troubleshooting://references/api-monitoring.md)**: Radar Agent Auth Fail, SSL Certificate, Debug Test5859### Performance60- **[performance.md](skill-blazemeter-troubleshooting://references/performance.md)**: High Response Time, 500 Response, Debug Test Multiple Scenarios, Partial Load, Selenium vs JMeter Load Testing, Test Works Locally but Not in BlazeMeter, Taurus Test Works Locally but Not in BlazeMeter, Test Won't Start6162### General63- **[general.md](skill-blazemeter-troubleshooting://references/general.md)**: Delete Non-Empty Project, Forbidden Domains, Chrome Extension Export JMX Failed, Support Feature Requests Submit, Support Feature Requests Track, Support Ticket Management6465### Integrations66- **[integrations.md](skill-blazemeter-troubleshooting://references/integrations.md)**: Integration New Relic Reporting6768### Security69- **[security.md](skill-blazemeter-troubleshooting://references/security.md)**: Apache Log4j2 Vulnerability7071## When to Use Each Reference7273- **API Monitoring**: When troubleshooting API Monitoring test failures, Radar Agent issues, or SSL certificate problems74- **Performance**: When troubleshooting Performance test failures, high response times, or execution issues75- **General**: When troubleshooting general issues, project deletion, or support requests76- **Integrations**: When troubleshooting integration issues77- **Security**: When addressing security vulnerabilities78