Getting Data In

Splunk License Violations Best practises?

SS1
Path Finder

Hi Everyone,

What are the best practices to follow in the event of 90% license usage? Can we take any precautionary measures so that the license usage doesn't reach maximum? I don't think disabling the specific index is a good idea since it might cause issues.

 

 

Labels (2)
0 Karma

gcusello
SplunkTrust
SplunkTrust

HI @SS1,

if you're working at the 90% of your license, in my opinion, you have to do the following things:

  • at first see if the 90% is a peak or usual,
  • thess plan your work to understand if you have to add more sources or not,
  • then analyze your logs to understand which are the sources more relevant,
  • between them you should understand if you can discard something of these logs (e.g. some EventCodes in wineventlogs) remembering that if you discard something, you cannot use it! (for more infos about discard logs see at https://docs.splunk.com/Documentation/Splunk/8.0.6/Forwarding/Routeandfilterdatad#Filter_event_data_...),
  • if the discarded logs are relevant (so you reduced your license consuption), continue with your normal work, if instead you cannor reduce quite your license consuption, the only choice is to buy additional license,
  • in the past, a violation blocked Splunk searches (not indexing), now instead you have only the annoying message "you're in violation..." but no blocks,
  • anyway a violation is when you exceed your license for five times, not only one.

Ciao.

Giuseppe

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!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...