Open marshalexander99 opened 1 year ago
Can you provide the entire error message you are receiving and the correlationId of the deployment?
No error messages are provided. The deployment completes without issue and no other data is produced. The rule simply fails to collect any data until changed to a location without a space in the code.
If the resource is being created successfully but not working correctly, that is an issue with the Microsoft.Insights/dataCollectionRules resource provider and not with Bicep. I would recommend opening a support ticket for this issue.
I will also reach out to the RP directly.
Have you recreated the issue? As this works via the portal and not via bicep I feel logging a support ticket will end up with me back here without a proper pointer
I have recreated the issue, however since we pass the entire request directly to the RP, and it is deploying correctly from our end but not running correctly, it something the resource provider needs to fix.
If the support ticket is being incorrectly routed to our team, we will work with the support team to fix it.
Is there any update on this Issue? I have the same Issue in my LAB. I have create an article about it: https://medium.com/p/82d393aeac14
Bicep version 0.13.1
Describe the bug When attempting to deploy a data collection rule via bicep, the rule doesn't get associated correctly with a log analytics workspace. Deploying via the portal the location 'uksouth' is used vs 'UK South' which comes via the bicep code and works fine with the rest of our landing zone deployment. I can only assume the space in UK South is the issue here and why the association fails.
To Reproduce Run the following bicep code and the log analytics workspace is not correctly associated with the data collection rule, providing that the location is 'UK South' (I'm assuming it doesn't like the space). To get it to work correctly, use 'uksouth'.
Additional context Add any other context about the problem here.