Why is the activity log stored in the adls gen2 container not a valid json

Question

Why is the activity log stored in the adls gen2 container not a valid json?

It's line by line, and the outer layer is missing '[]' and comma separation

Answer 1

Hi zmsoft,
Welcome to Microsoft Q&A, thanks for posting your query.

The activity log stored in the ADLS Gen2 container might consider as not valid JSON because the data is structured line by line, without following proper JSON formatting rules. A valid JSON format is required.

JSON data must be enclosed with an array, it must be start with [ and end with ] . If the outer array is missing, the logs won't be considered as a valid JSON entity.

JSON objects within an array must be separated by Commas. Without these commas between the log entities, the file won't confirm to JSON's Structural requirement.

This can be often happened because the activity logs may be stored as separate lines, which may make them easier to read line by line, but it results in an invalid format when treated as a single file.

• Add square brackets "[]" around the data.
• Ensure each line or object is separated by a comma (except the last one).

Reference:

https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/activity-log?tabs=powershell

Please let us know if you have any further queries. I’m happy to assist you further. 

---

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.