# \[Heartbeat\] Checking multiple http response codes
**URL:** https://discuss.elastic.co/t/heartbeat-checking-multiple-http-response-codes/214959
**Category:** Synthetics
**Created:** [January 14, 2020, 9:01am UTC](https://discuss.elastic.co/t/heartbeat-checking-multiple-http-response-codes/214959 "2020-01-14T09:01:00Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@seblg](https://discuss.elastic.co/u/seblg)
#### Post date: [January 14, 2020, 9:01am UTC](https://discuss.elastic.co/t/heartbeat-checking-multiple-http-response-codes/214959/1 "2020-01-14T09:01:00Z")
Hi,
We've started using heartbeat agents (6.8.2) and uptime monitoring for monitoring api endpoints.
We'd like to attribute all http reponse codes which are not 500 or 503 as being "up", going through documentation this doesn't seem possible. Either we do not set, in the monitor yml,
```
check.response:
status: x
```
and by default 4xx and 5xx are considered down, either we are only able to set **one** value in check.response status which will be labeled as **up**.
Is there a workaround or a solution for passing a list of response codes we expect to mean up or ones we want to set to down ?
Thanks,
---
### Author:  [@shahzad31](https://discuss.elastic.co/u/shahzad31)
#### Post date: [January 23, 2020, 9:25pm UTC](https://discuss.elastic.co/t/heartbeat-checking-multiple-http-response-codes/214959/2 "2020-01-23T21:25:00Z")
Hi Sebastien,
Functionality was recently implemented [https://github.com/elastic/beats/pull/15587](https://github.com/elastic/beats/pull/15587).
You will be able to get that in 7.7 release.
Regards
---
### Author:  [@shahzad31](https://discuss.elastic.co/u/shahzad31)
#### Post date: [January 23, 2020, 9:27pm UTC](https://discuss.elastic.co/t/heartbeat-checking-multiple-http-response-codes/214959/3 "2020-01-23T21:27:31Z")
I just realized you are using 6.8, so it may not help you. Unless you upgrade.
---
### Author:  [@Jugsofbeer](https://discuss.elastic.co/u/Jugsofbeer)
#### Post date: [January 30, 2020, 5:02pm UTC](https://discuss.elastic.co/t/heartbeat-checking-multiple-http-response-codes/214959/4 "2020-01-30T17:02:55Z")
ive been waiting for this enhancement for 9months, so another month or so till 7.7 is better than unknown timeframe.
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [January 30, 2020, 5:15pm UTC](https://discuss.elastic.co/t/heartbeat-checking-multiple-http-response-codes/214959/5 "2020-01-30T17:15:23Z")
Sorry for the time it took here @Jugsofbeer, in hindsight we probably should have prioritized this higher. At any rate, 7.6 is our next release so it'll probably be a bit longer than that. This feature just missed the cutoff for our 7.6 feature freeze/test only period unfortunately.
---
### Author:  [@Jugsofbeer](https://discuss.elastic.co/u/Jugsofbeer)
#### Post date: [January 30, 2020, 6:20pm UTC](https://discuss.elastic.co/t/heartbeat-checking-multiple-http-response-codes/214959/6 "2020-01-30T18:20:13Z")
With all the new features and fixes in 7.6 the time will pass very quickly anyway.
😃
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 23, 2020, 6:20pm UTC](https://discuss.elastic.co/t/heartbeat-checking-multiple-http-response-codes/214959/7 "2020-02-23T18:20:24Z")
This topic was automatically closed 24 days after the last reply. New replies are no longer allowed.