Getting Data In

Rsyslog config not work - does not write to the file

josedgaravito
New Member

Hi Guys I have the following configuration lines in rsyslog but none of them helps me write to the destination file.

if $msg contains "Tampering" then /var/log/camaras.log

if $msg contains "Start one" then /var/log/camaras.log

if $fromhost-ip=='172.16.1.5' and ($rawmsg contains 'Tampering') then /var/log/camaras.log

if $rawmsg contains 'Tampering' then {action(type="omfile" File="/var/log/camaras.log") stop}

if $rawmsg contains 'Tampering' then /var/log/camaras.log

the example message is

[RTSP SERVER]: Start one session, IP=172.16.57.3 [RTSP SERVER]: Tampering Detected, IP=172.16.57.8

What can be?

thanks for your help

0 Karma

jkat54
SplunkTrust
SplunkTrust

Does the syslog user have permission to write to those destinations?

Any clues in /var/log/messages ?

0 Karma

josedgaravito
New Member

Hello, yes, the user has permissions, I currently have the configuration like this:

if $ fromhost-ip == '172.16.254.25' then /var/log/camaras.log

and it works fine, but I have more than three thousand devices and the configuration file becomes unmanageable

Thanks

0 Karma

DavidHourani
Super Champion

Hi @josedgaravito,

You will need to define a template and apply it based on how you wish to classify your logs. Are you trying to build one file per host ip or have all the data in the camaras.log file ? How exactly are you expecting your data to be stored ?

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...