Monitoring Splunk

Splunk server crush

sbarinov
Path Finder

We had our Splunk server stopping by itself two days in a row.

I am trying to find the reason but I cannot find anything related in /opt/splunk/var/log/splunk.

Could someone please advise where I should be looking for the related logs?

Labels (2)
0 Karma

sbarinov
Path Finder

As it was found, there was a kernel out of memory error.

We are running Version:7.2.5 on 12GB RAM.

I am wondering what we can do about that.

I will try to limit the amount of records in alert searches since we have them running all the time.

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

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...