Skip to main content
Question

How can I get the default `@timestamp` on elastic output?

  • March 11, 2025
  • 75 replies
  • 207 views

Show first post

75 replies

  • Author
  • Known Participant
  • March 11, 2025

That's the document I set manually. Not working :slightly_smiling_face:


  • Author
  • Known Participant
  • March 11, 2025

Documentation problem maybe regarding "ingest pipeline". I used the field "Elastic pipeline" but that didn't work. I had to use the "extra parameters".


  • Author
  • Known Participant
  • March 11, 2025

Not working:


  • Author
  • Known Participant
  • March 11, 2025

Working:


  • Employee
  • March 11, 2025

I had problems with an older version of Cribl with the pipeline, it wasn't being put in the correct place in the url that was constructed for the API call


  • Author
  • Known Participant
  • March 11, 2025

After adding the extra parameter, I see this: `POST /_bulk?pipeline=remove_id HTTP/1.1`


  • Employee
  • March 11, 2025

What do you see when it is specified in the Elastic pipeline field?


  • Employee
  • March 11, 2025

I feel a bug report coming on....


  • Author
  • Known Participant
  • March 11, 2025

Just `_bulk`


  • Author
  • Known Participant
  • March 11, 2025

Was just looking at this with somebody else. The problem is that it needs to be "quoted"


  • Author
  • Known Participant
  • March 11, 2025

Then, it shows up in the proper place:```{"create":{"_index":"interfaces-sensors-ptx","pipeline":"remove_id","_id":"885zjZkprnmYaz69"}}```


  • Author
  • Known Participant
  • March 11, 2025

I think this should be a little clearer:```Elastic pipeline: To send data to an Elastic Ingest pipeline, optionally enter that pipeline's name as a constant.```


  • Author
  • Known Participant
  • March 11, 2025

optionally should not be there. It should say JavaScript or quoted constant.


<@U03CJ90F91A&gt; :point_up:


  • Employee
  • March 11, 2025

Sheesh, <@UUP82DJHE&gt;, nothing like calling me in at the end of a crazy long thread. But thanks for tagging me, I'll see if we can get that cleared up.


  • Employee
  • March 11, 2025

Hi <@U0410L186KS&gt;, if you just want to add the new @timestamp field to the event, in place of _time... this is an easy way to create a field with special characters.


  • Employee
  • March 11, 2025

`__e['@timestamp';]`


  • Author
  • Known Participant
  • March 11, 2025

<@U02JJLAGJHF&gt; Thanks. I also see that "undefined". Learning the tricks


  • Employee
  • March 11, 2025

then "undefined" just eliminates that other `_time` field from the event. Enjoy!!!


  • Author
  • Known Participant
  • March 11, 2025

What is so special with `__e` ?


  • Employee
  • March 11, 2025

Yep, steal the time from _time, throw it into a new custom field, then get rid of _time.


  • Employee
  • March 11, 2025

__e allows you to create/reference fields with custom characters.


  • Employee
  • March 11, 2025

  • Employee
  • March 11, 2025

Sometimes you will need to reference a field from a source that uses those "non standard" characters, etc. This way you can still use that data, or correct it, before moving on. OK? Good Luck <@U0410L186KS&gt;


  • Author
  • Known Participant
  • March 11, 2025

Got it.