Mailing-List: contact issues-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@jmeter.apache.org
From: bugzilla@apache.org
To: issues@jmeter.apache.org
Subject: [Bug 61122] GraphiteBackendListenerClient hierarchical sampler name
Date: Thu, 25 May 2017 16:29:48 +0000
Message-ID: <bug-61122-58895-PLxA3DV0nz@https.bz.apache.org/bugzilla/>
In-Reply-To: <bug-61122-58895@https.bz.apache.org/bugzilla/>
References: <bug-61122-58895@https.bz.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Auto-Submitted: auto-generated
MIME-Version: 1.0
archived-at: Thu, 25 May 2017 16:29:58 -0000

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

--- Comment #2 from Brahma <brahmad@gmail.com> ---
Thanks for the reply.

With InfluxDB Client I am running into other road blocks. Granted, it might=
 be
that I have to learn a little more about Grafana to overcome those.
Nevertheless, I will explain the problem.

With the InfluxDB Client, they have changed the measurement name to a fixed
property in the Client. With Graphite, the measurement name in the influx
database would be something like "rootPrefix.SamplerName.a.ok" (we set
rootPrefix to something like PE-1114). In Grafana, I can simply choose "Ali=
as
By =3D $1" to get the SamplreName in the legend. Switching to InfluxDB Clie=
nt,
the measurement name comes out as a static "measurement" (like, "PE-1114").=
 We
end up with just one measurement in the database no matter how many sampler=
s I
have in the test. The actual sampler name is recorded in the tag value for =
the
tag key =3D "transaction". Now, I am not sure how to read that transaction =
string
and parse it with a period separator to pass it to the legend text in the p=
lot.

I hope this is clear.

The other option is for me to wait until an example dashboard is created by
Grafana or some other expert with InfluxDB Client / JMeter combination for a
test.

Thanks.

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