<?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>topic Are there any plans to improve Segments? in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Are-there-any-plans-to-improve-Segments/m-p/300438#M39147</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Are there any plans to improve Segments?&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;I'm asking because I've been trying to create a Segment that provides the same visibility and scope as one of our Management Zones, and I'm running into several challenges.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;With Management Zones, once I define a set of entities, everything else works automatically:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;If I open the Services page and filter by Management Zone, I see all services related to those entities.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;If I open Problems and apply the Management Zone filter, I see all relevant problems.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;The same applies to Classic Dashboards.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;In general, any page that supports Management Zone filtering automatically inherits the correct scope.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;&lt;SPAN&gt;With Segments, however, the experience is very different.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;When creating a Segment, I need to think about every type of data I want it to affect:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;If I want Services to be visible, I need to explicitly include Service filters.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;If I want Dashboards to show the correct data, I need to ensure Metrics are filtered as well.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;If I want Problems to appear, I need to include Events in the Segment definition.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;&lt;SPAN&gt;In other words, I need to manually account for every data type instead of having Dynatrace automatically derive the scope from the selected entities.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;The complexity increases in hybrid environments. For example, I have an application that runs both on Kubernetes (GKE) and Cloud Run.&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;For GKE, I can usually filter by namespaces or workloads and most related entities are included.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;For Cloud Run, it's much harder. I often need to identify specific attributes to use as filters, and there isn't always an obvious or consistent way to achieve the same result.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;&lt;SPAN&gt;I also encountered a limitation where each rule group only allows up to 10 rules, and I cannot create an additional rule group for the same entity type. This makes it difficult to build larger or more complex scopes.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;Even after spending significant time creating detailed filtering rules, I have never been able to make a Segment produce the same results as the equivalent Management Zone. The visible services, problems, endpoints, and other entities never completely match.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;At this point, I decided to stop pursuing Segments and continue using Management Zones for now.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Are there any planned improvements to make Segments easier to configure, more scalable, and more aligned with the behavior that users are familiar with from Management Zones?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 08 Jun 2026 13:28:25 GMT</pubDate>
    <dc:creator>mmsz_ext</dc:creator>
    <dc:date>2026-06-08T13:28:25Z</dc:date>
    <item>
      <title>Are there any plans to improve Segments?</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Are-there-any-plans-to-improve-Segments/m-p/300438#M39147</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Are there any plans to improve Segments?&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;I'm asking because I've been trying to create a Segment that provides the same visibility and scope as one of our Management Zones, and I'm running into several challenges.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;With Management Zones, once I define a set of entities, everything else works automatically:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;If I open the Services page and filter by Management Zone, I see all services related to those entities.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;If I open Problems and apply the Management Zone filter, I see all relevant problems.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;The same applies to Classic Dashboards.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;In general, any page that supports Management Zone filtering automatically inherits the correct scope.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;&lt;SPAN&gt;With Segments, however, the experience is very different.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;When creating a Segment, I need to think about every type of data I want it to affect:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;If I want Services to be visible, I need to explicitly include Service filters.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;If I want Dashboards to show the correct data, I need to ensure Metrics are filtered as well.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;If I want Problems to appear, I need to include Events in the Segment definition.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;&lt;SPAN&gt;In other words, I need to manually account for every data type instead of having Dynatrace automatically derive the scope from the selected entities.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;The complexity increases in hybrid environments. For example, I have an application that runs both on Kubernetes (GKE) and Cloud Run.&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;For GKE, I can usually filter by namespaces or workloads and most related entities are included.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;For Cloud Run, it's much harder. I often need to identify specific attributes to use as filters, and there isn't always an obvious or consistent way to achieve the same result.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;&lt;SPAN&gt;I also encountered a limitation where each rule group only allows up to 10 rules, and I cannot create an additional rule group for the same entity type. This makes it difficult to build larger or more complex scopes.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;Even after spending significant time creating detailed filtering rules, I have never been able to make a Segment produce the same results as the equivalent Management Zone. The visible services, problems, endpoints, and other entities never completely match.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;At this point, I decided to stop pursuing Segments and continue using Management Zones for now.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Are there any planned improvements to make Segments easier to configure, more scalable, and more aligned with the behavior that users are familiar with from Management Zones?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jun 2026 13:28:25 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Are-there-any-plans-to-improve-Segments/m-p/300438#M39147</guid>
      <dc:creator>mmsz_ext</dc:creator>
      <dc:date>2026-06-08T13:28:25Z</dc:date>
    </item>
  </channel>
</rss>

