Getting Data In

Multiple sourcetypes from single directory source

jordans
Path Finder

SQL Server puts both the ERRORLOG and SQLAGENT logs in the same directory. When Splunk automatically assigns a sourcetype, it can end up with some random sourcetypes over time (e.g. ERRORLOG-95).

I have been assigning aliases to these random sourcetypes, but that is not a scalable solution.

How can I either:
- assign all ERRORLOG* sourcetypes to an alias
- manually specify that all ERRORLOG files get one sourcetype and the SQLAGENT logs in the same directory get another sourcetype

Thank you

Tags (2)
1 Solution

gkanapathy
Splunk Employee
Splunk Employee

The easiest way is to just use wildcard specifications in your input files, e.g.:

[monitor://c:\logs\SQLAGENT*.LOG]
sourcetype = sqlagent

[monitor://c:\logs\ERRORLOG*.LOG]
sourcetype = sqlerror

[monitor://c:\logs\]
sourcetype = sqlother

I added an entry to catch other logs, but that is optional. Splunk will work fine and chose the most specific (longest) matching monitor, provided you're collecting using version 4.1 or higher forwarders or indexers. In older versions, you can accomplish the same things (with a slightly more complexity) using a companion props.conf with [source::] stanzas to set the sourcetype on the forwarders. Finally, you can always use an index-time TRANSFORM, but that is the most complex and most resource-intensive method.

View solution in original post

gkanapathy
Splunk Employee
Splunk Employee

The easiest way is to just use wildcard specifications in your input files, e.g.:

[monitor://c:\logs\SQLAGENT*.LOG]
sourcetype = sqlagent

[monitor://c:\logs\ERRORLOG*.LOG]
sourcetype = sqlerror

[monitor://c:\logs\]
sourcetype = sqlother

I added an entry to catch other logs, but that is optional. Splunk will work fine and chose the most specific (longest) matching monitor, provided you're collecting using version 4.1 or higher forwarders or indexers. In older versions, you can accomplish the same things (with a slightly more complexity) using a companion props.conf with [source::] stanzas to set the sourcetype on the forwarders. Finally, you can always use an index-time TRANSFORM, but that is the most complex and most resource-intensive method.

jbsplunk
Splunk Employee
Splunk Employee

You can do a transform to change the sourcetype for ERRORLOG at index time. Instructions for this can be found at this splunk blog:

http://blogs.splunk.com/2010/02/11/sourcetypes-gone-wild/

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...