- Example with Special Agent of vSphere
Find out the detailed special agent command
OMD[<sitename>]:~$ cmk -D <vcenter-host> | more
Tags: [add_ip_addresses:add_ip_addresses_1], [address_family:ip-v4-only], [agent:special-agents], [criticality:prod],
[ip-v4:ip-v4], [networking:lan], [piggyback:auto-piggyback], [site:nagnis_master], [snmp_ds:no-snmp], [tcp:tcp]
Host groups: check_mk
Contact groups: all
Agent mode: No Checkmk agent, all configured special agents
Type of agent:
Program: /omd/sites/<sitename>/share/check_mk/agents/special/agent_vsphere -u 'user' -s 'password' -i hos
tsystem,virtualmachine,datastore,counters,licenses -P --spaces cut --snapshot_display vCenter --no-cert-check 'x.x.x.x'
Process piggyback data from /omd/sites/<sitename>/tmp/check_mk/piggyback/vcenter
checktype item params
An easier way would be this command: /bin/sh -c "$(cmk -D vcenter | grep -A1 "^Type of agent:" | grep "^ Program:" | cut -f2 -d':')"
Please note that if a line matching "^Type of agent:" followed by a line matching "^ Program:" exists more than once, then the output might be messed up.
Check if there are options for debugging
There are two options for debugging the request
Modify the special agent command by adding these two options
In CMK 1.6.0 you might find the option "--snapshot_display vCenter" in your CMK -D output. If that's the case, you can include this parameter.
Run the special agent with no debbug options, to create an agent output. With this file we can reproduce your issue
Please send us all three files. Now we're able to investigate further
# Debug Output
# Agent Output
Advanced Debugging Examples
Collect several agent outputs over a period of time:
Collect several trace files over a period of time: