Module: check_mk
Branch: master
Commit: 70ed8646b24b822c4e7691d16897f0d2de0f2938
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=70ed8646b24b82…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Thu Jan 9 15:54:58 2014 +0100
Edited werk 254
---
.werks/254 | 15 ++++++++++-----
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/.werks/254 b/.werks/254
index 2005bc2..eb42275 100644
--- a/.werks/254
+++ b/.werks/254
@@ -7,9 +7,14 @@ Version: 1.2.5i1
Date: 1389277479
Targetversion: future
-This feature allows to configure how spaces of VMs in esx hostsystem should be treated.
-Hostnames in the monitoring core generally are not allowed to have space.
-The new option -S (configurable via a WATO rule) can now set how to handle these spaces:<br>
-Option: -S cut -> The virtual machines name is cut after the first space<br>
-Option: -S underline -> All spaces of this virtual machine are replaced with underline
+This feature allows to configure how spaces of VMs of ESX should be treated.
+Hostnames in the monitoring core generally are not allowed to contain spaces.
+The new option <tt>-S</tt> (configurable via the WATO rule <i>Check state
+of VMWare ESX via vSphere</i>) can now set how to handle these spaces:
+
+<table>
+<tr><th>Option</th><th>Behaviour</th></tr>
+<tr><td class=tt>-S cut</td><td>The virtual machines name is cut after the first space</td></tr>
+<tr><td class=tt>-S underline</td><td>All spaces of this virtual machine are replaced with underline</td></tr>
+</table>
Module: check_mk
Branch: master
Commit: a71a8565a5bb651946850ad9fd5abcce24bf6da6
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=a71a8565a5bb65…
Author: Andreas Boesl <ab(a)mathias-kettner.de>
Date: Thu Jan 9 15:29:02 2014 +0100
agent_vsphere: Make handling of spaces in hostnames of ESX configurable
This feature allows to configure how spaces of VMs in esx hostsystem should be treated.
Hostnames in the monitoring core generally are not allowed to have space.
The new option -S (configurable via a WATO rule) can now set how to handle these spaces:<br>
Option: -S cut -> The virtual machines name is cut after the first space<br>
Option: -S underline -> All spaces of this virtual machine are replaced with underline
---
.werks/254 | 15 +++++++++++++++
ChangeLog | 1 +
2 files changed, 16 insertions(+)
diff --git a/.werks/254 b/.werks/254
new file mode 100644
index 0000000..2005bc2
--- /dev/null
+++ b/.werks/254
@@ -0,0 +1,15 @@
+Title: agent_vsphere: Make handling of spaces in hostnames of ESX configurable
+Level: 1
+Component: checks
+Class: feature
+State: unknown
+Version: 1.2.5i1
+Date: 1389277479
+Targetversion: future
+
+This feature allows to configure how spaces of VMs in esx hostsystem should be treated.
+Hostnames in the monitoring core generally are not allowed to have space.
+The new option -S (configurable via a WATO rule) can now set how to handle these spaces:<br>
+Option: -S cut -> The virtual machines name is cut after the first space<br>
+Option: -S underline -> All spaces of this virtual machine are replaced with underline
+
diff --git a/ChangeLog b/ChangeLog
index 93200fd..8449fae 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -33,6 +33,7 @@
* 0320 hitachi_hnas_fpga: new check for Hitachi HNAS storage systems
* 0321 brocade_mlx: enhancing checks (BR-MLX modules, more OK states)...
* 0323 emcvnx_hwstatus, emcvnx_hba, emcvnx_disks: new checks for EMC VNX storage systems
+ * 0254 agent_vsphere: Make handling of spaces in hostnames of ESX configurable...
* 0103 FIX: services: Fixed bug with service inventory defined in main.mk...
* 0299 FIX: borcade_mlx_fan: Prettified output, handling "other" state now
* 0300 FIX: cisco_fru_power: Trying not to inventorize not plugged in FRUs...
Module: check_mk
Branch: master
Commit: 1e229c1e6cd9c366d6006175064e6de3ce6919a8
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=1e229c1e6cd9c3…
Author: Bernd Stroessenreuther <bs(a)mathias-kettner.de>
Date: Wed Jul 31 15:07:16 2013 +0200
lun usage is no longer requested by customer
---
checkman/emc_storage.lun_usage | 30 ------------------------------
1 file changed, 30 deletions(-)
diff --git a/checkman/emc_storage.lun_usage b/checkman/emc_storage.lun_usage
deleted file mode 100644
index 215a55f..0000000
--- a/checkman/emc_storage.lun_usage
+++ /dev/null
@@ -1,30 +0,0 @@
-title: EMC Storage: Usage of LUNs
-agents: emc
-catalog: hw/storage
-license: GPL
-distribution: check_mk
-description:
- Reports the usage of LUNs on EMC storage systems.
-
- You can set levels for minimum free space to result in {WARN} and {CRIT}
- state. The levels can be given in absolute megabytes or percent of the
- total space available in the LUN.
-
- Hint for implementation: Look for "LUN Capacity(Megabytes):" line in
- section "LOGICAL UNIT NUMBER <my ID>" under "All logical Units Information"
- But: Where can we get actual used space in the LUN from? To be defined!
-
-item:
- The ID of the LUN as returned by the special agent.
- E. g. "18"
-
- Hint for implementation: Look for "LOGICAL UNIT NUMBER"
- lines in section "All logical Units Information"
-
-perfdata:
- One value: The used capacity in bytes, together with it's warn and crit
- levels as well as the maximum (also in bytes)
-
-inventory:
- Automatically configures one check for every LUN listed
- in the agent output.