Note that for any query type that has not been asked (the num is 0) this is not
displayed. This leads to somewhat unexpected "unprocessed" rrd files. I don't think
this really matters, but it is somewhat confusing.
Looking through daemon/stats.c I did not see where this behaviour of not printing
the types with 0 hits comes from. I'd like to print those are 0's to keep them in
the rrdtool/munin graphs.
I noticed this while chasing down some munin-graphs that were hanging after what
seemed to be the unlinking of the lock file. Did anyone else see this behaviour
of munin-graph eating up 99% cpu?
Note that for any query type that has not been asked (the num is 0) this is not
displayed. This leads to somewhat unexpected "unprocessed" rrd files. I don't think
this really matters, but it is somewhat confusing.
Looking through daemon/stats.c I did not see where this behaviour of not printing
the types with 0 hits comes from. I'd like to print those are 0's to keep them in
the rrdtool/munin graphs.
Unbound does not print type=0, at daemon/remote.c:760
You can also, maybe better, solve this at the munin script, in
unbound_munin_ at if $1=="config" and then the by_type)) p_config .. ;;
where you have the for x in `grep "^num.query.type" $state`; do ;;
which you want to be a full list.
I noticed this while chasing down some munin-graphs that were hanging after what
seemed to be the unlinking of the lock file. Did anyone else see this behaviour
of munin-graph eating up 99% cpu?