question

DrThomasHesse-9076 avatar image
0 Votes"
DrThomasHesse-9076 asked SaiKishor-MSFT commented

Azure Network Watcher exercise fails

I am running the Exercise - Troubleshoot a network by using Network Watcher monitoring and diagnostic tools in the Monitor and troubleshoot your end-to-end Azure network infrastructure by using network monitoring tools tutorial:
- https://docs.microsoft.com/en-us/learn/modules/troubleshoot-azure-network-infrastructure/3-exercise-troubleshoot-networking-with-network-watcher

I can create the network, the VMs, the (false) NSG rule, I can enable the Network Watcher and view the topology in the Azure Portal. It looks exactly like in the exercise guide.

But when I try to create the Connection Monitor following exactly the description in the exercise guide, I am always getting the following error message (after clicking create):

Connection Monitor Back-to-front-HTTP-test creation failed

What went wrong? How can I get more information on the failure?

Thanks a lot!

Best regards,
Thomas

azure-network-watcher
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@DrThomasHesse-9076 Thank you for reaching out to Microsoft Q&A.

I understand that you are unable to create a connections monitor although you followed steps given in the referred document.


I was able to follow the same and create it successfully. As shown below:


113988-image.png

However, I understand that you are receiving an error. Could you please copy paste the exact error here so I can understand and suggest accoridngly? Thank you!


0 Votes 0 ·
image.png (111.6 KiB)

Dear @SaiKishor-MSFT,

Thanks for picking this up so quickly. I could indeed solve the immediate issue myself: When I tried to create the connection monitor in Azure CLI, it responded with a meaningful error message telling me that the subscription was not registered for Microsoft.OperationalInsights. It was working fine (both in the UI and through CLI) when I added the registration.

Which leaves me with the following question: Why does the UI not give any meaningful error message? “Connection Monitor Back-to-front-HTTP-test creation failed” was the only error message I could see in the UI.

I also noticed that the failed transaction did create a Back-to-front-HTTP-test connection monitor. I could see that through the CLI, but not in the UI. So it seems the failed transaction was not cleanly rolled back.

And one more suggestion: You should add a hint in the exercise that the subscription must be registered for Microsoft.OperationalInsights. In a later exercise, "Troubleshoot a network by using Network Watcher metrics and logs", it is noticed that the subscription must be registered to microsoft.insights.

Thanks and best regards,
Thomas

0 Votes 0 ·

1 Answer

DrThomasHesse-9076 avatar image
0 Votes"
DrThomasHesse-9076 answered SaiKishor-MSFT commented

Dear @SaiKishor-MSFT,

Thanks for picking this up so quickly. I could indeed solve the immediate issue myself: When I tried to create the connection monitor in Azure CLI, it responded with a meaningful error message telling me that the subscription was not registered for Microsoft.OperationalInsights. It was working fine (both in the UI and through CLI) when I added the registration.

Which leaves me with the following question: Why does the UI not give any meaningful error message? “Connection Monitor Back-to-front-HTTP-test creation failed” was the only error message I could see in the UI.

I also noticed that the failed transaction did create a Back-to-front-HTTP-test connection monitor. I could see that through the CLI, but not in the UI. So it seems the failed transaction was not cleanly rolled back.

And one more suggestion: You should add a hint in the exercise that the subscription must be registered for Microsoft.OperationalInsights. In a later exercise, "Troubleshoot a network by using Network Watcher metrics and logs", it is noticed that the subscription must be registered to microsoft.insights.

Thanks and best regards,
Thomas

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@DrThomasHesse-9076 Thank you for confirming that it works now.

The UI usually gives an error message. This is the error message I received while I was working on it yesterday:

114217-nw-error.png

However, I understand that was not the case for you. I will reach out to our internal team regarding this and check why this happened as well as regarding the rollback and Microsoft.OperationalInsights registry. Thank you!


0 Votes 0 ·
nw-error.png (95.1 KiB)