Tim Connors <report...@rather.puzzling.org> writes: > Also, there seems to be missing documentation about how to configure > the warning threshold in plugins.conf. I've tried various permutations of > [diskstats] > env.latency.*warning [-300:1] etc, but nothing has yet worked for me.
The method for configuring warning and critical levels for each field is is up to the individual munin plugin. Some plugins support it, some don't and I don't think many of them use a common method to do so. The only other place to specify it with some concistency is on the munin master. Wildcards are not used, as far as I know, and likely not with "env.<something>" in plugins.conf. The "env.*" is a way to make outside data available for the plugins. "env.foo bar" sets an environment variable called "foo", with the value "bar" for the plugin to use. You'd have to read the plugin to check if it uses any environment variables. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
