-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
parser: support subsecond resolution with colon (%s:%L) #2210
Comments
I think we should go with the 'colon' support only and not make it configurable (just trying to avoid a config for a simple use case). @fujimotos can you take care of this ? |
@edsiper All right, I assigned this issue to myself. |
@fujimotos @edsiper Don't you guys think that time in millis should also be supported by default. We get the following logs with Log4j2 JSON layout:
Will having just %s or %L work for this? |
@thisisabhishek Can you submit a new issue for it? My understanding is that you want Fluent Bit to be aware of "milliseconds I assume this support is possible and useful, but I think it is a different |
Bug Report
Describe the bug
I have a 3rd party application (Forgerock OpenAM) that writes timestamps as follows in some log files:
Note that it uses a colon to separate subseconds, hence of the format "%S:%L". As per #703, only "%S.%L" (dot) and "%S,%L" (comma) are currently supported by fluent-bit.
To Reproduce
Consider log entries as follows:
Parser config:
The result:
Expected behavior
It should be possible to have any separator between %S and %L. This should be defined via Time_Format.
Your Environment
The text was updated successfully, but these errors were encountered: