Abstract
This article is about working with Management zones and Azure services overview page. For the sake of article we are going to take Azure load balancers service as an example. Article covers one of the many scenarios.
Problem
In an Azure environment with multiple standard load balancers, selecting "All" as the management zone displays all Azure load balancer services. However, when selecting the specific management zone to which a load balancer belongs, the load balancer service may not be visible. (Reference images)
When selecting "All" management zone:
When selecting proper management zone where service belongs to :
Resolution
Review the management zone rule.
The affected management zone might have rules to include the instances (CUSTOM_DEVICE) but not the services (CUSTOM_DEVICE_GROUP). The counter knows of the instances, but when it checks what to display, which should be a clickable Load balancer button, it sees no CUSTOM_DEVICE_GROUP's, so displays nothing. This can be helped by adding a rule to the management zone to include custom device groups, e.g.:
type("CUSTOM_DEVICE_GROUP"), toRelationship.IS_INSTANCE_OF(type("CUSTOM_DEVICE"))
where the part inside IS_INSTANCE_OF can be refined to match the rest of the management zone. Adding just
type("CUSTOM_DEVICE_GROUP")
should also work, but then more groups will be part of the management zone (but not the custom devices/instances themselves)
What to do next
If the suggested approach does not resolve the issue, we recommend opening a support case for further detailed investigation.
