Splunk Deployment Monitor Reporting Excessive GB Values for Licence Usage

[hanoc]

I have installed the splunk deployment monitor app to attempt to pull some stats on what our license usage patterns are.

One issue I see right off the bat is that in 'Licence Report' -> 'Daily License Usage for Last 60 Days' -> Ordered 'by License Pool' it tells me we indexed 130GB which is ok, however this is above our license limit of 120GB yet I don't have any license warnings and other searches I have subsequently made myself show different values.

Is the used search including non licensed data usage such as for the internal indexes?

[jtrucks]

In using pre-5.x clients, the deployment monitor app could report the volume of indexed data incorrectly. We stopped using the deployment monitor because we still have a pile of ancient clients sending data.

Try this:

earliest=-1month@d latest=@d+1h index=_internal source=*license_usage* type=RolloverSummary | eval _time=_time-1800  | convert timeformat="%m/%d/%Y" ctime(_time) as day | eval GB=b/1024/1024/1024 | stats sum(GB) by day

I put this in a dashboard and look at it every day.

You could get this from Splunk on Splunk (S.o.S.), as well.

[jtrucks]

Turns out, I didn't have it in a code block. I did have * around license_usage, but they didn't display right. Sorry about that.

[rmorlen]

Nice info. I modified it a bit:
earliest=-1month@d latest=@d+1h index=_internal source=*license_usage* type=RolloverSummary | eval _time=_time-1800 | convert timeformat="%m/%d/%Y" ctime(_time) as day | eval GB=b/1024/1024/1024 | stats sum(GB) by day

[araitz]

What version of Splunk and what version of deployment monitor are you using? We have done our best to avoid counting internal indexes in the tally, but we could have made a mistake.