On 2012-01-20T23:32:46-0000, Tel <li...@lnx-bsp.net> wrote: > There's another (minor) problem which is to say that returning 0 in > a situation where no IO has occurred is a lie, should return NaN or > NA but if you read the Munin protocol specification (see link below) > it claims "Output must be integer or decimal number," so the have no > provision for a plugin saying "hey, this value does not exist right > now" and that's strange because the RRD system does support NaN for > missing values -- but that's a bigger problem for another day. > > http://munin-monitoring.org/wiki/protocol-config
Actually, you can give a value of "U" to mean NaN, or "I have no value right now". I think it's documented on the munin trac wiki somewhere, but I can't find it right now, and it's hard to search for. Regarding this bug, I'm thinking we should disable autoconf for this plugin, since it is marked "legacy", and its functionality is duplicated by diskstats. http://munin-monitoring.org/changeset/3003 -- Kenyon Ralph -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin "IO Service Time" graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
