Forum Discussion
Create/Repeat Alert When A Pool or Node is Down
- Dec 11, 2019
I think an external monitor would be the good solution for this. You have to write your script along with some logger, so that it constantly throws logs about the status. But it will flood your log file for x intervals.
On good note, put the logging only for down state, for Up - do not put the logger.
This is doable using an Icall script. You can throw logs to the ltm file, sleep for certain intervals and again throw logs to the same.
But still, your requirement feels something like a process gap. Just because your monitoring software was paused for maintenance activity, you just shouldn't be throwing false alerts (because the pool member had come up after the activity).
Let us know one thing, after the work is complete, does the pool member come up or is it still down.
Also what kind of monitoring software are you using, Most of the monitoring platform follow MIB's and poll a certain set of intervals again and again. Even when you turn off & on later, it still makes the polling. It does not depend on the past logs of ltm.
Maybe if you could explain more on the monitoring software, we can suggest accordingly. Still Icall is your best bet on this as far I know.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com