I want to check a file for a certain pattern, so the LOG check seemed like the natural choice. I got it configured and started to see some red statuses come in for hosts where the pattern matched, but then about 35 minutes later, they all go green though nothing has changed on the client.
Looking at the msgs column on a host, I can see that the “Full log” is empty. Is this the expected behavior? The file I'm checking for patterns in is not really a log file and rarely changes. Maybe the test is designed to discard lines it's already processed after 30 minutes?
So is there a way to check something like a config file for invalid patterns? Do I need to write a custom script? Writing and distributing a custom test is not a big deal to me at all. What I dread is adding yet another column to the web view, which is why I was looking for a built-in test to use.
-- Rob McBroom <http://www.skurfer.com/>