[receiver/mongodbatlas] Fix log parsing for v4.2 clusters #14088
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
djaglowski
added
the
ready to merge
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.
Description:
MongoDB Atlas supports multiple MongoDB versions. v4.2 was the last version to use a non-structured log (https://www.mongodb.com/docs/v4.2/reference/log-messages/) - the next supported version begins using structured logging (https://www.mongodb.com/docs/v4.4/reference/log-messages/).
This means that v4.2 host logs must be parsed differently. Audit logs have remained JSON between versions (for 4.2: https://www.mongodb.com/docs/v4.2/reference/audit-message/#audit-message), so they didn't require any change to parse.
Link to tracking Issue: Resolves #14008
Testing: