Right now heartbeat assumes that a service has a single HTTP status code representing its up state. In this forum thread we found that isn't the case in the real world.
I propose we allow check.response.status to take an array of codes as an argument to better handle this situation. While it's not ideal, this is a real situation operators may find themselves in.
Right now heartbeat assumes that a service has a single HTTP status code representing its up state. In this forum thread we found that isn't the case in the real world.
I propose we allow
check.response.statusto take an array of codes as an argument to better handle this situation. While it's not ideal, this is a real situation operators may find themselves in.