Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Clear queued trap or syslog messages

Clear queued trap or syslog messages

Table of contents
Created by Michael Perez, last modified by MindTouch on Jun 23, 2016

Views: 2,108 Votes: 1 Revisions: 4

Overview

By default, trap and syslog actions are held in the MSMQ until they are processed. It is possible for a bad rule to generate a large volume of trap or syslog actions such as emails. This article provides steps on how to prevent additional actions from being processed.  

Environment

Orion Platform 2015.1.3 and earlier

Steps

  1. Open the Orion Service Manager and stop the Trap and/or Syslog service.  
  2. Open the Trap or Syslog viewer, select View, and then click Alerts/Filter Rules.
  3. Correct or disable the rule that is generating the flood of actions.
  4. Navigate to the MSMQ, expand Private Queues, expand either the /collector/processingqueue/core.trap.messages queue or the /collector/processingqueue/core.syslog.messages queue.
  5. Right-click on Queue Messages, click All Tasks, and then click Purge.
  6. Start the Trap and/or Syslog service from the Orion Service Manager.  

 

Now that the rule which was generating a large volume of actions has been corrected or disabled, the issue should no longer be present.  

 

Last modified

Tags

Classifications

Public