Getting Data In

Why are there field extraction issues when indexing Barracuda Web Security Gateway via syslog?

pl2345
Path Finder

We've been indexing logs from our Barracuda Web Security Gateway via our syslog server with a default sourcetype of syslog. It works ok but doesn't pull out all the fields and field extraction is hit or miss, as the logs aren't consistent. I've tried the various Barracuda apps and TA's on splunkbase, both current and archived, with no success. Has anyone else solved this problem?

Labels (2)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...