I had the problem starting with /etc/init.d/splunk start , but with /opt/splunk/bin/splunk start it worked. ... View more

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> ... View more

The path in you answer is misleading. I thought "default" was the app name, but it's a folder inside the app. It should read: - create an app in the deployment server in .../etc/deployment-apps/appname/default/outputs.conf Also, 2nd step can be done in splunk web interface, in Settings > Forwarder Management ... View more

Instead of a [source::udp:514] instanza, may I use [syslog]? My tcp and udp ports 514 are both manually sourcetyped to "syslog", Will splunk parse again after changing sourcetype? Or in this case will it ignore the first instanza of the props.conf? ... View more