Skip to end of metadata
Go to start of metadata

The job EEM_DOWNTIME_DAEMON is scanning the next 30 minutes if downtime is scheduled of any managed system used by any script.

If a workmode representing a downtime is found the job EEM_DOWNTIME_DAEMON has a spool output and there you see exactly which workmode of which system has been found:

Additionally two jobs are scheduled. The first one (job name Stop Scripts of <technical scenario>; report   AI_EEM_STOP_SCRIPTS_OF_TS) is scheduled when the workmode begins and stop all scripts of this technical scenario. The second job (job name Start Scripts of <technical scenario>; report AI_EEM_START_SCRIPTS_OF_TS) is scheduled when the workmode ends and starts all scripts of this technical scnenario.

Global Settings

The global settings for all EEM scripts if a workmode represents a downtime can be made in SOLMAN_SETUP step 2.7 (workmode Settings):

 
Whenever a workmode for a managed system is scheduled where the flag Monitoring enabled is not set the scripts are stopped.

Another example: You want the scripts to be automatically stopped when ever the managed/monitored system is in Maintenance, has a Planned Downtime or in Non Business Hours you can use this setting:

 

Script specific settings

For each script it can be specified if the global workmode settings should be ignored or not.
 
Example:The flag 'No Downtime' is set for the script 'EEM Selfcheck Script'. When the workmode 'Planned Downtime' is scheduled for one of the systems of the scenario 'SELF MONITORING' the script is not stopped. I.e. it will be executed on the Robots.
However, the script overall status will have a "Planned Downtime" (404) status.

Alert specific settings

For each script it is possible to supress that performance alerts are triggered depending on the workmode of the managed system. This allows that script executions are available in Monitoring and Reporting but performance alerts are not raised for a system with a special workmode.

  • No labels