<?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: Restrict metric_ingest OneAgent API access in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Restrict-metric-ingest-OneAgent-API-access/m-p/273003#M36036</link>
    <description>&lt;P&gt;Hello &lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/11931"&gt;@andre_vdveen&lt;/a&gt; as &lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/3364"&gt;@Julius_Loman&lt;/a&gt; says we managed to control this using local firewalls controlled centrally. You can make a rule to permit or deny connections to your configured port.&lt;/P&gt;</description>
    <pubDate>Wed, 19 Mar 2025 20:20:09 GMT</pubDate>
    <dc:creator>DanielS</dc:creator>
    <dc:date>2025-03-19T20:20:09Z</dc:date>
    <item>
      <title>Restrict metric_ingest OneAgent API access</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Restrict-metric-ingest-OneAgent-API-access/m-p/273000#M36033</link>
      <description>&lt;P&gt;Is there a way to restric access or usage of the&amp;nbsp;&lt;A title="OneAgent metric API" href="https://docs.dynatrace.com/docs/shortlink/local-api" target="_blank" rel="noopener"&gt;OneAgent metric API&lt;/A&gt;&amp;nbsp;so that certain users or groups cannot use it?&lt;BR /&gt;I don't see a way to do this via RBAC or ABAC.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 19:36:39 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Restrict-metric-ingest-OneAgent-API-access/m-p/273000#M36033</guid>
      <dc:creator>andre_vdveen</dc:creator>
      <dc:date>2025-03-19T19:36:39Z</dc:date>
    </item>
    <item>
      <title>Re: Restrict metric_ingest OneAgent API access</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Restrict-metric-ingest-OneAgent-API-access/m-p/273001#M36034</link>
      <description>&lt;P&gt;No.&amp;nbsp; Not using Dynatrace. The endpoint is available if you enable it for local ingest. You must use other options on the host to prevent specific users from accessing it like local firewall, selinux or apparmor.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 20:08:04 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Restrict-metric-ingest-OneAgent-API-access/m-p/273001#M36034</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2025-03-19T20:08:04Z</dc:date>
    </item>
    <item>
      <title>Re: Restrict metric_ingest OneAgent API access</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Restrict-metric-ingest-OneAgent-API-access/m-p/273003#M36036</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/11931"&gt;@andre_vdveen&lt;/a&gt; as &lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/3364"&gt;@Julius_Loman&lt;/a&gt; says we managed to control this using local firewalls controlled centrally. You can make a rule to permit or deny connections to your configured port.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 20:20:09 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Restrict-metric-ingest-OneAgent-API-access/m-p/273003#M36036</guid>
      <dc:creator>DanielS</dc:creator>
      <dc:date>2025-03-19T20:20:09Z</dc:date>
    </item>
  </channel>
</rss>

