Open JeffreyGarrett opened 5 years ago
I have the same issue. does anyone know about that?
@JeffreyGarrett and @leandroscardua looks like the issue is with Application Insights once Availability Test are added to the deployment.
After adding availability test to any deployment I create, I get the following:
Deployment failed. Correlation ID: an ID string here. { "code": "BadRequest", "message": "Bad Request", "innererror": { "diagnosticcontext": "context value here", "time": "2019-02-20T07:50:10.9359978Z" } }
I notice some warning headers here that allude to namespace changes in Azure Monitor, which now houses Application Insights:
Get-AzureRmLog -CorrelationId "ID string here" WARNING: 8:02:49 AM - ** The namespace for all the model classes will change from Microsoft.Azure.Management.Monitor.Management.Models to Microsoft.Azure.Management.Monitor.Models infuture releases. WARNING: 8:02:49 AM - The namespace for output classes will be uniform for all classes in future releases to make it independent of modifications in the model classes. WARNING: [Get-AzLog] Parameter deprecation: The DetailedOutput parameter will be deprecated in a future breaking change release.**
Maybe someone from Microsoft will chime in with more information or forward this information to the appropriate team.
Any update on this? I have the same issue here. @marlonsingleton are you saying that template has been put there without being tested or is it recently breaking because of another change?
I'm sure the template worked at the time of creation. The issue is likely due to another change. More specifically, at the time of my post, I also encountered issues deploying Availability Tests directly from the portal. @hosseinjayride have you tested from the portal?
Hi Guys,
I don't have any update :( I tried to use API instead powershell script. I'm having the same problem ...
On Mon, Mar 25, 2019, 6:03 AM Marlon Singleton, notifications@github.com wrote:
I'm not implying that at all. I'm sure the template worked at the time of creation. More specifically, at the time of my post, I encountered issues deploying Availability Tests directly from the portal as well. @hosseinjayride https://github.com/hosseinjayride have you tested from the portal?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Azure/azure-quickstart-templates/issues/5771#issuecomment-476128054, or mute the thread https://github.com/notifications/unsubscribe-auth/AXjerYqSfZkGCLivVCktKVK98N4vV06Mks5vaJ70gaJpZM4akRds .
Azure Portal > Help + Support > New Support Request or utilize your company's Azure support plan to investigate further. << My humble suggestion
Thanks @marlonsingleton for your reply. Actually, the issue for me was that I used the webtest tempate in this github quickstart-templates in conjunction with my own template. What I had was that I had my app insights deployed using "linked" template and the webtest from this repo. Turned out webtest deployment failed because the app insight was not deployed "directly" with the same template deployment.
I copied and pasted the template and the parameters, and deployed to a new resource group without changing anything or using linked template and it worked. So, nothing wrong with the template. Thanks.
However, for those who still have the issue (@JeffreyGarrett @leandroscardua ):
@hosseinjayride I'm glad you were able to successfully deploy along with webtest.
I was also struggling with this template, I got the following error message during deployment:
You cannot create or modify classic metric alerts for this subscription as this subscription
Classic alerts are no longer supported, so that’s no surprise. I hope this template get updated someday. I found some good documentation here that I used to resolve my problem:
[Template Name goes here](Template link goes here) dynamic-web-tests https://github.com/Azure/azure-quickstart-templates/tree/c99d83208f566f75bcd3301e645f5982c4b0a7c3/201-dynamic-web-tests
Issue Details
When deploying the template (after changing the values) the webtests deployment fails. The error we get is a basic request with no detail
BadRequest
Repro steps
template
parameters
Please let me know what else you need.