CSCvo36212 - Reporting Message Filter dont show correct information

[spacenet_support]

Hello,

is there any news on this bug? We ran into this one after an AsyncOS upgrade and need the Message Filter Reporting.

Thanks in advance

Christian Schulz

[tsilveruits]

We are experiencing this issue, as well, even with the 12.5 releases (ESA and SMA). Our ESAs on 12.5.0-066 are matching on all sorts of messages, which is also reflected in the reporting for message filter activity. For instance, in the mail logs on our syslog host, there are no matches for message filter X. But on the SMAs the reporting for the 12.5 ESAs shows over 760 K matches for message filter X and the message tracking reflects this, as well. Examining the results in message tracking that should match filter X, I confirm that they do not match message filter X. Since our message filters often match on multiple criteria, I thought perhaps message tracking/reporting might be incorrectly matching on one or any criteria. If there is a bug reporting on incomplete matches, this might account for the inaccuracies.

[tsilveruits]

There is also bug CSCvi27520, "[ESA] Message filter report will count for each action of a message," which is related to this issue. I can confirm that AsyncOS 12.5.0-636 for virtual SMAs is affected. Our ESAs are running 12.5.0-066, and they are reporting this issue as well. For instance, via the GUI on the ESAs, go to Monitor > Message Filters and the totals do not align with actual matches for each message filter.

This issue is not only affecting our reporting metrics, but our ability to use message tracking to effectively troubleshoot issues. We must now resort to grepping logs on our syslog host, which is slower than using the SMAs, which could benefit from speed improvements, as well.

[tsilveruits]

Good news! The 12.5.1-031 maintenance deployment release seems to have resolved the bug.