Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
This property determines how many events are processed simultaneously in each job, impacting the speed and efficiency of event management. |
| What area does it affect? |
Event Management |
| What does the default mean? |
The default value is "1", which sets the baseline numeric behavior for this property. |
| When should you review it? |
Review this property when optimizing event processing performance or during high event volume periods. |
Out of the box property record
Raw metadata from the property record.
| Property name |
evt_mgmt.max_objs_in_alert_query |
| Sys ID |
59577055937223006a4731f6357ffbb4 |
| Type |
integer |
| Application |
Global |
| Default value |
1 |
| Description |
Number of events to process in bulk during each event processing job. |
| Updated |
2020-03-16 14:46:39 |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... for the late arrivals or slow business rules defined on the em_alert table. Default = 2000 msec. Used when alerts and events are processed one at a time (when the evt_mgmt.max_objs_in_alert_query property is not defined or is set to 1). evt_mgmt.impact_calculation.alert_copy_delay_when_alerts_are_processed_in_ba The delay after creating or updating an alert, before it is used for impact calculation and grouping. Used to compensate ...
Related properties
More in evt_mgmt
Other properties in the same namespace.
All 117 properties in evt_mgmt →