This enable/disable INTEGER controls whether an event log entry is generated every time a packet hits this filter, and its own description notes that enabling it also forces the hit-counter status on. This matters operationally because event logs give an admin a timestamped audit trail of exactly when a security rule fired, not just a running total, which is useful for correlating a filter hit with a specific incident. An admin investigating a break-in attempt on VI 4 facing the Frame Relay uplink would enable this so each blocked packet also produces a log entry for later review.