<?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: Maintenance Windows and Open Problems in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Maintenance-Windows-and-Open-Problems/m-p/181009#M2864</link>
    <description>&lt;P&gt;Calling for DT Professional Help!!!!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This question has come up many times and the ambiguity of the Dynatrace documentation (&lt;A href="https://www.dynatrace.com/support/help/how-to-use-dynatrace/problem-detection-and-analysis/notifications-and-alerting/maintenance-windows/define-maintenance-window" target="_blank"&gt;https://www.dynatrace.com/support/help/how-to-use-dynatrace/problem-detection-and-analysis/notifications-and-alerting/maintenance-windows/define-maintenance-window&lt;/A&gt;) has been the result of countless Support tickets.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could someone from DT explain, once and for all, how Dynatrace handles the transitional states for all 3 options, in extremely detail. Then, please update the on-line documentation with it.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Getting the support answer of "DT is working as intended" but without the details of understanding exactly what "as intended" is causing lots of confusion.&amp;nbsp; &amp;nbsp;I need enough information and details so that I, as a client, can clearly predict Dynatrace's environmental responses and not have to try and make sense of them after the fact.&lt;/P&gt;</description>
    <pubDate>Fri, 18 Feb 2022 17:20:58 GMT</pubDate>
    <dc:creator>ct_27</dc:creator>
    <dc:date>2022-02-18T17:20:58Z</dc:date>
    <item>
      <title>Maintenance Windows and Open Problems</title>
      <link>https://community.dynatrace.com/t5/Alerting/Maintenance-Windows-and-Open-Problems/m-p/168012#M2440</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;
&lt;P&gt;What will happen when the maintenance windows duration is finished and there is still an open problem.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;If the problem detection and alerting configured as "Detect problems but don't alert".&lt;/LI&gt;
&lt;LI&gt;If the problem detection and alerting configured as "Disable problem detection during maintenance".&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Babar&lt;/P&gt;</description>
      <pubDate>Mon, 21 Jun 2021 15:12:12 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Maintenance-Windows-and-Open-Problems/m-p/168012#M2440</guid>
      <dc:creator>Babar_Qayyum</dc:creator>
      <dc:date>2021-06-21T15:12:12Z</dc:date>
    </item>
    <item>
      <title>Re: Maintenance Windows and Open Problems</title>
      <link>https://community.dynatrace.com/t5/Alerting/Maintenance-Windows-and-Open-Problems/m-p/168280#M2442</link>
      <description>&lt;P&gt;Under "Detect problems but don't alert" - the problem would stay open until resolved.&lt;/P&gt;&lt;P&gt;Under "Disable problem detection during maintenance" - the problem would open after crossing the applicable threshold&amp;nbsp;&lt;EM&gt;after&amp;nbsp;&lt;/EM&gt;the maintenance window is finished.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Refer to your alerting profiles to see how long the threshold needs to be crossed for the problem to open (for example, a delay of 3 minutes on an availability rule would require the threshold to be crossed for 3 minutes straight in order for the problem to be opened)&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jun 2021 13:59:02 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Maintenance-Windows-and-Open-Problems/m-p/168280#M2442</guid>
      <dc:creator>paul_ingle</dc:creator>
      <dc:date>2021-06-24T13:59:02Z</dc:date>
    </item>
    <item>
      <title>Re: Maintenance Windows and Open Problems</title>
      <link>https://community.dynatrace.com/t5/Alerting/Maintenance-Windows-and-Open-Problems/m-p/180967#M2863</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/30682"&gt;@paul_ingle&lt;/a&gt;&amp;nbsp;in the situation "&lt;SPAN&gt;&lt;EM&gt;Under "Detect problems but don't alert" - the problem would stay open until resolved.&lt;/EM&gt;", would the alert that was not sent during the window be sent once the window finishes?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Feb 2022 10:50:28 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Maintenance-Windows-and-Open-Problems/m-p/180967#M2863</guid>
      <dc:creator>fstekelenburg</dc:creator>
      <dc:date>2022-02-18T10:50:28Z</dc:date>
    </item>
    <item>
      <title>Re: Maintenance Windows and Open Problems</title>
      <link>https://community.dynatrace.com/t5/Alerting/Maintenance-Windows-and-Open-Problems/m-p/181009#M2864</link>
      <description>&lt;P&gt;Calling for DT Professional Help!!!!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This question has come up many times and the ambiguity of the Dynatrace documentation (&lt;A href="https://www.dynatrace.com/support/help/how-to-use-dynatrace/problem-detection-and-analysis/notifications-and-alerting/maintenance-windows/define-maintenance-window" target="_blank"&gt;https://www.dynatrace.com/support/help/how-to-use-dynatrace/problem-detection-and-analysis/notifications-and-alerting/maintenance-windows/define-maintenance-window&lt;/A&gt;) has been the result of countless Support tickets.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could someone from DT explain, once and for all, how Dynatrace handles the transitional states for all 3 options, in extremely detail. Then, please update the on-line documentation with it.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Getting the support answer of "DT is working as intended" but without the details of understanding exactly what "as intended" is causing lots of confusion.&amp;nbsp; &amp;nbsp;I need enough information and details so that I, as a client, can clearly predict Dynatrace's environmental responses and not have to try and make sense of them after the fact.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Feb 2022 17:20:58 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Maintenance-Windows-and-Open-Problems/m-p/181009#M2864</guid>
      <dc:creator>ct_27</dc:creator>
      <dc:date>2022-02-18T17:20:58Z</dc:date>
    </item>
    <item>
      <title>Re: Maintenance Windows and Open Problems</title>
      <link>https://community.dynatrace.com/t5/Alerting/Maintenance-Windows-and-Open-Problems/m-p/181012#M2865</link>
      <description>&lt;P&gt;I found a related topic, going deeper into the matter:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.dynatrace.com/t5/Alerting/Alerts-after-a-maintenance-window/m-p/114039" target="_blank"&gt;https://community.dynatrace.com/t5/Alerting/Alerts-after-a-maintenance-window/m-p/114039&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Feb 2022 17:39:16 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Maintenance-Windows-and-Open-Problems/m-p/181012#M2865</guid>
      <dc:creator>fstekelenburg</dc:creator>
      <dc:date>2022-02-18T17:39:16Z</dc:date>
    </item>
  </channel>
</rss>

