https://bz.apache.org/bugzilla/show_bug.cgi?id=65164

            Bug ID: 65164
           Summary: Send data to influxDB failed when measurement is
                    replaced by Property or Variable
           Product: JMeter
           Version: 5.3
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Main
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: JMETER 5.4.1

Hi,

I found a bug when JMeter send data to InfluxDB.
I use this configuration in the simple scenario

influxdbMetricsSender 
org.apache.jmeter.visualizers.backend.influxdb.HttpMetricsSender
influxdbUrl
http://${__P(InfluxDB_HostName,)}:${__P(InfluxDB_HostPort,)}/write?db=TEST
application     TEST_PLAN
measurement     ${__P(Name,)}
summaryOnly     false
samplersRegex   (^\d+).+
percentiles     99;95;90
testTitle       ${__P(InfluxDB_TestTitle,)}
eventTags       


JMETER IN GUI MODE
The scenario run correctly and I found data in db TEST

JMETER NO GUI MODE
I have a problem only with parameter measurement
measurement     ${__P(Name,)}


The parameters : 
influxdbUrl with this values is correct (GUI / NO GUI)
http://${__P(InfluxDB_HostName,)}:${__P(InfluxDB_HostPort,)}/write?db=TEST

testTitle with this values is correct (GUI / NO GUI)
${__P(InfluxDB_TestTitle,)}


application with this values is correct (GUI / NO GUI)
TEST_PLAN (or parameter or value)

BUT,

I try to use measurement with  ${__P(Name,)} and ${Name_1} : NOT OK in non gui 

2021-03-02 17:30:10,520 ERROR o.a.j.v.b.i.HttpMetricsSender: Error writing
metrics to influxDB Url: http://localhost:8086/write?db=TEST, responseCode:
400, responseBody: {"error":"partial write: unable to parse
',application=TEST_PLAN,transaction=internal
minAT=0,maxAT=0,meanAT=0,startedT=0,endedT=0 1614702610451000000': missing
measurement dropped=0"}

In conclusion, it's impossible to execute a scenario in non gui mode with
parameter measurement replaced by a Property from Backend Listener.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to