Module: check_mk
Branch: master
Commit: 9041d6b7ac67f2dfeeb7bc15cde3d1cd28c71085
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=9041d6b7ac67f2…
Author: Bernd Stroessenreuther <bs(a)mathias-kettner.de>
Date: Tue Jul 9 18:43:22 2013 +0200
inital version of check manpages for esx_vsphere_vm.*
---
checkman/esx_vsphere_vm.cpu | 20 ++++++++++++++++++++
checkman/esx_vsphere_vm.heartbeat | 28 ++++++++++++++++++++++++++++
checkman/esx_vsphere_vm.mem_usage | 21 +++++++++++++++++++++
checkman/esx_vsphere_vm.name | 16 ++++++++++++++++
4 files changed, 85 insertions(+)
diff --git a/checkman/esx_vsphere_vm.cpu b/checkman/esx_vsphere_vm.cpu
new file mode 100644
index 0000000..f05ce42
--- /dev/null
+++ b/checkman/esx_vsphere_vm.cpu
@@ -0,0 +1,20 @@
+title: Virtual Machine under ESX: number of virtual CPUs and demanded CPU GHz
+agents: vsphere
+catalog: os/kernel
+author: Mathias Kettner <mk(a)mathias-kettner.de>
+license: GPL
+distribution: check_mk
+description:
+ For a virtual machine running on ESX this check reports the number of
+ virtual CPUs assigned to it and the currently demanded CPU GHz.
+
+ The check always returns {OK} state.
+
+ See "Monitoring VMWare ESX with Check_MK" in the online documentation
+ as well.
+
+perfdata:
+ One value is returned: The currently demanded CPU MHz.
+
+inventory:
+ On each VM one check is generated.
diff --git a/checkman/esx_vsphere_vm.heartbeat b/checkman/esx_vsphere_vm.heartbeat
new file mode 100644
index 0000000..60b173c
--- /dev/null
+++ b/checkman/esx_vsphere_vm.heartbeat
@@ -0,0 +1,28 @@
+title: Virtual Machine under ESX: Heartbeat
+agents: vsphere
+catalog: os/ps
+author: Mathias Kettner <mk(a)mathias-kettner.de>
+license: GPL
+distribution: check_mk
+description:
+ For a virtual machine running on ESX this check reports the heartbeat
+ status (queried from vsphere agent)
+
+ This check returns:
+
+ {OK} if the guest operating system is responding normally
+ (vsphere state: green)
+
+ {WARN} on intermittent heartbeat. May be due to guest load.
+ (vsphere state: yellow)
+ or if VMware Tools are not installed or not running.
+ (vsphere state: gray)
+
+ {CRIT} if there is no heartbeat. Guest operating system may have stopped responding.
+ (vsphere state: red)
+
+ See "Monitoring VMWare ESX with Check_MK" in the online documentation
+ as well.
+
+inventory:
+ On each VM one check is generated.
diff --git a/checkman/esx_vsphere_vm.mem_usage b/checkman/esx_vsphere_vm.mem_usage
new file mode 100644
index 0000000..45c4218
--- /dev/null
+++ b/checkman/esx_vsphere_vm.mem_usage
@@ -0,0 +1,21 @@
+title: Virtual Machine under ESX: used Memory (RAM)
+agents: vsphere
+catalog: os/kernel
+author: Mathias Kettner <mk(a)mathias-kettner.de>
+license: GPL
+distribution: check_mk
+description:
+ The check reports used memory (RAM) for {host}, {guest}, {ballooned}, {private}
+ and {shared} memory.
+
+ The check always returns {OK} state.
+
+ See "Monitoring VMWare ESX with Check_MK" in the online documentation
+ as well.
+
+perfdata:
+ One value for each of {host}, {guest}, {ballooned}, {private}
+ and {shared} memory.
+
+inventory:
+ On each VM one check is generated.
diff --git a/checkman/esx_vsphere_vm.name b/checkman/esx_vsphere_vm.name
new file mode 100644
index 0000000..b33f8fa
--- /dev/null
+++ b/checkman/esx_vsphere_vm.name
@@ -0,0 +1,16 @@
+title: Virtual Machine under ESX: Name of the VM
+agents: vsphere
+catalog: os/misc
+author: Mathias Kettner <mk(a)mathias-kettner.de>
+license: GPL
+distribution: check_mk
+description:
+ This check reports the name the virtual machine has within ESX.
+
+ The check always returns {OK} state.
+
+ See "Monitoring VMWare ESX with Check_MK" in the online documentation
+ as well.
+
+inventory:
+ On each VM one check is generated.