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?

Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...