If a monitoring object is configured to run at 8:30am, as an example, this is the time set for the monitoring object to be enqueued for data collection within the managed system.
If the data collection for the object is set to run in background within the monitoring object configuration UI, this means that it will be enqueued within the BPM_DATA_COLLECTION* background job in the managed system scheduled to run at this time.
As there can only be one instance of the BPM_DATA_COLLECTION_1* background job running in the managed system at a given time, if the previous instance of the job is scheduled to run and starts at 8:25am and takes 8 minutes to run due to large data volumes for collection or a large volume of objects enqueued for collection at that time, the data collection job scheduled to run at 8:30am will not start until 8:33am and the monitoring object scheduled to execute at 8:30am will not be executed until 8:33am.
The time set in the data collection schedule of the monitoring object configuration UI is the time at which the key figure is to be executed for data collection, not the time at which alerts are to be generated, and delays of a few minutes are typical in the alerting results. In the case of data collection and alerting for large data volume sets, the time between data collection start and alert generation can be even greater.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.