# Metricbeat kibana no stable

**URL:** <https://discuss.elastic.co/t/metricbeat-kibana-no-stable/299091>\
**Category:** Beats\
**Tags:** beats-module, metricbeat\
**Created:** [March 8, 2022, 1:03pm UTC](https://discuss.elastic.co/t/metricbeat-kibana-no-stable/299091 "2022-03-08T13:03:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gerardgorrion](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gerardgorrion/32/85495_2.png) [@gerardgorrion](https://discuss.elastic.co/u/gerardgorrion)\
**Post date:** [March 8, 2022, 1:03pm UTC](https://discuss.elastic.co/t/metricbeat-kibana-no-stable/299091/1 "2022-03-08T13:03:10Z")

</div>

We are triying to deploy metricbeat to monitor kibana in eck with stack monitoring. The problem is, the monitoring is not working fine:

Kibana stack monitoring:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/a/daf46d2c72d20d460f49fcc8423cc0e7b42bcb08.png)

Last 15 min of a single kibana node (continous monitoring is no working):

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/a/aa793e484594aad8fb1343b69669afca3d118390.png)

Example of self monitoring kibana node running ok:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/8/9825d24c78c46d44d8333758dbc01014ebcc6444.png)

Metricbeat:

> <https://github.com/elastic/cloud-on-k8s/blob/2.0/config/recipes/beats/stack_monitoring.yaml>

Metricbeat config modules:

```auto
            templates:
              - condition:
                  contains:
                    kubernetes.labels.app: elasticsearch
                config:
                  - module: elasticsearch
                    metricsets:
                      - ccr
                      - cluster_stats
                      - enrich
                      - index
                      - index_recovery
                      - index_summary
                      - ml_job
                      - node_stats
                      - shard
                    period: 10s
                    hosts: "https://${data.host}:${data.ports.https}"
                    username: ${MONITORED_ES_USERNAME}
                    password: ${MONITORED_ES_PASSWORD}
                    # WARNING: disables TLS as the default certificate is not valid for the pod FQDN
                    # TODO: switch this to "certificate" when available: https://github.com/elastic/beats/issues/8164
                    ssl.verification_mode: "none"
                    xpack.enabled: true
              - condition:
                  contains:
                    kubernetes.labels.app: elasticsearch
                config:
                  - module: kibana
                    metricsets:
                      - stats
                    period: 10s
                    hosts: "http://kibana-kb-http:5601"
                    username: ${MONITORED_ES_USERNAME}
                    password: ${MONITORED_ES_PASSWORD}
                    # WARNING: disables TLS as the default certificate is not valid for the pod FQDN
                    # TODO: switch this to "certificate" when available: https://github.com/elastic/beats/issues/8164
                    ssl.verification_mode: "none"
                    xpack.enabled: true

```

Versions:  
eck operator: 1.9  
elasticseach and kibana: 7.16.2  
metricbeat: 7.16.2

Thanks!

---

<div class="post-metadata">

**Author:** ![gerardgorrion](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gerardgorrion/32/85495_2.png) [@gerardgorrion](https://discuss.elastic.co/u/gerardgorrion)\
**Post date:** [March 10, 2022, 7:44am UTC](https://discuss.elastic.co/t/metricbeat-kibana-no-stable/299091/2 "2022-03-10T07:44:15Z")

</div>

Here more tests:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/0/e086d9593e56bbf74237e477685af148a5a35cbe.png)

Monitoring start: 08:30 with 2 kibana pod replicas.  
At 08:31 put 1 replicas of kibana  
At 08:38 put 3 replicas of kibana

Seem like when there're more than a replica, the monitoring is not working fine.

Some idea? Regards

---

<div class="post-metadata">

**Author:** ![gerardgorrion](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gerardgorrion/32/85495_2.png) [@gerardgorrion](https://discuss.elastic.co/u/gerardgorrion)\
**Post date:** [March 15, 2022, 10:27am UTC](https://discuss.elastic.co/t/metricbeat-kibana-no-stable/299091/3 "2022-03-15T10:27:20Z")

</div>

Some idea if this metric is correctly? we think that can be some missconfig...

---

<div class="post-metadata">

**Author:** ![Tetiana\_Kravchenko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tetiana_kravchenko/32/102683_2.png) [@Tetiana\_Kravchenko](https://discuss.elastic.co/u/Tetiana_Kravchenko)\
**Post date:** [March 16, 2022, 10:48am UTC](https://discuss.elastic.co/t/metricbeat-kibana-no-stable/299091/4 "2022-03-16T10:48:51Z")

</div>

Hi @gerardgorrion !

Sorry for the late reply.  
The first thing I've noticed in your configuration is that you are using the same conditions for both Elasticsearch and kibana:

```auto
- condition:
    contains:
    kubernetes.labels.app: elasticsearch

```

do you see any issues with Elasticsearch metrics/dashboards?  
could you please try to use more explicit conditions? and check if it helps somehow: you could use [kubernetes.container.name](https://www.elastic.co/guide/en/beats/metricbeat/current/configuration-autodiscover.html#_pod_specific) for example.

---

<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:** [April 13, 2022, 12:48pm UTC](https://discuss.elastic.co/t/metricbeat-kibana-no-stable/299091/5 "2022-04-13T12:48:59Z")

</div>

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