Beats: [Heartbeat] Support for multiple status codes

[andrewvc]

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.

[elasticmachine]

Pinging @elastic/uptime

[hjmwijnen]

+1 - is there currently any workaround?

[weedaj]

+1

[william20111]

+1 this would be useful. HA Vault cluster would give both a 200 if you hit the master or a 429 if you get a backup instance. As you say this is a requirement for some real world examples

[bartDecos]

+1

[andrewvc]

This was merged into our 7.x branch (targeting the 7.7 release) thanks to the awesome contribution from @amandahla in https://github.com/elastic/beats/pull/15587 . Thanks @amandahla !

[amandahla]

I’m glad I was able to help! :-)