On Wed, Oct 31, 2012 at 9:52 PM, Eric Holscher wrote:
> A couple obvious places:
>
> Latency to backend systems. So, any time that I call out to my cache
> backend or database, keep track of round trip latency of those.
>
> Full system latency. So, From the time a request enters the URL routing
>
We use django-statsd in conjunction with statsd and rely upon
inserting monkey patches into the stack. Having some hooks in Django
that can be used to monitor that stuff would be really useful.
Currently we've got patches for redis, sql queries, cache queries,
template parsing and rendering along
A couple obvious places:
Latency to backend systems. So, any time that I call out to my cache
backend or database, keep track of round trip latency of those.
Full system latency. So, From the time a request enters the URL routing
until it gets sent back to a client.
Request counts. Keep track
If you use/monitor/graph metrics (the idea, not Coda's library, but that
would be good, too), I'd like to hear from you.
What sort of metrics, under what implementation, would be useful to you
operationally?
--
You received this message because you are subscribed to the Google Groups
"Django de
