realtime newsfeed monitoring?

Russ Allbery rra at
Wed May 24 09:45:39 UTC 2000

Ilya Etingof <ilya at> writes:

> Yes, innreport is a great tool however it is supposed to be ran daily so
> it doesn't provide realtime statistics. The innfeed.status & inn.status
> gather realtime data however they do not provide a history of changes
> hence I can't plot a graph using these files.

> Is there already a tool for gathering and plotting newsfeed data in the
> realtime? I'm thinking of something similar to flowdelay but plotting
> figures on per newsfeed basis and in greater details.

I've seen a few different channel feeds that maintain things like graphs
of where you're getting messages from, but beyond that I'm not aware of
anything like this.

> Otherwise, what would be the most appropriate way of gathering a table
> of newsfeed values from innd and innfeed? Perhaps, I would need
> arts-offered, arts-accepted, arts-refused, arts-rejected values and
> maybe the same params expressed in bytes rather then in articles.

> I've looked into "checkpoint" records innd and innfeed place into log
> file as of the possible source for my graph.  The only inconvinience I
> notice about it so far as that innd puts checkpoint statistics for every
> peer connection separately rather then a summary for all connections to
> arbitrary peer like innfeed does.

This should be fairly easily fixable by accumulating them with your tool;
innd's architecture isn't particularly well-suited for doing the summary
itself (status.c does this to some degree, but it's a bit brute-force
about it and it still doesn't remember statistics across closes of

If I were you, I'd be inclined to use the existing log information as a
basis for generating these statistics.  I'd be interested to see what you
come up with if you end up with anything that seems to work; it sounds
like a useful idea.

Russ Allbery (rra at             <>

More information about the inn-workers mailing list