List,
I have configured a fair number of jobs (scheduled tasks, cron jobs, etc)
so that they report their exit status as an OpenNMS event. The event can
then be used to trigger notification when a job fails.
One issue that I am facing, especially in the Windows world, is that some
jobs may fail to start because the password of the user they run as has
been changed or has expired.
To handle these cases I'd like to setup an automation so that if an event
does not re-occur within, say, 24h another notification is sent out. I have
looked into vacuumd and it looks like the right tool for the job, but
before I go about reinventing the wheel I thought that perhaps I should try
asking on the list.
Ideas, suggestions are most welcome.
TIA,
Umberto
I have configured a fair number of jobs (scheduled tasks, cron jobs, etc)
so that they report their exit status as an OpenNMS event. The event can
then be used to trigger notification when a job fails.
One issue that I am facing, especially in the Windows world, is that some
jobs may fail to start because the password of the user they run as has
been changed or has expired.
To handle these cases I'd like to setup an automation so that if an event
does not re-occur within, say, 24h another notification is sent out. I have
looked into vacuumd and it looks like the right tool for the job, but
before I go about reinventing the wheel I thought that perhaps I should try
asking on the list.
Ideas, suggestions are most welcome.
TIA,
Umberto