# Filebeat xpack.monitoring.elasticsearch.period?

**URL:** <https://discuss.elastic.co/t/filebeat-xpack-monitoring-elasticsearch-period/123765>\
**Category:** Elasticsearch\
**Created:** [March 13, 2018, 3:40pm UTC](https://discuss.elastic.co/t/filebeat-xpack-monitoring-elasticsearch-period/123765 "2018-03-13T15:40:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pfseth](https://avatars.discourse-cdn.com/v4/letter/p/e9bcb4/32.png) [@pfseth](https://discuss.elastic.co/u/pfseth)\
**Post date:** [March 13, 2018, 3:40pm UTC](https://discuss.elastic.co/t/filebeat-xpack-monitoring-elasticsearch-period/123765/1 "2018-03-13T15:40:54Z")

</div>

The documentation is not clear

> period
> 
> The time interval (in seconds) when metrics are sent to the Elasticsearch cluster. A new snapshot of Filebeat metrics is generated and scheduled for publishing each period. The default value is 60 \* time.Second.

What should be the value, i tried this in filebeat.yml

> xpack.monitoring.elasticsearch.hosts: ["[https://esa1-ir.com:9200](https://esa1-ir.com:9200)", "[https://esa2-ir.com:9200](https://esa2-ir.com:9200)"]  
> xpack.monitoring.elasticsearch.username: "${XMON)"  
> xpack.monitoring.elasticsearch.password: "${XPAS}"  
> xpack.monitoring.elasticsearch.compression\_level: "1"  
> xpack.monitoring.elasticsearch.bulk\_max\_size: "100"  
> xpack.monitoring.elasticsearch.period: "60s"  
> xpack.monitoring.elasticsearch.ssl.ca: "/etc/filebeat/certificates/root-ca.pem"  
> xpack.monitoring.elasticsearch.ssl.verification\_mode: "none"

I get this error in elasticsearch

> [2018-03-13T11:18:03,396][DEBUG][r.suppressed] path: /\_xpack/monitoring/\_bulk, params: {system\_id=beats, system\_api\_version=6, interval=1m0s}  
> org.elasticsearch.ElasticsearchParseException: failed to parse [1m0s]  
> at org.elasticsearch.common.unit.TimeValue.parse(TimeValue.java:365) ~[elasticsearch-6.2.2.jar:6.2.2]  
> at org.elasticsearch.common.unit.TimeValue.parseTimeValue(TimeValue.java:335) ~[elasticsearch-6.2.2.jar:6.2.2]

---

<div class="post-metadata">

**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\
**Post date:** [March 15, 2018, 2:34pm UTC](https://discuss.elastic.co/t/filebeat-xpack-monitoring-elasticsearch-period/123765/2 "2018-03-15T14:34:27Z")

</div>

> [@pfseth](#):
>
> xpack.monitoring.elasticsearch.period: "60s"

Try

`xpack.monitoring.elasticsearch.period: "60"

I'll raise an issue for improving the documentation also, thanks for bringing this up

---

<div class="post-metadata">

**Author:** ![pfseth](https://avatars.discourse-cdn.com/v4/letter/p/e9bcb4/32.png) [@pfseth](https://discuss.elastic.co/u/pfseth)\
**Post date:** [March 15, 2018, 2:37pm UTC](https://discuss.elastic.co/t/filebeat-xpack-monitoring-elasticsearch-period/123765/3 "2018-03-15T14:37:14Z")

</div>

Thanks @ikakavas, well does it have to be only in seconds ?

For 5 minutes do i have to set it as 300

---

<div class="post-metadata">

**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\
**Post date:** [March 15, 2018, 3:01pm UTC](https://discuss.elastic.co/t/filebeat-xpack-monitoring-elasticsearch-period/123765/4 "2018-03-15T15:01:54Z")

</div>

Hi,

This is actually a bug because of the difference in how filebeat parses the value and the formats the Elasticsearch supports. We have [opened an issue](https://github.com/elastic/beats/issues/6561) for this, for now can you try

`xpack.monitoring.elasticsearch.period: "59s"`

as a quick workaround ?

---

<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 12, 2018, 3:02pm UTC](https://discuss.elastic.co/t/filebeat-xpack-monitoring-elasticsearch-period/123765/5 "2018-04-12T15:02:06Z")

</div>

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