Skip to content

log: increase precision in log's timestamp to nanoseconds - #9986

Closed
lecaros wants to merge 2 commits into
3.2from
backport-9985-to-3.2
Closed

lecaros wants to merge 2 commits into
3.2from
backport-9985-to-3.2

Conversation

@lecaros

@lecaros lecaros commented Feb 21, 2025

Copy link
Copy Markdown
Contributor

backport #9985 to 3.2


Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

Signed-off-by: lecaros <lecaros@calyptia.com>
Signed-off-by: lecaros <lecaros@calyptia.com>
@lecaros

lecaros commented Mar 5, 2025

Copy link
Copy Markdown
Contributor Author

not backporting this to 3.2

@lecaros lecaros removed this from the Fluent Bit Next milestone Mar 5, 2025
@pwhelan

pwhelan commented Mar 5, 2025

Copy link
Copy Markdown
Contributor

Have to asses the risk, might reopen later.

@pwhelan

pwhelan commented Mar 13, 2025

Copy link
Copy Markdown
Contributor

Is it possible to make the new nanosecond precision optional and disabled by default? If so I would approve it for 3.2.

@edsiper we might want to consider porting the same option to master.

@patrick-stephens

Copy link
Copy Markdown
Contributor

Is it possible to make the new nanosecond precision optional and disabled by default? If so I would approve it for 3.2.

@edsiper we might want to consider porting the same option to master.

Yeah I think we should keep current behaviour as the default - we do not know what folks are doing with timestamps so may break things on upgrade from experience.

@lecaros lecaros closed this May 20, 2025

This branch was previously deployed

1 inactive deployment
pr — 34f9e631 Deployed Mar 13, 2025 by pwhelan
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants