Fix parsing of rsyslog precision timestamps #84
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jjakob
force-pushed
the
zmlogger_fix_precision_timestamps
branch
from
61d95fb
to
b2160e5
Compare
|
|
jjakob
force-pushed
the
zmlogger_fix_precision_timestamps
branch
from
b2160e5
to
a9c9233
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When rsyslog is set to use high precision timestamps (in rsyslog.conf), zmlogger, zmlogprocess and zmdailyreport stop working due to a fixed assumption that /var/log/zimbra.log will use the traditional timestamp format. This makes the regex work for both traditional and high precision timestamps so it is backwards compatible.