<?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: Sending recurring notifications in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Sending-recurring-notifications/m-p/227157#M3845</link>
    <description>&lt;P&gt;Created Product idea as suggested. But is there any workaround we can use ? We of course can create multiple checks with different days-before-expiration checks but it sounds lame and costs more.&lt;/P&gt;</description>
    <pubDate>Tue, 31 Oct 2023 13:26:21 GMT</pubDate>
    <dc:creator>olegus</dc:creator>
    <dc:date>2023-10-31T13:26:21Z</dc:date>
    <item>
      <title>Sending recurring notifications</title>
      <link>https://community.dynatrace.com/t5/Alerting/Sending-recurring-notifications/m-p/227049#M3842</link>
      <description>&lt;P&gt;We have synthetics monitors that check SSL certificate expiration for domains and send alerts if they expire in 30 days or less. The problem we have is that DT sends out one notification when it detects the problem (&amp;lt;30 days before expiration) and the second one when certificate is expired already. In many cases the first warning is just ignored.&lt;/P&gt;
&lt;P&gt;Is it possible to setup alerting profile to send recurring notifications&amp;nbsp; weekly/dayly even though if a problem is still open?&lt;/P&gt;
&lt;P&gt;Ideally would be to send alerts weekly for the first 3 weeks and daily for the last week before expiration, considering synthetic monitor is setup to fail if certificate expires in 30 days .&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2023 10:47:24 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Sending-recurring-notifications/m-p/227049#M3842</guid>
      <dc:creator>olegus</dc:creator>
      <dc:date>2023-11-07T10:47:24Z</dc:date>
    </item>
    <item>
      <title>Re: Sending recurring notifications</title>
      <link>https://community.dynatrace.com/t5/Alerting/Sending-recurring-notifications/m-p/227089#M3843</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/65794"&gt;@olegus&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems to me that there is no such possibility at the moment. (Maybe I'm wrong&lt;span class="lia-unicode-emoji" title=":smiling_face_with_smiling_eyes:"&gt;😊&lt;/span&gt;)&lt;/P&gt;&lt;P&gt;I recommend to create a new Produckt Idea, because honestly it is a useful functionality.&lt;/P&gt;&lt;P&gt;Radek&lt;/P&gt;</description>
      <pubDate>Tue, 31 Oct 2023 08:45:51 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Sending-recurring-notifications/m-p/227089#M3843</guid>
      <dc:creator>radek_jasinski</dc:creator>
      <dc:date>2023-10-31T08:45:51Z</dc:date>
    </item>
    <item>
      <title>Re: Sending recurring notifications</title>
      <link>https://community.dynatrace.com/t5/Alerting/Sending-recurring-notifications/m-p/227157#M3845</link>
      <description>&lt;P&gt;Created Product idea as suggested. But is there any workaround we can use ? We of course can create multiple checks with different days-before-expiration checks but it sounds lame and costs more.&lt;/P&gt;</description>
      <pubDate>Tue, 31 Oct 2023 13:26:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Sending-recurring-notifications/m-p/227157#M3845</guid>
      <dc:creator>olegus</dc:creator>
      <dc:date>2023-10-31T13:26:21Z</dc:date>
    </item>
  </channel>
</rss>

