Andrew Aylett's questions

I have a few servers that are monitored by munin, and fairly frequently one of a selection of units has a transient failure to read data. That gets me two emails, one telling me that all the values are unknown and the second five minutes later letting me know that everything's OK after all.

As far as I can tell, munin is functioning as designed here, but I'd like to know if there's any way to delay sending the initial 'unknown' alert for one update cycle, so transient unknowns aren't reported? All my current setup is achieving is training me to ignore the warning mails.

Failing that, is there any way to disable sending the 'unknown' alerts and their corresponding recovery alerts altogether?

I'm storing my salt sls files in a git repository, but I have the perennial problem that I can't verify my YAML represents a valid set of states that could be applied (I've also had difficulty validating my YAML -- that's much easier, though). Ideally, I'd like some way to verify my states on my workstation before committing them. Failing that, some way to check in a pre-receive hook so I can at least stop dodgy code from hitting the server.