Re: [Cake] Munin-Plugins

["Toke Høiland-Jørgensen" <toke@toke.dk>]

Ruben <ruben@vfn-nrw.de> writes:

> Hey Toke,
>
> Thanks for your fast response!
>
> Am 13.09.2018 12:27 schrieb Toke Høiland-Jørgensen <toke@toke.dk>:
>
>
>     Ruben <ruben@vfn-nrw.de> writes:
>
>     > Hey guys,
>     >
>     > I've already mentioned this in a response to dtaht on GitHub, but here
>     > again for everyone:
>     >
>     > I was wondering if it's possible to extend the tin statistics by
>     > packets for backlog.
>
>     Why do you need packets when there's already bytes?
>
> Easy: dtaht requested a packets graph with ecn marks, which is also
> packets, so backlog as bytes do not fit, backlog as packets do.
>
> The idea was to do a multi-graph which is one graph with combined
> stats for all tins and sub graphs for all tins.
>
> On the main graph a backlog in packets is available, but I would need
> to leave out the backlog for the tins, which is somewhat confusing.

Why not just do both backlogs in bytes?

>     > Also I haven't found details on the man page, but haven't looked in
>     > the code how exactly flows are defined for the new 2 level fair
>     > queueings.
>
>     A flow is a flow (hash on the regular 5-tuple). Unless you install
>     custom tc filters, in which case a flow could be anything you want it to
>     be...
>
>     > I would like to show hosts as well as flows in a graph, in the various
>     > states as summary as well as per tin. But hosts aren't shown in the
>     > statistics. But they could be helpful to see unexpected rises if
>     > someone is abusing the system.
>
>     Hmm, guess we could do "number of hosts per tin" accounting as well as
>     flows. But it would be bloating up the already bloated statistics. But
>     on the other hand, they are already quite bloated, so another pair of
>     stats maybe wouldn't make much of a difference?
>
>
> How important is a row more or less? It's quite verbose already (what
> I like) - as long as the number is available without much additionally
> work needed.

It's the additional complexity of recording the stats internally in cake
I'm worried about, not the extra lines of output :)

-Toke