Splunk® App for VMware (Legacy)

Configuration Guide

Acrobat logo Download manual as PDF


On August 31, 2022, the Splunk App for VMware will reach its end of life. After this date, Splunk will no longer maintain or develop this product. The functionality in this app is migrating to a content pack in Data Integrations. Learn about the Content Pack for VMware Dashboards and Reports.
This documentation does not apply to the most recent version of Splunk® App for VMware (Legacy). For documentation on the most recent version, go to the latest release.
Acrobat logo Download topic as PDF

Namespaces used in Splunk App for VMware

In Splunk App for VMware, all performance data is stored in tsidx namespaces. You can see a list of all of the namespaces used by the app in the $SPLUNK_HOME/etc/apps/SA-VMW-Performance/default/savedsearches.conf file. This information is used to populate dashboards with performance data throughout Splunk App for VMware. If the tsidx namespaces are created correctly, then performance data populates the index and you can see a list of all of the tsidx namespaces that are used in the App Install Health dashboard in the VMware Performance Data TSIDX Namespaces panel. Click on a tsidx namespace to drill down to the search that populates it.

Splunk App for VMware creates a number of tsidx namespaces that are used to store the summary statistical data used by the dashboards. The tables list the namespaces defined in Splunk App for VMware and the attributes associated with each namespace. For each namespace, each table lists the location, the searches that populate the namespace, which is also called the generating search, the search used to identify the fields that store the data in the namespace, and the suggested retention period for the data.

vmw_perf_cpu_virtualmachine

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-cpu-virtualmachine
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:VirtualMachine sourcetype=vmware:perf:cpu | table * | fields - _*

vmw_perf_disk_virtualmachine

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-disk-virtualmachine
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:VirtualMachine sourcetype=vmware:perf:disk | table * | fields - _*

vmw_perf_datastore_virtualmachine

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-datastore-virtualmachine
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:VirtualMachine sourcetype=vmware:perf:datastore | table * | fields - _*

vmw_perf_mem_virtualmachine

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-mem-virtualmachine
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:VirtualMachine sourcetype=vmware:perf:mem | table * | fields - _*

vmw_perf_net_virtualmachine

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-net-virtualmachine
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:VirtualMachine sourcetype=vmware:perf:net | table * | fields - _*

vmw_perf_power_virtualmachine

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-power-virtualmachine
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:VirtualMachine sourcetype=vmware:perf:power | table * | fields - _*

vmw_perf_resdisk_virtualmachine

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-resdisk-virtualmachine
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:VirtualMachine sourcetype=vmware:perf:resdisk | table * | fields - _*

vmw_perf_rescpu_virtualmachine

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-rescpu-virtualmachine
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:VirtualMachine sourcetype=vmware:perf:rescpu | table * | fields - _*

vmw_perf_sys_virtualmachine

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-sys-virtualmachine
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:VirtualMachine sourcetype=vmware:perf:sys | table * | fields - _*

vmw_perf_cpu_hostsystem

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-cpu-hostsystem
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:HostSystem sourcetype=vmware:perf:cpu | table * | fields - _*

vmw_perf_disk_hostsystem

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-disk-hostsystem
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:HostSystem sourcetype=vmware:perf:disk | table * | fields - _*

vmw_perf_datastore_hostsystem

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-datastore-hostsystem
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:HostSystem sourcetype=vmware:perf:datastore | table * | fields - _*

vmw_perf_hbr_hostsystem

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-hbr-hostsystem
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:HostSystem sourcetype=vmware:perf:hbr | table * | fields - _*

vmw_perf_net_hostsystem

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-net-hostsystem
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:HostSystem sourcetype=vmware:perf:net | table * | fields - _*

vmw_perf_power_hostsystem

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-power-hostsystem
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:HostSystem sourcetype=vmware:perf:power | table * | fields - _*

vmw_perf_resstorageadapter_hostsystem

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-resstorageadapter-hostsystem
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields

vmw_perf_storageadapter_hostsystem

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-storageadapter-hostsystem
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:HostSystem sourcetype=vmware:perf:storageadapter | table * | fields - _*

vmw_perf_storagepath_hostsystem

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-storagepath-hostsystem
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:HostSystem sourcetype=vmware:perf:storagepath | table * | fields - _*

vmw_perf_sys_hostsystem

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-sys-hostsystem
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:HostSystem sourcetype=vmware:perf:sys | table * | fields - _*

vmw_perf_rescpu_hostsystem

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-rescpu-hostsystem
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source=VMPerf:HostSystem sourcetype=vmware:perf:rescpu | table * | fields - _*

vmw_inv_datastore_virtualmachine

Details Description
Location SA-VMW-Performance
Generating search tsidx-inv-datastore-virtualmachine
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields source = VMInv:datastore sourcetype="vmware:inv:datastore" | table * | fields - _*

vmw_perf_cpu_resourcepool

This namespace is currently reserved but unused in the App.

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-cpu-resourcepool
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields Not available

vmw_perf_mem_resourcepool

This namespace is currently reserved but unused in the App.

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-mem-resourcepool
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields Not available

vmw_perf_cpu_clustercomputeresource

This namespace is currently reserved but unused in the App.

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-cpu-clustercomputeresource
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields Not available

vmw_perf_mem_clustercomputeresource

This namespace is currently reserved but unused in the App.

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-mem-clustercomputeresource
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields Not available

vmw_perf_vmop_clustercomputeresource

This namespace is currently reserved but unused in the App.

Details Description
Location SA-VMW-Performance
Generating search tsidx-perf-vmop-clustercomputeresource
Schedule runs every 5 minutes
Suggested retention period 2,184 days
Search to populate the fields Not available
Last modified on 31 July, 2015
PREVIOUS
Enable and disable threshold settings 		  NEXT
Manage namespace file size

This documentation applies to the following versions of Splunk® App for VMware (Legacy): 3.1.1, 3.1.2, 3.1.3, 3.1.4

Was this documentation topic helpful?


You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters