<?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: kubernetes restart pods by memory in Container platforms</title>
    <link>https://community.dynatrace.com/t5/Container-platforms/kubernetes-restart-pods-by-memory/m-p/236508#M2196</link>
    <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/65321"&gt;@Ellery&lt;/a&gt;&amp;nbsp;does the microservice create an actual memdump? One option would be to use &lt;A href="https://docs.dynatrace.com/docs/platform-modules/applications-and-microservices/profiling-and-optimization/memory-profiling" target="_self"&gt;Memory Profiling within Dynatrace.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I believe the &lt;A href="https://docs.dynatrace.com/docs/platform-modules/applications-and-microservices/profiling-and-optimization/memory-profiling#all-allocations" target="_self"&gt;allocation hotspots&lt;/A&gt; may be what you are most interested in.&lt;/P&gt;</description>
    <pubDate>Wed, 07 Feb 2024 17:59:38 GMT</pubDate>
    <dc:creator>bsnurka</dc:creator>
    <dc:date>2024-02-07T17:59:38Z</dc:date>
    <item>
      <title>kubernetes restart pods by memory</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/kubernetes-restart-pods-by-memory/m-p/231642#M2086</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I have the following issue: in my Kubernetes ecosystem, I have a microservice that keeps restarting due to memory issues. We've increased the memory, but it still continues to restart. What Dynatrace shows me is that it restarted due to memory. Does Dynatrace have any way to help me debug and indicate the cause or which method is causing the memory problem or consumption?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2023 09:40:44 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/kubernetes-restart-pods-by-memory/m-p/231642#M2086</guid>
      <dc:creator>Ellery</dc:creator>
      <dc:date>2023-12-13T09:40:44Z</dc:date>
    </item>
    <item>
      <title>Re: kubernetes restart pods by memory</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/kubernetes-restart-pods-by-memory/m-p/236508#M2196</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/65321"&gt;@Ellery&lt;/a&gt;&amp;nbsp;does the microservice create an actual memdump? One option would be to use &lt;A href="https://docs.dynatrace.com/docs/platform-modules/applications-and-microservices/profiling-and-optimization/memory-profiling" target="_self"&gt;Memory Profiling within Dynatrace.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I believe the &lt;A href="https://docs.dynatrace.com/docs/platform-modules/applications-and-microservices/profiling-and-optimization/memory-profiling#all-allocations" target="_self"&gt;allocation hotspots&lt;/A&gt; may be what you are most interested in.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Feb 2024 17:59:38 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/kubernetes-restart-pods-by-memory/m-p/236508#M2196</guid>
      <dc:creator>bsnurka</dc:creator>
      <dc:date>2024-02-07T17:59:38Z</dc:date>
    </item>
  </channel>
</rss>

