All Apps and Add-ons

Why am I missing cpu count data in my Server Virtualization dashboard?

luisgustavo
Explorer

When you click a Virtual Machine or Host in a dashboard (server virtualization app) the first dashboard shows vm/host name, and CPU count or vCPU/pCPU ratio. These are always N/A for me.
Seems that either the search is missing a filter to use only records that have the cpu count field, or the scripts do not put this field in all records.

0 Karma

luisgustavo
Explorer

Trying to fix the Virtual Machine dashboard (when you click a VM), i added vm_cpu_count=*, so the first hidden search became:

    <param name="search">
                    `servervirt_index` sourcetype=hypervisor:*:vm vm_cpu_count=* vm_name="$vmname$" |
                    head 1 |
                    fields vm_host vm_cpu_count
    </param>

About the hosts dashboard (when you click a host), there seems to be a similar problem, but changing the eventtype to eventtype=servervirt:* in the third search seems to fix it:

                <param name="search">
                    eventtype=servervirt:* cpu_count="*" hyp_hostname="$hostname$" |
                    head 1 |
                    fields hyp_hostname cpu_count |
                    rename hyp_hostname as vm_host cpu_count as pCPU |
                    join type=inner vm_host [search eventtype=servervirt:vm:* vm_cpu_count=* | dedup vm_id | fields vm_cpu_count, vm_host | stats sum(vm_cpu_count) as vCPU by vm_host ] |
                    eval avgcpu=round(vCPU/pCPU,2) |
                    rangemap field=avgcpu ok=0-`alerts-high_vCPU_to_pCPU` default=critical |
                    table vm_host, pCPU, vCPU, avgcpu, range
                </param>
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...