Real‑time Monitoring System for JMeter Performance Testing Using InfluxDB, Prometheus, Grafana, and Docker‑Compose

Introduction – During load testing with JMeter, the default HTML report is only available after the test finishes, lacking real‑time visibility of metric spikes. Adding Basic Graphs plugins is possible but incurs heavy performance overhead, so a dedicated monitoring system is required.

Monitoring System Components – The stack consists of InfluxDB (a Go‑based time‑series database), Prometheus (open‑source monitoring and alerting toolkit), and Grafana (web‑based visualization platform) which together provide real‑time metric collection, storage, and dashboarding.

Implementation Principle – JMeter’s Backend Listener streams metrics to InfluxDB; Grafana reads from InfluxDB (or Prometheus) and displays the data on configurable dashboards. The workflow is: collect → store → visualize.

Deployment Options – The system can be set up on Windows for small‑scale tests or, preferably, on Linux using Docker‑Compose for easier management, reproducibility, and isolation of services.

Docker‑Compose Implementation

1. docker-compose.yml – defines services for Grafana, Prometheus, InfluxDB and their configurations, ports, volumes, and restart policies.

2. Directory structure – includes separate folders for Grafana configuration, dashboards, and Prometheus configuration.

3. Configuration files – sample snippets for Grafana’s config.monitoring , Prometheus’s prometheus.yml , and environment variables.

Example docker-compose.yml excerpt:

version: '3'
services:
    grafana:
        image: grafana/grafana:latest
        container_name: jk_grafana
        ports:
            - 3000:3000
        env_file:
            - ./grafana/config.monitoring
    prometheus:
        image: prom/prometheus:latest
        container_name: jk_prometheus
        ports:
            - 9090:9090
        volumes:
            - ./prometheus:/etc/prometheus
            - ./prometheus/prometheus.yml:/etc/prometheus/prometheus.yml:ro
    influxdb:
        image: influxdb:1.8.10
        container_name: jk_influxdb
        ports:
            - 8083:8083
            - 8086:8086
            - 8090:8090
        volumes:
            - ./influxdb/db:/var/lib/influxdb
            - ./influxdb/config/influxdb.generated.conf:/etc/influxdb/influxdb.generated.conf

To start the stack, run docker-compose up -d in the directory containing the compose file.

Configuring the Monitoring System

1. JMeter Backend Listener – Install jmeter-prometheus-plugin-0.6.0.jar , configure the listener with the InfluxDB write endpoint (e.g., http://x.x.x.x:8086/write?db=jmeterDB ).

2. InfluxDB setup – Create the database jmeterDB inside the InfluxDB container using the Influx CLI.

docker-compose exec influxdb bash
influx
> CREATE DATABASE jmeterDB
> SHOW DATABASES

3. Grafana data source – Add InfluxDB as a data source in Grafana, point it to the jmeterDB database, and import or create dashboards to visualize JMeter metrics.

4. Running the test – Execute JMeter in non‑GUI mode with the Backend Listener enabled; metrics are streamed to InfluxDB and appear in Grafana dashboards in real time.

Conclusion – By integrating JMeter with InfluxDB, Prometheus, and Grafana via Docker‑Compose, testers gain continuous insight into performance metrics, enabling rapid detection of anomalies and more reliable load‑test results.