<?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: suppression for OS patching in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/suppression-for-OS-patching/m-p/236379#M4094</link>
    <description>&lt;P&gt;We leverage tags for this. We have automation that applies tags with the hosts with the name of the maintenance window. Then we have recurring windows defined that applies to those hosts&lt;/P&gt;</description>
    <pubDate>Tue, 06 Feb 2024 15:52:35 GMT</pubDate>
    <dc:creator>Kor01</dc:creator>
    <dc:date>2024-02-06T15:52:35Z</dc:date>
    <item>
      <title>suppression for OS patching</title>
      <link>https://community.dynatrace.com/t5/Alerting/suppression-for-OS-patching/m-p/236334#M4089</link>
      <description>&lt;P&gt;wondering how you deal with&amp;nbsp; suppression for OS patching&amp;nbsp; on a wide number of servers :&lt;/P&gt;
&lt;P&gt;Looking for how I can do an estate wide suppression for OS patching to either suppress 100s of servers in&amp;nbsp; 2 hour window or just general advice on how thew community are doing this for OS patching&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Feb 2024 10:57:07 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/suppression-for-OS-patching/m-p/236334#M4089</guid>
      <dc:creator>sel300900</dc:creator>
      <dc:date>2024-02-07T10:57:07Z</dc:date>
    </item>
    <item>
      <title>Re: suppression for OS patching</title>
      <link>https://community.dynatrace.com/t5/Alerting/suppression-for-OS-patching/m-p/236364#M4090</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;You can create a &lt;A title="Maintenance window" href="https://docs.dynatrace.com/docs/shortlink/maintenance-window" target="_blank" rel="noopener"&gt;Maintenance window&lt;/A&gt;&amp;nbsp;for hosts involved.&lt;/P&gt;&lt;P&gt;You can reference them by management zones or tags but it depends how you organize your environment.&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Tue, 06 Feb 2024 12:54:01 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/suppression-for-OS-patching/m-p/236364#M4090</guid>
      <dc:creator>AntonPineiro</dc:creator>
      <dc:date>2024-02-06T12:54:01Z</dc:date>
    </item>
    <item>
      <title>Re: suppression for OS patching</title>
      <link>https://community.dynatrace.com/t5/Alerting/suppression-for-OS-patching/m-p/236371#M4093</link>
      <description>&lt;P&gt;you could also add this into a pipeline where the hosts selected are posted into a Maintenance Window. Also are the hosts in particular defined prior to patching. You could tag them with a patch group number and then associate a MW to all of those entities of the Patch group number value.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Feb 2024 14:28:52 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/suppression-for-OS-patching/m-p/236371#M4093</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2024-02-06T14:28:52Z</dc:date>
    </item>
    <item>
      <title>Re: suppression for OS patching</title>
      <link>https://community.dynatrace.com/t5/Alerting/suppression-for-OS-patching/m-p/236379#M4094</link>
      <description>&lt;P&gt;We leverage tags for this. We have automation that applies tags with the hosts with the name of the maintenance window. Then we have recurring windows defined that applies to those hosts&lt;/P&gt;</description>
      <pubDate>Tue, 06 Feb 2024 15:52:35 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/suppression-for-OS-patching/m-p/236379#M4094</guid>
      <dc:creator>Kor01</dc:creator>
      <dc:date>2024-02-06T15:52:35Z</dc:date>
    </item>
    <item>
      <title>Re: suppression for OS patching</title>
      <link>https://community.dynatrace.com/t5/Alerting/suppression-for-OS-patching/m-p/236394#M4095</link>
      <description>&lt;P&gt;I would not recommend reusing Maintenance Windows or leverage methods that fixate on tags. Reason being is that as the tag is removed, or as a Maintenance Window is reused, any historical context of the applied Maintenance Window on the entity is erased.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ChadTurner_0-1707251827751.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/17429iC6D0B2204641ADBE/image-size/large?v=v2&amp;amp;px=999" role="button" title="ChadTurner_0-1707251827751.png" alt="ChadTurner_0-1707251827751.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ChadTurner_2-1707251893042.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/17431i973527D3B56C2EF0/image-size/large?v=v2&amp;amp;px=999" role="button" title="ChadTurner_2-1707251893042.png" alt="ChadTurner_2-1707251893042.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>Tue, 06 Feb 2024 20:38:35 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/suppression-for-OS-patching/m-p/236394#M4095</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2024-02-06T20:38:35Z</dc:date>
    </item>
  </channel>
</rss>

