<?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: RUM injection when application is served by nginx + varnish + apache in Real User Monitoring</title>
    <link>https://community.dynatrace.com/t5/Real-User-Monitoring/RUM-injection-when-application-is-served-by-nginx-varnish-apache/m-p/72032#M349</link>
    <description>&lt;P&gt;By default the injection applies as early as possible in the response delivery chain. That means that Apache will try to inject first. If you want to do injection at nginx, you need to turn of real user monitoring javascript injection for the apache process group. &lt;/P&gt;&lt;P&gt;Go to the settings - monitoring - monitoring overivew - process groups and edit the settings for your apache process group.&lt;/P&gt;&lt;P&gt;On Varnish we will not do an injection, so the injection will take place at nginx.&lt;/P&gt;</description>
    <pubDate>Wed, 30 May 2018 10:55:09 GMT</pubDate>
    <dc:creator>AlexanderSommer</dc:creator>
    <dc:date>2018-05-30T10:55:09Z</dc:date>
    <item>
      <title>RUM injection when application is served by nginx + varnish + apache</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/RUM-injection-when-application-is-served-by-nginx-varnish-apache/m-p/72031#M348</link>
      <description>&lt;P&gt;Hi dynatrace community,&lt;/P&gt;&lt;P&gt;I encounter an application that is deployed with the following architecture :&lt;/P&gt;&lt;P&gt;web browser =&amp;gt; 2 x nginx =&amp;gt; 2 x varnish cache =&amp;gt; 3 x apache httpd servers&lt;/P&gt;&lt;P&gt;How is injected RUM and what is the rule adopted by dynatrace to avoid injection in apache ? &lt;BR /&gt;Thank's in advance for your answer and help.&lt;/P&gt;&lt;P&gt;Best Regards.&lt;BR /&gt;Alain&lt;/P&gt;</description>
      <pubDate>Tue, 29 May 2018 15:16:53 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/RUM-injection-when-application-is-served-by-nginx-varnish-apache/m-p/72031#M348</guid>
      <dc:creator>asauvanet</dc:creator>
      <dc:date>2018-05-29T15:16:53Z</dc:date>
    </item>
    <item>
      <title>Re: RUM injection when application is served by nginx + varnish + apache</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/RUM-injection-when-application-is-served-by-nginx-varnish-apache/m-p/72032#M349</link>
      <description>&lt;P&gt;By default the injection applies as early as possible in the response delivery chain. That means that Apache will try to inject first. If you want to do injection at nginx, you need to turn of real user monitoring javascript injection for the apache process group. &lt;/P&gt;&lt;P&gt;Go to the settings - monitoring - monitoring overivew - process groups and edit the settings for your apache process group.&lt;/P&gt;&lt;P&gt;On Varnish we will not do an injection, so the injection will take place at nginx.&lt;/P&gt;</description>
      <pubDate>Wed, 30 May 2018 10:55:09 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/RUM-injection-when-application-is-served-by-nginx-varnish-apache/m-p/72032#M349</guid>
      <dc:creator>AlexanderSommer</dc:creator>
      <dc:date>2018-05-30T10:55:09Z</dc:date>
    </item>
    <item>
      <title>Re: RUM injection when application is served by nginx + varnish + apache</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/RUM-injection-when-application-is-served-by-nginx-varnish-apache/m-p/72033#M350</link>
      <description>&lt;P&gt;Thank's Alexander. That is the needed answer.&lt;BR /&gt;Best Regards&lt;/P&gt;&lt;P&gt;Alain&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jun 2018 12:15:39 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/RUM-injection-when-application-is-served-by-nginx-varnish-apache/m-p/72033#M350</guid>
      <dc:creator>asauvanet</dc:creator>
      <dc:date>2018-06-22T12:15:39Z</dc:date>
    </item>
  </channel>
</rss>

