Cheap Health Check URL?

What would a cheap health check request be for TeamCity? I'm looking at placing TC behind a HWLB, not strictly for load balancing but mainly for port mapping + cold spare setup (easier to swap out via HWLB than via DNS).

5 comments
Comment actions Permalink

Just wondering... am I the only one who is even thinking of running TC behind a load balancer? nobody doing Nagios checks or anything?

0
Comment actions Permalink

Need to say, we do not support load balancing - when two cluster nodes work in parallel. But you can setup high avalability cluster. take a look at articles
Setup TeamCity in Replication/Clustering Environment
Move TeamCity Installation to a New Machine

For health check - what do you expect from it? I mean, what's wrong with http://server/overview.html ?

Michael

0
Comment actions Permalink

A health check URL should be one that is safe to poll for once  a second and with a predictable return value. I don't think overview.html with qualify - I was hoping there was a specific URL that would return a simple "OK" response after doing some cheap checks. It should not load up the system with lengthy page renderings...

Meanwhile, thanks for the links. I'm aware that I can't do load balancing - but I can do failover - even if I have to do it by hand, and since we already have a hardware load balancer, it is easier to do it via the load balancer than mucking with DNS - but in order for it to even make sense, I need to detect when to fail over.

0
Comment actions Permalink

What about login.html - that's static and doesn't require any additional actions like authentication.

1
Comment actions Permalink

We definitely need this for Kubernetes deployments in Google Container Engine. This is due to GCE load-balancer Ingress controller, requiring that:

  • All Kubernetes services must serve a 200 page on '/', or whatever custom value you've specified through GLBC's --health-check-path argument.

Unfortunately, during the installation phase all requests are redirected to "/mnt" using 302 redirect.  This means that there is no way to access TeamCity to complete setup, since the backend will be flagged as "unhealthy" in GCE load-balancer and it wouldn't serve requests to it.

Bamboo, for example, has "/rest/api/latest/server" endpoint, which is accessible without authentication and can be used in the Kubernetes' "readinessProbe":

0

Please sign in to leave a comment.