I am using the most recent snapshot dated May 9th.
This message is replicated for all our files that are above and below the threshold:
/oradump/cdp/logs/CDPServer.6.out File was modified 45 seconds ago - should be <0
client-local.cfg:file:/oradump/cdp/logs/CDPServer.8.out hobbit-clients.cfg:FILE "%^/oradump/cdp/logs/CDPServer.8.out" yellow mtime<300
We have about 20 files some are above the 300 second threshold and some below, regardless ALL are yellow.
'should be <0', is this a bug, tough requirement though?
From the documentation:
mtime>MIN.MTIME mtime<MAX.MTIME checks how long ago the file was last modified (in seconds). E.g. to check if a file was updated within the past 10 minutes (600 seconds): *mtime<600*. Or to check that a file has NOT been updated in the past 24 hours: *mtime>86400*.
This makes sense to me, alarm if the file was updated less than 10 minutes ago, alarm if the file has not been updated in 24 hours?
They way it appears to work based on my entry above (mtime<300) is, alarm if mtime>300, or stay green as long as mtime<300. It would be preferable, if it worked like the documentation, I think that reads better.
For the 'msgs' column, is there a way to turn 'Full Log' off so it doesn't make the web page look less than stellar? Or add some wrapping code. I realize I am using the latest alpha, but I know you are looking for some feedback.
We really do appreciate these new columns it will eliminate quite a number of custom scripts on various hosts, thank you.