A JMeter listener plugin that sends test results to InfluxDB v2.0 for real-time monitoring and visualization in Grafana.
JMeter InfluxDB2 Listener Plugin is an open-source backend listener for Apache JMeter that sends performance test results to an InfluxDB v2.0 database. It solves the problem of real-time test monitoring by enabling live dashboards in Grafana, providing insights into aggregate reports, errors, and response details as tests run.
Performance test engineers and DevOps teams who use JMeter for load testing and need real-time visualization of test results through InfluxDB and Grafana.
Developers choose this plugin because it offers a seamless integration with the latest InfluxDB v2.0, provides configurable performance tuning to handle high loads, and includes a comprehensive Grafana dashboard for immediate, interactive analysis of test metrics.
Influx DB v2.0 listener plugin for Apache JMeter. Provides the possibility to see the online dashboard (aggregation table, errors, the response body of failures).
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Includes a pre-built Grafana dashboard (ID 13644) for live monitoring of throughput, response times, and errors, replicating JMeter's reporting with enhanced interactivity.
Saves detailed data like response codes, error messages, and response bodies for failures, allowing deeper analysis than standard JMeter outputs.
Offers configurable batch size and flush intervals to optimize data sending, with logs showing elapsed import times for fine-tuning under different loads.
Features a configurable error threshold to stop data import and prevent out-of-memory errors, as highlighted in the 'Important notes' section.
Only supports JMeter 5.6.3 and requires Java 11 or higher, which can lock out users on older or newer JMeter/Java versions.
Demands detailed configuration of InfluxDB buckets, tokens, and performance parameters like flush intervals, adding operational overhead and a steeper learning curve.
Introduces latency from batch sending and memory usage, requiring careful monitoring and tuning to avoid issues, as admitted in the 'Sending metrics performance tuning' notes.