-
Notifications
You must be signed in to change notification settings - Fork 396
(Azure) Resolve invalid JSON Object under properties field #1015
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
mattsp1290
merged 5 commits into
DataDog:master
from
d1g1tal-lore-34:jcruz/fix-log-properties
Nov 6, 2025
Merged
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
ca62654
fix(azure): Resolve properties field issue, that contains JSON string…
d1g1tal-lore-34 4411f19
Added test cases, for fixPropertiesJsonString for code coverage
d1g1tal-lore-34 486d79e
Applied recommendation from mattsp1290, which simplifies the if condi…
d1g1tal-lore-34 e37c2a1
Finalized the simplified function, added missing return statements
d1g1tal-lore-34 9867288
Added additional test cases for fixPropertiesJsonString, that handles…
d1g1tal-lore-34 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function has a lot of return paths that all seem to do the same thing. This could be simplified a bit to have a single return and combine our checks into a single statement to verify whether or not record.properties has one of these malformed objects.
We'll need to do a little verification on our end to make this work with live data and double check the behavior of nested message and level fields.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mattsp1290 I went ahead and took the changes that you've recommended. I added a couple of return clauses that ensures:
I have also added a couple of additional test cases, that will test nested objects.