-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Bug: Get-UAL collection crashes because of a duplicate key #131
Comments
Interesting! Why would Microsoft put duplicate keys in their logs..? I've never had this issue before (we never use SOF-ELK), so I've only used the flag in our testing environments. I tried running it a couple of times but unfortunately, I can't reproduce the error. By the way, looking at your log blob, it doesn't seem like a normal UAL entry but more like Azure to me. No Google hits on the workload I guess we could do something dirty like this (not tested), but I'm not sure how often it happens or if there are other fields with the same issue.
I added the blob you provided to
Replacing the field names with different names seems to get rid of the error.
Doesn't feel like a good solution but yea.. |
Hi,
I attempted to collect UAL logs from my tenant using the
Get-UAL
cmdlet, but this fails with the following error:I actually found the AuditData blob, which actually causes this error:
This Blob contains the 'EventName' and 'eventName' keys which
ConvertFrom-Json
(from here) can't process.According to the Microsoft documentation, this can be fixed using the
-AsHashTable
argument. But that argument is only supported by Powershell 6.0 and newer.Do you see any other generic solution to fix this?
The text was updated successfully, but these errors were encountered: