<?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 ​Requirements of proxy that connects OneAgent in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Requirements-of-proxy-that-connects-OneAgent/m-p/75939#M4481</link>
    <description>&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;We would like to know the requirements about proxy using with OneAgent.&lt;BR /&gt;&lt;BR /&gt;In this case, I suppose OneAgent -&amp;gt; proxy -&amp;gt; SaaS Cluster(no Security Gateway). &lt;/P&gt;&lt;P&gt;The communication between Dyatrace managed cluster and Mission Control requires follows. &lt;BR /&gt;We would like to make sure that the similar requirements are not needed, just in case.&lt;BR /&gt;&lt;BR /&gt;While if other requirements exist, we would like to know that. &lt;/P&gt;&lt;BLOCKQUOTE&gt;Communication between Dynatrace Managed clusters and Mission Control can also be routed via a proxy, but the proxy must allow web sockets and, if the proxy is clustered, it must provide sticky sessions for web socket communication. Also, the proxy must support the SNI TLS extension. &lt;/BLOCKQUOTE&gt;&lt;P&gt;I have already referred the document, but could not find any description of that &lt;/P&gt;&lt;P&gt;Best Regards,&lt;BR /&gt;&lt;BR /&gt;Noah Kobayashi&lt;/P&gt;</description>
    <pubDate>Wed, 20 Jun 2018 11:22:58 GMT</pubDate>
    <dc:creator>nkobayashi1</dc:creator>
    <dc:date>2018-06-20T11:22:58Z</dc:date>
    <item>
      <title>​Requirements of proxy that connects OneAgent</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Requirements-of-proxy-that-connects-OneAgent/m-p/75939#M4481</link>
      <description>&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;We would like to know the requirements about proxy using with OneAgent.&lt;BR /&gt;&lt;BR /&gt;In this case, I suppose OneAgent -&amp;gt; proxy -&amp;gt; SaaS Cluster(no Security Gateway). &lt;/P&gt;&lt;P&gt;The communication between Dyatrace managed cluster and Mission Control requires follows. &lt;BR /&gt;We would like to make sure that the similar requirements are not needed, just in case.&lt;BR /&gt;&lt;BR /&gt;While if other requirements exist, we would like to know that. &lt;/P&gt;&lt;BLOCKQUOTE&gt;Communication between Dynatrace Managed clusters and Mission Control can also be routed via a proxy, but the proxy must allow web sockets and, if the proxy is clustered, it must provide sticky sessions for web socket communication. Also, the proxy must support the SNI TLS extension. &lt;/BLOCKQUOTE&gt;&lt;P&gt;I have already referred the document, but could not find any description of that &lt;/P&gt;&lt;P&gt;Best Regards,&lt;BR /&gt;&lt;BR /&gt;Noah Kobayashi&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jun 2018 11:22:58 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Requirements-of-proxy-that-connects-OneAgent/m-p/75939#M4481</guid>
      <dc:creator>nkobayashi1</dc:creator>
      <dc:date>2018-06-20T11:22:58Z</dc:date>
    </item>
    <item>
      <title>Re: ​Requirements of proxy that connects OneAgent</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Requirements-of-proxy-that-connects-OneAgent/m-p/75940#M4482</link>
      <description>&lt;P&gt;See my answer here: &lt;A href="https://community.dynatrace.com/spaces/482/dynatrace-open-qa/questions/204319/requirements-of-proxy-that-connects-private-securi.html" rel="noopener noreferrer" target="_blank"&gt;https://community.dynatrace.com/spaces/482/dynatrace-open-qa/questions/204319/requirements-of-proxy-that-connects-private-securi.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Oct 2023 15:01:15 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Requirements-of-proxy-that-connects-OneAgent/m-p/75940#M4482</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2023-10-16T15:01:15Z</dc:date>
    </item>
  </channel>
</rss>

