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!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...