Splunk Search

How do I debug this Health status error?

Keerthi
Path Finder

Hi, Am new to splunk and will be needing assitance in the health status of splunk.How to debug the below errors in red.

Keerthi_0-1674048253826.png

 

Labels (1)
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @Keerthi,

if you click on the red flag, there's a description and a link to documentation to understand the problem.

Anyway, you can see the skipped searches in the monitoring Console, Searches.

The problem usually is one (or both) of these:

  • you have not suffient resources (CPU and RAM, especially CPUs),
  • your storage isn't sufficientely performant (Splunk requires at least 800 IOPS, better 1200).

 About Tailreader, you should understand (using the Monitoring Console Healtcheck) what's the sourcetype and if there's some error in parsing.

Ciao.

Giuseppe

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!

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...

Manage Datasets and Connections in Catalog on Splunk Cloud Platform

Set Up Data Where You Use It Catalog already helps teams find and understand data across Splunk indexes, ...

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