Problem with @timestamp time in indexes

Hello, we have filebeat sending messages directly to elasticsearch index. And we found such problem, @timestamp in kibana view ( when we search) is different from timestamp we have in file on server( which use filebeat). Looks like elastic change timestamp - to time when document was indexed, not timestamp from original document( which could be found in file on server) How to fix that ? Because it's important for us to have correct messages order in time

Are you using a specific filebeat module?
How your logs are parsed?
Are you using an ingest pipeline?

I use filebeat 7.4.2, logs are text files with json ojects on each row. I do not use igest pipline

So elasticsearch just index the json content as you are sending it.
You need to define an ingest pipeline to rename the field which contains the event date to @timestamp.

So if we have such field named @timestamp in logs on server, will it be replaced? Beacause our event date fiels called @timestamp - default name ...

Can you show a document?

Here is docuent in index

And here is document in log on server

Could you run



  • INDEXNAME is the filebeat index name
  • ID is the _id of the document

And share the output here.

Please don't post images of text as they are hard to read, may not display correctly for everyone, and are not searchable.

Instead, paste the text and format it with </> icon or pairs of triple backticks (```), and check the preview window to make sure it's properly formatted before posting it. This makes it more likely that your question will receive a useful answer.


I can't see any other timestamp in this document. So I don't understand what the problem is. Unless you removed important things in the example you shared?

Nothing removed. And problem is that time stamps in index and in file are different.
20:18:29 in index and 20:18:23 in file.

Can you share the full json document without removing anything?

I did not remove any fields, i just replace some text to xxx, is that important? ( there only index name, log filename, message, hostname and thats all )

Yes it is

{"_index":"trendhero-2020.02.21-000001","_type":"_doc","_id":"GG5_sXABULG93gUD3XMn","_version":1,"_seq_no":846086,"_primary_term":1,"found":true,"_source":{"@timestamp":"2020-03-06T20:18:29.973Z","log":{"file":{"path":"/var/log/report-generator/report-generator.log"},"offset":14310474576},"report_uuid":"bf0f8a56-4a46-4cf1-8706-491b3607eaf3","input":{"type":"log"},"ecs":{"version":"1.1.0"},"exportable":true,"level":"info","message":"Get full report request","host":{"name":"1ps-api"},"agent":{"hostname":"1ps-api","id":"448f24c9-d971-4558-8651-b57f65cc4de2","version":"7.4.2","type":"filebeat","ephemeral_id":"9bf7ff2d-3c39-4e04-8b8d-d2fe300d4f3e"},"username":"_eva.vls_"}}

So which field elasticsearch is supposed to use as a timestamp of the event?

I don't see anything that has been collected by filebeat which looks like a timestamp.

Could you share the log line that has been collected by filebeat which corresponds to this Event in elasticsearch?

{"@timestamp":"2020-03-06T20:18:23.894670031Z","exportable":true,"level":"info","message":"Get full report request","report_uuid":"bf0f8a56-4a46-4cf1-8706-491b3607eaf3","username":"_eva.vls_"}

What is the filebeat configuration?


- type: log
  enabled: true
  json.keys_under_root: true
    - /var/log/report-generator/report-generator.log

#================================ Outputs =====================================

# Configure what outputs to use when sending the data collected by the beat.
# Multiple outputs may be used.

#-------------------------- Elasticsearch output ------------------------------
  # Array of hosts to connect to.
  hosts: [""]
  index: "trendhero-%{+yyyy.MM.dd}"

  # Optional protocol and basic auth credentials.
  protocol: "https"
  username: "elastic"
  password: "REMOVED"

  name: 'trendhero'
  pattern: 'trendhero-*'
  enabled: false

setup.ilm.enabled: auto
setup.ilm.rollover_alias: "trendhero"
setup.ilm.pattern: "{now/d}-000001"

logging.level: info

 - drop_event:
                   exportable: true