<?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: Dynatrace Oneagent update schedule in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-Oneagent-update-schedule/m-p/297941#M38918</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;As I mentioned earlier, Dynatrace does &lt;STRONG&gt;not provide an official fixed release schedule or exact dates&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;What we observe in practice is a ~4-week release cycle, but this should be treated as an approximation, not something guaranteed. The exact release timing can shift depending on validation, stability, or urgent fixes.&lt;/P&gt;&lt;P&gt;Because of that, it’s not possible to reliably predict a specific week or day in advance.&lt;/P&gt;&lt;P&gt;Additionally, you can always track upcoming updates directly in the Cluster Management Console (CMC), where the exact scheduled update time for your environment is visible.&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="maitanance.jpg" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/32787iFF7EFC6E34238DCA/image-size/large?v=v2&amp;amp;px=999" role="button" title="maitanance.jpg" alt="maitanance.jpg" /&gt;&lt;/span&gt;&lt;BR /&gt;A common and safe strategy is to stay on a “one version behind” approach.&lt;BR /&gt;In practice, this means excluding the newest OneAgent version in Installation packages until you're ready to adopt it. This gives you more control and avoids unexpected updates during critical periods.&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2.jpg" style="width: 877px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/32788i596432822A2E3276/image-size/large?v=v2&amp;amp;px=999" role="button" title="2.jpg" alt="2.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 17 Apr 2026 15:38:54 GMT</pubDate>
    <dc:creator>t_pawlak</dc:creator>
    <dc:date>2026-04-17T15:38:54Z</dc:date>
    <item>
      <title>Dynatrace Oneagent update schedule</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-Oneagent-update-schedule/m-p/296678#M38818</link>
      <description>&lt;P&gt;Dear people&lt;/P&gt;&lt;P&gt;We would like to gain precise insight into the OneAgent release cycle to better align our internal change management calendar. Specifically, we have the following questions:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Release Interval:&lt;/STRONG&gt; Do you maintain a fixed schedule for new OneAgent versions (e.g., strictly every 4 weeks)?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Fixed Release Day:&lt;/STRONG&gt; On which specific day of the week is a new version typically officially released (General Availability)?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Rollout Phasing:&lt;/STRONG&gt; Is there a consistent pattern regarding the days on which the rollout to SaaS tenants begins relative to the official release date?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Exceptions:&lt;/STRONG&gt; Are there specific periods during the year (e.g., December or during major conferences like Dynatrace Perform) where the regular release cycle is paused or altered?&lt;/P&gt;&lt;P&gt;We look forward to your response so we can optimize our update windows accordingly.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Mar 2026 13:03:54 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-Oneagent-update-schedule/m-p/296678#M38818</guid>
      <dc:creator>Hugo1984</dc:creator>
      <dc:date>2026-03-25T13:03:54Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Oneagent update schedule</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-Oneagent-update-schedule/m-p/296686#M38819</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;haha, it's a great topic &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;BR /&gt;Here’s how it typically works&lt;BR /&gt;Dynatrace generally follows a ~4-week release cycle for OneAgent versions.&lt;BR /&gt;However, this is not strictly fixed, but there can be slight shifts depending on internal validation, security updates, or feature readiness.&lt;/P&gt;&lt;P&gt;Fixed release day (GA)&lt;BR /&gt;There is no officially guaranteed fixed weekday, but in practice, releases are most often published around mid-week (typically Wednesday/Thursday).&lt;/P&gt;&lt;P&gt;Rollout phasing (SaaS)&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;After GA, the rollout to SaaS environments is progressive (phased rollout)&lt;/LI&gt;&lt;LI&gt;It usually starts shortly after release and can take several days to fully propagate across all tenants&lt;/LI&gt;&lt;LI&gt;The exact timing depends on cluster, region, and stability checks&lt;/LI&gt;&lt;LI&gt;This means your tenant might receive the update a few days after GA&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;There is no formally published “freeze” period, but:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Releases may be slightly adjusted around major events (e.g., Perform)&lt;/LI&gt;&lt;LI&gt;End-of-year (December) can sometimes have slower or shifted releases, but not a strict pause&lt;/LI&gt;&lt;LI&gt;Critical/security updates can always override the standard cadence&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Wed, 25 Mar 2026 13:59:16 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-Oneagent-update-schedule/m-p/296686#M38819</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2026-03-25T13:59:16Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Oneagent update schedule</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-Oneagent-update-schedule/m-p/296693#M38820</link>
      <description>&lt;P&gt;Hello t_pawlak,&lt;/P&gt;&lt;P&gt;Thanks for your answer. So a new version is released every four weeks, but you can give an estimate of when a new version will be released during the month?&lt;/P&gt;&lt;P&gt;The reason why I ask this is because we have to take into account the patch timing of the OS teams in our company. My strategy would be to install the new versions before the OS teams start patching their systems. They always restart their systems by default after patching and then the new OneAgent version can be activated at the same time.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Mar 2026 14:32:41 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-Oneagent-update-schedule/m-p/296693#M38820</guid>
      <dc:creator>Hugo1984</dc:creator>
      <dc:date>2026-03-25T14:32:41Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Oneagent update schedule</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-Oneagent-update-schedule/m-p/297941#M38918</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;As I mentioned earlier, Dynatrace does &lt;STRONG&gt;not provide an official fixed release schedule or exact dates&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;What we observe in practice is a ~4-week release cycle, but this should be treated as an approximation, not something guaranteed. The exact release timing can shift depending on validation, stability, or urgent fixes.&lt;/P&gt;&lt;P&gt;Because of that, it’s not possible to reliably predict a specific week or day in advance.&lt;/P&gt;&lt;P&gt;Additionally, you can always track upcoming updates directly in the Cluster Management Console (CMC), where the exact scheduled update time for your environment is visible.&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="maitanance.jpg" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/32787iFF7EFC6E34238DCA/image-size/large?v=v2&amp;amp;px=999" role="button" title="maitanance.jpg" alt="maitanance.jpg" /&gt;&lt;/span&gt;&lt;BR /&gt;A common and safe strategy is to stay on a “one version behind” approach.&lt;BR /&gt;In practice, this means excluding the newest OneAgent version in Installation packages until you're ready to adopt it. This gives you more control and avoids unexpected updates during critical periods.&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2.jpg" style="width: 877px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/32788i596432822A2E3276/image-size/large?v=v2&amp;amp;px=999" role="button" title="2.jpg" alt="2.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Apr 2026 15:38:54 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-Oneagent-update-schedule/m-p/297941#M38918</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2026-04-17T15:38:54Z</dc:date>
    </item>
  </channel>
</rss>

