Deployment Architecture

Splunk CRC check

ankithreddy777
Contributor

I have one log file at particular path on server1. I am forwarding it to splunk index=index1.
I have another log file on server2, whose path and name of file is same as that of log file on server1. I am forwarding it to same index=index=1.

But I can see only the log file ingested from server1 but not from server 2.

As per CRC check it will check first 256 bytes. But this check is at forwarder level or the indexer level.
If it is at forwarder level, why it is not picking the same log on different server/forwarder.
If it is at indexer level, how to handle this kind of situation to ingest logs on different servers with same name, path and same first 256 bytes. Here I cannot use crcSalt as my logs are rotating.

0 Karma

woodcock
Esteemed Legend

The CRC check is at a forwarder level (more accurately, at a splunk-instance level, since you can run more than one splunk instance on a forwarder). Start with splunk list monitor and them move to btool to check your configurations if it does not show up as an input.

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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...