From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id E6DA83B2A4 for ; Thu, 13 Sep 2018 06:27:26 -0400 (EDT) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1536834445; bh=aob2Zowxt972dUS0MkBppq/GYQVOxbklDoL8ps++DwA=; h=From:To:Subject:In-Reply-To:References:Date:From; b=lF0KpzDol6aLzJW585PbKo6MMgHEr3+ey1qWlMBYxO2LiBQSiBX7D1xK9hQ0aD3ti T2R75g+7csMhb53hxfVtiWSF3YfgjrXfk7LwURzHGJJWisnchy/BBkffFUmM0UXFL3 4loWi4mRn+JVw8pp5pJ8wf3V1ydYLTBChulFJPpcMTBowEO7Cip2Zj4toeH+yVJVDQ szccxjElNebvZ3cXVFYj4BaI4j2zbRjfDNY6EPt3yaiKoy7UKFbP2sdT5nsFpz03Ki b3ehr9rVdNUmvglGMlx+lMirvULXoYOkRsPDaDlfwk3iAATs+gnVp5IzA5HYcaOFbQ SjKJqxyYbksrA== To: Ruben , cake@lists.bufferbloat.net In-Reply-To: References: Date: Thu, 13 Sep 2018 12:27:24 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87pnxhheur.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Cake] Munin-Plugins X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2018 10:27:27 -0000 Ruben 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? > 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? Does anyone else have an opinion on this? -Toke