<?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 Migrating from Docker-only to generic container metrics in Dynatrace in Dynatrace tips</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-tips/Migrating-from-Docker-only-to-generic-container-metrics-in/m-p/167030#M544</link>
    <description>&lt;P&gt;Docker Inc, founded by Soloman Hykes, laid the foundation for cloud native computing. Built upon the Linux addition of LXC cgroups in 2008, Docker became the de-facto runtime engine for containerized workloads.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Today we have some alternative container runtimes to choose from including containerd and CRI-O, which use the Container Runtime Interface (CRI) as a standard way of integrating with Kubernetes. In 2019 the Kubernetes team decided to deprecate support for Docker, in favor or containerd and CRI-O, as it requires an extra translation layer (“shim”) for CRI support. Docker compatibility will continue through Kubernetes 1.22, expected later this year, though major cloud providers may end Docker support months earlier.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Seamless migration to containerd and CRI-O&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Containerd and CRI-O support was enabled by default in Dynatrace environments created after v1.83 (fall of 2019). If you’re unsure of your environment’s birthdate, or you want to confirm a frictionless transition from the Docker runtime to containerd and CRI-O, navigate to Settings &amp;gt; Processes and Containers &amp;gt; Container Monitoring and enable both settings.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screen Shot 2021-06-02 at 11.04.16.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/1168i36C75D157F908339/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screen Shot 2021-06-02 at 11.04.16.png" alt="Screen Shot 2021-06-02 at 11.04.16.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Important Dynatrace monitoring changes&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;As the industry shifts towards generic container metrics so will Dynatrace. Please walk through the following steps to avoid potential monitoring or alerting problems as Dynatrace begins its own deprecation timeline for Docker-only support, targeted at removal on&lt;STRIKE&gt; January 1, 2022&lt;/STRIKE&gt;&lt;STRONG&gt;&amp;nbsp;September 2022.&amp;nbsp;&lt;/STRONG&gt;Please note, the deprecation will not cover container injection for automated deep monitoring of processes in Docker containers, but Docker specific container metrics and screens.&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Browse through the list of metrics in the table below.&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Communicate with your team that these metrics come directly from the Docker API, rather than from a generic place. Let them know that any dashboards, alerts or API integrations using these metrics must be modified.&lt;SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;Let your team know the Docker screen in Dynatrace will be replaced by generic container views, and refer them to this article if they have questions.&lt;/LI&gt;
&lt;/OL&gt;
&lt;TABLE width="604"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Deprecated (Docker-only) metric&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;&lt;STRONG&gt;Generic container metric&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Container bytes received&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.bytes_rx2&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;&lt;SPAN&gt;builtin:tech.nettracer.bytes_rx&lt;/SPAN&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Container bytes transmitted&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.bytes_tx2&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;&lt;SPAN&gt;builtin:tech.nettracer.bytes_tx&lt;/SPAN&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Devicemapper data space available&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.devicemapper_data_space_available&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;No generic container-level metric planned.&lt;BR /&gt;In K8s please use the &lt;A href="https://www.dynatrace.com/support/help/shortlink/pvc-metrics-k8s" target="_self"&gt;PVC extension&lt;/A&gt;.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Devicemapper data space used&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.devicemapper_data_space_used&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;No generic container-level metric planned.&lt;BR /&gt;In K8s please use the &lt;A href="https://www.dynatrace.com/support/help/shortlink/pvc-metrics-k8s" target="_self"&gt;PVC extension&lt;/A&gt;.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Devicemapper meta-data space available&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.devicemapper_metadata_space_available&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;No generic container-level metric planned.&lt;BR /&gt;In K8s please use the &lt;A href="https://www.dynatrace.com/support/help/shortlink/pvc-metrics-k8s" target="_self"&gt;PVC extension&lt;/A&gt;.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Devicemapper meta-data space used&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.devicemapper_metadata_space_used&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;No generic container-level metric planned.&lt;BR /&gt;In K8s please use the &lt;A href="https://www.dynatrace.com/support/help/shortlink/pvc-metrics-k8s" target="_self"&gt;PVC extension&lt;/A&gt;.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Container cpu usage&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.cpu_usage2&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;&lt;SPAN&gt;builtin:containers.cpu.usagePercent&lt;BR /&gt;builtin:containers.cpu.usagePercent&lt;/SPAN&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Container memory percent&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.memory_percent&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;builtin:containers.memory.usagePercent&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Container memory usage&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.memory_usage2&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;builtin:containers.memory.residentSetBytes&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Container throttled time&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.throttled_time2&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;builtin:containers.cpu.throttledTime&lt;BR /&gt;&lt;SPAN&gt;builtin:containers.cpu.throttledMilliCores&lt;/SPAN&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Number of containers running&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.no_of_containers_running&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;Use this expression:&lt;/P&gt;
&lt;P&gt;builtin:containers.cpu.usageSystemMilliCores:splitBy():count&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;Note: Metric expression can be used for the overall number of containers in an environment. Splitting by image is subject to further improvement.&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Number of containers launched&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.no_of_containers_launched&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;&lt;EM&gt;removed&lt;/EM&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Number of containers terminated&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.no_of_containers_terminated&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;&lt;EM&gt;removed&lt;BR /&gt;&lt;BR /&gt;Note: You can use Process Group availability settings to monitor if any process becomes unavailable or to define a certain threshold (e.g. how many process group instances must be available). Containers, which have been terminated unexpectedly, will impact Process Group (Instance) availability.&lt;/EM&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Number of containers running&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.no_of_containers_per_pgi&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;&lt;EM&gt;removed&lt;/EM&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;New generic container metrics in Dynatrace&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Our migration to generic container support brings along a handful of benefits including new metrics in the data explorer, as well as container metrics in a number of different screens such as the workload view shown below.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screen Shot 2021-06-02 at 11.06.05.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/1169iBEA061649E913E63/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screen Shot 2021-06-02 at 11.06.05.png" alt="Screen Shot 2021-06-02 at 11.06.05.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; &lt;/P&gt;
&lt;P&gt; &lt;/P&gt;</description>
    <pubDate>Thu, 11 Aug 2022 06:38:34 GMT</pubDate>
    <dc:creator>mreider</dc:creator>
    <dc:date>2022-08-11T06:38:34Z</dc:date>
    <item>
      <title>Migrating from Docker-only to generic container metrics in Dynatrace</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-tips/Migrating-from-Docker-only-to-generic-container-metrics-in/m-p/167030#M544</link>
      <description>&lt;P&gt;Docker Inc, founded by Soloman Hykes, laid the foundation for cloud native computing. Built upon the Linux addition of LXC cgroups in 2008, Docker became the de-facto runtime engine for containerized workloads.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Today we have some alternative container runtimes to choose from including containerd and CRI-O, which use the Container Runtime Interface (CRI) as a standard way of integrating with Kubernetes. In 2019 the Kubernetes team decided to deprecate support for Docker, in favor or containerd and CRI-O, as it requires an extra translation layer (“shim”) for CRI support. Docker compatibility will continue through Kubernetes 1.22, expected later this year, though major cloud providers may end Docker support months earlier.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Seamless migration to containerd and CRI-O&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Containerd and CRI-O support was enabled by default in Dynatrace environments created after v1.83 (fall of 2019). If you’re unsure of your environment’s birthdate, or you want to confirm a frictionless transition from the Docker runtime to containerd and CRI-O, navigate to Settings &amp;gt; Processes and Containers &amp;gt; Container Monitoring and enable both settings.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screen Shot 2021-06-02 at 11.04.16.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/1168i36C75D157F908339/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screen Shot 2021-06-02 at 11.04.16.png" alt="Screen Shot 2021-06-02 at 11.04.16.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Important Dynatrace monitoring changes&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;As the industry shifts towards generic container metrics so will Dynatrace. Please walk through the following steps to avoid potential monitoring or alerting problems as Dynatrace begins its own deprecation timeline for Docker-only support, targeted at removal on&lt;STRIKE&gt; January 1, 2022&lt;/STRIKE&gt;&lt;STRONG&gt;&amp;nbsp;September 2022.&amp;nbsp;&lt;/STRONG&gt;Please note, the deprecation will not cover container injection for automated deep monitoring of processes in Docker containers, but Docker specific container metrics and screens.&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Browse through the list of metrics in the table below.&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Communicate with your team that these metrics come directly from the Docker API, rather than from a generic place. Let them know that any dashboards, alerts or API integrations using these metrics must be modified.&lt;SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;Let your team know the Docker screen in Dynatrace will be replaced by generic container views, and refer them to this article if they have questions.&lt;/LI&gt;
&lt;/OL&gt;
&lt;TABLE width="604"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Deprecated (Docker-only) metric&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;&lt;STRONG&gt;Generic container metric&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Container bytes received&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.bytes_rx2&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;&lt;SPAN&gt;builtin:tech.nettracer.bytes_rx&lt;/SPAN&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Container bytes transmitted&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.bytes_tx2&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;&lt;SPAN&gt;builtin:tech.nettracer.bytes_tx&lt;/SPAN&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Devicemapper data space available&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.devicemapper_data_space_available&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;No generic container-level metric planned.&lt;BR /&gt;In K8s please use the &lt;A href="https://www.dynatrace.com/support/help/shortlink/pvc-metrics-k8s" target="_self"&gt;PVC extension&lt;/A&gt;.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Devicemapper data space used&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.devicemapper_data_space_used&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;No generic container-level metric planned.&lt;BR /&gt;In K8s please use the &lt;A href="https://www.dynatrace.com/support/help/shortlink/pvc-metrics-k8s" target="_self"&gt;PVC extension&lt;/A&gt;.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Devicemapper meta-data space available&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.devicemapper_metadata_space_available&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;No generic container-level metric planned.&lt;BR /&gt;In K8s please use the &lt;A href="https://www.dynatrace.com/support/help/shortlink/pvc-metrics-k8s" target="_self"&gt;PVC extension&lt;/A&gt;.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Devicemapper meta-data space used&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.devicemapper_metadata_space_used&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;No generic container-level metric planned.&lt;BR /&gt;In K8s please use the &lt;A href="https://www.dynatrace.com/support/help/shortlink/pvc-metrics-k8s" target="_self"&gt;PVC extension&lt;/A&gt;.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Container cpu usage&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.cpu_usage2&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;&lt;SPAN&gt;builtin:containers.cpu.usagePercent&lt;BR /&gt;builtin:containers.cpu.usagePercent&lt;/SPAN&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Container memory percent&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.memory_percent&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;builtin:containers.memory.usagePercent&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Container memory usage&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.memory_usage2&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;builtin:containers.memory.residentSetBytes&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Container throttled time&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.throttled_time2&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;builtin:containers.cpu.throttledTime&lt;BR /&gt;&lt;SPAN&gt;builtin:containers.cpu.throttledMilliCores&lt;/SPAN&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Number of containers running&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.no_of_containers_running&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;Use this expression:&lt;/P&gt;
&lt;P&gt;builtin:containers.cpu.usageSystemMilliCores:splitBy():count&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;Note: Metric expression can be used for the overall number of containers in an environment. Splitting by image is subject to further improvement.&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Number of containers launched&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.no_of_containers_launched&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;&lt;EM&gt;removed&lt;/EM&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Number of containers terminated&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.no_of_containers_terminated&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;&lt;EM&gt;removed&lt;BR /&gt;&lt;BR /&gt;Note: You can use Process Group availability settings to monitor if any process becomes unavailable or to define a certain threshold (e.g. how many process group instances must be available). Containers, which have been terminated unexpectedly, will impact Process Group (Instance) availability.&lt;/EM&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="448"&gt;
&lt;P&gt;&lt;STRONG&gt;Number of containers running&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;builtin:containers.no_of_containers_per_pgi&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="156"&gt;
&lt;P&gt;&lt;EM&gt;removed&lt;/EM&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;New generic container metrics in Dynatrace&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Our migration to generic container support brings along a handful of benefits including new metrics in the data explorer, as well as container metrics in a number of different screens such as the workload view shown below.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screen Shot 2021-06-02 at 11.06.05.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/1169iBEA061649E913E63/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screen Shot 2021-06-02 at 11.06.05.png" alt="Screen Shot 2021-06-02 at 11.06.05.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; &lt;/P&gt;
&lt;P&gt; &lt;/P&gt;</description>
      <pubDate>Thu, 11 Aug 2022 06:38:34 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-tips/Migrating-from-Docker-only-to-generic-container-metrics-in/m-p/167030#M544</guid>
      <dc:creator>mreider</dc:creator>
      <dc:date>2022-08-11T06:38:34Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating from Docker-only to generic container metrics in Dynatrace</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-tips/Migrating-from-Docker-only-to-generic-container-metrics-in/m-p/201809#M655</link>
      <description>&lt;P&gt;great update&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/7579"&gt;@mreider&lt;/a&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jan 2023 16:34:22 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-tips/Migrating-from-Docker-only-to-generic-container-metrics-in/m-p/201809#M655</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2023-01-09T16:34:22Z</dc:date>
    </item>
  </channel>
</rss>

