Custom User Action

[AquariusDarius]

Hello Community,

I have a question regarding our plan to monitor a third-party web page—one that is not managed by our application where the Dynatrace agent is deployed. Since this is an entirely separate web page, what are the requirements for monitoring it? Would we need to inject a JavaScript tag into the page's code for Dynatrace to track its performance?

If you have any documentation or tips that could help us with this task, I’d appreciate it.

Thank you!

[AntonPineiro]

Hi,

If you cannot install OneAgent, you can try Set up agentless Real User Monitoring.

Best regards

[ChadTurner]

As @AntonPineiro mentioned, you can set up Agentless RUM. Which if you have access to the development of the page, say it is hosted in AWS, you can add in the JavaScript Library Tag data to start pulling Application data into Dynatrace:

Now if you don't have access to the application - its indeed fully 3rd party and you cannot access the webfront code, you can always set up synthetics that will execute a set of tasks on the page and provide you performance results of the given page/test. You can set up the frequency as well as number of locations that the site is tested from. Example, from 5 locations in the world, at a Frequency of every 5 mins, all locations were able to hit the site, provide the data performance wise and do any other actions such as search on the site, send an email etc... All reporting performance and any failures in the steps. 

Hope this helps! 

[AquariusDarius]

Hi @ChadTurner,

Thank you for the information. I have a follow-up question regarding this.

Previously, we attempted to set up synthetic monitoring for this page, but it was ineffective. I believe we were unable to obtain the necessary permissions to access the page due to privacy restrictions.

Now that we are in discussions with the page owners, would it be possible to mask certain data on the webpage and focus solely on performance monitoring? The page in question is a payment page, and it contains sensitive information such as credit card numbers.

Looking forward to your thoughts.

[ChadTurner]

So the payment page, that is a page you encounter after logging and navigating the pages. To which, if you cannot drop the RUM JS tag by way of manually inserting or OneAgent Deployment.... you would need to leverage Synthetics. If that page is after credential login, you'll need to use a live or test account to access that payment page. It all depends on the overall design of your application, If your organization has a test account great, if that test account can create dummy transactions, even better.