On 03/15/2013 08:20 AM, Thiago H de Paula Figueiredo wrote:
On Fri, 15 Mar 2013 09:45:11 -0300, Joachim Van der Auwera
<joac...@progs.be> wrote:
On 03/15/2013 01:26 PM, trsvax wrote:
Monitoring is something Tapestry lacks, Etsy's StatsD
seems to be popular.
Something quite similar (though not distributed) is easy using
geomajas-project-profiling, see
http://blog.progs.be/453/profiling-live-application.
What about https://github.com/joshcanfield/tapestry-monitoring, from
Josh Canfield?
StatsD is nice and easy to work with. We're using it at work. I even
have it running at home. From StatsD we dump into Graphite. There is no
reason why a developer couldn't easily implement their own little chunks
of code to send metrics to a service that would push them out to StatsD.
You could easily rewrite the timing filter from the demo to write to
StatsD instead of a logger.
We also use collectd to perform JMX monitoring, and from there into
Graphite. There are several other tools to pull from JMX and push to
Graphite or elsewhere.
Josh's monitoring module looks interesting. Since it's JMX, you can use
any of the tools used to extract JMX, including collectd.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
