<?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 Deploying OneAgent in a non-privileged container in Container platforms</title>
    <link>https://community.dynatrace.com/t5/Container-platforms/Deploying-OneAgent-in-a-non-privileged-container/m-p/53421#M709</link>
    <description>&lt;P&gt;Our applications are running on top of a fully-managed container platform (OpenShift in this case) to which we neither have direct access to the underlying nodes nor the permission to run containers in privileged mode.&lt;/P&gt;&lt;P&gt;Is there any possibility to monitor our application containers despite these limitations?&lt;/P&gt;&lt;P&gt;If not, are there any future plans to reduce the privilege requirements for installing &amp;amp; running the OneAgent and allow monitoring of applications in this type of scenario? I'm thinking along the lines of a "thin" agent similar to AppMon agents which can be injected directly into an application process/container...&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Enrico&lt;/P&gt;</description>
    <pubDate>Mon, 05 Feb 2018 11:36:07 GMT</pubDate>
    <dc:creator>Enrico_F</dc:creator>
    <dc:date>2018-02-05T11:36:07Z</dc:date>
    <item>
      <title>Deploying OneAgent in a non-privileged container</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Deploying-OneAgent-in-a-non-privileged-container/m-p/53421#M709</link>
      <description>&lt;P&gt;Our applications are running on top of a fully-managed container platform (OpenShift in this case) to which we neither have direct access to the underlying nodes nor the permission to run containers in privileged mode.&lt;/P&gt;&lt;P&gt;Is there any possibility to monitor our application containers despite these limitations?&lt;/P&gt;&lt;P&gt;If not, are there any future plans to reduce the privilege requirements for installing &amp;amp; running the OneAgent and allow monitoring of applications in this type of scenario? I'm thinking along the lines of a "thin" agent similar to AppMon agents which can be injected directly into an application process/container...&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Enrico&lt;/P&gt;</description>
      <pubDate>Mon, 05 Feb 2018 11:36:07 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Deploying-OneAgent-in-a-non-privileged-container/m-p/53421#M709</guid>
      <dc:creator>Enrico_F</dc:creator>
      <dc:date>2018-02-05T11:36:07Z</dc:date>
    </item>
    <item>
      <title>Re: Deploying OneAgent in a non-privileged container</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Deploying-OneAgent-in-a-non-privileged-container/m-p/53422#M710</link>
      <description>&lt;P&gt;Hi Enrico,&lt;/P&gt;&lt;P&gt;thanks for reaching out. Yes there is a possibility to monitor your application although you do not have direct access to the underlying nodes of your OpenShift cluster. You can add OneAgent for PaaS monitoring (a "thin" agent) to your application container. To do that, you basically can follow two approaches: (i) deploying the OneAgent at image build time&lt;BR /&gt;(which involves modifying the image build process); or (ii) deploying the OneAgent at&lt;BR /&gt;container runtime.&lt;/P&gt;&lt;P&gt;I can also share examples on how to do that with you. Also, we recently looked into AWS&lt;BR /&gt;Fargate and came up with exactly these two approaches for PaaS monitoring of&lt;BR /&gt;AWS Fargate deployments. We plan to publish a blog post on AWS Fargate in&lt;BR /&gt;the next couple of days.&lt;/P&gt;&lt;P&gt;Hope this helps for the&lt;BR /&gt;moment.&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Daniela &lt;/P&gt;</description>
      <pubDate>Wed, 07 Feb 2018 06:45:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Deploying-OneAgent-in-a-non-privileged-container/m-p/53422#M710</guid>
      <dc:creator>daniela_rabiser</dc:creator>
      <dc:date>2018-02-07T06:45:21Z</dc:date>
    </item>
    <item>
      <title>Re: Deploying OneAgent in a non-privileged container</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Deploying-OneAgent-in-a-non-privileged-container/m-p/53423#M711</link>
      <description>&lt;P&gt;The mentioned blog post is already available here: https://www.dynatrace.com/news/blog/first-steps-with-aws-fargate/&lt;/P&gt;</description>
      <pubDate>Wed, 07 Feb 2018 10:40:17 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Deploying-OneAgent-in-a-non-privileged-container/m-p/53423#M711</guid>
      <dc:creator>daniela_rabiser</dc:creator>
      <dc:date>2018-02-07T10:40:17Z</dc:date>
    </item>
    <item>
      <title>Re: Deploying OneAgent in a non-privileged container</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Deploying-OneAgent-in-a-non-privileged-container/m-p/53424#M712</link>
      <description>&lt;A rel="user" href="https://answers.dynatrace.com/users/16098/view.html" nodeid="16098"&gt;@Daniela R &lt;/A&gt;blog post is missing important information how to use the thin PaaS agent. Is this &lt;A href="https://github.com/dynatrace-innovationlab/oneagent-paas-install"&gt;https://github.com/dynatrace-innovationlab/oneagent-paas-install&lt;/A&gt;&lt;P&gt; the correct method? (as it clearly says not yet ready).&lt;BR /&gt;Second question - how are the PaaS agents licensed? At this time, Dynatrace server side monitoring is licensed by Host Units, but PaaS agents are not counted in this metric. (My experience with AIX "PaaS" agents in recent Dynatrace Managed deployment).&lt;/P&gt;</description>
      <pubDate>Wed, 21 Feb 2018 10:15:13 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Deploying-OneAgent-in-a-non-privileged-container/m-p/53424#M712</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2018-02-21T10:15:13Z</dc:date>
    </item>
  </channel>
</rss>

