topic Re: Splunk License Violation - Investigate additional data for last 24hrs in Installation

Splunk License Violation - Investigate additional data for last 24hrs

gagandeep_arora — Wed, 25 Oct 2017 15:27:10 GMT

Last night the license usage passed 95%, which used to float around 60-65%. There would definitely be additional host or logs started ingesting data yesterday.

Is there a way I can trace down if any source or host is added within last 24hrs or if I can find who impacted the license usage?

Re: Splunk License Violation - Investigate additional data for last 24hrs

cpetterborg — Wed, 25 Oct 2017 16:41:49 GMT

"It depends" - Always a good answer. If you don't have lots of SQUASHED data, then the following searches can help you out.

To find out what index has the most data, use the following search:

index=_internal source=*license_usage.log type="Usage" | stats sum(b) as total by idx | eval totalGB=total/1024/1024/1024 | fields idx, totalGB | sort -totalGB

To find out which host is the big offender:

index=_internal source=*license_usage.log type="Usage" | eval h=if(len(h)=0 OR isnull(h),"(SQUASHED)",h) | eval s=if(len(s)=0 OR isnull(s),"(SQUASHED)",s) | eval idx=if(len(idx)=0 OR isnull(idx),"CM",idx) | stats sum(b) as b by h, idx | eval GB=(b/1024/1024/1024) | sort -GB | fields - b

Squashed data is what you get when there are too many entries in a given time period for Splunk to separate things out by host. Usually this isn't a problem until you get LOTS of forwarders.

Re: Splunk License Violation - Investigate additional data for last 24hrs

gagandeep_arora — Thu, 26 Oct 2017 16:52:45 GMT

This was not something specific I was looking for but this was interesting,, Cheers..

Re: Splunk License Violation - Investigate additional data for last 24hrs

cpetterborg — Sat, 28 Oct 2017 17:54:43 GMT

My answer was in reply to your:

or if I can find who impacted the license usage

Re: Splunk License Violation - Investigate additional data for last 24hrs

koshyk — Sun, 29 Oct 2017 16:45:57 GMT

be careful on one aspect as "license" is calculated based on _indextime, but when you search data on the host it is _time (eventtime) which might span multiple days.