Forum Discussion
Native method to manually change the state of a monitor
- May 14, 2014
http://support.f5.com/kb/en-us/solutions/public/7000/400/sol7444.html?sr=37369745
You can add logging statements to your external monitor to view the variable output. /var/log/ltm is a good target.
Once I know the variables, I play with the script from the shell until it behaves like I expect.
Make sure you have handling to gracefully exit the process included in the script. These monitors fire off at the interval you specify, usually seconds, and they can stack up quite quickly and cause memory contention issues.
http://support.f5.com/kb/en-us/solutions/public/7000/400/sol7444.html?sr=37369745
You can add logging statements to your external monitor to view the variable output. /var/log/ltm is a good target.
Once I know the variables, I play with the script from the shell until it behaves like I expect.
Make sure you have handling to gracefully exit the process included in the script. These monitors fire off at the interval you specify, usually seconds, and they can stack up quite quickly and cause memory contention issues.
- eblair84_141985May 15, 2014NimbostratusSo, then the last question I have is what part does the "variables" play in the external monitor? The "arguments" parameter makes sense in an argv[] sense.
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