Splunk Enterprise

Troubleshooting

whitecat001
Explorer

Hello
I am getting this warning and the sample data looks like this


02-22-2012 17:01:12.280 +0000 WARN DateParserVerbose - A possible timestamp match
(Wed Feb 22 17:01:12 2012) is outside of the acceptable time window. If this timestamp is correct, consider adjusting MAX_DAYS_AGO and MAX_DAYS_HENCE. Context="source::/var/opt/jira/log/atlassian-jira-security.log|host::syn|atlassian_jira|remoteport::47375"

 

Labels (1)
0 Karma

PickleRick
SplunkTrust
SplunkTrust

Either you indeed have very strange data (from more than 10 years ago?) or you have badly onboarded sources and date is wrongly parsed.

0 Karma

whitecat001
Explorer

Is there anything i can do to make the error go away?

0 Karma

PickleRick
SplunkTrust
SplunkTrust

Yes. Verify your sources and their config in Splunk. Without more information we can't tell you anything more than that.

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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...