<h2 id=”ruxit-agent-improvements-and-fixes”>Ruxit Agent improvements and fixes</h2>

<p>We’ve added several performance improvements that reduce the overhead and CPU usage of Java, .NET and Node.js agents.</p>
<h2 id=”iis-10-support-added”>IIS 10 support added</h2>

<p>As Windows 10 is now officially released, the Ruxit agent now also supports IIS 10.</p>
<h2 id=”nginx-beta-support”>Nginx Beta Support</h2>

<p>With Ruxit Agent 1.77 we are introducing Nginx Beta support. You need to enable Nginx support in the host or technology settings – see the screenshot below. Visit the <a href=”https://www.dynatrace.com/blog/beta-availability-of-nginx-monitoring/”>Nginx beta announcment</a> for more information.</p>
<h2 id=”real-user-monitoring-javascript-tag-injection-on-java-or-iis-without-server-root”>Real user monitoring JavaScript tag injection on Java or IIS without server root</h2>

<p>Ruxit Agent 1.77 will now inject by default the real user monitoring tag with requests context path instead of root “/” if no other path is explicitly configured in the Ruxit advanced application settings. This feature is available for Ruxit Agents on Java and IIS.
This solves problems on new Tomcats and JBoss servers where the context root “/” is not available per default. So downloading the Ruxit real user monitoring library from “http://host.com/” is not possible, but as a web application is deployed with a context path of “sample/” it is possible for “http://host.com/sample/”. Ruxit Agent 1.77 will now use this web application defined context path as default path to the JavaScript library and the beacon signal.</p>