Gatling 200M3a - conf graphite.rootPathPrefix not being applied

Gatling (Open-Source)
1

Hi all,

New Gatling user here … Thanks for the great software!

I modified Gatling configuration for graphite rootPathPrefix to “string.gatling”

and modified Graphite’s storage-schemas.conf to use
pattern= ^string.gatling…*

However, in the Graphite page, I see the stats showing up as gatling.*

I expected that the rootPathPrefix value would be used as the metric path.

Not a big deal, but, I wanted to bring it to your attention.

Thanks
Sajjad

2

Did you properly uncommented the line (remove the leading #)?

3

graphite {
#light = false # only send the all* stats
host = “hostname.amazonaws.com”
port = 2003
protocol = “tcp” # Choose between ‘tcp’ or ‘udp’
rootPathPrefix = “string.gatling”
bucketWidth = 1024
#bufferSize = 8192
}

Where, “hostname” replaces the actual host name
and “string” replaces the actual string being used there.

4

OK, will investigate tomorrow (or Nicolas, maybe? :wink: )

5

Hi,

I did a quick test with Gatling 2M3a and I can’t reproduce your issue.

With the following configuration :

graphite {
#light = false # only send the all* stats
host = “192.168.56.101”
port = 2003
#protocol = “tcp” # Choose between ‘tcp’ or ‘udp’
rootPathPrefix = “geneva.gatling”
#bucketWidth = 100
#bufferSize = 8192
}

I was able to run a simulation called “Nicolas” and have the following stats showing up in graphite :

image.png

Can I ask you what is the exact “string” prefix?

6

Same thing here: can’t reproduce with string = “hello”

image.png

7

Thank you. It appears that I had mis-configured Graphite. My apologies.

Simplified the graphite storage-schema.conf and now, I am seeing the correct expected behavior.

Confirmed that tcpdump of traffic includes the correct string sent by Gatling. ( I should have done that before writing the original request).

image.png

8

No prob.
Thanks for the update.

cheers
Nicolas

image.png