Thank you LJ Longwing.

Thanks,
Radhika Narayanan

From: ARSList [mailto:[email protected]] On Behalf Of LJ LongWing
Sent: Monday, January 15, 2018 8:42 PM
To: ARSList
Subject: Re: Monitoring Remedy from Load balancer

Narayanan,
I have a tool that is available on my site that does exactly that

http://remedylegacy.com/tools/apllbmonitor/<https://urldefense.proofpoint.com/v2/url?u=http-3A__remedylegacy.com_tools_apllbmonitor_&d=DwMFaQ&c=H50I6Bh8SW87d_bXfZP_8g&r=blQKSsGpUV3vEddB0ufOi2izy5lUOikNQGO3le4xQkw&m=P-q0HYow-OUzOK8kTEUnQroT5yUKn5icTtzfEmb8NzU&s=6zpiDBDL7URSBcgKzN1qXq9r2eOvHtqNmgtVz62aNMA&e=>

it has rudimentary checks that it does OOTB but allows you to customize a 
filter guide on the server to perform whatever wellness checks you need to 
perform.

On Mon, Jan 15, 2018 at 2:51 AM, Narayanan, Radhika 
<[email protected]<mailto:[email protected]>> wrote:
Hi List,

Are there ways to route requests to Remedy AR Server nodes from F5 Load 
balancer based on health of the Remedy application , in addition to regular TCP 
Port based checking & routing?

There is F5 load balancer forwarding requests to AR Servers based on AR TCP 
Port health check. If a server responds on TCP port, then the load balancer 
will forward requests to that server based on routing algorithm. In 
circumstances, where port responds but Remedy application doesn’t respond,  
have you got suggestions on alternate ways of health check that can be 
implemented on Load balancer that is also taken into account before forwarding 
the request to AR Server(s)?

Thanks,
Radhika Narayanan


--
ARSList mailing list
[email protected]<mailto:[email protected]>
https://mailman.rrr.se/cgi/listinfo/arslist<https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.rrr.se_cgi_listinfo_arslist&d=DwMFaQ&c=H50I6Bh8SW87d_bXfZP_8g&r=blQKSsGpUV3vEddB0ufOi2izy5lUOikNQGO3le4xQkw&m=P-q0HYow-OUzOK8kTEUnQroT5yUKn5icTtzfEmb8NzU&s=995mFJQ-5eH83Jh4mDVKZVpFzKfTO5yFxuIkOiSuoSs&e=>

-- 
ARSList mailing list
[email protected]
https://mailman.rrr.se/cgi/listinfo/arslist

Reply via email to