Bug 63478 - BackendListener: Allow using runtime variables
Summary: BackendListener: Allow using runtime variables
Status: NEW
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 5.1.1
Hardware: PC All
: P2 enhancement (vote)
Target Milestone: JMETER_5.2
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-31 07:00 UTC by sergiy.iampol
Modified: 2019-05-31 08:02 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sergiy.iampol 2019-05-31 07:00:28 UTC
trying to use BackendListener and observed runtime variables are not written to influxDB.

Properties, on the other hand, can be written to influx.

So I can separate test results by some ID by setting measurement=${__P(SOME_ID)}

What I'm looking for is a splitting results by thread group name, as I may have up to several dozens of them within the same test.

Tried to use following:
TAG_scenarioName=${__threadGroupName}
TAG_someJmeterVar=${SOME_JMETER_VAR}
TAG_someJmeterVarAsGroovy=${__groovy(vars.get("SOME_JMETER_VAR"),)}
eventTags=${__threadGroupName}
testTitle=${__threadGroupName} (this one makes less sense, but still..)

and none of those works

Those are works:
TAG_injectorName=${__machineName()}
TAG_predefinedVar=${USER_DEFINED_VAR} (I believe this is thanks to https://bz.apache.org/bugzilla/show_bug.cgi?id=57962)

So as I understand problem is with runtime variables only. Is it possible to make runtime variables accessible for the BackendListener? Or maybe there is some workaround for such case?
Comment 1 sergiy.iampol 2019-05-31 08:02:04 UTC
p.p.s. also tried use a separate BackendListener per each thread group (with TAG_scenarioName=TG_Name_N) but seems like only one BackendListener can be used within one testplan.