Nimsoft Monitor exchange monitor...

exchange_monitor Guide v3.4 series

Nimsoft® Monitor™

Legal Notices Copyright © 2012, Nimsoft Corporation

Warranty

The material contained in this document is provided "as is," and is subject to being changed, without notice, in future editions. Further, to the maximum extent permitted by applicable law, Nimsoft Corporation disclaims all warranties, either express or implied, with regard to this manual and any information contained herein, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Nimsoft Corporation shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or of any information contained herein. Should Nimsoft Corporation and the user have a separate written agreement with warranty terms covering the material in this document that conflict with these terms, the warranty terms in the separate agreement shall control.

Technology Licenses

The hardware and/or software described in this document are furnished under a license and may be used or copied only in accordance with the terms of such license.

No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Nimsoft Corporation as governed by United States and international copyright laws.

Restricted Rights Legend

If software is for use in the performance of a U.S. Government prime contract or subcontract, Software is delivered and licensed as "Commercial computer software" as defined in DFAR 252.227-7014 (June 1995), or as a "commercial item" as defined in FAR 2.101(a) or as "Restricted computer software" as defined in FAR 52.227-19 (June 1987) or any equivalent agency regulation or contract clause. Use, duplication or disclosure of Software is subject to Nimsoft Corporation’s standard commercial license terms, and non-DOD Departments and Agencies of the U.S. Government will receive no greater than Restricted Rights as defined in FAR 52.227-19(c)(1-2) (June 1987). U.S. Government users will receive no greater than Limited Rights as defined in FAR 52.227-14 (June 1987) or DFAR 252.227-7015 (b)(2) (November 1995), as applicable in any technical data.

Trademarks

Adobe®, Acrobat®, Acrobat Reader®, and Acrobat Exchange® are registered trademarks of Adobe Systems Incorporated.

Intel® and Pentium® are U.S. registered trademarks of Intel Corporation.

Java(TM) is a U.S. trademark of Sun Microsystems, Inc.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Netscape(TM) is a U.S. trademark of Netscape Communications Corporation.

Oracle® is a U.S. registered trademark of Oracle Corporation, Redwood City, California.

UNIX® is a registered trademark of the Open Group.

Contact Nimsoft

For your convenience, Nimsoft provides a single site where you can access information about Nimsoft products.

At http://support.nimsoft.com/, you can access the following:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ Nimsoft Support policies and guidelines

■ Other helpful resources appropriate for your product

Provide Feedback

If you have comments or questions about Nimsoft product documentation, you can send a message to [email protected].

http://support.nimsoft.com/

mailto:[email protected]


Contents 5

Contents

Chapter 1: exchange_monitor 3.4 7

Installation Notes ......................................................................................................................................................... 9

exchange_monitor Configuration .............................................................................................................................. 11

The Setup tab ...................................................................................................................................................... 12

The Status tab ..................................................................................................................................................... 16

The Message Pool tab ......................................................................................................................................... 18

The Profile Setup tab ........................................................................................................................................... 21

Excluding Instances ............................................................................................................................................. 24

Exchange logon user description ............................................................................................................................... 25

Executing cmdlet on Exchange Server........................................................................................................................ 30

exchange_monitor Metrics ........................................................................................................................................ 31

Glossary 35


Chapter 1: exchange_monitor 3.4

This description applies to version 3.42

This section contains the following topics:

Documentation Changes (see page 8) Installation Notes (see page 9) exchange_monitor Configuration (see page 11) Exchange logon user description (see page 25) Executing cmdlet on Exchange Server (see page 30) exchange_monitor Metrics (see page 31)

Installation Notes

8 exchange_monitor Guide

Documentation Changes

This table describes the version history for this document.

Version Date What's New?

3.42 October 2011 Initial Release

Installation Notes


Installation Notes

The probe dynamically generates Quality of Service table names. Some of these table names might contain more than 64 characters, which can create problems when inserting data into the SLM database. When a NimBUS Server earlier than 3.35 creates the SLM database, the name column, in the S_QOS_DEFINITION table of the SLM database, is 64 bytes. You must update the size of the name column to 255 bytes. The latest data_engine qos discards definitions that are greater than 64 characters. If you do not update the size of the name column, earlier versions of the data_engine might fail.

Update the size of the name column to 255 bytes manually by using a database tool:

Design the table S_QOS_DEFINITION table and change the size of the name column to

'varchar(255)'.

Update the size of the name column to 255 bytes by running the following query on the database (Note that this query will not work on SQL Server 2000):

-- Added code to change field width of the name column of the S_QOS_DEFINITION table

-- A constraint needs to be dropped first to be allowed to do so

declare @const varchar(500),@sql varchar(500)

--Remove temp table, if exists.

IF Exists(SELECT * FROM tempdb.dbo.sysobjects WHERE [ID] =

OBJECT_ID('tempdb.dbo.##Objects')) DROP TABLE ##Objects

--Creating new temp table.

create table ##Objects (iname varchar(255),is_pk int)

-- Inserts indexes that are primary key on the table.

insert into ##Objects SELECT [name],is_primary_key FROM sys.indexes WHERE object_id

= OBJECT_ID(N'[dbo].[S_QOS_DEFINITION]')

-- Adding values to variables.

select @const = iname from ##Objects where is_pk = 1 set @SQL = 'ALTER TABLE

[dbo].[S_QOS_DEFINITION] DROP CONSTRAINT [' + @const + ']'

-- Dropping the PK constraint.

EXEC (@SQL)

-- Cleaning up temp table.

drop table ##Objects

-- Altering table, modifing name, and addeding new PK.

ALTER TABLE [S_QOS_DEFINITION] ALTER COLUMN [name] [varchar](255) not null

ALTER TABLE [dbo].[S_QOS_DEFINITION] ADD PRIMARY KEY CLUSTERED (

[name] ASC

) ON [PRIMARY]

The probe uses other probes to provide data that is used for checking the Exchange Server health. These probes are listed in the probe package and they are automatically installed with the probe. However, you must ensure that these probes are present in the NimBUS Archive.

Report information is gathered using WMI, LDAP and HTTP requests. (2003)

Report information is gathered using LDAP and Exchange PowerShell cmdlets. (2007 and 2010 mailbox).

Installation Notes


Note: Configuration values and profiles are stored in locations such as /setup, /perfmon, /processes, /services, and /ntevl sections. If you are running the Exchange server in a cluster, the sections are prefixed with /evs/server-<virtual_server_name>. For example, a virtual server called exch-grp-01 results in a /setup section that looks like /evs/server-exch-grp-01/setup. This allows configuration settings to follow each virtual server as it moves around. This is applicable to the 4 sections mentioned above, except for 2 keys in /setup, which is the loglevel key and the logfile key, which are always in the /setup section and they never move with the virtual server.

The following server roles are supported by the probe:

■ Mailbox

■ Client Access

■ Hub Transport

■ Edge Transport

This probe must be installed on each Exchange Server to be monitored, and the probe detects which roles are present and activates the profiles accordingly.

The probe collects and makes information available through a callback function. It collects monitored values of performance counters and checkpoints on an exchange server.

The probe does not monitor these checkpoints directly, but retrieves and uses values monitored by four other Nimsoft probes:

■ perfmon

The Performance Monitoring Probe (perfmon) acts as a data repository, fetching and holding performance object values from one or more computers, requested by other Nimsoft probes on your system.

■ ntservices

The ntservices probe monitors the list of installed services, detecting which of them are running.

■ ntevl

The ntevl probe monitors the event logs for new messages.

■ processes

The processes probe monitors the operating system for certain processes defined by a set of profiles in the probe configuration file.

These four probes must also be installed on the exchange server. When installing the exchange_monitor probe, it checks if the four probes already are installed on the exchange server. If not, it checks if the probes are available in the local Hub Archive. If so, they are automatically installed, otherwise you are asked to install them manually.

exchange_monitor Configuration


The probe is delivered with a set of predefined profiles, ready to use. The list of profiles is found under the Profiles tab. You can activate/deactivate profiles, open the properties dialog for a profile by double-clicking on it, and you can also select different alarm message to be issued on alarm conditions.

Alarm messages available are listed under the Messages tab. You can add, delete or modify messages.


Double-clicking the line representing the exchange_monitor probe in the Infrastructure Manager brings up the configuration tool for the probe.

Note: If monitoring exchange in a cluster, and a node contains two Exchange servers, the following dialog will pop up, asking you to choose for which Exchange server you will change the probe configuration parameters. Choose the one you want and click the OK button.

Once this is done, a new button, "Choose another server", will appear on the Setup tab of the probe. Clicking this button lets you switch between the two servers, deciding for which of them you want to modify the monitoring parameters.



The Setup tab

The Setup tab contains three sub-tabs and specifies the general properties for the probe. Note that the two tabs Report information and Mailbox growth does not apply and are deactivated (greyed out) in this version.

Field Description

General setup

Log Level Sets the level of details written to the log file. Log as little as possible during normal operation to minimize disk consumption, and increase the amount of detail when debugging.

Performance monitoring enabled

Selecting this option enables for monitoring of all profiles available from the perfmon probe. The Performance check interval value is read from the perfmon probe.

Process monitoring enabled

Selecting this option enables for monitoring of all profiles available from the processes probe. The Process check interval value can be specified in seconds.

Service monitoring enabled

Selecting this option enables for monitoring of all profiles available from the services probe. The Service check interval value can be specified in seconds.

Event monitoring enabled

Selecting this option enables for monitoring of all profiles available from the ntevl probe. The Event check interval value can be specified in seconds.



Field Description

Report information

For detailed information about logon parameters defined on this tab, see the section Exchange logon user description.

Gather report information

Ticking this option instructs the probe to make all gathered information available for the exchange_monitor_reports product.

This option is initially turned off and disabled. You must specify HTTP, VMI and LDAP identifications successfully (this is tested by clicking the corresponding test buttons and getting green indicators). Then this option is enabled and can be turned on.

Force update of report information

Clicking this button forces the probe to immediately gather the most current Exchange information.

Filter stores and databases for other servers

This option is by default turned on. Use this option if you want to make sure that only databases and stores on the Exchange server monitored by the probe are found and reported. This ensures that databases and stores on other Exchange servers on the same domain are excluded.

Database size

Note that this field applies for Exchange Server 2003 only.

The Exchange Server 2003 database concists of two different files; EDB and SLV. Select if you the database size to be reported as a summary of these two files, or the size of one of the two files.

WMI identification (2003 Server)

Exchange cmd-let

identification

(2007 Server)

The report information is gathered using WMI on Exchange server 2003 and Exchange cmd-let on Exchange server 2007, and the following logon information must be specified:

- User.

- Domain

- Password

Clicking the test button test the WMI/Exchange cmd-let logon parameters specified.



Field Description

LDAP identification

The report information is gathered from Active Directory (AD), using LDAP, and the following LDAP logon information must be specified:

- AD Server

- User.

Note: If the user name specified is not accepted, specify the username on the format <user name>@<domain name> or as the LDAP DN (Distinguished Name of the user, for example

CN=Koert Struijk,OU=Users,OU=Nimsoft,DC=nimsoft,DC=no)

- Password

- Base DN (LDAP BaseDN field)

Distinguished name for the domain of which this directory server is a member. e.g. dc=mydomain,dc=com.

- Config DN (LDAP ConfDN field)

The probe will query your directory server (root DSE) for the name of your configuration container (configurationNamingContext).

You can optionally specify the distinguishedName (DN) of your configuration container in this field, and the probe will use this value instead of querying the directory server.

LDAP Test (button)

Clicking the test button tests the LDAP logon parameters specified.

If LDAP authentication fails, try to add the domain name to the user name (e.g. [email protected] mailto:[email protected]).

If your mailbox users and distribution groups are spread around in multiple domains, you will need to specify one Active Directory domain controller for each domain using the Manage AD Servers dialog (see below).

Manage AD Servers (button)

The LDAP identification section (see above) lets you specify LDAP logon information for one AD Server.

Clicking this button opens the Manage AD Servers dialog, enabling you to manage several AD servers.

You may add servers and specify the LDAP logon information (as described above) for each of them:

AD Server

- User.

- Password

- Base DN (LDAP BaseDN field)

Advanced (button) Clicking this button opens the LDAP connection properties dialog.





Field Description

HTTP identification

Note that this field applies for Exchange Server 2003 only.

The report information is gathered from the Exchange server, using WebDAV, and the following HTTP logon information must be specified:

■ - Server

■ - User

■ - Password

Clicking the test button test the HTTP logon parameters specified.

Server requires https (SSL):

Check this option if you rather want to use SSL. In that case you also must specify the SSL port to be used (see below).

SSL port:

The SSL port to be used if the Server requires https (see above) is selected.

Mailbox growth

Check mailbox growth

Checking this option makes the probe check the growth of the mailboxes on the Exchange server.

Note that this option requires that the Gather report information option on the Report information tab is selected, otherwise the Mailbox tab is greyed out and cannot be selected.

Check interval The interval (in seconds) between each time the probe checks the Exchange server for mailbox growth.

Mailbox size in Kilobytes

This parameter requires that the Check mailbox growth option (above) is checked. Otherwise the parameter is greyed out.

Growth limit on each iteration

Specify the maximum allowed mailbox growth limit.

Only mailbox growths bigger than the number specified here are considered when counting the number of times the size of a mailbox has increased iteratively (see Iterations of growth before size alarm is issued below).

Iterations of growth before size alarm is issued

The mailbox sizes are checked at the check interval specified.

If the size of a mailbox has increased iteratively the number of times specified here, a mailbox size alarm will be issued.

Check only mailboxes with size greater than

Only mailboxes with size greater than specified here will be checked for size growth.



Field Description

Mailbox items This parameter requires that the Check mailbox growth option (above) is checked. Otherwise the parameter is greyed out.

Growth limit on each iteration

Specify the maximum allowed item growth limit.

Only item growths bigger than the number specified here are considered when counting the number of times the number of items in a mailbox has increased iteratively (see Iterations of growth before item alarm is issued below).

Iterations of growth before item alarm is issued

The mailboxes are checked for number of items at the check interval specified.

If the number of items in a mailbox has increased iteratively the number of times specified here, a mailbox items alarm will be issued.

Check only mailboxes with more items than

Only mailboxes containing more items than the number specified here will be checked for item growth.

The Status tab

This tab lists the status of all checkpoints for all active profiles.



Note the colored icon showing the severity level of the current values measured for some of the profiles. This applies only to profiles with a defined alarm threshold.

■ Name

The name of the checkpoint. Note the colored icon showing the severity level of the current values measured for profiles with a defined alarm threshold.

■ Group

The checkpoints are grouped into different logical groups, describing what kind of measurement the profile performs (such as memory, disk, processor).

■ Type

Describes the type of checkpoint, depending on from which probe the checkpoint is retrieved:

■ Perf

Checkpoints from the perfmon probe.

■ Service

Checkpoints from the services probe .

■ Event

Checkpoints from the ntevl probe.

■ Process

Checkpoints from the processes probe.

■ Value

The most current value measured.

■ Unit

The unit of the measured value (e.g. MB, %, Mb/s etc.).

■ At

The time (<month> <day> <time>) the current value was measured.

■ Alarm limit

The threshold value defined for the profile. A breach of this value will result in an alarm message.



The Message Pool tab

This tab contains the message pool which is a list of predefined alarm messages. The messages can be referred to in specific profiles.



The following commands are available when you right-click in the message list:

■ Add message

Creates a new message and presents you with the Message properties window described below.

■ Message properties

Edit the selected Message.

■ Remove message

Delete the selected Message. You will be asked to confirm the deletion.

Message properties



Name

Each message must be given a unique name. This name is used to refer to the message from the profiles.

Alarm situation

The message can be made the default message for a particular alarm situation. You must leave this field empty if another message is to be the default.

Text

The alarm message text. Variable expansion is supported, and the following variables are available:

■ group

■ profile

■ value

■ unit

■ limit

Level

The severity level assigned to any alarm message.

Subsystem

The subsystem ID of alarms generated by this profile, a string or an ID managed by the nas.



The Profile Setup tab

This tab lists all the monitoring profiles that are available in the probe configuration file.

You can use the following types of monitoring profiles with the exchange_monitor probe:

■ Service

■ Process

■ Perf

■ Ntevl



To update the properties of a monitoring profile

1. In the Profile setup tab, do one of the following:

■ Double-click a monitoring profile.

■ Right-click a monitoring profile and click Profile properties.

The Profile properties window opens.

1. Update the parameters of the profile.

2. Edit the alarm parameters and click OK.

3. In the probe configuration window, click Apply.

Profile Parameters

Field Description

Name Type the name of the profile.

Active Select this check box to activate this profile.

Active profiles appear in the profile list under the Profile Setup tab.

Description Type a description for this profile.

This field is optional.

Alarm Limit Specify an alarm threshold value.

The probe compares this value with the monitored value.

Note: This field is available only for perf profiles.

Compare Type Click the operator that the probe must use to compare the monitored value with the alarm threshold.



Message on Alarm Click the alarm message that must appear for the alarm condition.

Note: The profile uses the standard alarm message by default. This drop-down lists all the messages available in the Message Pool tab.

Message Clear Click the message that must appear when the new value is within the alarm threshold.

Exclude Instances Click this button to view the Exclude instances window.

Note: This button appears only for perf profiles that have the instance value as instance = <all> in the configuration file.

For information about how to exclude monitoring instances, see Excluding instances.



Excluding Instances

A monitoring profile can have multiple instances. If you do not want the probe to monitor an instance within a profile, you can exclude the instance.

The Exclude instances button appears in the Profile properties when the following conditions are met while the probe reads the instance and object keys from the configuration file:

1. The object is for a perf profile.

2. The value of the profile instance key is instance = <all>.

To exclude an instance

1. In the Profile properties dialog-box, click Exclude instances.

2. In the Available instances box, click the instance that you want to exclude, and then click the >> button.

3. Click OK to exclude this instance.

Exchange logon user description



Under the Setup tab, you have to specify logon users for WMI, LDAP and HTTP. You can use 3 different users, or the same user.

This section describes the requirements that has to be met to enable the probe to collect data. It has been tested in our lab with default domain policies. Note however that the setup may vary, depending on your forest setup and group policies.

LDAP

This user must be authorized to log into your Active Directory using the LDAP protocol.

This user requires read access to the configurationNamingContext tree, and specifically the administrative group entry in your active directory, where exchange servers store most information.

The easiest way to add these access rights to a user, is to open the Exchange System Manager, right click on your administrative group which contains the server(s) which you want to access, and choose Delegate control. Add your ldap user to the Exchange View Only Administrator role.

User name syntaxes in Active Directory ® (AD).

Four known syntaxes are valid when authenticating against Active Directory ® using LDAP protocol, simple binds.

1. Full DN, e.g.

CN=Ben Talk,OU=West,OU=Users,DC=domain,DC=com

2. NT Account Name (e.g. NIMCLUS\e1john)

3. User Principal Name (UPN) (e.g. [email protected] mailto:[email protected]), contained in the userPrincipalName attribute of the user in Active Directory ®.

4. Plain username (e.g. user), contained in the displayName attribute in Active Directory ®

The UPN syntax looks like an e-mail address, but don’t confuse this with the mail attribute of the user. They may be equal, but it is 2 different attributes.

For option 2 and 3, see the figure below.

Right-click the user in MMC snapin "Active Directory Users and Computers", and click Properties and choose the "Account" tab.





For option 4, see the figure below.



For option 1, you need to use another tool, such as ADSIEDIT.MSC, LDP or any other LDAP browser tool. It is not possible to our knowledge, to view the distinguishedName property of an object through the MMC snapin "Active Directory Users and Computers".

Known issues

It is recommended to use the NT Account Name or UPN syntax. But it may cause problems to use the UPN syntax. Active Directory ® enforces/ensures that a users sAMAccountName property is unique within a Active Directory ® forest. And the domain NETBIOS name is also enforced to be unique. Together they (domain netbios name and sAMAccountNAme of a user) is unique within a forest.

UPN is not guaranteed to be unique in Active Directory ® forest. If two or more users have the same UPN, none of them will be able to authenticate using the UPN name.

The same goes for plain username. It need to be unique within a forest.

WMI user

The probe will execute the "report collector" program as a background process, in the context of this uses (i.e. "Run as…"). This users context will be used when connecting to the exchange shares and WMI queries.

■ This user must be a domain user.

■ This user is member of the default domain group called Domain Users (or equivalent rights).

■ This user must be member of the domain security group called "Exchange Servers".

■ This user must be added to the "local administrators" group on the machine running the exchange server.

■ This user must also be delegated control of the "Exchange View Only administrator" role.

If you are running your exchange servers in a cluster, please note that you will have to add the WMI monitoring account to the local administrators group of all those nodes that can be owners of your virtual exchange servers.

You will have to reboot your exchange server in order for this effect to take place.

HTTP (WebDav) user permissions.

■ This user will be used when contacting the exchange server to query for public folder information, with WebDAV (http) protocol against the IIS (Outlook Web Access (OWA) also uses WebDAV).

■ This user must be a domain user.

■ This user is member of the default domain group called Domain Users (or equivalent rights).



■ This user requires at least these client permissions (Read permissions, List Contents and Read Property) on the folders in the folder hierarchy.

Information is gathered using the 3 different accounts.

HTTP user will be used in the WebDAV protocol over http to talk to IIS, where the public folders is hosted and reachable. Data for the "public folder owner" report is gathered here.

The actual list of public folders is retreived through WMI.

WMI – the exchange_monitor probes starts a background process in the context of the WMI user (i.e. Run as… command). The users context is used when accessing the WMI namespaces on the server running the exchange server.

In the WMI namespace root\MicrosoftExchangeV2, Exchange Server 2003 exposes several classes, and the data collector retreives instanes of the following wmi classes.

■ Exchange_PublicFolder – instances of public folders, and public folder replication information (to which stores are the folders replicated)

■ Exchange_Server – instance of the server

■ Exchange_Mailbox – instanes of mailboxes (sizes, deleted items, item count)

■ Exchange_MessageTrackingEntry – message tracking entries

In the WMI namespace root\CIMV2, instances of the following classes are read:

■ Win32_NTLogEvent – whitespace information

■ LDAP – or Active Directory – will be queried to read additional information about the Exchange Server configuration. In the

■ configurationNamingContext – exchange server information and structure of storage groups, stores (both public and mailbox), db quotas.

■ One or more domains can be queried for distribution lists and its members.

■ Queries are made to retreive users who belong to the storage groups we found in the configurationNamingContext.

■ Users mailboxes, mail addresses, delegates, memberOfs, account control, password last set etc.

It is then all tied together before its stored and ready to be retreived from the exchange_monitor_backend probe.

The report collector will also try to access the database files directly (the .edb files), and read the physical size of the files. The information about where the physical files are stored, is part of the information retreived from configurationNamingContext.



The reports have been devided into 10 child reports, from exchange_monitor point of view. Internal that controls how often the data is collected cannot be changed, but is as follows.

They are:

■ Traffic_summary, updated when data is older than 24 hours or at midnight.

■ Public_folders, updated when data is older than 24 hours or at midnight.

■ Domains, updated when data is older than 24 hours or at midnight.

■ Servers, updated when data is older than 24 hours or at midnight.

■ Mailboxes, updated when data is older than 10 minutes if you have enabled "monitor mailbox growth", otherwise it should be 60 minutes.

■ Display_names, updated when mailboxes are updated.

■ Partners, updated when data is older than 24 hours or at midnight.

■ Mailbox_activity, updated when data is older than 24 hours or at midnight.

■ Groups, updated when mailboxes are updated.

■ Databases, updated when data is older than 24 hours or at midnight.

The exchange_monitor_backend probe will query and check the timestamps of all these reports. If the exchange_monitor probe being queried has newer information on any of the reports, it will be collected by the backend and inserted into the SQL database.

The exchange_monitor_backend operates on the same aging policy as the exchange_monitor probe,which means, if it has all the data it needs from 1 server. It will not query that server again for 1 hour, before the mailboxdata is concidered old.

This means that if the exchange_monitor can’t for some reason read e.g. the message tracking logs, the backend will not get an accurate timestamp and will keep querying the exchange_monitor probe until it provides new data, once the exchange_monitor_backends data for the reports regarding traffic is older than 24 hours.

It is important to set up the report collection and make sure that all the reports receive data, otherwise your probes will be using more network bandwith than neccesary.

Executing cmdlet on Exchange Server


Executing cmdlet on Exchange Server

To execute the cmdlet on the Exchange server, you should have 'Exchange View-Only Administrators' privilege. In addition to this this, you need to add 'Exchange View-Only Administrators' group to 'Allow log on locally' policy of the Exchange server.

To achieve this, go to Security Settings and click User Rights Assignment. All the policies will be listed in the right pane. Double click on 'Allow log on locally' and add 'Exchange View-Only Administrators' group.

You also need to give read-write access permissions to the probe folder so that the datacollector can write the data to the cfg file and the log file.

exchange_monitor Metrics



The following table describes the checkpoint metrics that can be configured using the exchange_monitor probe.

Monitor Name Units Description

QOS_EXCHANGE_CLUSTER_VM_TOTAL_16MB_FREE_BLOCKS

Blocks VM Total 16 MB Free blocks

QOS_EXCHANGE_CLUSTER_VM_TOTAL_LARGE_FREE_BLOCK_MEGABYTES

Megabytes VM Total Large Free Block Megabytes

QOS_EXCHANGE_DISK_AVERAGE_DISK_BYTES_PER_TRANSFER

Bytes / Transfer

Average Disk Bytes per Transfer

QOS_EXCHANGE_DISK_AVERAGE_DISK_QUEUE_LENGTH Requests Average Disk Queue Length

QOS_EXCHANGE_DISK_AVERAGE_DISK_READ_QUEUE_LENGTH

Requests Average Disk Read Queue Length

QOS_EXCHANGE_DISK_AVERAGE_DISK_SECONDS_PER_READ

Seconds / Read

Average Disk Seconds per Read

QOS_EXCHANGE_DISK_AVERAGE_DISK_SECONDS_PER_WRITE

Seconds / Write

Average Disk Seconds per Write

QOS_EXCHANGE_DISK_AVERAGE_DISK_WRITE_QUEUE_LENGTH

Requests Average Disk Write Queue Length

QOS_EXCHANGE_DISK_PERCENT_DISK_TIME Percent Percent Disk Time

QOS_EXCHANGE_IS_FOLDER_OPENS_PER_SECOND_-_MAILBOXES

Opens / Second

Folder Opens per Second - Mailboxes

QOS_EXCHANGE_IS_FOLDER_OPENS_PER_SECOND_-_MBX

Opens / Second

Folder Opens per Second - MBX

QOS_EXCHANGE_IS_FOLDER_OPENS_PER_SECOND_-_PF Opens / Second

Folder Opens per Second - PF

QOS_EXCHANGE_IS_FOLDER_OPENS_PER_SECOND_-_PUBLIC_FOLDERS

Opens / Second

Folder Opens per Second - Public Folders

QOS_EXCHANGE_IS_MESSAGE_OPENS_PER_SECOND_-_MAILBOXES

Opens / Second

Message Opens per Second - Mailboxes

QOS_EXCHANGE_IS_MESSAGE_OPENS_PER_SECOND_-_MBX

Opens / Second

Message Opens per Second - MBX

QOS_EXCHANGE_IS_MESSAGE_OPENS_PER_SECOND_-_PF

Opens / Second

Message Opens per Second - PF

QOS_EXCHANGE_IS_MESSAGE_OPENS_PER_SECOND_-_PUBLIC_FOLDERS

Opens / Second

Message Opens per Second - Public Folders



QOS_EXCHANGE_IS_RECEIVE_QUEUE_SIZE_-_MAILBOXES

Messages Receive Queue Size - Mailboxes

QOS_EXCHANGE_IS_RECEIVE_QUEUE_SIZE_-_MBX Messages Receive Queue Size - MBX

QOS_EXCHANGE_IS_RECEIVE_QUEUE_SIZE_-_PF Messages Receive Queue Size - PF

QOS_EXCHANGE_IS_RECEIVE_QUEUE_SIZE_-_PUBLIC_FOLDERS

Messages Receive Queue Size - Public Folders

QOS_EXCHANGE_IS_SEND_QUEUE_SIZE_-_MBX Messages Send Queue Size - MBX

QOS_EXCHANGE_IS_SEND_QUEUE_SIZE_-_PF Messages Send Queue Size - PF

QOS_EXCHANGE_IS_SEND_QUEUE_SIZE_-_PUBLIC_FOLDERS

Messages Send Queue Size - Public Folders

QOS_EXCHANGE_IS_USER_COUNT Users User Count

QOS_EXCHANGE_MEMORY_AVAILABLE_MEGABYTES Megabytes Available Megabytes

QOS_EXCHANGE_MEMORY_PAGE_FAULTS_PER_SECOND

Page Faults / Second

Page Faults per Second

QOS_EXCHANGE_MEMORY_PAGES_PER_SECOND Pages / Second

Pages per Second

QOS_EXCHANGE_MEMORY_PAGING_FILE_USAGE Percent Paging File Usage

QOS_EXCHANGE_MEMORY_POOL_NONPAGED_MEGABYTES

Megabytes Pool Nonpaged Megabytes

QOS_EXCHANGE_MEMORY_VIRTUAL_MEGABYTEES_USED_BY_INFORMATION_STORE

Megabytes Virtual Megabytes used by Information Store

QOS_EXCHANGE_MEMORY_VM_LARGEST_BLOCK_SIZE_-_INFORMATION_STORE

Megabytes VM Largest Block Size - Information Store

QOS_EXCHANGE_MTA_AVERAGE_QUEUE_TIME Seconds Average Queue Time

QOS_EXCHANGE_MTA_CONNECTION_QUEUE_LENGTH Messages Connection Queue Length

QOS_EXCHANGE_MTA_MESSAGES_PER_SECOND Messages / Second

Messages per Second

QOS_EXCHANGE_MTA_WORK_QUEUE_LENGTH Messages Work Queue Length

QOS_EXCHANGE_NETWORK_CURRENT_BANDWIDTH Megabits / Second

Current Bandwidth

QOS_EXCHANGE_NETWORK_ERRORS_PER_SECOND Errors / Second

Errors per Second

QOS_EXCHANGE_NETWORK_KILOBYTES_RECEIVED_PER_SECOND

Kilobytes / Second

Kilobytes Received per Second

QOS_EXCHANGE_NETWORK_KILOBYTES_SENT_PER_SECOND

Kilobytes / Second

Kilobytes Sent per Second



QOS_EXCHANGE_NETWORK_KILOBYTES_TOTAL_PER_SECOND

Kilobytes / Second

Kilobytes Total per Second

QOS_EXCHANGE_NETWORK_KILOBYTES_TOTAL_PER_SECOND_-_REDIRECTOR

Kilobytes / Second

Kilobytes Total per Second - Redirector

QOS_EXCHANGE_PROCESSOR_ELAPSED_TIME_-_EMSMTA

Seconds Elapsed Time - emsmta

QOS_EXCHANGE_PROCESSOR_ELAPSED_TIME_-_MAD Seconds Elapsed Time - mad

QOS_EXCHANGE_PROCESSOR_ELAPSED_TIME_-_STORE Seconds Elapsed Time - store

QOS_EXCHANGE_PROCESSOR_PROCESSOR_TIME Percent Processor Time

QOS_EXCHANGE_PROCESSOR_PROCESSOR_TIME_-_EMSMTA

Percent Processor Time - emsmta

QOS_EXCHANGE_PROCESSOR_PROCESSOR_TIME_-_INETINFO

Percent Processor Time - inetinfo

QOS_EXCHANGE_PROCESSOR_PROCESSOR_TIME_-LSASS Percent Processor Time - Isass

QOS_EXCHANGE_PROCESSOR_PROCESSOR_TIME_-_MAD

Percent Processor Time - mad

QOS_EXCHANGE_PROCESSOR_PROCESSOR_TIME_-_STORE

Percent Processor Time - store

QOS_EXCHANGE_PROCESSOR_PROCESSOR_TIME_-_SYSTEM

Percent Processor Time - System

QOS_EXCHANGE_SMTP_LOCAL_QUEUE_LENGTH Messages Local Queue Length

QOS_EXCHANGE_SMTP_MESSAGES_DELIVERED_PER_SECOND

Messages / Second

Messages Delivered per Second

QOS_EXCHANGE_SMTP_MESSAGES_RECEIVED_PER_SECOND

Messages / Second

Messages Received per Second

QOS_EXCHANGE_SMTP_REMOTE_QUEUE_LENGTH Messages Remote Queue Length

Glossary 35

Glossary

Nimsoft Monitor exchange monitor...

Documents

Transcript of Nimsoft Monitor exchange monitor...