Latest Microsoft Monitoring Agent

Latest Microsoft Monitoring Agent

Rate This
  • Comments 3

The Application Insights team has released a new agent for Application Performance Management scenarios.  This updated agent is version 7.1.11196.0 and is available here.  If you are already using version 7.1.11115.0 then upgrading to this agent can be done by uninstalling the old one and then installing the newer version (for Azure Cloud Services the new agent version will be updated when the role is recycled next).  If you are using a version before 7.1.11115.0 then follow the instructions here.  Here is a description of the changes:

  • At the end of the MMMA agent setup there is an option (selected by default) which will automatically restart IIS so the .NET profiler can be registered


  • In a scenario where the server is being monitored by a System Center management group APM data will only be sent to the Application Insights service after installing the newer version of the agent.  (before this latest version APM data – ie. exception events and performance events could be sent to both a System Center management group and Application Insights)  Management Packs and all non APM scenarios continue to function as expected from the System Center management group from this preview version of MMA.
  • For the Azure Cloud Service scenario there were some security and reliability changes made to the instrumentation tool (ie. the files called UnifiedBootstrap.bat & UnifiedBootstrap.ps1 that were placed into the AppInsightsAgent folder) and the latest is available here.



Vlad Joanovic

Program Manager

Leave a Comment
  • Please add 3 and 8 and type the answer here:
  • Post
  • I am trying to monitor my WCF service for performance and exceptions and came across MS Monitoring agent. I see you can filter instrumentation to specified modules but it will have an adverse affect on the application. Is there a way to do monitoring without any impact ? What are the best strategies and tools for production environment ?


  • @HSN - monitoring should have little to no impact - our goal is <2-5% CPU.  That said it would be good to test in an environment before you deploy in production.

  • Is this the same as the AppFabric monitoring ?

Page 1 of 1 (3 items)