<?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 OneAgent - Hibernation in Cloud platforms</title>
    <link>https://community.dynatrace.com/t5/Cloud-platforms/OneAgent-Hibernation/m-p/249373#M1670</link>
    <description>&lt;DIV class=""&gt;As part of our migration of applications into the cloud, we have come across a strange problem.&lt;/DIV&gt;
&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class=""&gt;One of our application teams is deploying "auto scaling" within AWS, it builds 4 servers and puts 2 servers into "hibernation" when not needed then they auto "wake" on demand when required.&lt;/DIV&gt;
&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class=""&gt;When this happens, the OneAgent disconnects from all the previously injected processes which stops deep level monitoring. We would then be forced to restart the processes for the one-agent to inject back in. This is not practical as restarting these processes causes application impact.&lt;/DIV&gt;
&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class=""&gt;Is there any workaround for this?&lt;/DIV&gt;</description>
    <pubDate>Mon, 01 Jul 2024 09:06:31 GMT</pubDate>
    <dc:creator>Rich</dc:creator>
    <dc:date>2024-07-01T09:06:31Z</dc:date>
    <item>
      <title>OneAgent - Hibernation</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/OneAgent-Hibernation/m-p/249373#M1670</link>
      <description>&lt;DIV class=""&gt;As part of our migration of applications into the cloud, we have come across a strange problem.&lt;/DIV&gt;
&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class=""&gt;One of our application teams is deploying "auto scaling" within AWS, it builds 4 servers and puts 2 servers into "hibernation" when not needed then they auto "wake" on demand when required.&lt;/DIV&gt;
&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class=""&gt;When this happens, the OneAgent disconnects from all the previously injected processes which stops deep level monitoring. We would then be forced to restart the processes for the one-agent to inject back in. This is not practical as restarting these processes causes application impact.&lt;/DIV&gt;
&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class=""&gt;Is there any workaround for this?&lt;/DIV&gt;</description>
      <pubDate>Mon, 01 Jul 2024 09:06:31 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/OneAgent-Hibernation/m-p/249373#M1670</guid>
      <dc:creator>Rich</dc:creator>
      <dc:date>2024-07-01T09:06:31Z</dc:date>
    </item>
    <item>
      <title>Re: OneAgent - Hibernation</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/OneAgent-Hibernation/m-p/252851#M1712</link>
      <description>&lt;P&gt;The fundamentals of Dynatrace include that injectable processes will need to be restarted/recycled in order to inject. If the 2 servers sleeping, I'm assuming they are turned off, then upon start up those processes might need to be recycled, I would recommend making those segments part of the start up script.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The only other way around this is to leverage a monitoring mode that doesn't need recycling which in turn wont do injection. That would be discovery, and infrastructure mode.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Aug 2024 20:00:07 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/OneAgent-Hibernation/m-p/252851#M1712</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2024-08-07T20:00:07Z</dc:date>
    </item>
  </channel>
</rss>

