On Premises Website Monitoring

The Minified JavaScript file

If you want to use our website monitoring features, you can find the minified JavaScript snippet under the path /eum.min.js. Assuming that the machine running the on premises backend has a hostname of “instana-backend”, you’ll find the file under the following path:

http://instana-backend:2999/eum.min.js

This file can be put in your delivery lifecycle and the HTML templates of your application.

The Monitoring Endpoint

The backend machine accepts HTTP GET and POST requests under the path /. With the same assumption as above, your users’ browsers will report to this endpoint:

http://instana-backend:2999

Proxying the Monitoring Endpoint

By proxying the endpoint, you are able to customize how the endpoint is available for your users. You can configure TLS certificates, ports, and loadbalancers. Below are some short examples (you’ll only need one of those) on how you can proxy the website tracing endpoint using mostly common webserver software:

With nginx

Please note the required trailing slashes

upstream eumtracer {
  server instana-backend:2999;
  keepalive 6;
}
server {
  listen 443 ssl;

  location /eum/ {
    proxy_pass http://eumtracer/;
    proxy_set_header X-Real-IP $remote_addr;
  }
}

With Apache Httpd

Please note the required trailing slashes.

<VirtualHost *:*>
    ProxyPreserveHost On

    ProxyPass /eum/ http://instana-backend:2999/

    ServerName your-domain.io
</VirtualHost>

Analyzing Issues

To analyze issue, do the following:

  1. Open the URL to the JavaScript manually in the browser. Do you get JavaScript as a response by the server?

    • If this is failing, and you are using a proxy, keep in mind that the path to the JavaScript file probably changed. With our example proxy configs above, the path would be /eum/eum.min.js. Did you take the trailing slashes into account, i.e. does your proxy strip the /eum path?
    • If this is failing, and you aren’t using a proxy, keep in mind that the Instana website component only binds to port 2999.
    • Still not working? Contact support and explain the setup, send the proxy config, and explain how you are trying to access the script.
  2. Add the website monitoring snippet to your application.

    • If you aren’t seeing any website traces, use the website debug script. Instead of accessing eum.min.js, use eum.debug.js. This will log a bunch of information about configuration and transmission to the browser console. Inspect the console and resolve any further issues.
    • Still not working? Contact support and explain the setup, send the proxy config, and explain how you are trying to access the script, as well as the output of the debug script.