Getting Data In

Best Practise: Different Log Sources

FRoth
Contributor

How do you handle different source types?

Do you create an index for every type of source i.e. an index called "unix" for all the logs coming from Linux, Solaris and Unix systems and an index "windows" for all Windows clients an servers.

That was my first impulse ...

Or do you receive everything into a "main" index and separate everything in the searches by appropriate search statements?

0 Karma
1 Solution

gkanapathy
Splunk Employee
Splunk Employee

Generally, put things in the same index unless you have a specific reason to do otherwise and understand how any why you would want it. The general reasons might include:

  • Differential data retention
  • Access control
  • Performance

Note that while the above are possible reasons or concerns, it doesn't mean that simply using more indexes is a solution, e.g., putting every single source into a different index will often make performance worse, or might make it better.

View solution in original post

0 Karma

gkanapathy
Splunk Employee
Splunk Employee

Generally, put things in the same index unless you have a specific reason to do otherwise and understand how any why you would want it. The general reasons might include:

  • Differential data retention
  • Access control
  • Performance

Note that while the above are possible reasons or concerns, it doesn't mean that simply using more indexes is a solution, e.g., putting every single source into a different index will often make performance worse, or might make it better.

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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...