-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Filebeat][microsoft][m365_defender] Error processing when alerts.entities is an empty list #31223
Labels
Comments
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
3 tasks
leehinman
added a commit
that referenced
this issue
Apr 11, 2022
- remove `alerts.entities` when it is an empty list. Prevents errors where `alerts.entities` is assumed to be a Map. Closes #31223
leehinman
added a commit
that referenced
this issue
Apr 12, 2022
leehinman
added a commit
that referenced
this issue
Apr 12, 2022
kush-elastic
pushed a commit
to kush-elastic/beats
that referenced
this issue
May 2, 2022
- remove `alerts.entities` when it is an empty list. Prevents errors where `alerts.entities` is assumed to be a Map. Closes elastic#31223
chrisberkhout
pushed a commit
that referenced
this issue
Jun 1, 2023
- remove `alerts.entities` when it is an empty list. Prevents errors where `alerts.entities` is assumed to be a Map. Closes #31223
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When
json.alerts.entities
is an empty list, we get the error message:most likely from
The text was updated successfully, but these errors were encountered: