All Apps and Add-ons

TA-Tomato: parsing log file vs UDP

ys
New Member

I'm configuring TA-Tomato to process logs from DD-WRT router.  I've successfully configured data input to listen on UDP/514 port with source type "tomato" and it receives logs from my router just fine.  However, this only works for basic logs detailed logs showing both accepted and dropped packets overwhelm the router.  I want to capture detailed logs.

My router has no problem logging detailed logs into a file, so I've configured router to write log to a directory I've made accessible on the network.   I've mounted this directory on the Splunk server.

When I changed the data input to a file, logs are not correctly parsed.  I only see "tomato:dnsmasq-dhcp" sourcetypes, yet I've confirmed other logs are present in the file.  Why are they not picked up?

Labels (1)
Tags (2)
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

What Is Splunk? Here’s What You Can Do with Splunk

Hey Splunk Community, we know you know Splunk. You likely leverage its unparalleled ability to ingest, index, ...

Level Up Your .conf25: Splunk Arcade Comes to Boston

With .conf25 right around the corner in Boston, there’s a lot to look forward to — inspiring keynotes, ...

Manual Instrumentation with Splunk Observability Cloud: How to Instrument Frontend ...

Although it might seem daunting, as we’ve seen in this series, manual instrumentation can be straightforward ...