You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Basically all of our logs contain timestamps like 1591375232, 1591375232.833 or 1591375232.833587995 (in the same logfile) and it would be a pity to loose the fractions.
Describe the solution you'd like
The Unix format in the timestamp stage should also accept fractional seconds.
Describe alternatives you've considered
Current alternative is to write a regex that only extracts the full seconds, but this is clearly not very nice.
* support unix timestamps with fractional seconds
see #2193
* add test for parsing unix timestamp with fractions
* mention Unix timestamp with fractions in docs
* return error if timestamp is not split into two parts
* don't capitalize error
Co-authored-by: Cyril Tovena <cyril.tovena@gmail.com>
Co-authored-by: Cyril Tovena <cyril.tovena@gmail.com>
Is your feature request related to a problem? Please describe.
Basically all of our logs contain timestamps like
1591375232
,1591375232.833
or1591375232.833587995
(in the same logfile) and it would be a pity to loose the fractions.Describe the solution you'd like
The
Unix
format in thetimestamp
stage should also accept fractional seconds.Describe alternatives you've considered
Current alternative is to write a regex that only extracts the full seconds, but this is clearly not very nice.
Additional context
Maybe something like this in util.go:
The text was updated successfully, but these errors were encountered: