Getting Data In

Is it possible to have a separate log file for errors occurring only within a specific Splunk App?

mariasudolska
New Member

Hi all,

I am posting this question because I was not able to find the answer so far. I know that Splunk logs a lot about itself and that there are various log files in $SPLUNK_HOME/var/log/splunk. However, I would like to know whether it is possible to keep a separate log file that would contain only errors (and other messages) related to using a specific Splunk App, e.g. Search & Reporting or any custom developed App. Or in other words: when I develop a Splunk App, is it possible to specify something like an App error log?

If it is not possible at all, then the only option to search for errors would be to write specific searches for index=_internal and filter out the relevant information, is that right?

Thanks a lot.

0 Karma
1 Solution

nickhills
Ultra Champion

Many Splunk apps write log lines into their own files for scripted/modular inputs, custom commands a lookups.
If your building your inputs in Python you can use the SDK to do the same
http://dev.splunk.com/view/logging/SP-CAAAFCN

If my comment helps, please give it a thumbs up!

View solution in original post

0 Karma

nickhills
Ultra Champion

Many Splunk apps write log lines into their own files for scripted/modular inputs, custom commands a lookups.
If your building your inputs in Python you can use the SDK to do the same
http://dev.splunk.com/view/logging/SP-CAAAFCN

If my comment helps, please give it a thumbs up!
0 Karma

mariasudolska
New Member

Many thanks for the answer.

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