update: extend logpoint_m365_mapping with additional fields and operation mapping#22
Open
tastysammich wants to merge 1 commit intologpoint:mainfrom
Open
update: extend logpoint_m365_mapping with additional fields and operation mapping#22tastysammich wants to merge 1 commit intologpoint:mainfrom
logpoint_m365_mapping with additional fields and operation mapping#22tastysammich wants to merge 1 commit intologpoint:mainfrom
Conversation
Added some additional mappings that could be yielded through m365 logs
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
This PR updates the
logpoint_m365_mappingdictionary to include additional Microsoft 365 fields and align the mapping even more closely with Logpoint’s schema.Changes
Application→application_idObjectId→object_idRequestType→request_typeOperationmapping from"operation"to"action"for consistencyThese changes aim to improve coverage of M365 event fields in Logpoint backend mappings for more accurate normalization and reducing ambiguity in field naming (& further providing more context for downstream queries and analytics). Please let me know if there's a need to work on an alternative solution with the operation field or any other field to bridge this change well, thank you for working with me on all this! 😃