PH_Rule_Avail_PH_19
Enabled
Detects that Worker input event queue is very large (greater than 100MB). This indicates that the workers are falling behind in handling events and cannot keep pace with the rate at which workers are sending events.
9
Performance
FortiSIEM
No Technique Specified
Internal
FortiSIEM Self Monitoring
Correlation
See if any FortiSIEM process is taking up excessive CPU/memory resources on Worker nodes. Consider adding more workers and/or adding resources to workers. Make sure there are no bottlenecks in storage insertion.
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
600 seconds
If the following defined pattern/s occur within a 600 second time window.
AOLargeEventQueue
This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.
This is the query logic that matches incoming events
eventType = "PH_EVT_HANDLER_EVT_QUEUE_WARNING"
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
hostName
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT (*) >= 1 AND AVG(totBytes64) > 104857600
This section defines which fields in matching raw events should be mapped to the incident attributes in the resulting incident.
The available raw event attributes to map are limited to the group by attributes and the aggregate event constraint fields for each subpattern
hostName = AOLargeEventQueue.hostName,
totBytes64 = AOLargeEventQueue.AVG(totBytes64)