<?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 Follow-up on old thread: Separate problems open for each service in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Follow-up-on-old-thread-Separate-problems-open-for-each-service/m-p/281933#M37139</link>
    <description>&lt;P&gt;Hello team,&lt;/P&gt;
&lt;P&gt;I'm revisiting this topic to see if there have been any updates or workarounds since it was last discussed two years ago.&lt;/P&gt;
&lt;P&gt;I'm referring to this previous thread: "Dynatrace merges the service problems with same root cause. But is there a way to have separate problems open for each of those services?"&lt;/P&gt;
&lt;P&gt;In short, the issue is that Dynatrace groups service problems that share the same root cause into a single problem. However, in some cases, we would prefer to have separate problems created per affected service, even if the root cause is shared.&lt;/P&gt;
&lt;P&gt;Has anyone found a way to achieve this behavior, or is this still a limitation in the current version?&lt;/P&gt;
&lt;P&gt;Any insights or experiences would be greatly appreciated.&lt;/P&gt;
&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
    <pubDate>Tue, 22 Jul 2025 12:20:17 GMT</pubDate>
    <dc:creator>RomanG</dc:creator>
    <dc:date>2025-07-22T12:20:17Z</dc:date>
    <item>
      <title>Follow-up on old thread: Separate problems open for each service</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Follow-up-on-old-thread-Separate-problems-open-for-each-service/m-p/281933#M37139</link>
      <description>&lt;P&gt;Hello team,&lt;/P&gt;
&lt;P&gt;I'm revisiting this topic to see if there have been any updates or workarounds since it was last discussed two years ago.&lt;/P&gt;
&lt;P&gt;I'm referring to this previous thread: "Dynatrace merges the service problems with same root cause. But is there a way to have separate problems open for each of those services?"&lt;/P&gt;
&lt;P&gt;In short, the issue is that Dynatrace groups service problems that share the same root cause into a single problem. However, in some cases, we would prefer to have separate problems created per affected service, even if the root cause is shared.&lt;/P&gt;
&lt;P&gt;Has anyone found a way to achieve this behavior, or is this still a limitation in the current version?&lt;/P&gt;
&lt;P&gt;Any insights or experiences would be greatly appreciated.&lt;/P&gt;
&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jul 2025 12:20:17 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Follow-up-on-old-thread-Separate-problems-open-for-each-service/m-p/281933#M37139</guid>
      <dc:creator>RomanG</dc:creator>
      <dc:date>2025-07-22T12:20:17Z</dc:date>
    </item>
  </channel>
</rss>

