# How to use Lens to visualize/consider monitors down in a row

**URL:** <https://discuss.elastic.co/t/how-to-use-lens-to-visualize-consider-monitors-down-in-a-row/289966>\
**Category:** Synthetics\
**Tags:** kql-kibana-query-language\
**Created:** [November 23, 2021, 3:47pm UTC](https://discuss.elastic.co/t/how-to-use-lens-to-visualize-consider-monitors-down-in-a-row/289966 "2021-11-23T15:47:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jkambic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jkambic/32/53306_2.png) [@jkambic](https://discuss.elastic.co/u/jkambic)\
**Post date:** [November 23, 2021, 8:10pm UTC](https://discuss.elastic.co/t/how-to-use-lens-to-visualize-consider-monitors-down-in-a-row/289966/2 "2021-11-23T20:10:00Z")

</div>

Hi @rschirin - thanks for your interest in querying Heartbeat data.

Unfortunately there's no easy way to do this out-of-the-box. Our team has had similar challenges when discussing features like this for the Uptime application. We typically focus on overall number down within a given span, rather than tracking individual ordering of pings. For example, that's how the [query](https://github.com/elastic/kibana/blob/main/x-pack/plugins/uptime/server/lib/requests/get_monitor_status.ts#L63) responsible for tracking [monitor status rule](https://www.elastic.co/guide/en/observability/7.15/monitor-status-alert.html)s/alerting works.

It might be possible to do this using a custom [scripted metric aggregation](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-metrics-scripted-metric-aggregation.html), but that [would not be easy to visualize](https://discuss.elastic.co/t/visualizing-scripted-metric-aggregations-in-kibana/217258/3).

---

_[View the full topic](https://discuss.elastic.co/t/how-to-use-lens-to-visualize-consider-monitors-down-in-a-row/289966)._