Getting Data In

historic data not ingesting

ankithreddy777
Contributor

I ingested the logs data to Splunk Uat servers, it got ingested all data including the historic data, But when I ingested same data in to the Splunk Production servers, only current data is ingested. Historic data is not ingested. Is there any settings that should override to ingest historic data. I am not using "ignoreolderthan" in my inputs.conf. My forwarder currently sending data to two groups of indexers.

0 Karma

chillao123
Explorer

Did you check size restrictions?

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Does the production Splunk have a different data retention policy? Perhaps historic data is being immediately frozen. Just how old is "historic"?

---
If this reply helps you, Karma would be appreciated.

ankithreddy777
Contributor

normal Frozen age for index is 562 days as seen in distributed console of CM. apart from this is there any saperate retention policy for historic data. I have all data in splunk from the point I started ingesting.

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