Skip to content
Discussion options

You must be logged in to vote

get_enrichment_table_record does not wait or retry when a key is missing. The two file sources run independently, so metadata is not guaranteed to reach the table before its log events.

Omitting flush_interval makes writes visible immediately after insertion, but does not remove that ordering race. I reproduced both behaviors on Vector 0.60.0.

There is also a restart issue: the memory table starts empty, while the metadata file's saved checkpoint can prevent it from being read again. I verified that locally too.

For reliable enrichment, include the metadata in each log event, or, if the metadata is available before startup, consolidate it into a CSV loaded by a file enrichment table. If y…

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
1 reply
@valentino-aguiar-gsa
Comment options

Comment options

You must be logged in to vote
0 replies
Answer selected by pront
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
source:file Anything `file` source related domain:config Anything related to configuring Vector domain:enriching Anything related to enriching Vector's events with context data domain:enrichment_tables Anything related to Vector's enrichment tables enrichment_table:memory Anything related to the `memory` enrichment table
2 participants