InfluxDB integration for Gatling

Send load test metrics to InfluxDB.

Introduction

The InfluxDB integration allows Gatling Enterprise Edition to send load-test metrics - such as response times, throughput, and error rates - directly into an InfluxDB time series database. Once enabled, performance data from Gatling Enterprise Edition is sent to InfluxDB, where it can be correlated with infrastructure and application metrics already collected in your InfluxDB database.

With this integration in place, you can:

  • Monitor Gatling scenarios alongside server-level KPIs (CPU, memory, network) in a single dashboard.
  • Investigate performance issues more effectively by overlaying load-test metrics on traces, logs, and resource utilization charts.

Compatibility

This integration supports any backend compatible with the InfluxDB Line Protocol (ILP) over HTTP. This includes InfluxDB 1, 2 and 3, but also other products such as QuestDB.

Prerequisites

  • A valid Authorization header
  • Your InfluxDB database (we support InfluxDB 1, 2 and 3)
  • A Gatling Enterprise Edition account with private locations that can connect to the InfluxDB database.

Install the InfluxDB integration

The InfluxDB integration requires installation steps on your private locations control plane.

In your control-plane configuration, in the section system-properties, add:

control-plane {
  locations = [
    {
      system-properties {
        "gatling.enterprise.influx.api.authorization" = "<your Authorization header>"
        "gatling.enterprise.influx.api.url" = "<your InfluxDB API url>"
        "gatling.enterprise.influx.useProxy" = "<true to use the same proxy as for the Gatling API>" # optional, default is false
      }
    }
  ]
}
// InfluxDB 1
Token <YOUR_API_TOKEN>

// InfluxDB 2
Token <YOUR_API_TOKEN>

// InfluxDB 3
Bearer <YOUR_API_TOKEN>
// InfluxDB 1
http(s)//host:port/api/v3/write_lp?db=mydb&precision=s

// InfluxDB 2
http(s)//host:port/api/v2/write?org=myorg&bucket=mybucket&precision=s

// InfluxDB 3
http(s)//host:port/write?db=mydb&precision=second

Uninstall the InfluxDB integration

To remove the link between Gatling Enterprise Edition and InfluxDB, remove the lines containing gatling.enterprise.influx in your control-plane configuration.

Tables schema

Gatling Enterprise Edition creates the following schema in your InfluxDB database:

Common Tags
run_id
test
team
load_generator
Table Specific Tags Fields
gatling_enterprise_users scenario start_count,
end_count,
max_concurrent
gatling_enterprise_requests scenario,
group,
request
count
gatling_enterprise_responses scenario,
group,
request,
status
count,
time_mean,
time_min,
time_p50,
time_p95,
time_p99,
time_p999,
time_max
gatling_enterprise_responses_by_code scenario,
group,
request,code
count
gatling_enterprise_group_durations scenario,
group,
status
count,
time_mean,
time_min,
time_p50,
time_p95,
time_p99,
time_p999,
time_max
gatling_enterprise_group_cumulated scenario,
group,
status
count,
time_mean,
time_min,
time_p50,
time_p95,
time_p99,
time_p999,
time_max
gatling_enterprise_dns runId,
test,
team,
load_generator,hostname,status
count,
time_mean,
time_min,
time_p50,
time_p95,
time_p99,
time_p999,
time_max
gatling_enterprise_connections remote bandwidth_usage_sent,
bandwidth_usage_received,
tcp_open_count,
tcp_close_count
gatling_enterprise_tcp_states remote,
state
count
gatling_enterprise_tcp_connects remote,
status
count,
time_mean,
time_min,
time_p50,
time_p95,
time_p99,
time_p999,
time_max
gatling_enterprise_tls_handshakes remote,
status
count,
time_mean,
time_min,
time_p50,
time_p95,
time_p99,
time_p999,
time_max
gatling_enterprise_cpu user,
sys
gatling_enterprise_mem ram_max,
ram_used,
heap_max,
heap_committed,
heap_used

Edit this page on GitHub