<?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 Re: Better handling of mobile app crashes in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Better-handling-of-mobile-app-crashes/m-p/290209#M6031</link>
    <description>&lt;P&gt;The New RUM experience will have better error/crash grouping in Error Inspector and also features to manage crashes are planned there.&lt;/P&gt;</description>
    <pubDate>Tue, 25 Nov 2025 08:56:40 GMT</pubDate>
    <dc:creator>Patrick_H</dc:creator>
    <dc:date>2025-11-25T08:56:40Z</dc:date>
    <item>
      <title>Better handling of mobile app crashes</title>
      <link>https://community.dynatrace.com/t5/Alerting/Better-handling-of-mobile-app-crashes/m-p/279340#M5705</link>
      <description>&lt;P&gt;Is there a more effective way to manage and group mobile app crashes?&lt;/P&gt;
&lt;P&gt;We have a customer using a suite of mobile apps, and while crash detection is working well, we're seeing many repeated problem reports for the &lt;STRONG&gt;same underlying crash&lt;/STRONG&gt;. This leads to unnecessary duplication and noise in reporting.&lt;/P&gt;
&lt;P&gt;Ideally, we'd like to identify crashes we've already seen and tag them accordingly — for example, with a flag like seenBefore=true — to help us prioritize new or unique issues more efficiently.&lt;/P&gt;
&lt;P&gt;In settings we are limited with options:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="GregOReilly_0-1749797378612.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/28474i3062E0AE2B615C1C/image-size/medium?v=v2&amp;amp;px=400" role="button" title="GregOReilly_0-1749797378612.png" alt="GregOReilly_0-1749797378612.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Nov 2025 14:01:27 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Better-handling-of-mobile-app-crashes/m-p/279340#M5705</guid>
      <dc:creator>GregOReilly</dc:creator>
      <dc:date>2025-11-24T14:01:27Z</dc:date>
    </item>
    <item>
      <title>Re: Better handling of mobile app crashes</title>
      <link>https://community.dynatrace.com/t5/Alerting/Better-handling-of-mobile-app-crashes/m-p/290209#M6031</link>
      <description>&lt;P&gt;The New RUM experience will have better error/crash grouping in Error Inspector and also features to manage crashes are planned there.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Nov 2025 08:56:40 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Better-handling-of-mobile-app-crashes/m-p/290209#M6031</guid>
      <dc:creator>Patrick_H</dc:creator>
      <dc:date>2025-11-25T08:56:40Z</dc:date>
    </item>
  </channel>
</rss>

