20:02:23 <sumpfralle3> #startmeeting
20:02:23 <MeetBot> Meeting started Wed Jan  6 20:02:23 2021 UTC.  The chair is sumpfralle3. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:02:23 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
20:02:39 <sumpfralle3> It is Wednesday evening again - time for our weekly IRC meeting.
20:04:59 <bcg> 2.0.66 with unknown_limit fix?
20:06:37 * h01ger waves
20:06:59 <TheSnide> hi :)
20:07:44 <mdadm> CRITICALs: munin graph is 312.52 (outside range [:285]). -> http://guide.munin-monitoring.org/en/latest/reference/munin.conf.html#munin-conf -> munin.graph critical 1000 << will this get rid of the alert noted in the beginning of this line?  (only occurrs during heavy I/O / load)
20:07:55 <sumpfralle3> bcg: yes, I wanted to suggest this. I will do it now.
20:08:19 <bcg> thanks.
20:10:27 <sumpfralle3> just for the reference (regarding mdadm's question): he asked this in the "other" IRC channel and I redirected him here.
20:10:56 <sumpfralle3> My answer there was: you can override the warning/critical values in the configuration section of that node (on the master): http://guide.munin-monitoring.org/en/latest/reference/munin.conf.html#field-directives
20:11:42 <mdadm> yep that's me just wanted to verify the syntax, I checked the plugin-directive URL as well, I've added that into my conf file, will see if that fixes it tonight thx
20:15:21 <sumpfralle3> great!
20:15:44 <sumpfralle3> TheSnide: I just tagged and pushed 2.0.66. You are welcome to upload it :)
20:17:32 <sumpfralle3> mdadm: ah, I somehow overlooked the remaining part of your comment here. Sorry :)
20:18:12 <TheSnide> will do
20:18:26 <sumpfralle3> I guess, you would put "fieldname.critical 1000" below the problematic "node" entry in your /etc/munin/munin.conf (or below /etc/munin/munin-conf.d).
20:19:11 <sumpfralle3> mdadm: the "fieldname" is the one, which exceeds its value. Try "munin-run PLUGIN" to get it.
20:23:04 <mdadm> Example message -> https://pastebin.com/Eg7zVj5B
20:23:14 <mdadm> It is the actual graphing process itself exceeding 300 sec due to high load
20:26:56 <mdadm> Almost need a `global' or munin-runtime warn/critical alert
20:27:16 <mdadm> CRITICALs: munin graph < not finding a correlating fieldname for this
20:31:18 <sumpfralle3> mdadm: it seems to be the "munin_stats" plugin and the field "graph". Thus "munin_stats.graph.critical 1000" should be the proper line, I guess.
20:31:30 <sumpfralle3> Please report back - I will include this as an example in the documentation.
20:32:00 <mdadm> got it, will see if it recurs tonight, added in there, thanks!
21:15:19 <sumpfralle3> #endmeeting