Monitoring Splunk

Indexer disk utilisation critical

Martin583
Explorer

I have a warning on Monitoring console of my cluster master, that my Index disk utilisation is critically high. I have a 30 day retention policy set on all my indexes however the disk utilisation is continuing to rise.

In monitoring console - Indexing - indexes and volumes - instance - Indexes table.

I am seeing Data Age vs Frozen age that I have data much older than my retention policy.

To me that would suggest I have hot buckets that have not rolled over perhaps due to data ingest latency or incorrect timestamps preventing the roll over.

Could this be the source of my increasing disk utilisation?

My understanding is that if a rolling restart of my Indexers occurred then all buckets would roll over, however I know there has been a restart within the time frame indicated by the data age.

Labels (1)
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 ...