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

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

Draft
wants to merge 2 commits into
base: 3.2
Choose a base branch
from

Conversation

lecaros
Copy link
Contributor

@lecaros lecaros commented Feb 21, 2025

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
Copy link
Contributor Author

lecaros commented Mar 5, 2025

not backporting this to 3.2

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

pwhelan commented Mar 5, 2025

Have to asses the risk, might reopen later.

@pwhelan
Copy link
Contributor

pwhelan commented Mar 13, 2025

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
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.

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