Reset Search



5551 - Is HTTP Health Monitoring for a vTM Pool Node with Windows Integrated Authentication supported?

« Go Back


Last Modified Date4/11/2018 12:51 PM

Is HTTP Health Monitoring for a vTM Pool Node with Windows Integrated Authentication supported?

Traffic Manager Health Monitoring

Problem or Goal

No it is not.

Only Basic Authentication is available for configuration for a HTTP health monitor.

This RFE (Request For Enhancement) for it -VTM-12036

However, there is no target milestone available currently for its implementation. 

If simply monitoring the Server reachability status is sufficiant, perhaps a Ping or TCP montitor will help do the job. 

Another alternative (and a more complex one), is to write a script, that uses the linux "curl" command with the "--ntlm" argument set. 

This script can then be run by an "External program monitor ". 

From the documentation: 

External Program 

This runs an executable program or script, located on the traffic manager under ZEUSHOME/zxtm/conf/scripts. Two fixed arguments, ip address and port, are sent to this program in the form "--port=80 --ipaddr=". The opportunity to specify further arguments, again of the form "--<arg>=<value>", is provided on the monitor edit page. An exit code of 0 is classed as a success; a code other than 0, or a timeout, is a failure. The facility to upload and manage your external monitor programs can be found on the Monitor Programs page. 

Stingray provides a Perl module, ZEUSHOME/zxtm/lib/perl/Zeus/ZXTM/, which provides functions to parse the arguments, write logs, and exit with success or failure. Scripts written in Perl can reference the module directly to incorporate this functionality. 

When creating a monitor of this type, you specify the program you wish to run from the drop-down list provided. All programs that appear in this list are those stored under ZEUSHOME/zxtm/conf/scripts. A further option, custom..., allows you to specify the full path to a program or script stored on the traffic manager at an alternative location. As Stingray automatically manages files inside of the 'scripts' directory across the cluster, any files you refer to outside of this directory MUST exist at the same location on each machine in the cluster. Failing to do so may cause an error on each traffic manager that cannot locate this program within its own filesystem. "

Related Links
Attachment 1 
Created ByCode Deployment



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255