lqss11 / jmeter-telegraf-influxdb-grafana Goto Github PK

Throughout this code you can simply run a jmeter test using several powerful technologies allowing you to easily analyze and monitor your test plans in real time in an automated way (docker-compose).

This repo provides several features to the user such as:

• Load test scenario creation: In this part we are going to create different environments consisting of multiple IP addresses (containers)
• Persist test results: It consists of persisting each test data in a database in addition to a log file and result csv file.
• Environments monitoring: It is about monitoring the containers of host docker engine and load test metrics.
• Dockerize the stack: Will give us the ability to run tests easier, and not to worry much about the environment we are working on.

Starting the test will only take few steps: -Clone the repository in:

$ git clone https://github.com/LQss11/Jmeter-telegraf-influxdb-grafana.git

-The following command will run our docker-compose file which in fact will build our specified images with context then create and run our containers in the same network:

$ docker-compose up --build

-Then connect to jmeter's container and chose whether you want to run the load test in a single machine (run.sh) or in a distributed mode (run-dist.sh):

docker exec -it jmeter bin/bash ./Scripts/run.sh

docker exec -it jmeter bin/bash ./Scripts/run-dist.sh

In case telegraf has an issue collecting data to influxdb make sure to give permissions to docker.sock inside the container:

docker exec -it telegraf sh -c "chmod 777 /var/run/docker.sock"

This project was made by a combination of coll tools such as:

1. .env file contains all variables used for the docker-compose.yml file
2. You can have more information about the telegraf.conf file which is responsible on setting up the specific data we want to collect from our docker host. for more information click here.
3. In this project we used an influxdb version that uses Next-Generation InfluxDB 2.0 Platform but with SQL instead of FlexQL since the majority of grafana's dashboards are available with SQL not FlexQL.