We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm not sure what has changed. I had this working up to last week.
Currently when I run a JMeter test, no data appears in the influx database. These are my settings
testName: test nodeName: JMeter influxDBHost: influxDBPort: 8086 influxDBUser: jmeter influxDBPassword: influxDBDatabase: retentionPolicy: autogen samplerList: .* useRegexForSamplerList: true
I can run the test and load is produced. There are no errors in the JMeter log, however not data seems to be transferred to influx DB.
I've tried using the default Influx Backend Listener and that seems to work fine.
Any advice is appreciated
The text was updated successfully, but these errors were encountered:
I am facing similar issue, I check the DB
below tables are populated with data but all Http requests are having status as Failure in table samples.
requestsRaw samples testStartEnd total virtualUsers
@soulchips , you were able to resolve the issue ?
Sorry, something went wrong.
No branches or pull requests
I'm not sure what has changed. I had this working up to last week.
Currently when I run a JMeter test, no data appears in the influx database.
These are my settings
testName: test
nodeName: JMeter
influxDBHost:
influxDBPort: 8086
influxDBUser: jmeter
influxDBPassword:
influxDBDatabase:
retentionPolicy: autogen
samplerList: .*
useRegexForSamplerList: true
I can run the test and load is produced. There are no errors in the JMeter log, however not data seems to be transferred to influx DB.
I've tried using the default Influx Backend Listener and that seems to work fine.
Any advice is appreciated
The text was updated successfully, but these errors were encountered: