Splunk Enterprise

License Warning

jkamdar
Communicator

In last couple of days, I have seen few license alerts:

This pool has exceeded its configuration poolsize=5GB bytes. A CLE warning has been recorded for all members. 

Then I tried to look at the License Usage report by host and I see couple of issues:

1. My indexer itself it using up most of the license. 

2. My indexer is listed twice, one in all capitol (SPLUNK-SERVER1) and 2nd one, regular FQDN (splunk-server1.mydomain).

For the 1st issue, checked more and saw /var/log/audit/audit.log is the culprit. What can I do to limit it?

For the 2nd issue, I guess, I have spelled out server name differently.  Where can I check other than /opt/splunk/etc/system/local/server.conf?

Thanks for your help. 

Labels (1)
0 Karma

PickleRick
SplunkTrust
SplunkTrust

Check the usage by sourcetype, index... Then check what kind of logs these are. We don't know yohr environment, we don't know your data.

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!

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...

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

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...