Pp 13603 add time stamps #21
Merged
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
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.
Next batch of time extraction.
I'm keeping an eye on how large
index.tsis getting and will consider splitting the time functions out into a separate file if necessary later on. The regex for the audit logs of/msg=audit\((\d+\.\d{3}):\d+\)/is based upon a message including something likemsg=audit(1739184096.304:468)which seems pretty safe based on looking at the formats, it could be made a little looser if we just looked for\(\d+\.\d{3}):\d+\, seems a balance between making sure we get what we expect versus becoming too brittle to future log format changes 🤷