Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Server & Application Monitor (SAM) > Determine which threshold is failing in AppInsight for Exchange

Determine which threshold is failing in AppInsight for Exchange

Table of contents
Created by Chris Foley, last modified by MindTouch on Jun 23, 2016

Views: 105 Votes: 1 Revisions: 6

Overview

There are some components within AppInsight for Exchange that contain different thresholds for different resources. For example, the 'Database File and transaction log info dir' component which monitors database size, transaction log size and white space. When a threshold fails within this component, AppInsight for Exchange does not provide information as to which specific threshold is failing.

This issue is still being discussed as a feature request and this article provides a temporary workaround to help determine which specific threshold is failing.

Environment

  • SAM v6.1 and later
  • All Windows versions

Steps

  1. Log in to the system which hosts the SAM application.
  2. Run LogAdjuster.exe.
  3. In the Collector section, change the Data Processor entry to DEBUG.
  4. Click Apply and close the LogAdjuster.
  5. Restart the Orion services.
  6. Wait until the AppInsight for Exchange polling completes (approximately 30 minutes).
  7. Open the following files in C:\ProgramData\SolarWinds\Collector\Logs\Plugins\:

    APM.BlackBox.Exchg.Application.Statistics.Api.txt

    APM.BlackBox.Exchg.Application.Statistics.Api.txt.{Number}

  8. Search for entries similar to the following:
    2016-01-07 11:28:39,859 [STP DatabaseProcessing Thread #1] DEBUG SolarWinds.APM.Collector.BL.ComponentEntity - [ABXM:1750] Updating old 'EXCHG_Database_Size' threshold statuses.
    2016-01-07 11:28:39,859 [STP DatabaseProcessing Thread #1] DEBUG SolarWinds.APM.Collector.BL.ComponentEntity - [ABXM:1750] Collecting of old 'EXCHG_Database_Size' threshold's statuses has been started.
    2016-01-07 11:28:39,859 [STP DatabaseProcessing Thread #1] DEBUG SolarWinds.APM.Collector.BL.ComponentEntity - [ABXM:1750] The latest status for 'EXCHG_Database_Size' threshold is: 'Critical'.
  9. The last line contains the threshold name and status information.

    Threshold name:
         * EXCHG_Database_Size for Database Size Threshold
         * EXCHG_Database_TransactionLogSize for Database Transaction Log Size Threshold
         * EXCHG_DatabaseFile_Usage for Database File Usage Threshold
         * EXCHG_TransactionLogFile_Usage for Database Transaction Log File Usage Threshold
         * EXCHG_DatabaseFile_Whitespace for Database File Whitespace Threshold
         * EXCHG_DatabaseFile_VolumeAvail for Database File Volume Available Threshold
         * EXCHG_TransactionLogFile_VolumeAvail for Database Transaction Log File Volume Available Threshold

    Status: Critical/Warning/etc.

  10. With this information, you can determine which threshold is failing. Adjust if necessary.

 

 

Last modified

Tags

Classifications

Public