exec
and http
sources add a .timestamp
field to the event after decoding
#20404
Labels
meta: good first issue
Anything that is good for new contributors.
source: exec
Anything `exec` source related
source: http_server
Anything `http_server` source related
type: bug
A code related bug.
A note for the community
Problem
When log namespacing is enabled, I expect only the event to be in
.
For the socket source, this is the case no matter if
decoding
configuration is specified or not.For the exec and http sources, when
decoding
configuration is added, there is an additional.timestamp
field. Also, when there is no decoding configuration, the message is available inside a.message
key rather than at.
.Maybe there is a reason for the inconsistency but it was definitely surprising to me. Also, I'm not sure what this additional timestamp field represents since its value is different to
%vector.ingest_timestamp
.Configuration
Version
0.37.1
Debug Output
No response
Example Data
Commands to generate data
Without decoding
With decoding
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered: