Azure Network Watcher exercise fails

Dr. Thomas Hesse 16 Reputation points
2021-07-10T16:17:33.27+00:00

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:

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
Azure Network Watcher
An Azure service that is used to monitor, diagnose, and gain insights into network performance and health.
161 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dr. Thomas Hesse 16 Reputation points
    2021-07-13T06:18:58.8+00:00

    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 person found this answer helpful.