<?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: .net 7 based containers in Container platforms</title>
    <link>https://community.dynatrace.com/t5/Container-platforms/net-7-based-containers/m-p/212687#M1617</link>
    <description>&lt;P&gt;Hi&lt;BR id="isPasted" /&gt;&lt;BR /&gt;There is no additional configuration required, but too restrictive health checks and/or resource constraints can lead to container start-up issues with .NET applications.&lt;BR /&gt;&lt;BR /&gt;The OneAgent .NET code module injects into the application on process start-up and when the first technology specific assembly is loaded. This whole process takes a couple of (~2-4) seconds. Too restrictive CPU limits can lead to an increase in start-up time and memory limits can generally result in the container getting OOMKilled as there is a temporarily increased memory requirement on process start-up [1]. This short delay could potentially result in failed health checks.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;It would be interesting to know whether the application runs successfully outside of a containerized environment or without the health checks (and resource constraints) in order to rule out a OneAgent feature not functioning properly.&lt;BR /&gt;&lt;BR /&gt;I would suggest opening a support ticket for a deeper analysis of the issue.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Gurpreet&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;[1] &lt;A href="https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/memory-requirements#technology-dependent-memory-demand" target="_blank"&gt;https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/memory-requirements#technology-dependent-memory-demand&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 19 May 2023 13:06:56 GMT</pubDate>
    <dc:creator>Gurpreet_Juttla</dc:creator>
    <dc:date>2023-05-19T13:06:56Z</dc:date>
    <item>
      <title>.net 7 based containers</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/net-7-based-containers/m-p/211069#M1577</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Our containers are equipped with health checks that verify communication across containers and resources (ESBs/databases) during startup. They attempt to do so only a few dozen times, with timeouts in place to ensure safety. If they continue to fail after these attempts, they shut down on their own (i.e., they give up).&lt;/P&gt;&lt;P&gt;This is&amp;nbsp; behavior we observed with the old dynatrace one agent 1.261, which is why we disabled Dynatrace on our production environment. Unfortunately, after updating to the newest agent 1.263&amp;nbsp; (with .net 7 support) we are seeing the ame behavior during tests on our acceptance environment.&lt;/P&gt;&lt;P&gt;Is there any additional configuration/requirements we need to do with .net 7 based containers?&lt;/P&gt;&lt;P&gt;If you need any additional information, please let me know.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Cheers,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Tom.&lt;/P&gt;</description>
      <pubDate>Mon, 01 May 2023 08:53:02 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/net-7-based-containers/m-p/211069#M1577</guid>
      <dc:creator>tom_taminiau</dc:creator>
      <dc:date>2023-05-01T08:53:02Z</dc:date>
    </item>
    <item>
      <title>Re: .net 7 based containers</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/net-7-based-containers/m-p/212687#M1617</link>
      <description>&lt;P&gt;Hi&lt;BR id="isPasted" /&gt;&lt;BR /&gt;There is no additional configuration required, but too restrictive health checks and/or resource constraints can lead to container start-up issues with .NET applications.&lt;BR /&gt;&lt;BR /&gt;The OneAgent .NET code module injects into the application on process start-up and when the first technology specific assembly is loaded. This whole process takes a couple of (~2-4) seconds. Too restrictive CPU limits can lead to an increase in start-up time and memory limits can generally result in the container getting OOMKilled as there is a temporarily increased memory requirement on process start-up [1]. This short delay could potentially result in failed health checks.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;It would be interesting to know whether the application runs successfully outside of a containerized environment or without the health checks (and resource constraints) in order to rule out a OneAgent feature not functioning properly.&lt;BR /&gt;&lt;BR /&gt;I would suggest opening a support ticket for a deeper analysis of the issue.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Gurpreet&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;[1] &lt;A href="https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/memory-requirements#technology-dependent-memory-demand" target="_blank"&gt;https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/memory-requirements#technology-dependent-memory-demand&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 19 May 2023 13:06:56 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/net-7-based-containers/m-p/212687#M1617</guid>
      <dc:creator>Gurpreet_Juttla</dc:creator>
      <dc:date>2023-05-19T13:06:56Z</dc:date>
    </item>
  </channel>
</rss>

