Monitoring Splunk

After upgrading a single Splunk Enterprise instance type from 2vCPU to 4vCPUs, why isn't Splunk seeing additional CPUs?

Euphrates
Engager

I have a single Splunk instance on an Amazon AMI RHEL box. I upgraded instance type from 2vCPU to 4vCPUs, and Splunk for some reason cannot see the additional CPUs. However, it did pick up the memory upgraded (8 to 16).

I have yet to find an answer to this online.

Tags (2)
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 ...