# Issues with @timestamp vs timestamp

**URL:** <https://discuss.elastic.co/t/issues-with-timestamp-vs-timestamp/375433>\
**Category:** Elasticsearch\
**Created:** [March 5, 2025, 7:49am UTC](https://discuss.elastic.co/t/issues-with-timestamp-vs-timestamp/375433 "2025-03-05T07:49:00Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [March 7, 2025, 12:34pm UTC](https://discuss.elastic.co/t/issues-with-timestamp-vs-timestamp/375433/9 "2025-03-07T12:34:58Z")

</div>

Have you seen [this thread](https://discuss.elastic.co/t/what-is-the-default-source-of-the-timestamp-field-in-filebeat/343640)? Based on this I believe both Filebeat and Logstash will set the @timestamp field to the current time if this field does not already exist.

---

_[View the full topic](https://discuss.elastic.co/t/issues-with-timestamp-vs-timestamp/375433)._