DCRUM and Dynatrace integration

Salut JL

Hmmm - not sure about all the details in how the integration is built between the DC RUM and Dynatrace as I'm still a beginner on Dynatrace - but.

 I would guess that since the CAS contains data on a 5 minute boundary, the correlation will be less exact, while the ADS contains all the details about every transaction (just as Dynatrace) which would make it more of a 1 for 1 match when it comes to the individual transactions - but perhaps someone else knows more details?

HI Jean-Louis,

First of all for this integration to work you will need to have the AMD linked into the dynatrace server in the integration settings of the dynatrace server. I suppose you have done that otherwise the ADS purepathid would not work.

Now, what I have noticed is that it only works if you have a certain url and this will be send to dynatrace as a filter.  But from some of the links there is no URL and then I don't get a result back from dynatrace. The ADS is better as it provides the exact purepathid so it can be linked. As ULF already said, and you know, the CAS only contains aggregate data and the ADS contains the specific user request and therefore one to one with dynaTrace.

Another issue that you might encounter is that the time settings between CAS and dynatrace server are different so that time window does not match. Also check your url that it was not created with a regex, maybe the CAS does not send the original URL. Hope this helps in narrowing down the issue.

My 2 cents,

Pieter.

I was doing some tests, have a look at the dyntrace client. Sometimes when you look at multiple url's and keep the dynatrace client open it doesn't refresh properly. Try to the following close the dashboard "DC RUM Integration" and click the link again in the CAS. Sometimes that helps and the data is correctly loaded.

Cheers Pieter.

Thanks for your answers. It's possible that some sofware services use a Regex to rewrite the URL in my customer environment.

This experience shows that the integration is much better with the PurepathID dimension!

It's a very bad experience for a customer to have no data in de Dynatarce server when he uses the dynatarce integration. In some cases, it's better to avoid the integration from the Dynatrace Server with the CAS data and use only the purepathID.

For this customer, I have changed the reports DMI and force the integartion to use only the PurepathID.

After that the integration is 100% succesful.

Find the DMI attached to this post and the doc to use it.

Integration DCRUM-Dynatrce with PurepathID.docx

Slow Operation Loads - ALL.xml

Regards

JLL