If non-zero, hits are being dropped due to an overloaded pipelined.

When this value is not zero, the indicated number of TCP packets were dropped from the pipelined process due to overloaded conditions.

Analysis: This value must not be zero. You can specify the maximum permitted size for individual TCP packets through the Tuning Parameters in the Interface tab.

• See DNCA Web Console - Interface Tab.

If some hits are being dropped, the overload condition can be caused by too many privacy rules or too much complexity in them.

• See Downloading Privacy Configuration.

When this statistic is summed across all DNCA instances, the result indicates that the total number of hits lost due to exceeding the specified TCP packet size. To calculate the % of total, divide this value by sum of the Captured before hit processing statistics for all DNCA instances, which is the total hits count for delivery to the pipeline queue.

• See Stats per Instance.

Increasing the number of pipelines under the pipeline tab can help alleviate this issue.

• See Pipeline Settings.