Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write SequenceNumber in jboss-logmanager-ecs-formatter #154

Open
matthiaswelz opened this issue Dec 10, 2021 · 0 comments
Open

Write SequenceNumber in jboss-logmanager-ecs-formatter #154

matthiaswelz opened this issue Dec 10, 2021 · 0 comments
Labels
agent-java community Issues and PRs created by the community triage Issues and PRs that need to be triaged

Comments

@matthiaswelz
Copy link

matthiaswelz commented Dec 10, 2021

Hi,

because the "@timestamp" fields in ECS logging only support millisecond-precision, a sequence number is needed to keep the order of events. Adding this sequence number in FileBeat does not seem possible - only workarounds exist which include disabling multithreading (see https://discuss.elastic.co/t/sequence-number-for-ecs-events-received-by-tcp/291348 ).

Thus, the ECS formatter should add the sequence number ( https://www.elastic.co/guide/en/ecs/current/ecs-event.html#field-event-sequence ).

In case of the co.elastic.logging.jboss.logmanager.EcsFormatter this should be trivial as the ExtLogRecord from which the JSON is built already includes a method getSequenceNumber.

Adding the sequence number would solve a range of other issues regarding to log event order.

@github-actions github-actions bot added agent-java community Issues and PRs created by the community triage Issues and PRs that need to be triaged labels Dec 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agent-java community Issues and PRs created by the community triage Issues and PRs that need to be triaged
Projects
None yet
Development

No branches or pull requests

1 participant