We should move the reactor aliveness check from U1 into txstatsd, and report the reactor delay as a metric.
I don't think txstatsd is the appropriate place for this.
The reactor inspector should find its way into some twisted-utils project, or possibly, proposed to the Twisted project.
On Mon, Oct 31, 2011 at 9:04 AM, Ian Wilkinson <email address hidden> wrote: > I don't think txstatsd is the appropriate place for this.
Why not? We're generating metrics on the number of writers and readers. We can just as well report the reactor delay.
This was about the reactor inspector becoming a reusable module. Hence the mention of a separate project, and for it to be a dependency for txstatsd.
I think it good to employ it in txstatsd; I just think it better to have it as a separate dependency.
Bug watches keep track of this bug in other bug trackers.
I don't think txstatsd is the appropriate place for this.
The reactor inspector should find its way into some twisted-utils project, or possibly, proposed to the Twisted project.