Comments have been closed on this page. Please use AppMon & UEM Open Q & A forum for questions about this plugin.



Microsoft CRM V4.0 Sensor Pack


This Knowledge Sensor Pack can be used to help quantify and diagnose performance issues related to Microsoft CRM version 4.0 specific code



dynaTrace Diagnostics Version

>= 5.5


dynaTrace software


dynaTrace BSD





Sensor Pack Description


This Sensor Pack has not been tested under heavy production load.  This Sensor Pack was designed with production in mind but please test with your specific application before putting this Sensor Pack into a production environment.


  1. Save the attached file locally to the computer where the dynaTrace Diagnostics Client is installed.
  2. Unzip the file.
  3. In the dynaTrace Diagnostics Client, right-click on the Diagnostics Server and select 'Preferences...'.
  4. Click on "Sensor Packs".
  5. Click on the "Import..." button.
  6. Select "Custom Sensor Type (*.dtdcs)" in the "Files of type" dropdown.
  7. Navigate to the directory where you extracted the .dtdcs file and click "Open".

You can confirm successful import by observing the MS CRM 4 Sensor Pack in the Sensor Packs Panel. This Knowlege Sensor Pack is now Placed and Active within all System Profiles on this Diagnostics Server.

Exercise the MS CRM 4 application and open up the API view to see the new "MS CRM 4" API

  1. Anonymous (login to see details)

    I am running CRM 4, and I want to get this Sensor Pack Working. So far I see that its imported, but I cannot select it for placement.

    Also I would like to get the pure path to transvers through the callouts.

    1. Anonymous (login to see details)

      If you are using version 4.0 + autosensors should take care of the instrumentation and you should not need this sensor.

  2. Anonymous (login to see details)

    My client is running CRM 2016.  So if I read the above correctly.... we should not need the CRM 4.0 Fastpack as the dynatrace 6.3 or 6.5 should cover everything on instrumentation and we should not be additional sensors.... is this correct?



    1. Anonymous (login to see details)

      I have been working on 2016 CRM with DT 6.5.  For the most part that is right. However if you are looking to get measures on the plugins that becomes a different issue.

      I can get the errors from the plugins, I can see some of the path through auto sensors but you can not tag plugin. It does show up as an auto sensors. To help with getting count we have added Plugin tracing code and I am grabbing the argument.

      I am still playing around with it to find a better way other than our dev's adding code.  I can upload more data if you want.