Re: [Nagios-devel] [Nagiosplug-devel] Testing the upcoming release
Posted: Thu Jun 28, 2012 12:42 pm
On 06/27/2012 07:05 PM, Jochen Bern wrote:
> On 06/27/2012 04:04 PM, Holger Wei=DF wrote:
>> Then again, according to
>> http://nagios.sourceforge.net/docs/3_0/pluginapi.html
>> the old output might be interpreted as a valid way to spit out
>> performance data (even though the first line contains no perfdata part=
).
>> I wouldn't have been sure whether Nagios actually passes this on as
>> performance data, but it seems you were able to use it?
>=20
> I can't say that I've tested it systematically, but I'm not aware of an=
y
> problems in parsing multiline syntax in Nagios 3.x. Guess I'll slap a
> test plugin together, just in case ...
As it turns out, there *is* a small gotcha in how my 3.2.3 processes the
full-blown multiline format:
# ../libexec/check_multiline
Play Rock|foo=3D1 bar=3D2
Paper Scissors
Lizard Spock|baz=3D3 org=3D4
eeny=3D5 meeny=3D6
miny=3D7 moe=3D8
# grep -A 2 Play ../var/spool/status.dat
plugin_output=3DPlay Rock
long_plugin_output=3DPaper Scissors\nLizard Spock
performance_data=3Dfoo=3D1 bar=3D2baz=3D3 org=3D4 eeny=3D5 meeny=3D=
6 miny=3D7 moe=3D8
(Note the missing whitespace between bar and baz. My test plugin doesn't
*provide* any whitespace there other than the EOL, on purpose, of course.=
)
I wonder how 3.3.x and 3.4.x handle this case ... ?
Regards,
J. Bern
--=20
Jochen Bern, Systemingenieur --- LINworks GmbH
Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt
PGP (1024D/4096g) FP =3D D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C2=
7
Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202
Unternehmenssitz Weiterstadt, Gesch=E4ftsf=FChrer Metin Dogan, Oliver Mic=
hel
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
> On 06/27/2012 04:04 PM, Holger Wei=DF wrote:
>> Then again, according to
>> http://nagios.sourceforge.net/docs/3_0/pluginapi.html
>> the old output might be interpreted as a valid way to spit out
>> performance data (even though the first line contains no perfdata part=
).
>> I wouldn't have been sure whether Nagios actually passes this on as
>> performance data, but it seems you were able to use it?
>=20
> I can't say that I've tested it systematically, but I'm not aware of an=
y
> problems in parsing multiline syntax in Nagios 3.x. Guess I'll slap a
> test plugin together, just in case ...
As it turns out, there *is* a small gotcha in how my 3.2.3 processes the
full-blown multiline format:
# ../libexec/check_multiline
Play Rock|foo=3D1 bar=3D2
Paper Scissors
Lizard Spock|baz=3D3 org=3D4
eeny=3D5 meeny=3D6
miny=3D7 moe=3D8
# grep -A 2 Play ../var/spool/status.dat
plugin_output=3DPlay Rock
long_plugin_output=3DPaper Scissors\nLizard Spock
performance_data=3Dfoo=3D1 bar=3D2baz=3D3 org=3D4 eeny=3D5 meeny=3D=
6 miny=3D7 moe=3D8
(Note the missing whitespace between bar and baz. My test plugin doesn't
*provide* any whitespace there other than the EOL, on purpose, of course.=
)
I wonder how 3.3.x and 3.4.x handle this case ... ?
Regards,
J. Bern
--=20
Jochen Bern, Systemingenieur --- LINworks GmbH
Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt
PGP (1024D/4096g) FP =3D D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C2=
7
Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202
Unternehmenssitz Weiterstadt, Gesch=E4ftsf=FChrer Metin Dogan, Oliver Mic=
hel
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]