Anthony P. avatar image
Anthony P. asked ·

In Dynatrace SaaS, how can we tell which nodejs servers are actively instrumented with RUM?

We have a openshift based system that uses about 40 "micro" web servers with openshift-router controlling the "http routing". We can see that a "ruxit" url in the browser but how can we tell which micro webserver it comes from? We have tried looking in the log files to no avail. Dynatrace does indicate the docker container/pod that is showing certail urls but there does not appear to be any confirmation of the RUM injection in the log files.. Can a "RUM injection" log be turned on for example?



10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Julius L. avatar image
Julius L. answered ·

AFAIK you can't. You can turn off/on RUM instrumentation at different levels.
On "Application" level - (you can even have special rules for particular pages) then the rules for injection get pushed to Oneagents.
On "Process group" level as @Alexander S. suggests, this will turn off/on injection for all applications served by services in all processes in the process group.

The most accurate answer will be to loop through every nodejs server for every application with some curl GET/POST (don't forget to set User-Agent to a real browser) and look for the JavaScript file. There can be several reasons why RUM JS will not get injected even if everything is setup correctly in Dynatrace (proxy / firewall / non-standard application / ... )

3 comments Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Thanks Julius, I just thought there may be a debug option that would let use see what RUM was actually doing on nodejs...

0 Likes 0 · ·

Some information can be seen in the Oneagent logs (rules for injecting). But this actually does not imply RUM JS will be injected for particular request. More information can be seen if debug flags for RUM are enabled. However they must be set by Dynatrace support. I'm not aware of any debug settings exposed in SaaS or Managed.

0 Likes 0 · ·

Thanks Julius for the comment., It would be great if Dynatrace would make available documentation that has info about how to turn debugging on for the OneAgent.. It would certainly reduce the amount of support calls we would have to make when the automated installation fails in some way and at least give us a chance to troubleshoot before we have to contact support...:-(

0 Likes 0 · ·
Alexander S. avatar image
Alexander S. answered ·

By default every instance which is monitored with a Dynatrace OneAgent will do RUM injection and RUM beacon handling. The RUM GET and POST you are referring are for downloading the RUM JS file and the POST is the beacon which is send back from the browser.

RUM JS injection and beacon handling can be turned off at process level if needed.

1 comment Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Thanks Alex, we are seeing the GET and POST fine and even with a type=check but no user sessions are seen... Look like we are back to curl...

0 Likes 0 · ·

Space Topics

mobile monitoring dotnet synthetic monitoring reports iis chat kubernetes servicenow amazon web services mysql mainframe rest api errors cassandra dashboard oneagent sdk cmc application monitoring openkit smartscape request attributes monitoring developer community user tagging log monitoring services ufo syntheticadvisory activegate ip addresses auto-detection high five award oracle hyperion webserver uem usql iib test automation license web performance monitoring ios news migration management zones index ibm mq web services custom event alerts notifications sso host monitoring knowledge sharing reports browser monitors java hybris sap vmware maintenance window user action naming javascript appmon ai synthetic classic availability tipstricks automation extensions session replay diagnostic tools permissions davis assistant faq documentation problem detection http monitors server easytravel apdex aws-quickstart network docker tags and metadata cloud foundry google cloud platform synthetic monitoring process groups account usability dynatrace saas gui paas openshift key user actions administration user actions postgresql synthetic locations oneagent security Dynatrace Managed user management custom python technologies mongodb openstack user session monitoring continuous delivery citrix configuration alerting NGINX timestamp action naming linux nam installation masking error reporting database mission control jmeter recorder apache mobileapp RUM php threshold azure purepath davis scripting agent aix nodejs android