IT Operations Discussions
All the up-time. All the nines.

ITSI Adhoc mstats search not splitting by host entities

Dpeedahnb
Explorer

My base search:

| mstats avg(Processor.%_Processor_Time) AS windows_avgcpu, avg(cpu.idle) AS linux_avgcpuidle, avg(cpu_metric.pctIdle) AS aix_avgcpuidle
avg(LogicalDisk.%_Free_Space) AS windows_avgdiskfree, avg(df.free) AS linux_avgdiskfree, avg(df_metric.UsePct) AS aix_avgdiskused
avg(Memory.%_Committed_Bytes_In_Use) AS windows_avgmemoryused, avg(memory.free) AS linux_avgmemoryfree, avg(vmstat_metric.memFreePct) AS aix_avgmemoryfree
avg(Network_Interface.Bytes_Total/sec) as windows_avgtotalbytes
WHERE `sai_metrics_indexes` BY host
| eval windows_avgdiskused=100-windows_avgdiskfree
| eval linux_avgcpu=100-linux_avgcpuidle, linux_avgdiskused=100-linux_avgdiskfree, linux_avgmemoryused=100-linux_avgmemoryfree
| eval aix_avgcpu=100-aix_avgcpuidle, aix_avgmemoryused=100-aix_avgmemoryfree
| eval avgcpu = coalesce(linux_avgcpu, windows_avgcpu, aix_avgcpu)
| eval avgdiskused = coalesce(windows_avgdiskused, linux_avgdiskused, aix_avgdiskused)
| eval avgmemoryused = coalesce(linux_avgmemoryused, windows_avgmemoryused, aix_avgmemoryused)
| fields host,avgcpu,avgdiskused,avgmemoryused,windows_avgtotalbytes

My entities are split into each host, automatically in a csv, names of entities are host names, with alias being host=(hostname) and also ENTITY_TITLE=(hostname), information is servertype=newage

With no entity splits in the base search, the services work correctly, as well as the KPI's from the base search, however when using a split by host in the base search and filtering to services, the services & KPI's always display as NA when theses settings are made in the base search.

I'll also attach an image of one of my entities produced by the upload using CSV

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...