[prev in list] [next in list] [prev in thread] [next in thread] 

List:       grinder-use
Subject:    Re: [Grinder-use] GraphiteLogFeeder: charting Grinder performance
From:       Travis Bear <travis_bear () yahoo ! com>
Date:       2011-12-06 20:15:44
Message-ID: 1323202544.43606.YahooMailNeo () web114711 ! mail ! gq1 ! yahoo ! com
[Download RAW message or body]

Thomas,=A0

Thanks for checking out GLF. =A0Let me know if you have any troubles with i=
t. =A0Am I understanding you right, you are sending=A0real-time=A0Grinder d=
ata to your (modified) StatsD? =A0If so, I'd like to hear more details abou=
t how you are getting that done. =A0(StatsD messaging code inside your Grin=
der scripts?)=A0WRT using StatsD in our Java environment, we certainly coul=
d have gone down that road. =A0But in our case there was existing JMX data =
we wanted to track anyway, so it made sense for us to track all that stuff =
via jmxtrans.=A0

Cheers,

-Travis



----- Original Message -----
From: Thomas Falkenberg <falkenbt@googlemail.com>
To: grinder-use@lists.sourceforge.net
Cc: =

Sent: Tuesday, December 6, 2011 9:46 AM
Subject: Re: [Grinder-use] GraphiteLogFeeder: charting Grinder performance =
data in Graphite

This is great, I just incorperated grinder with graphite a couple of
days ago. I wrote an e-mail to the list las weekbut it didn't get
through, I had to re-subscribe first. (The e-mail was about accessing
TPS stats within The Grinder, just found the same point on your page:
"add support in the grinder for the agent process to report TPS and
other info normally sent to the console to StatsD instead of (or in
addition to) the console UI.")

We're going the real-time approach with a modified statsd (again,
etsy) in the middle (between The Grinder and graphite). Statsd buffers
the information and sends several metrics to graphite within the
default interval of 10 seconds (count, upper, lower, mean, upper 90
percentile). We forked it in order to get different intervals
reported(1s, 10s, 60s):=A0 https://github.com/fec/statsd
The packets are sent to statsd via UDP, so it's fire and forget and
not dependent on availability of statsd/graphite.

This approach would not work with existing logfiles, so your solution
is a perfect addition.

Thank you for sharing, I will give it a try this week since we have
the perfect use case: In one project The Grinder is running in an
environment with no access to our graphite instance. So offline
post-test analysis is the only way to go.

Btw. we're a also a java shop and I see no reason why statsd/graphite
should not be used here. You might also want to take a look at tools
like logstash and graylog2 which we are starting to use. Logstash can
also be used to send extracted logfile information to statsd
(http://logstash.net/docs/1.0.17/outputs/statsd).

-Thomas

> For a while, I've been interested in using Graphite to visualize Grinder =
performance data. =A0Graphite has several attractions. =A0In addition to be=
ing able to interactively build many different chart types, it can be used =
to manage and chart other types of data as well; most notably, OS-level and=
 application-level performance metrics. =A0I recently got a little time to =
work on this, and have released a basic tool named Graphite Log Feeder that=
 reads the data in Grinder logs and feeds it into a running instance of Gra=
phite.
>
> https://bitbucket.org/travis_bear/graphitelogfeeder/
>
>
> Here's a writeup which includes a bit more detail on Graphite Log Feeder,=
 some example graphs, and a more general sense of how it fits in the overal=
l environment where I work.
>
> http://blackanvil.blogspot.com/2011/12/integrating-grinder-performance-da=
ta.html
>
>
>
> Thanks!
>
>
> -Travis
>
>
> -------------------------------------------------------------------------=
-----
> Cloud Services Checklist: Pricing and Packaging Optimization This white p=
aper is intended to serve as a reference, checklist and point of discussion=
 for anyone considering optimizing the pricing and packaging model of a clo=
ud services business. Read Now!
> http://www.accelacomm.com/jaw/sfnl/114/51491232/
> _______________________________________________
> grinder-use mailing list
> grinder-use@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/grinder-use

---------------------------------------------------------------------------=
---
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point o=
f =

discussion for anyone considering optimizing the pricing and packaging mode=
l =

of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
_______________________________________________
grinder-use mailing list
grinder-use@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/grinder-use


---------------------------------------------------------------------------=
---
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point o=
f =

discussion for anyone considering optimizing the pricing and packaging mode=
l =

of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
_______________________________________________
grinder-use mailing list
grinder-use@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/grinder-use
[prev in list] [next in list] [prev in thread] [next in thread]