I have more than once found a Munin multi graph set being rendered unreadable by single graph peaking 100 times over the rest of the graphs in the set. The classical example is the Linux (over)committed memory graph on a system leaking memory, peaking in the 100GB area, making the other system memory graphs that are playing along about 1-4GB almost invisible:
One could of course put a hard limit in the RRD file, in my example, at the pysical memory in the machine in question, but this means that I loose oversight by hiding what’s probably a problem. A better solution is to split the graph out, that is, prevent it from graphing in the common memory set, and put it in custom graph. Consider the following munin.conf snipplet:
[my.server.tld]
address my.server.tld
memory.committed.graph no
memory_committed.graph_title Committed Memory
memory_committed.update no
memory_committed.graph_category system
memory_committed.graph_order \
memory=my.server.tld:memory.committed
This produces the following graphs:
Problem solved.
Thanks so much! This is exactly what i was looking for.
Great tip, works perfectly.
Thanks!
This is exactly what I need. Damn that commited memory graph.
Thank you, thank you, thank you.
Thanks a lot!
How could i do this with two or more values (for example Coretemp 1,2,etc.)?
Adam, you can do this for as many graphs in the plot that you want. Something like this, maybe:
[my.server.tld]
address my.server.tld
foo.something.graph no
foo.else.graph.no
foo_something_else.graph_title Something Else
foo_something_else.update no
foo_something_else.graph_category somecategory
foo_something_else.graph_order \
something=my.server.tld:foo.something \
else=my.server.tld:foo.else
could anyone help for …unbound graphs splits….