Forum Discussion

Altostratus

Dec 04, 2017

parsing health monitor events

I've set up a system for shipping member up/down events over to Logstash which then injects into InfluxDB, giving us visualization and alerting (specifically for excessive flapping in pools). We do p...

Ray_330743
Dec 06, 2017
The answer is you don't.

You're not supposed to get multiple results like that.

F5 support let me know that you're only supposed to get the last check's result and that the presence of other check results is due to a bug. See https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/related/relnote-supplement-hotfix-bigip-12-1-2.html: "636149-3 : Multiple monitor response codes to single monitor probe failure"

This bug goes away in 12.1.2HF2.

The details in the release notes drop some hints that might help you parse them if you're really interested and haven't yet upgraded.

The support technician let me know that I could enable "Monitor Logging" for particular members, and that might be a good way to get more detail on what the monitor sees. (Thanks, Chad!)

Ray_330743

Altostratus

Dec 06, 2017

The answer is you don't.

You're not supposed to get multiple results like that.

F5 support let me know that you're only supposed to get the last check's result and that the presence of other check results is due to a bug. See https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/related/relnote-supplement-hotfix-bigip-12-1-2.html: "636149-3 : Multiple monitor response codes to single monitor probe failure"

This bug goes away in 12.1.2HF2.

The details in the release notes drop some hints that might help you parse them if you're really interested and haven't yet upgraded.

The support technician let me know that I could enable "Monitor Logging" for particular members, and that might be a good way to get more detail on what the monitor sees. (Thanks, Chad!)