-
When a VRL transform emits multiple events, it does not copy over, or otherwise include at all, any event metadata. Subsequent transforms and sinks lose access to the source_type, timestamp, and other Vector-generated fields, along with metadata that is generated from the source. Is there a reason for this? Currently now, I have to do something like the following to basically "reconstruct" the metadata in a VRL transform before emitting the multiple events. For reference, this is when reading Azure Event Hub events using a Kafka source. The events are batched by Event Hub into a records array.
All so I can maintain the original event structure when emitting the multiple values. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
This feels weird, but I guess this is what
Note that if you did
You'd end up with multiple events properly, but |
Beta Was this translation helpful? Give feedback.
This feels weird, but I guess this is what
unnest()
really is for? I've sort of reduced it down to the following now...Note that if you did
You'd end up with multiple events properly, but
message
would have a single child objectrecords
that then contained the record data.