Monitoring Splunk

Detailed Reporting on License Costs per Event

shocko
Contributor

Guys, is it possible to break down licnse impact on the following:

  • Per Index
  • Per SourceType
  • Per Source
  • Per Event in index i.e. all events with EventCode=302

??

Labels (1)
0 Karma
1 Solution

zacharychristen
Path Finder

It is possible to get a breakdown of index, sourcetype, and source. However, for a certain EventCode can be tricky. First to get the usage for index, sourcetype, source, or even host, try the following:

index=_internal sourcetype=splunkd component=metrics group=<group_to_filter> series=*

where you can set the group field to be:
1. per_index_thruput
2. per_sourcetype_thruput
3. per_host_thruput
4. per_source_thruput

and (optionally) you can choose a specific series. For example, if you use the group per_index_thruput the series would be the index i.e. series=windows.

Full example:

index=_internal sourcetype=splunkd component=metrics group=per_index_thruput series=windows earliest=-7d@d latest=@d
| timechart span=1d sum(kb) as sum_kb by series 

For a specific EventCode, you could get a good estimation by seeing what percentage of your events are using that EventCode and correlate that to your metrics logs.

i.e.

index=windows
| top 0 EventCode
| search EventCode=302

note the percent column and cross reference to the previous metrics logs. This won't be exact, but it will give you a good idea.

View solution in original post

zacharychristen
Path Finder

It is possible to get a breakdown of index, sourcetype, and source. However, for a certain EventCode can be tricky. First to get the usage for index, sourcetype, source, or even host, try the following:

index=_internal sourcetype=splunkd component=metrics group=<group_to_filter> series=*

where you can set the group field to be:
1. per_index_thruput
2. per_sourcetype_thruput
3. per_host_thruput
4. per_source_thruput

and (optionally) you can choose a specific series. For example, if you use the group per_index_thruput the series would be the index i.e. series=windows.

Full example:

index=_internal sourcetype=splunkd component=metrics group=per_index_thruput series=windows earliest=-7d@d latest=@d
| timechart span=1d sum(kb) as sum_kb by series 

For a specific EventCode, you could get a good estimation by seeing what percentage of your events are using that EventCode and correlate that to your metrics logs.

i.e.

index=windows
| top 0 EventCode
| search EventCode=302

note the percent column and cross reference to the previous metrics logs. This won't be exact, but it will give you a good idea.

shocko
Contributor

Thanks so much for this!

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...