Getting Data In

Data randomly stopped indexing full xml file

tccooper
Explorer

As of midnight, 1/15/2020, we have about 3.5 Indexes which are no longer indexing the entirety of the XML files being monitored on the UF. I have looked through the splunkd.log files and searched throughout the _internal indexes to see if anything obvious is sticking out, but that's not the case. The XML files are being parsed up through the header and sometimes to the first line, but the remainder does not show up in the system. Everything was working fine up until now. Any help would be appreciated!

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