Azure Traffic Manager Endpoints show Degraded Even when 200 is Returned

Question

I have an Azure Traffic Manager Profile with two Endpoints (Linux VM's running RabbitMQ).

The endpoints are of Type "Azure Endpoint" and the Target Resource Type is "Public IP Address".

When I look at the Traffic Manager Profile it reports that the Status of the profile is "Enabled", and the Monitor Status is "Degraded".

On Each of the endpoints it reports that their Status is "Enabled" and the Monitor Status is "Degraded".

I have the Traffic Manager Profile configured with Protocol as "HTTP" and Port as 15672 and the path as "/index.html".

The problem is I can't tell why it is reporting "Degraded" because if I do a wget command.

wget <vmname1>.cloudapp.azure.com:15672/index.html

Resolving <vmname1>.cloudapp.azure.com... <ip address>
Connecting to <vmname1>.cloudapp.azure.com|<ip address>|:15672... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1419 (1.4K) [text/html]

All the "documentation" (which for Azure is frustratingly just blog posts) says that if it returns 200 then it should be "Online" and not "Degraded".

Jonathan Tuliani - MSFT Jonathan Tuliani - MSFT · Accepted Answer · 2016-05-27T09:08:51

Based on your reply, it is very likely that the issue is that the Traffic Manager health checks are being blocked by your NSG rules.

We don't have an easy way to configure Traffic Manager in NSGs today, nor do we publish the Traffic Manager health check source IP addresses. These are gaps we are planning to fill. In the meantime, the recommended workaround is to use a dedicated health check page running on a different TCP port for Traffic Manager, and apply the NSG only to the port used by your application.

Azure Traffic Manager Endpoints show Degraded Even when 200 is Returned

2 Answers