# Heartbeat monitor for multiple pods inside 1 deployment

**URL:** https://discuss.elastic.co/t/heartbeat-monitor-for-multiple-pods-inside-1-deployment/321310
**Category:** Beats
**Tags:** heartbeat
**Created:** [December 15, 2022, 1:24pm UTC](https://discuss.elastic.co/t/heartbeat-monitor-for-multiple-pods-inside-1-deployment/321310 "2022-12-15T13:24:53Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![OlLap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ollap/32/115365_2.png) [@OlLap](https://discuss.elastic.co/u/OlLap)
#### Post date: [December 15, 2022, 1:24pm UTC](https://discuss.elastic.co/t/heartbeat-monitor-for-multiple-pods-inside-1-deployment/321310/1 "2022-12-15T13:24:53Z")

</div>

Hello,

Is is possible with heartbeat configuration monitor all pods (replicas) inside one deployment together to see on Kibana UI something like "3/3 are UP" or "1/3 are UP"?

My current configuration creates new entry for each pod

```auto
 config:
    heartbeat:
      autodiscover:
        providers:
        - type: kubernetes
          resource: pod
          templates:
          - config:
            - type: http
              name: "${data.kubernetes.pod.name}"
              check.response.status: 200
              schedule: "@every 15s"
              timeout: 5s
              hosts: ["http://${data.host}:${data.port}/health"]

```

---

<div class="post-metadata">

### Author: ![emilioalvap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/emilioalvap/32/99310_2.png) [@emilioalvap](https://discuss.elastic.co/u/emilioalvap)
#### Post date: [December 16, 2022, 4:47pm UTC](https://discuss.elastic.co/t/heartbeat-monitor-for-multiple-pods-inside-1-deployment/321310/2 "2022-12-16T16:47:18Z")

</div>

Hi @OlLap,

Unfortunately, that's not how group checs are implemeted. Check groups (3/3 are UP) require a _static_ list of hosts/urls to know beforehand when all targets have been hit and returned.

Autodiscover targets are dynamic in nature and the scheduler does not know how these relate to one another to build a check group. So for each of the matches we generate a new monitor config.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 13, 2023, 6:47pm UTC](https://discuss.elastic.co/t/heartbeat-monitor-for-multiple-pods-inside-1-deployment/321310/3 "2023-01-13T18:47:37Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.