<?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 Help with Synthetics/RUM on non-http traffic in Real User Monitoring</title>
    <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Help-with-Synthetics-RUM-on-non-http-traffic/m-p/297121#M7306</link>
    <description>&lt;P class=""&gt;Hi! We have a new app we’re launching and trying to get some RUM and Synthetics setup. However, I've been running into some problems getting our observability configured.&lt;/P&gt;
&lt;P class=""&gt;This is an IoT app that is being loaded onto our new agentic coffee maker/brewing product, so we are leveraging HTCPCP/1.0 (&lt;A href="https://www.ietf.org/rfc/rfc2324.txt" target="_blank" rel="noopener"&gt;RFC 2324&lt;/A&gt;) for handling internet traffic and was hoping the community might have some workarounds?&lt;/P&gt;
&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL class=""&gt;
&lt;LI&gt;Needs to support the BREW method. Right now POST is supported so we’re getting by okay for now. However, the POST method is technically deprecated, so I’m not sure how long we have and I’d like to get away from it ASAP before this gets us into a weird spot with supportability! (That is super important to our org)&lt;/LI&gt;
&lt;LI&gt;I’m having trouble with the additional HTCPCP headers (addition-type, syrup-type, milk-type specifically). Does the RUM tag code strip these out? Eventually we’d like to get these into bizevents, but just seeing them anywhere in the UI would be helpful. I’ll attach a har file in a bit (need to walk over to the testing kitchen where the dev coffee pots are currently plugged in and coordinate with our Barista Engineering Team for a good time to capture one).&lt;/LI&gt;
&lt;LI&gt;I need to do a validation on some response body content for a specific response code (418). The RFC states “The resulting entity body MAY be short and stout.” How would we validate how stout a response body is for each synthetic test executed? (this also needs to run every 5 min from 400 public locations, btw)&lt;/LI&gt;
&lt;/UL&gt;
&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class=""&gt;Thanks in advance!&lt;/P&gt;
&lt;P class=""&gt;Korwin&lt;/P&gt;</description>
    <pubDate>Mon, 27 Apr 2026 11:10:53 GMT</pubDate>
    <dc:creator>Kor03</dc:creator>
    <dc:date>2026-04-27T11:10:53Z</dc:date>
    <item>
      <title>Help with Synthetics/RUM on non-http traffic</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Help-with-Synthetics-RUM-on-non-http-traffic/m-p/297121#M7306</link>
      <description>&lt;P class=""&gt;Hi! We have a new app we’re launching and trying to get some RUM and Synthetics setup. However, I've been running into some problems getting our observability configured.&lt;/P&gt;
&lt;P class=""&gt;This is an IoT app that is being loaded onto our new agentic coffee maker/brewing product, so we are leveraging HTCPCP/1.0 (&lt;A href="https://www.ietf.org/rfc/rfc2324.txt" target="_blank" rel="noopener"&gt;RFC 2324&lt;/A&gt;) for handling internet traffic and was hoping the community might have some workarounds?&lt;/P&gt;
&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL class=""&gt;
&lt;LI&gt;Needs to support the BREW method. Right now POST is supported so we’re getting by okay for now. However, the POST method is technically deprecated, so I’m not sure how long we have and I’d like to get away from it ASAP before this gets us into a weird spot with supportability! (That is super important to our org)&lt;/LI&gt;
&lt;LI&gt;I’m having trouble with the additional HTCPCP headers (addition-type, syrup-type, milk-type specifically). Does the RUM tag code strip these out? Eventually we’d like to get these into bizevents, but just seeing them anywhere in the UI would be helpful. I’ll attach a har file in a bit (need to walk over to the testing kitchen where the dev coffee pots are currently plugged in and coordinate with our Barista Engineering Team for a good time to capture one).&lt;/LI&gt;
&lt;LI&gt;I need to do a validation on some response body content for a specific response code (418). The RFC states “The resulting entity body MAY be short and stout.” How would we validate how stout a response body is for each synthetic test executed? (this also needs to run every 5 min from 400 public locations, btw)&lt;/LI&gt;
&lt;/UL&gt;
&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class=""&gt;Thanks in advance!&lt;/P&gt;
&lt;P class=""&gt;Korwin&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2026 11:10:53 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/Help-with-Synthetics-RUM-on-non-http-traffic/m-p/297121#M7306</guid>
      <dc:creator>Kor03</dc:creator>
      <dc:date>2026-04-27T11:10:53Z</dc:date>
    </item>
  </channel>
</rss>

