<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Azure services not visible when selecting the Management zones in Troubleshooting</title>
    <link>https://community.dynatrace.com/t5/Troubleshooting/Azure-services-not-visible-when-selecting-the-Management-zones/ta-p/264740</link>
    <description>&lt;H1&gt;Abstract&lt;/H1&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H1&gt;&lt;STRONG&gt;Problem&lt;/STRONG&gt;&lt;/H1&gt;
&lt;P&gt;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)&lt;/P&gt;
&lt;P&gt;When selecting "All" management zone:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="bhushangholap_0-1733740132194.png" style="width: 768px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/25113i67C9FFDF32A56ACD/image-dimensions/768x471?v=v2" width="768" height="471" role="button" title="bhushangholap_0-1733740132194.png" alt="bhushangholap_0-1733740132194.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;When selecting proper management zone where service belongs to :&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="bhushangholap_1-1733740290638.png" style="width: 768px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/25114i7CDC6EA23AF091D5/image-dimensions/768x455?v=v2" width="768" height="455" role="button" title="bhushangholap_1-1733740290638.png" alt="bhushangholap_1-1733740290638.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp;&lt;/P&gt;
&lt;H1&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/H1&gt;
&lt;P&gt;&lt;SPAN&gt;Review the management zone rule.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The affected management zone might have rules to include the instances (CUSTOM_DEVICE) but not the services (CUSTOM_DEVICE_GROUP).&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;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.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;This can be helped by adding a rule to the management zone to include custom device groups, e.g.:&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="javascript"&gt;type("CUSTOM_DEVICE_GROUP"), toRelationship.IS_INSTANCE_OF(type("CUSTOM_DEVICE")) &lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;where the part inside IS_INSTANCE_OF can be refined to match the rest of the management zone. Adding just&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="javascript"&gt;type("CUSTOM_DEVICE_GROUP") &lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;should also work, but then more groups will be part of the management zone (but not the custom devices/instances themselves)&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H1&gt;What to do next&lt;/H1&gt;
&lt;P&gt;If the suggested approach does not resolve the issue, we recommend opening a support case for further detailed investigation.&lt;/P&gt;</description>
    <pubDate>Fri, 13 Dec 2024 15:40:22 GMT</pubDate>
    <dc:creator>bhushangholap</dc:creator>
    <dc:date>2024-12-13T15:40:22Z</dc:date>
    <item>
      <title>Azure services not visible when selecting the Management zones</title>
      <link>https://community.dynatrace.com/t5/Troubleshooting/Azure-services-not-visible-when-selecting-the-Management-zones/ta-p/264740</link>
      <description>&lt;H1&gt;Abstract&lt;/H1&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;H1&gt;&lt;STRONG&gt;Problem&lt;/STRONG&gt;&lt;/H1&gt;
&lt;P&gt;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)&lt;/P&gt;
&lt;P&gt;When selecting "All" management zone:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="bhushangholap_0-1733740132194.png" style="width: 768px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/25113i67C9FFDF32A56ACD/image-dimensions/768x471?v=v2" width="768" height="471" role="button" title="bhushangholap_0-1733740132194.png" alt="bhushangholap_0-1733740132194.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;When selecting proper management zone where service belongs to :&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="bhushangholap_1-1733740290638.png" style="width: 768px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/25114i7CDC6EA23AF091D5/image-dimensions/768x455?v=v2" width="768" height="455" role="button" title="bhushangholap_1-1733740290638.png" alt="bhushangholap_1-1733740290638.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp;&lt;/P&gt;
&lt;H1&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/H1&gt;
&lt;P&gt;&lt;SPAN&gt;Review the management zone rule.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The affected management zone might have rules to include the instances (CUSTOM_DEVICE) but not the services (CUSTOM_DEVICE_GROUP).&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;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.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;This can be helped by adding a rule to the management zone to include custom device groups, e.g.:&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="javascript"&gt;type("CUSTOM_DEVICE_GROUP"), toRelationship.IS_INSTANCE_OF(type("CUSTOM_DEVICE")) &lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;where the part inside IS_INSTANCE_OF can be refined to match the rest of the management zone. Adding just&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="javascript"&gt;type("CUSTOM_DEVICE_GROUP") &lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;should also work, but then more groups will be part of the management zone (but not the custom devices/instances themselves)&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H1&gt;What to do next&lt;/H1&gt;
&lt;P&gt;If the suggested approach does not resolve the issue, we recommend opening a support case for further detailed investigation.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Dec 2024 15:40:22 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Troubleshooting/Azure-services-not-visible-when-selecting-the-Management-zones/ta-p/264740</guid>
      <dc:creator>bhushangholap</dc:creator>
      <dc:date>2024-12-13T15:40:22Z</dc:date>
    </item>
  </channel>
</rss>

