elastic / elastic/integrations
[Feature Request] Improve the field mapping for Modified Properties in Microsoft Entra ID/Audit Logs
- Dominant language
- Handlebars
- Stars
- 333
- Forks
- 647
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 225
Description
**Describe the feature:**
Change the mapping of modified properties. Use the value of display name to name the rest of the field names.
For example:
`azure.auditlogs.properties.target_resources.0.modified_properties.1.display_name: 'Group.DisplayName'`
to be
```
azure.modified_properties.group_display_name.old_value = "Test"
azure.modified_properties.group_display_name.new_value = "Test-1"
```
This way the fields names are easily recognized and their associated values.
**Describe the use case:**
Using fields that are mapped like this is not ideal we have like 19 values per each and requires management as one field's expected value changes. Its hard to predict that azure.auditlogs.properties.target_resources.0.modified_properties.1.display_name will be the same field.
Currently to deal with nested json, the fields are parsed or mapped like this;
```
azure.auditlogs.properties.target_resources.*.modified_properties.*.display_name
azure.auditlogs.properties.target_resources.*.modified_properties.*.new_value
azure.auditlogs.properties.target_resources.*.modified_properties.*.old_value
```
Leading to this:
```
"azure.auditlogs.properties.target_resources.0.modified_properties.1.display_name"
"azure.auditlogs.properties.target_resources.0.modified_properties.1.new_value"
"azure.auditlogs.properties.target_resources.0.modified_properties.1.old_value"
"azure.auditlogs.properties.target_resources.0.modified_properties.2.display_name"
"azure.auditlogs.properties.target_resources.0.modified_properties.2.new_value"
"azure.auditlogs.properties.target_resources.0.modified_properties.2.old_value"
```
Contributor guide
Assessment
This issue has not been assessed yet.