Module: check_mk
Branch: master
Commit: ee4ef64da49b697d767bae8a47b490be52a373c0
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=ee4ef64da49b69…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Mon Oct 27 16:10:46 2014 +0100
Updated formatting of Werk #1425, yet again
---
.werks/1425 | 24 +++++++++++++-----------
1 file changed, 13 insertions(+), 11 deletions(-)
diff --git a/.werks/1425 b/.werks/1425
index 901afa2..ad812c8 100644
--- a/.werks/1425
+++ b/.werks/1425
@@ -1,6 +1,6 @@
-Title: New section header option "encoding"
+Title: New section header option "encoding" for agent output
Level: 1
-Component: checks
+Component: core
Compatible: compat
Version: 1.2.5i6
Date: 1414421080
@@ -10,15 +10,17 @@ If you write your own check plugins you might know that a section
header can contain additional options separated by a colon.
For example:
+For section headers of agent outputs an additional option <tt>encoding</tt>
+has been introduced. Generally all check plugins should output valid UTF-8
+encoded text. In some instances this is not possible, because the plugin
+itself has its own hardcoded encoding. With the encoding option you can
+specify the encoding for this entire section. Check_MK will then decode the
+given section output and recode it into UTF-8 for further processing.
+Example:
+
F+:
-<<<lnx_distro:sep(124):persist(141442125)>>>
+<<<win_foobar:encoding(cp1252)>>>
F-:
-An additional option <tt>encoding</tt> has been introduced.
-Generally all check plugins should output valid utf-8 encoded text.
-In some instances this is not possible, because the plugin itself
-has its own hardcoded encoding. With the encoding option you can specify
-the encoding for this entire section.
-
-Check_MK will decode the given section output and recode it into utf-8 for
-further processing.
+You find a list of all available encoding
+<a
href="https://docs.python.org/2.4/lib/standard-encodings.html">…;>here</a>.