M3 (or its newer version which you should be using – M3v3) can do pretty much. However it can’t do anything.
M3 is good at timing execution of commands, apply simple parsing and upload the data to Monitis. Allowing you as the SysAdmin (and end-user of M3) to easily shape and design Custom Monitors for your system improving overall system uptime and stability.
Many times this is indeed what happens when trying to monitor different applications. The simple process of ‘Execution -> Parsing -> Reporting’ gets the job done. What happens when it doesn’t?
Well, I’ll tell you what happens – you are left a bit puzzled and think you’ll have to implement the Custom Monitors API which Monitis provide. True – until not long ago.
M3v3 bring you ‘Raw Commands’ capability in its last version.
Read the full post