<?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 Get alerted when a problem is updated in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Get-alerted-when-a-problem-is-updated/m-p/254184#M4782</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;We are using ServiceNOW integration for problem notifications and it is being used as custom integration not the classic ServiceNOW integration that is available. Currently when a particular problem is created the webhook is called and also the webhook is called when the same problem is closed. The problem we are getting here is when a problem is created there are like 5-6 impacted entities in this case. The webhook is triggered as soon as the problem is created but the root cause is detected after some delay. There is no placeholder for root cause that can be passed in the problem payload. As a result of this limitation there is a problem in identifying and mapping the exact impacted entity.&lt;/P&gt;
&lt;P&gt;Can anyone suggest an alternative or even best a solution to this problem ??&lt;/P&gt;</description>
    <pubDate>Wed, 25 Sep 2024 07:50:04 GMT</pubDate>
    <dc:creator>Maheedhar_T</dc:creator>
    <dc:date>2024-09-25T07:50:04Z</dc:date>
    <item>
      <title>Get alerted when a problem is updated</title>
      <link>https://community.dynatrace.com/t5/Alerting/Get-alerted-when-a-problem-is-updated/m-p/254184#M4782</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;We are using ServiceNOW integration for problem notifications and it is being used as custom integration not the classic ServiceNOW integration that is available. Currently when a particular problem is created the webhook is called and also the webhook is called when the same problem is closed. The problem we are getting here is when a problem is created there are like 5-6 impacted entities in this case. The webhook is triggered as soon as the problem is created but the root cause is detected after some delay. There is no placeholder for root cause that can be passed in the problem payload. As a result of this limitation there is a problem in identifying and mapping the exact impacted entity.&lt;/P&gt;
&lt;P&gt;Can anyone suggest an alternative or even best a solution to this problem ??&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2024 07:50:04 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Get-alerted-when-a-problem-is-updated/m-p/254184#M4782</guid>
      <dc:creator>Maheedhar_T</dc:creator>
      <dc:date>2024-09-25T07:50:04Z</dc:date>
    </item>
    <item>
      <title>Re: Get alerted when a problem is updated</title>
      <link>https://community.dynatrace.com/t5/Alerting/Get-alerted-when-a-problem-is-updated/m-p/265452#M5257</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/76275"&gt;@Maheedhar_T&lt;/a&gt;, did you manage to solve this one? It would be great if you share it with the Community &lt;span class="lia-unicode-emoji" title=":rocket:"&gt;🚀&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2024 09:13:22 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Get-alerted-when-a-problem-is-updated/m-p/265452#M5257</guid>
      <dc:creator>GosiaMurawska</dc:creator>
      <dc:date>2024-12-17T09:13:22Z</dc:date>
    </item>
    <item>
      <title>Re: Get alerted when a problem is updated</title>
      <link>https://community.dynatrace.com/t5/Alerting/Get-alerted-when-a-problem-is-updated/m-p/265604#M5275</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/76275"&gt;@Maheedhar_T&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you seek delaying the reported alerts, you can increase the "Delay" timing within the configured severities among the alerting profiles.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://docs.dynatrace.com/docs/analyze-explore-automate/notifications-and-alerting/alerting-profiles" target="_blank"&gt;https://docs.dynatrace.com/docs/analyze-explore-automate/notifications-and-alerting/alerting-profiles&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://www.youtube.com/watch?v=PeAFTM0_6Dw" target="_blank"&gt;https://www.youtube.com/watch?v=PeAFTM0_6Dw&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2024-12-18_12h17_30.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/25298i1179478E012C1410/image-size/large?v=v2&amp;amp;px=999" role="button" title="2024-12-18_12h17_30.png" alt="2024-12-18_12h17_30.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Also from ServiceNow side you can validate the same concern if it's configurable from its end would be an added value.&lt;/P&gt;&lt;P&gt;Hoping it helps.&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2024 09:08:35 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Get-alerted-when-a-problem-is-updated/m-p/265604#M5275</guid>
      <dc:creator>Peter_Youssef</dc:creator>
      <dc:date>2024-12-18T09:08:35Z</dc:date>
    </item>
  </channel>
</rss>

