Getting Data In

Best practice when data is imported wrong?

kfelts68
Explorer

What would be the best practice / standard operating procedure when data is imported wrong into Splunk? I imported a webserver server error logs into splunk and did not select the correct date / time.

See this thread - https://answers.splunk.com/answers/771988/time-column-and-event-date-are-different.html

Now that the data has been imported, and I know it is wrong, should the data be removed? I am not even sure how to remove data from splunk?

Or, rename the server error log, reupload, and search only the new error log name?

This is a windows 10 system using free Splunk.

0 Karma

woodcock
Esteemed Legend

If it is in an index all by itself, just delete the whole index. If not, then use the ... | delete command to hide it from searches (it will still be there because data in a Splunk index is immutable, but it will not show in any search results). The worst thing that you can do is to do nothing: do not leave junk in Splunk.

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