GitHub user rgoers added a comment to the discussion: Is using %uuid{RANDOM}
pattern in JsonTemplateLayout considered garbage-free?
I would need to read more on the subject but I have to assume this is very
similar to the problem I faced with Flume. It guarantees delivery but it
doesn't guarantee an event won't be delivered multiple times. This is solved by
providing a unique id. Log4j's TimeBased UUID solves this problem by adding a
unique id when the event is created. Whether there are multiple appenders or
not only matters depending on where they are trying to deliver the data.
However, it definitely makes more sense to ensure the UUID is injected into the
LogEvent before any Appenders process it.
I am not sure why you are assuming only multiple Appenders can cause duplicates
to occur.
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3585#discussioncomment-12757187
----
This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org
