# \[FunctionBeat\] Timestamp Issue when collecting logs from cloudwatch

**URL:** <https://discuss.elastic.co/t/functionbeat-timestamp-issue-when-collecting-logs-from-cloudwatch/219026>\
**Category:** Beats\
**Tags:** functionbeat\
**Created:** [February 12, 2020, 3:24pm UTC](https://discuss.elastic.co/t/functionbeat-timestamp-issue-when-collecting-logs-from-cloudwatch/219026 "2020-02-12T15:24:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ben\_Ismail\_Mohamed](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ben_ismail_mohamed/32/51072_2.png) [@Ben\_Ismail\_Mohamed](https://discuss.elastic.co/u/Ben_Ismail_Mohamed)\
**Post date:** [February 12, 2020, 3:24pm UTC](https://discuss.elastic.co/t/functionbeat-timestamp-issue-when-collecting-logs-from-cloudwatch/219026/1 "2020-02-12T15:24:41Z")

</div>

Hello

We have a problem sending cloudwatch events to our Elasticsearch Cluster. The error is on the Timestamp Configuration set to the collecte date instead of the cloudwatch event timestamp. So with a large volume of data we can have a delay of several seconds between the 2 dates and also we lost the order of the received events.

We use the version 7.5 of Elasticsearch and the 7.5.2 for FunctionBeat.

May i know how to configure the functionbeat to get the cloudwatch event timestamp instead of setting the current date of collect?

Thank you

Regards

---

<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:** [March 4, 2020, 5:24am UTC](https://discuss.elastic.co/t/functionbeat-timestamp-issue-when-collecting-logs-from-cloudwatch/219026/2 "2020-03-04T05:24:45Z")

</div>

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