@Tilman Goldboom Apologies for the delayed response.
I tested the scenario with the exact json log content and transformation query, as you had shared in the question and cannot reproduce this issue. I tested it in "Germany West Central" region as well as in other regions. Here are the possible root causes:
- Please check if the uploaded file which contains the sample log in JSON format does not contain illegible/non-visible characters causing the parsing to fail.
- It might have been a transient error - and could have been resolved on its own.
Could you confirm if you are able to create the table now, with the required input?
An alternative approach would be to use the steps mentioned in the link below:
Collect logs from a text or JSON file with Azure Monitor Agent
For the script used to create the table, you could modify it to match the schema of table you need and provide the transformation query in the Data collection rule created.
Hope this helps.
If the answer did not help, please add more context/follow-up question for it. Else, if the answer helped, please click Accept answer so that it can help others in the community looking for help on similar topics.