We really need a true Pool Member status not just a node status. Node status and pool member status is not the same thing, nodes can be assigned to multiple pools and have different health checks.
Can you clarify what exactly you mean? I monitor our F5 and its individual nodes just fine... what are you trying to accomplish that you can't currently?
Right, node status is fully available. The terms nodes and pool members cannot necessarily be used interchangeably. A node can be a member of multiple pools and can be marked down at the pool member level instead the node level. So just because the member is down in one pool does not necessarily mean it is down in another pool. In that case the node is still showing up and we cannot alert that the member is down.
Has this been addressed yet?
I understand there will be major improvements for F5s in the next release of NPM, to include member awareness.
Does anyone know when we can expect the new release with the new improvements for F5s?
probably still up to a few months out. I think they are staring ux testing for F5 improvements this week. maybe a month or two for beta...pure speculation on my part though.
Hi,
Have you got any trick to configure the same alert is actual pool node goes down then it should trigger the alert ?
Thanks
