In some scenarios it makes sense to turn off automatic injection of the real user monitoring JavaScript tag for specific process groups. One such scenario involves running an Apache in front of your Java application servers, where all HTML content is rendered on the Java application servers. In such an example, Apache only hosts static content. Although Ruxit Agent won’t inject the JavaScript tag into non-HTML content on the Apache server, and the content-type check doesn’t really impact overhead, it’s best to turn off automatic injection for the Apache to avoid the content-type check entirely.

Another scenario involves running different web applications (WAR files) that have different security settings on your Java tier. In such instances it can be difficult to find an allowable directly for injection of the real user monitoring JavaScript library and beacon signal. If you’re also running a web server like Apache or IIS in front of your Java tier, you can disable the real user monitoring JavaScript tag injection for the Java process groups and perform the JavaScript tag injection only on the Apache or IIS tier.

JavaScript tag injection