Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > Barracuda Web Filter Syslog Events Not Appearing in Console

Barracuda Web Filter Syslog Events Not Appearing in Console

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,429 Votes: 0 Revisions: 10


None of the syslog events from your Barracuda Web Filter are appearing in LEM.


  • All Barracuda Web Filters
  • All LEM versions


Barracuda Web Filter will send its syslog data to local4.log. It can't be configured to send data to a different facility. The presence of another device pointing to the same logging facility as the Barracuda triggers this issue. 

The Barracuda device and Cisco ASA device connector are set to receive and send data to local4.log by default. Since the Barracuda can't be adjusted, the other device(s) must be configured to send their syslog data to a different facility.


  1. Configure the Barracuda Web Filter to send its syslog data to the LEM appliance.
  2. Verify that the Barracuda Web Filter connector is enabled under Manage > Appliances.
  3. Reconfigure any other device sending its syslog data to local4.log (such as Cisco ASA devices) and their connectors in the LEM appliance so they point to an empty logging facility. This frees up local4.log for the Barracuda Web Filter.


Last modified