# Prometheus metric when upstream goes unhealthy

**URL:** <https://discuss.konghq.com/t/prometheus-metric-when-upstream-goes-unhealthy/4448>\
**Category:** General\
**Created:** [September 17, 2019, 4:42am UTC](https://discuss.konghq.com/t/prometheus-metric-when-upstream-goes-unhealthy/4448 "2019-09-17T04:42:30Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![hbagdi](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/hbagdi/32/562_2.png) [@hbagdi](https://discuss.konghq.com/u/hbagdi)\
**Post date:** [September 19, 2019, 5:43pm UTC](https://discuss.konghq.com/t/prometheus-metric-when-upstream-goes-unhealthy/4448/4 "2019-09-19T17:43:04Z")

</div>

Kong Vitals includes some visibility into latency of the upstream but I don’t think it has metrics around (un)healthiness of targets of Upstreams (yet).

---

_[View the full topic](https://discuss.konghq.com/t/prometheus-metric-when-upstream-goes-unhealthy/4448)._