Influxdb Reporter - Issues Troubleshooting

[sergiodegrazia]

I have been trying to use the new Influxdb Reporting feature with no luck, mainly due to the absence of errors and logs for this tool.
I have created a YML file as below (I have redacted the IP address of my load test servers and InfluxDB server).

execution:
- distributed:
  - XXX.XX.XX.X
  - XXX.XX.XX.X
  scenario: Load_Test

scenarios:
  Load_Test:
    script: example.jmx

modules:
  influxdb-reporter:
    host: XXX.XX.XX.XXX
    port: 8086
    username: 
    password: 
    database: taurus
    measurement: jmeter
    summary: true
    percentiles: true
    send-data: true
    send-interval: 1s

Executing this YML does not send details into my InfluxDB instance, but no errors appear in the bzt.log file so it is tricky to identify the reasons.

I have created a 'taurus' database to collect the results.
The InfluxDB has no authentication.
The firewall is set to allow all traffic from the load test servers on port 8086.

Is anyone able to help? Is my YML well-formatted? Can this reporting feature run on a distributed load test?

[matus-gazo]

Try adding "application" field as described here: #1706

I am working on documenting that field AND making it optional, but waiting for release sign off this week.

[matus-gazo]

Try removing the empty username/password fields if they are really empty. Other than that we'd need logs to move further

[sergiodegrazia]

Hi again, same results unfortunately with no username and password fields (see YML below). I am also attaching the bzt.log file generated by this last execution but I can't see any 'influx' details aside from the YML filename.

execution:
- distributed:
  - XXX.XX.XX.X
  - XXX.XX.XX.X
  scenario: Load_Test

scenarios:
  Load_Test:
    script: example.jmx

modules:
  influxdb-reporter:
    host: XXX.XX.XX.XXX
    port: 8086
    database: taurus
    measurement: jmeter
    summary: true
    percentiles: true
    send-data: true
    send-interval: 1s

bzt.log

[matus-gazo]

Hi, I don't have much experience with this yet since we just added this very recently as a community addition, maybe the author @RaphC could help here. I see in the log no aggregation is done, maybe that is the issue (ie logging "Bypassing consolidation because of single result" ). In addition, you are still missing "application" property in influxdb-reporter section.

Another thing you could try is adding reporting section like this (untested):

reporting:
  - final-stats
  - console
  - influxdb-reporter

[sergiodegrazia]

Got it now! Please find the working YML file below.
This configuration correctly sends details to my InfluxDB database.

Thanks for your help!

execution:
- distributed:
  - XXX.XX.XX.X
  - XXX.XX.XX.X
  scenario: Load_Test

scenarios:
  Load_Test:
    script: example.jmx

reporting:
  - final-stats
  - console
  - influxdb-reporter

modules:
  influxdb-reporter:
    host: XXX.XX.XX.X # influxdb address (default: localhost)
    port: 8086 # port (default: 8086)
    database: taurus # the datasource name
    measurement: jmeter # the measurement name
    summary: true # overall samples count and percent of failures
    percentiles: true # send average times and percentiles
    send-data: true # enable/disable the sending
    send-interval: 1s # send data each n-th second
    application: example-28-03-2023

[RaphC]

Hi,

You're right. The plugin must be explicitely enabled on reporting section. Agree with you @matus-gazo : I'm not fully convinced with the application attribute. Maybe a default value (the scenario name or id ?)...
I also noticed a doc error I'll fix soon.

@sergiodegrazia : a feedback will be welcome ;). Sure some enhancements are needed.

[matus-gazo]

Released 1.16.22 with doc updates and making the application tag optional. Hope that helps!

[sergiodegrazia]

Thanks for your help!