<?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 manage maintenance in Dynatrace Managed Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-maintenance/m-p/165600#M1654</link>
    <description>&lt;P&gt;It might happen, especially if you are on a managed istance.&lt;BR /&gt;&lt;BR /&gt;Usually you have to go trought the fundamentals, for example:&lt;BR /&gt;&lt;BR /&gt;was your Vm doing good on the vCenter (disk latency / network connectivity ecc...)&lt;BR /&gt;was there any problem related to network&lt;BR /&gt;what were the event notified in your /cmc&lt;BR /&gt;did you run and download cluster diagnostic from /cmc&lt;BR /&gt;&lt;BR /&gt;I can tell you in my case similar problem occured in two separate occasion:&lt;BR /&gt;&lt;BR /&gt;- when I didn't registered my host names on the organization DNS server&lt;BR /&gt;- when there was a full backup (not an official Dynatrace backup method) on the VM and that sent the disk latency at super high timings&lt;BR /&gt;&lt;BR /&gt;If nothings rings a bell you can always officially engage the support. Hope you will find a solution that fits you&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 06 May 2021 20:52:54 GMT</pubDate>
    <dc:creator>y_buccellato</dc:creator>
    <dc:date>2021-05-06T20:52:54Z</dc:date>
    <item>
      <title>Dynatrace Managed maintenance</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-maintenance/m-p/165590#M1653</link>
      <description>&lt;P&gt;Hi guys,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;have any of you experienced the same thing as what I am experiencing right now with Dynatrace Managed?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jun 2023 09:30:39 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-maintenance/m-p/165590#M1653</guid>
      <dc:creator>sandi_pusghiyan</dc:creator>
      <dc:date>2023-06-14T09:30:39Z</dc:date>
    </item>
    <item>
      <title>Re: dynatrace manage maintenance</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-maintenance/m-p/165600#M1654</link>
      <description>&lt;P&gt;It might happen, especially if you are on a managed istance.&lt;BR /&gt;&lt;BR /&gt;Usually you have to go trought the fundamentals, for example:&lt;BR /&gt;&lt;BR /&gt;was your Vm doing good on the vCenter (disk latency / network connectivity ecc...)&lt;BR /&gt;was there any problem related to network&lt;BR /&gt;what were the event notified in your /cmc&lt;BR /&gt;did you run and download cluster diagnostic from /cmc&lt;BR /&gt;&lt;BR /&gt;I can tell you in my case similar problem occured in two separate occasion:&lt;BR /&gt;&lt;BR /&gt;- when I didn't registered my host names on the organization DNS server&lt;BR /&gt;- when there was a full backup (not an official Dynatrace backup method) on the VM and that sent the disk latency at super high timings&lt;BR /&gt;&lt;BR /&gt;If nothings rings a bell you can always officially engage the support. Hope you will find a solution that fits you&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 06 May 2021 20:52:54 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-maintenance/m-p/165600#M1654</guid>
      <dc:creator>y_buccellato</dc:creator>
      <dc:date>2021-05-06T20:52:54Z</dc:date>
    </item>
  </channel>
</rss>

