Getting Data In

Syslogging via tailing a logfile

NK_1
Path Finder

Ideally, we'd like to modify the application to syslog directly for indexing by Splunk.
In the meantime, is there any adverse effect to tailing the last line of the log, and invoking logger to syslog?


#!/bin/bash
tail -n1 -F -q MyLogFile.log | \
while read -r line ; do
# send to local syslog
logger -t MyAppTag -p local1.info `echo "$line"`
done

Tags (4)

Linegod
Path Finder

We replace syslog with rsyslog, which can send arbitrary files to syslog.

rsyslog imfile

NK_1
Path Finder

That would involve installing the forwarder on every host we use. Our hosts are already set up to forward local syslogged events to be indexed by Splunk, and I am trying to leverage that mechanism.

0 Karma

numentajpb
Engager

I'm curious, why not have splunkforwarder just monitor the logfile directly?

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 ...