cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
btlyric
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 1 of 2

control handshake failed log message

Jump to solution

Is there a recommended way to specifically ignore certain handshakefailed (or other internally-generated) errors?

For example, I have a rule set that handles coaching for a specific destination. This site uses SSL. There are certain client programs which will attempt to hit that site, but since they don't have any functionality to handle the coaching page, the handshake fails. The failure is logged.40,000+ times/day.

I was thinking something like this:

Message.TemplateName equals "handshakefailed" AND

User-Agent equals X AND

URL.DestinationIP is in range x.x.x.x/y

Action: Continue

Event: Set Log Handler = no logging

I started by trying to set the log handler to one that doesn't log anything, but that wasn't successful because there's nowhere before the Default log handler to insert the rule so that it gets activated.

So what I've implemented is a rule in the base Default log handler that uses the original criteria, but uses action Stop Cycle.

This appears to work. Any reason that I shouldn't do this?

Thanks!

1 Solution

Accepted Solutions
asabban
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 2

Re: control handshake failed log message

Jump to solution

Hello,

using stop cycle on top of the logs is a suitable way to prevent MWG from logging specific requests. When I want to exclude something I usually do it the same way 🙂

Probably it would be an additional benefit to file an SR with support and analyze why the error is thrown so often?

Maybe it would be another option to add a stop ruleset rule to the coaching rule set that disabled coaching for the user-agents that fail. You don't need to skip log file writing for errors that don't happen.

Best,

Andre

View solution in original post

1 Reply
asabban
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 2

Re: control handshake failed log message

Jump to solution

Hello,

using stop cycle on top of the logs is a suitable way to prevent MWG from logging specific requests. When I want to exclude something I usually do it the same way 🙂

Probably it would be an additional benefit to file an SR with support and analyze why the error is thrown so often?

Maybe it would be another option to add a stop ruleset rule to the coaching rule set that disabled coaching for the user-agents that fail. You don't need to skip log file writing for errors that don't happen.

Best,

Andre

View solution in original post

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community