Add optional pid to regex expression for java log files for 2024.2 #179
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
…Regex is adjusted to optionally pull in id (assumed to be PID) and successfully parse 2024.2+ logs.
|
Thanks for the contribution! Before we can merge this, we need @jroodNHA to sign the Salesforce Inc. Contributor License Agreement. |
|
I have had both @jroodNHA and @joshisrood sign the license agreement. Let me know if there is anything that needs to be done from the contributor side. |
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.
Fix for #178 .
In 2024.2 java logs, a new id is added directly following ts_offset. Regex is adjusted to optionally pull in id (assumed to be PID) and successfully parse 2024.2+ logs.