# Metricbeat etcd module can't work with etcd v3.3.8

**URL:** <https://discuss.elastic.co/t/metricbeat-etcd-module-cant-work-with-etcd-v3-3-8/155739>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [November 7, 2018, 2:20pm UTC](https://discuss.elastic.co/t/metricbeat-etcd-module-cant-work-with-etcd-v3-3-8/155739 "2018-11-07T14:20:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jun\_Zhang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jun_zhang/32/25863_2.png) [@Jun\_Zhang](https://discuss.elastic.co/u/Jun_Zhang)\
**Post date:** [November 7, 2018, 2:20pm UTC](https://discuss.elastic.co/t/metricbeat-etcd-module-cant-work-with-etcd-v3-3-8/155739/1 "2018-11-07T14:20:48Z")

</div>

my config:

```
metricbeat.modules:
- module: etcd
  metricsets: ["leader", "self", "store"]
  period: 10s
  hosts: ["https://172.27.128.71:2379"]
  ssl:
    certificate: "/etc/cert/client.pem"
    key: "/etc/cert/client-key.pem"
    certificate_authorities: ["/etc/cert/ca.pem"]
    verification_mode: "none"

```

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/6/56c78f25aaf86dc7e91dd0cfdb91dc8bae7d255c.png)

---

<div class="post-metadata">

**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\
**Post date:** [November 7, 2018, 3:36pm UTC](https://discuss.elastic.co/t/metricbeat-etcd-module-cant-work-with-etcd-v3-3-8/155739/2 "2018-11-07T15:36:19Z")

</div>

We are testing the metricbeat `etcd` module with `etcd` 3.2: [https://github.com/elastic/beats/blob/master/metricbeat/module/etcd/\_meta/Dockerfile](https://github.com/elastic/beats/blob/master/metricbeat/module/etcd/_meta/Dockerfile)

It sounds like we need to enhance the module to work with `etcd` 3.3 as well. If you have a GitHub account, would you mind filing an enhancement issue for this over here: [https://github.com/elastic/beats/issues/new](https://github.com/elastic/beats/issues/new)? That way you'll be notified of it's progress. If you don't have a GitHub account, let me know and I'll create the issue for you.

Thanks,

Shaunak

---

<div class="post-metadata">

**Author:** ![Jun\_Zhang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jun_zhang/32/25863_2.png) [@Jun\_Zhang](https://discuss.elastic.co/u/Jun_Zhang)\
**Post date:** [November 8, 2018, 7:22am UTC](https://discuss.elastic.co/t/metricbeat-etcd-module-cant-work-with-etcd-v3-3-8/155739/3 "2018-11-08T07:22:33Z")

</div>

Done.

> <https://github.com/elastic/beats/issues/8986>

---

<div class="post-metadata">

**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\
**Post date:** [November 14, 2018, 12:22pm UTC](https://discuss.elastic.co/t/metricbeat-etcd-module-cant-work-with-etcd-v3-3-8/155739/4 "2018-11-14T12:22:01Z")

</div>

Hi @Jun_Zhang,

I have tried to reproduce the problem with 3.3.8 and 3.3.10 but current module seems to work fine (at least it generates events). I am adding [some tests](https://github.com/elastic/beats/pull/9068) to cover these versions.

I wonder if the problem can be specific of its usage with https or something related to etcd API version. In any case there should be errors in logs. Could you check if there is any error in metricbeat logs?

It'd be also useful to have the etcd parameters and the configuration you are using.

And if you have the chance, it'd be also great if you could try to reproduce the issue with etcd 3.2 and/or without SSL.

Thanks!

---

<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:** [December 12, 2018, 12:22pm UTC](https://discuss.elastic.co/t/metricbeat-etcd-module-cant-work-with-etcd-v3-3-8/155739/5 "2018-12-12T12:22:01Z")

</div>

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