Hello @aldiaz,

Are you referring to the health check for availability via a Publisher or an actual keepalive?  There is no keepalive between the Publisher and private app today but there is a reachability check every 60 seconds.  Currently, this reachability check is not configurable but I’d suggest reaching out to your local account team to capture your requirements as there is an existing enhancement request for customizing this health check. 

Hello sshiflett,

Thanks very much for you answer. I opened a case and they told me that this reachability check is in pilot phase at the moment but they are working on it.

Do you know if this reachability check is over all ports that you have configured for private app?

Best Regards!

@aldiaz ,

The check depends on the app definition configuration.  When you have more than one host, a wildcard, or a CIDR block defined there will not currently be a reachability check.  In cases where a single host is defined, the check will occur on the first port in the range or list of ports provided.  So in that way, you can somewhat tailor the reachability check by ensuring the port you’d like to check is the first one in the list. 

Hello,

Assuming a private apps is defined with a single hostname (with the exception of CIDR or wildcard domain) and reachability status is normal, what is the default traffic behaviour if the publishers associated with the app are suddenly unable to each the app? Is the traffic dropped?

Is reachability only relevant in scenarios where a single hostname in an app is defined?

The private app FAQ document states the following.

• • When an app is specifies with multiple ports or a port range, the Publisher will use only the first port from the list or range to check availability. For example, port range 70-90 will return unreachable, even if you are listening on port 80, because the only port that will be checked is 70 (this is a known limitation).

• • If an app definition specifies multiple ports and/or port ranges, it will check whether any of them is reachable. For example, if you specify 22, 70-90, if it’s able to reach port 22, it will mark the app as reachable.

Can anyone clarify these statements as they appears to be contradictory. 

We have created an app using a single hostname and multiple ports. In traffic logs, we are observing the publisher reachability check running for ALL ports on all publishers. This contradicts what is stipulated above. 

Is there any update regarding whether or not reachability can be disabled for specific apps? 

Regards,

Simon