Throttling of Alarm Data Sent to Enterprise Manager

The Enterprise Manager Agent Web application installed on every system server that communicates with the Enterprise Manager regarding any configuration changes or alarm messages for the relevant server. on each server in the enterprise runs two jobs that transmit alarm data to the Enterprise Manager. These jobs include:

• AlarmJob - This job runs every 30 seconds. This job transmits the active alarm data that displays in the Alarm Dashboard, as noted in How Active Alarm Data is Sent to the Alarm Dashboard.

• AlarmSyncJob - This job runs every 30 minutes. This job transmits data that ensures the Alarm Dashboard remains synchronized with the current state of active alarms on each server. For details, see Alarm Synchronization and the Alarm Dashboard.

The Enterprise Manager Agent application on each managed server Server that is managed by the Enterprise Manager application. employs an alarm data throttling mechanism. This throttling mechanism ensures that the amount of alarm data sent to the Enterprise Manager application does not overload the system resources and affect server performance.

This alarm throttling mechanism does the following:

• Ensures that the AlarmJob and the AlarmSyncJob never run simultaneously. Only a single thread is allocated for both alarm jobs. If one job is running, the other alarm job cannot start until the running job completes its work.

• When a job completes its work, there is a 500-millisecond delay before the job runs again, or before the other job starts.

  For example, if AlarmJob can run two separate times to transmit all active alarm data to the Enterprise Manager. The job runs once, then waits a half-second, then runs a second time. Similarly, if AlarmJob is running when AlarmSyncJob is scheduled to start, there is a half-second delay after AlarmJob completes before AlarmSyncJob starts. The two jobs do not run concurrently.