Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.


Home > Success Center > Web Performance Monitor (WPM) > WPM monitors stop reporting for any third-party application

WPM monitors stop reporting for any third-party application

Created by Erica Gill, last modified by MindTouch on Jun 23, 2016

Views: 4 Votes: 0 Revisions: 3


This article describes a scenario where WPM Monitors stop reporting suddenly. In this scenario, any third-party application interfacing with WPM to manage or unmanage transactions must be verified.


WPM 2.2 and earlier


Third-party applications interfacing with WPM to manage or unmanage transactions may be incorrectly configured or may not be correctly managing or unmanaging transactions.


  1. Determine the time of the issue.
  2. Observe any historical events on Transactions at or before this time. 
  3. Determine if there are multiple manage and unmanage actions overlapping with multiple manage tasks taking place before a unmanage or multiple unmanage tasks before a single manage task. If there are any, this indicates that there is a conflict in the arrangement of tasks.
  4. Identify the source of the manage/unmanage events and test if the issue occurs when these are disabled.
Last modified
05:18, 23 Jun 2016