This is the continuation of Part 3: Newly Added Analysis Services. This is the fourth blog post in a series of 5 that will give you an overview of how to configure the UCM Azure monitoring, alerting and viewing of monitoring data. Stay tuned for Part 5: Newly Added Web Services of this series of blog posts coming very soon!
The 11 services newly added services can be categorized into three main categories:
Below are the details of the recently added services.
We have added five network related services.
Azure provides two types of load balancer - Basic Load Balancer and Standard Load Balancer. Azure does not support monitoring for Basic Load Balancer so you will be able to see only standard load balancer dashboards in UCM.
Figure 15: Standard Load Balancer dashboard page Taking a closer look at the dashboard, we see there are six metrics which are monitored:
More details can be found upon navigating to the Details page.
Figure 16: Standard Load Balancer dashboard
Figure 17: Application Gateway dashboard page
Monitoring an Application Gateway can tell you precisely about the traffic flowing through your infrastructure. Abnormal behaviors can be tracked by configuring alerts on the throughput metric. Upon navigating to Application Gateway Dashboard, you will see one dashboard for each of the running application gateways. You can browse through all the dashboards using the next and the previous buttons.
Application Gateway dashboard helps you monitor the number of bytes per second the Application Gateway has served. The metric is named as Throughput.
You can open the Details page by clicking the ‘Details’ button to see the detailed view and historical data.
Figure 18: Application Gateway dashboard
Figure 19: Virtual Network Gateway dashboard page
Monitoring a virtual network gateway will help you gain visibility into the statistics of bytes and packets traveling through the tunnel along with the bandwidth consumption. Sudden increase or decrease in the bandwidth consumption means serious problems that need to be resolved in time to avoid failures. You can quickly set alerts to get notified about these changes.
Metrics for the Virtual Network Gateway:
While this seems like very limited information, the goal of these metrics is to ensure that different sites are connected to each other, and the data is flowing between them.
Also, you can see a more detailed view and graphs upon navigating to the details page by clicking the ‘Details’ button.
Figure 20: Virtual Network Gateway dashboard
Monitor bandwidth utilization of your express route circuit and set alerts to get notified if the bandwidth is under- or over-utilized.
Figure 21: Express Route Circuit dashboard page
Let us see the metrics of the Express Route Circuit.
Express Route Circuit currently has two metrics that can be monitored:
We show the averaged values and the unit is count per second, so that means the number of bits in or out per second.
Click on the ‘Details’ button to see more detailed views and samples up to one year old. Figure 22: Express Route Circuit dashboard
All of the traffic manager profiles created in your Azure account will automatically appear on the dashboard page. You can click on the details page to get a more detailed view.
If the monitoring protocol is set as HTTP or HTTPS, the Traffic Manager probing agent makes a GET request to the endpoint using the protocol, port, and relative path given. If it gets back a 200-OK response, then that endpoint is considered healthy.
If the monitoring protocol is TCP, the Traffic Manager probing agent initiates a TCP connection request using the port specified. If the endpoint responds to the request with a response to establish the connection, that health check is marked as a success, and the Traffic Manager probing agent resets the TCP connection.
If the response is a different value, or, if no response is received within the timeout period specified, then the Traffic Manager probing agent re-attempts according to the Tolerated Number of Failures setting (no re-attempts are done if this setting is 0). If the number of consecutive failures is higher than the Tolerated Number of Failures setting, then that endpoint is marked as unhealthy.
Figure 23: Traffic Manager Profile dashboard page
Let us take a closer look at the dashboard.
Two metrics are available to monitor:
Click on the ‘Details’ button to see more detailed views and samples up to one year old.
Figure 24: Traffic Manager Profile dashboard
For any questions, you can post a comment or contact email@example.com.
Refer also to Part 5: Newly Added Web Services of this series of blog posts!
Stay tuned to see more features and more monitoring support getting added to Uptime Cloud Monitor in near future.
Sign up for a 14 day FREE TRIAL of Uptime Cloud Monitor (no credit card required).
You can find more information about Uptime Cloud Monitor pricing options here.
We charge only $0.08 per month per metric!
Sign up today!