<?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: ruxit gateway requests in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/ruxit-gateway-requests/m-p/246996#M32551</link>
    <description>&lt;P&gt;Ruxit gateway is Dynatrace ActiveGate. Based on the metric endpoint I assume it's an application in Kubernetes and you are scraping the Prometheus metrics from the /metrics endpoint.&amp;nbsp;&lt;BR /&gt;The HTTP Response 406 is returned from your application, so I'd recommend looking at your application why it is not accepting the request. The request Content-Type header is text/plain.&lt;/P&gt;</description>
    <pubDate>Fri, 31 May 2024 06:28:03 GMT</pubDate>
    <dc:creator>Julius_Loman</dc:creator>
    <dc:date>2024-05-31T06:28:03Z</dc:date>
    <item>
      <title>ruxit gateway requests</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/ruxit-gateway-requests/m-p/246950#M32540</link>
      <description>&lt;P&gt;We made a change to our application monitored by Dynatrace.&lt;/P&gt;&lt;P&gt;Before the change we saw something called "ruxit gateway" make requests to our "/metrics" endpoint.&lt;/P&gt;&lt;P&gt;The previous implementation returned HTTP200 with content-type "text/plain; version=0.0.4; charset=utf-8"&lt;/P&gt;&lt;P&gt;We made a small change that (should!) serve the same response and content-type.&lt;/P&gt;&lt;P&gt;However we're now seeing &lt;A href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/406" target="_self"&gt;HTTP406&lt;/A&gt;s in response suggesting an issue with content negotiation.&lt;/P&gt;&lt;P&gt;I'm just looking for information on what "ruxit gateway" is and what content-type is in the requests to "/metrics".&lt;/P&gt;&lt;P&gt;This should give me some information to try to figure out what has been broken.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 May 2024 10:58:15 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/ruxit-gateway-requests/m-p/246950#M32540</guid>
      <dc:creator>manstis</dc:creator>
      <dc:date>2024-05-30T10:58:15Z</dc:date>
    </item>
    <item>
      <title>Re: ruxit gateway requests</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/ruxit-gateway-requests/m-p/246996#M32551</link>
      <description>&lt;P&gt;Ruxit gateway is Dynatrace ActiveGate. Based on the metric endpoint I assume it's an application in Kubernetes and you are scraping the Prometheus metrics from the /metrics endpoint.&amp;nbsp;&lt;BR /&gt;The HTTP Response 406 is returned from your application, so I'd recommend looking at your application why it is not accepting the request. The request Content-Type header is text/plain.&lt;/P&gt;</description>
      <pubDate>Fri, 31 May 2024 06:28:03 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/ruxit-gateway-requests/m-p/246996#M32551</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2024-05-31T06:28:03Z</dc:date>
    </item>
    <item>
      <title>Re: ruxit gateway requests</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/ruxit-gateway-requests/m-p/247001#M32555</link>
      <description>&lt;P&gt;Thank-you&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/3364"&gt;@Julius_Loman&lt;/a&gt;&amp;nbsp;for the pointer.&lt;/P&gt;&lt;P&gt;Upon debugging we noted that our application's default content-type was application/json and our refactoring had removed the explicit content negotiation for text/plain. Adding this back has solved our problem.&lt;/P&gt;</description>
      <pubDate>Fri, 31 May 2024 07:35:37 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/ruxit-gateway-requests/m-p/247001#M32555</guid>
      <dc:creator>manstis</dc:creator>
      <dc:date>2024-05-31T07:35:37Z</dc:date>
    </item>
  </channel>
</rss>

