Operations Manager

Guide

Version: 10.10
10.10, December 2017
Copyright © 2017 by MicroStrategy Incorporated. All rights reserved.
Trademark Information
The following are either trademarks or registered trademarks of MicroStrategy Incorporated or its affiliates in the United States and certain other countries:
MicroStrategy, MicroStrategy 10, MicroStrategy 10 Secure Enterprise, MicroStrategy 9, MicroStrategy 9s, MicroStrategy Analytics, MicroStrategy Analytics Platform, MicroStrategy
Desktop, MicroStrategy Library, MicroStrategy Operations Manager, MicroStrategy Analytics Enterprise, MicroStrategy Evaluation Edition, MicroStrategy Secure Enterprise,
MicroStrategy Web, MicroStrategy Mobile, MicroStrategy Server, MicroStrategy Parallel Relational In-Memory Engine (MicroStrategy PRIME), MicroStrategy MultiSource,
MicroStrategy OLAP Services, MicroStrategy Intelligence Server, MicroStrategy Intelligence Server Universal, MicroStrategy Distribution Services, MicroStrategy Report Services,
MicroStrategy Transaction Services, MicroStrategy Visual Insight, MicroStrategy Web Reporter, MicroStrategy Web Analyst, MicroStrategy Office, MicroStrategy Data Mining Services,
MicroStrategy Narrowcast Server, MicroStrategy Health Center, MicroStrategy Analyst, MicroStrategy Developer, MicroStrategy Web Professional, MicroStrategy Architect,
MicroStrategy SDK, MicroStrategy Command Manager, MicroStrategy Enterprise Manager, MicroStrategy Object Manager, MicroStrategy Integrity Manager, MicroStrategy System
Manager, MicroStrategy Analytics App, MicroStrategy Mobile App, MicroStrategy Tech Support App, MicroStrategy Mobile App Platform, MicroStrategy Cloud, MicroStrategy R
Integration, Dossier, Usher, MicroStrategy Usher, Usher Badge, Usher Security, Usher Security Server, Usher Mobile, Usher Analytics, Usher Network Manager, Usher Professional,
MicroStrategy Services, MicroStrategy Professional Services, MicroStrategy Consulting, MicroStrategy Customer Services, MicroStrategy Education, MicroStrategy University,
MicroStrategy Managed Services, BI QuickStrike, Mobile QuickStrike, Transaction Services QuickStrike Perennial Education Pass, MicroStrategy Web Based Training (WBT),
MicroStrategy World, Best in Business Intelligence, Pixel Perfect, Global Delivery Center, Direct Connect, Enterprise Grade Security For Every Business, Build Your Own Business
Apps, Code-Free, Welcome to Ideal, The World’s Most Comprehensive Analytics Platform, The World’s Most Comprehensive Analytics Platform. Period.
Other product and company names mentioned herein may be the trademarks of their respective owners.
Specifications subject to change without notice. MicroStrategy is not responsible for errors or omissions. MicroStrategy makes no warranties or commitments concerning the availability
of future products or versions that may be planned or under development.
Patent Information
This product is patented. One or more of the following patents may apply to the product sold herein: U.S. Patent Nos. 6,154,766, 6,173,310, 6,260,050, 6,263,051, 6,269,393, 6,279,033,
6,567,796, 6,587,547, 6,606,596, 6,658,093, 6,658,432, 6,662,195, 6,671,715, 6,691,100, 6,694,316, 6,697,808, 6,704,723, 6,741,980, 6,765,997, 6,768,788, 6,772,137, 6,788,768, 6,798,867,
6,801,910, 6,820,073, 6,829,334, 6,836,537, 6,850,603, 6,859,798, 6,873,693, 6,885,734, 6,940,953, 6,964,012, 6,977,992, 6,996,568, 6,996,569, 7,003,512, 7,010,518, 7,016,480, 7,020,251,
7,039,165, 7,082,422, 7,113,993, 7,127,403, 7,174,349, 7,181,417, 7,194,457, 7,197,461, 7,228,303, 7,260,577, 7,266,181, 7,272,212, 7,302,639, 7,324,942, 7,330,847, 7,340,040, 7,356,758,
7,356,840, 7,415,438, 7,428,302, 7,430,562, 7,440,898, 7,486,780, 7,509,671, 7,516,181, 7,559,048, 7,574,376, 7,617,201, 7,725,811, 7,801,967, 7,836,178, 7,861,161, 7,861,253, 7,881,443,
7,925,616, 7,945,584, 7,970,782, 8,005,870, 8,051,168, 8,051,369, 8,094,788, 8,130,918, 8,296,287, 8,321,411, 8,452,755, 8,521,733, 8,522,192, 8,577,902, 8,606,813, 8,607,138, 8,645,313,
8,761,659, 8,775,807, 8,782,083, 8,812,490, 8,832,588, 8,943,044, 8,943,187. 8,958,537, 8,966,597, 8,983,440, 8,984,274, 8,984,288, 8,995,628, 9,027,099, 9,027,105, 9,037, 577, 9,038,152,
9,076,006, 9,086,837, 9,116,954, 9,124,630, 9,154,303, 9,154,486, 9,160,727, 9,166,986, 9,171,073, 9,172,699, 9,173,101, 9,183, 317, 9,195,814, 9,208,213, 9,208,444, 9,262,481, 9,264,415,
9,264,480, 9,269,358, 9,275,127, 9,292,571, 9,300,646, 9,311,683 9,313,206, 9,330,174, 9,338,157, 9,361,392, 9,378,386, 9,386,416, 9,391,782, 9,397,838, 9,397,980, 9,405,804, 9,413,710,
9,413,794, 9,430,629, 9,432,808, 9,438,597, 9,444,805, 9,450,942, 9,450,958, 9,454,594, 9,507,755, 9,513,770, 9,516,018, 9,529,850, 9,563,761, 9,565,175, 9,608,970, 9,640,001, 9,646,165,
9,680,908, 9,697,146, 9,697,350, 9,742,764, 9,742,781, 9,743,235, 9,762,564, 9,794,245, 9,801,053, and 9,807,074. Other patent applications are pending.
 1
CONTENTS
Overview and Additional Resources iii
Description of this guide iii
About this book iv
Resources v
1. Getting Started with MicroStrategy Operations Manager 1
Introduction 1
Setting up Operations Manager 2
Accessing Operations Manager 2
Viewing high-level information about your environments 3
Viewing detailed information about an environment 8
Configuring Operations Manager 8
2. Defining the Servers, Environments, and Groups to Monitor 10
Creating and maintaining environments 10
Managing servers 14
Creating and maintaining groups 16
3. Configuring the System to Notify You of Problems 18
Turning alerts on or off 18
Configuring alerts 19
Available alert categories 19
Monitoring machine usage and performance with configuration alerts 20
Monitoring cache and Intelligence Server availability with MicroStrategy 3-tier client
alerts 28
Monitoring Web and Mobile Server availability with MicroStrategy 4-tier client alerts32
Monitoring Intelligence Server performance with MicroStrategy Intelligence Server
alerts 35

© 2017, MicroStrategy Inc. i

Operations Manager Guide

Monitoring Enterprise Manager with MicroStrategy Enterprise Manager alerts 40

Monitoring Mobile ASPx with MicroStrategy Mobile ASPx alerts 40
Monitoring Mobile JSP with MicroStrategy Mobile JSP alerts 41
Monitoring Web JSP with MicroStrategy Web JSP alerts 42
4. Monitoring Your MicroStrategy System 43
Viewing alerts for an environment 43
Viewing the overall health of an environment 44
Monitoring environment activity 48
Index 59

ii © 2017, MicroStrategy Inc.

 1
OVERVIEW AND ADDITIONAL
RESOURCES

Description of this guide

This guide provides instructions for managing, monitoring, and setting alerts for all of your
MicroStrategy systems from one console called MicroStrategy Operations Manager.
• Chapter 1, Getting Started with MicroStrategy Operations Manager
Operations Manager is a console that offers you much information about your system.
This chapter introduces you to the console and its pages and provides steps for viewing
the overall health of your environments, viewing details about environments, and
configuring what information displays on the console.
• Chapter 2, Defining the Servers, Environments, and Groups to Monitor
In Operations Manager, servers make up environments, which make up groups. These
allow you to manage and monitor your system at different levels—from a high level with
groups, down to a detailed level with servers. This chapter provides steps for defining
which servers compose your environments, which environments compose your groups,
and how you can monitor and manage the components of each.
• Chapter 3, Configuring the System to Notify You of Problems
You can view information about your MicroStrategy components at any time with
Operations Manager. However, you have better things to do with your time than
watching the performance of those systems. If you want to be informed when certain
usage or resource thresholds are crossed, you can configure counters and alerts in
Operations Manager. This chapter explains what alerts and counters you can enable
and provides steps for configuring them.
• Chapter 4, Monitoring Your MicroStrategy System

© 2017, MicroStrategy Inc. iii

Operations Manager Guide

Operations Manager provides many details about each environment in your

MicroStrategy system. This chapter introduces you to environment-level alerts;
heartbeat monitors for usage, memory, and processing information; and real-time
system monitors you can use. It provides steps for accessing and configuring these and
for managing the items they monitor.

About this book

The following sections provide the location of examples, list prerequisites for using this book,
and describe the user roles the information in this book was designed for.

Dates in the MicroStrategy Tutorial project are updated to reflect the current year. The sample
documents and images in this guide, as well as the procedures, were created with dates that
may no longer be available in the Tutorial project. Replace them with the first year of data in
your Tutorial project.

How to find business scenarios and examples

Some of the concepts discussed in this guide are accompanied by business scenarios or
other descriptive examples. Many of the examples use the MicroStrategy Tutorial, which is
MicroStrategy’s sample warehouse, metadata, and project. Information about the
MicroStrategy Tutorial can be found in the MicroStrategy Basic Reporting Guide.
Detailed examples of advanced reporting functionality can be found in the Advanced
Reporting Guide.

What’s new in this guide

MicroStrategy 10.7
Operations Manager is no longer available for new installations of MicroStrategy. Customers
upgrading to MicroStrategy 10.7 that have Operations Manager already installed will be
given the option to keep it as part of the Upgrade. Enterprise Manager functionality is now
controlled through Command Manager. Enterprise Manager documentation can now be
found in the Enterprise Manager Guide.

MicroStrategy 10
• This guide is new for this release.

Prerequisites
Before working with this document, you should be familiar with the information in the System
Administration Guide.

Who should use this guide

This document is designed for:

iv © 2017, MicroStrategy Inc.

 Operations Manager Guide

• System administrators responsible for monitoring and maintaining the MicroStrategy

business intelligence system
• Network administrators who may need to configure network connections between the
system’s components

Education
MicroStrategy Education Services provides a comprehensive curriculum and highly skilled
education consultants. Many customers and partners from over 800 different organizations
have benefited from MicroStrategy instruction.
Courses that can help you prepare for using this manual or that address some of the
information in this manual include:
• Implementing MicroStrategy: Development and Deployment
• MicroStrategy Administration
For the most up-to-date and detailed description of education offerings and course curricula,
visit http://www.microstrategy.com/Education.

Resources
Documentation
MicroStrategy provides both manuals and online help; these two information sources
provide different types of information, as described below:
• Manuals: In general, MicroStrategy manuals provide:
▫ Introductory information and concepts
▫ Examples and images
▫ Checklists and high-level procedures to get started
To access documentation resources from any location, click here.
Most of these manuals are also available printed in a bound, soft cover format. To
purchase printed manuals, contact your MicroStrategy Account Executive with a
purchase order number.
• Help: In general, MicroStrategy help provides:
▫ Detailed steps to perform procedures
▫ Descriptions of each option on every software screen

© 2017, MicroStrategy Inc. v

Operations Manager Guide

Translations
Due to translation time, manuals in languages other than English may contain information
that is one or more releases behind. You can see the version number on the title page of
each manual.

Finding information
You can search all MicroStrategy books and Help for a word or phrase, with a simple
Google™ search at http://www.google.com. For example, type “MicroStrategy derived
metric” or “MicroStrategy logical table” into a Google search. As described above, books
typically describe general concepts and examples; Help typically provides detailed steps and
screen options. To limit your search to MicroStrategy books, on Google’s main page you can
click More, then select Books.

Additional formats
MicroStrategy manuals are available as electronic publications, downloadable on the Apple
iBookstore or Google Play, and can be read on your iOS or Android device respectively. To
download a book, search for the book’s title in the iBookstore or Google Play respectively. To
view a list of manuals that are currently available, scan the following QR codes using your
device’s camera:
For iOS devices, scan the following QR code:

For Android devices, scan the following QR code:

For new MicroStrategy releases, it may take several days for the latest manuals to be
available on the iBookstore or Google Play.

vi © 2017, MicroStrategy Inc.

 Operations Manager Guide

Guides for MicroStrategy overview and evaluation

• Introduction to MicroStrategy
Instructions for installing, configuring, and using the MicroStrategy Evaluation Edition of
the software. This guide also includes a detailed, step-by-step evaluation process of
MicroStrategy features, where you perform reporting with the MicroStrategy Tutorial
project and its sample business data.
• MicroStrategy Evaluation Edition Quick Start Guide
Overview of the installation and evaluation process, and additional resources.

Resources for Security

• Usher Help
Steps to setup your Usher Security network, and control access to logical and physical
resources.

Manuals for query, reporting, and analysis

• MicroStrategy Installation and Configuration Guide
Information to install and configure MicroStrategy products on Windows, UNIX, Linux,
and HP platforms, as well as basic maintenance guidelines.
• MicroStrategy Upgrade Guide
Instructions to upgrade existing MicroStrategy products.
• MicroStrategy Project Design Guide
Information to create and modify MicroStrategy projects, and understand facts,
attributes, hierarchies, transformations, advanced schemas, and project optimization.
• MicroStrategy Basic Reporting Guide
Instructions to get started with MicroStrategy Developer and MicroStrategy Web, and
how to analyze data in a report. Includes the basics for creating reports, metrics, filters,
and prompts.
• MicroStrategy Advanced Reporting Guide
• MicroStrategy Report Services Document Creation Guide
Instructions to design and create Report Services documents, building on information in
the Document and Dashboard Analysis Guide. It is organized to help guide you through
creating a new document, from creating the document itself, to adding objects to the new
document, and formatting the document and its objects.
• MicroStrategy Dashboards and Widgets Creation Guide

© 2017, MicroStrategy Inc. vii

Operations Manager Guide

Instructions for designing and creating MicroStrategy Report Services dashboards, a

type of document that is optimized for viewing online and for user interactivity. It builds on
the basic concepts about documents presented in the MicroStrategy Report Services
Document Creation Guide.
• MicroStrategy In-memory Analytics Guide
Information to use MicroStrategy OLAP Services features, including Intelligent Cubes,
derived metrics, derived elements, dynamic aggregation, view filters, and dynamic
sourcing.
• MicroStrategy Office User Guide
Instructions for using MicroStrategy Office to work with MicroStrategy reports and
documents in Microsoft® Excel, PowerPoint, and Word, to analyze, format, and
distribute business data.
• MicroStrategy Mobile Analysis Guide
Information and instructions for using MicroStrategy Mobile to view and analyze data,
and perform other business tasks with MicroStrategy reports and documents on a
mobile device.
• MicroStrategy Mobile Design and Administration Guide
Information and instructions to install and configure MicroStrategy Mobile, as well as
instructions for a designer working in MicroStrategy Developer or MicroStrategy Web to
create effective reports and documents for use with MicroStrategy Mobile.
• MicroStrategy System Administration Guide
Concepts and high-level steps to implement, deploy, maintain, tune, and troubleshoot a
MicroStrategy business intelligence system.
• MicroStrategy Supplemental Reference for System Administration
Information and instructions for MicroStrategy administrative tasks such as configuring
VLDB properties and defining data and metadata internationalization, and reference
material for other administrative tasks.
• MicroStrategy Functions Reference
Function syntax and formula components; instructions to use functions in metrics, filters,
attribute forms; examples of functions in business scenarios.
• MicroStrategy MDX Cube Reporting Guide
Information to integrate MicroStrategy with MDX cube sources. You can integrate data
from MDX cube sources into your MicroStrategy projects and applications.

Manuals for Analytics Modules

• Manual for the Human Resources Analytics Module
• Human Resources Analytics Module Reference

viii © 2017, MicroStrategy Inc.

 Operations Manager Guide

Software Development Kits

• MicroStrategy Developer Library (MSDL)
Information to understand the MicroStrategy SDK, including details about architecture,
object models, customization scenarios, code samples, and so on.
• MicroStrategy Web SDK

The Web SDK is available in the MicroStrategy Developer Library, which is part of the
MicroStrategy SDK

Documentation for MicroStrategy Portlets

• Enterprise Portal Integration Help
Information to help you implement and deploy MicroStrategy BI within your enterprise
portal, including instructions for installing and configuring out-of-the-box MicroStrategy
Portlets for several major enterprise portal servers.

Help
Each MicroStrategy product includes an integrated help system to complement the various
interfaces of the product as well as the tasks that can be accomplished using the product.
Some of the MicroStrategy help systems require a web browser to be viewed. For supported
web browsers, see the MicroStrategy Readme.
MicroStrategy provides several ways to access help:
• Help button: Use the Help button or ? (question mark) icon on most software windows to
see help for that window.
• Help menu: From the Help menu or link at the top of any screen, select MicroStrategy
Help to see the table of contents, the Search field, and the index for the help system.
• F1 key: Press F1 to see context-sensitive help that describes each option in the software
window you are currently viewing.

For MicroStrategy Web, MicroStrategy Web Administrator, and MicroStrategy Mobile Server,
pressing the F1 key opens the context-sensitive help for the web browser you are using to
access these MicroStrategy interfaces. Use the Help menu or ? (question mark) icon to
access help for these MicroStrategy interfaces.

Accessing manuals and other documentation sources

The manuals are available here as well as from the machine where MicroStrategy was
installed.

© 2017, MicroStrategy Inc. ix

Operations Manager Guide

Adobe Acrobat Reader is required to view these manuals. If you do not have Acrobat Reader
installed on your computer, you can download it here.

The best place for all users to begin is with the MicroStrategy Basic Reporting Guide.

To access documentation resources on Windows

1 In Windows, choose Start > Programs (or All Programs) > MicroStrategy
Documentation > Product Manuals.
2 Click the link for the desired manual or other documentation source.
3 If you click the link for the Narrowcast Services SDK Guide, a File Download dialog box
opens. This documentation resource must be downloaded. Select Open this file
from its current location, and click OK.

If bookmarks are not visible on the left side of an Acrobat (PDF) manual, from the View
menu click Bookmarks and Page. This step varies slightly depending on your version of
Adobe Acrobat Reader.

To access documentation resources on UNIX and Linux

1 Within your UNIX or Linux machine, navigate to the directory where you installed
MicroStrategy. The default location is /opt/MicroStrategy, or
$HOME/MicroStrategy/install if you do not have write access to
/opt/MicroStrategy.
2 From the MicroStrategy installation directory, open the Help folder.
3 Open the Product_Manuals.htm file in a web browser. A page opens in your
browser showing a list of available manuals in PDF format and other documentation
sources.
4 Click the link for the desired manual or other documentation source.
5 If you click the link for the Narrowcast Services SDK Guide, a File Download dialog box
opens. This documentation resource must be downloaded. Select Open this file
from its current location, and click OK.

If bookmarks are not visible on the left side of an Acrobat (PDF) manual, from the View
menu click Bookmarks and Page. This step varies slightly depending on your version of
Adobe Acrobat Reader.

Documentation standards
MicroStrategy online help and PDF manuals (available both online and in printed format) use
standards to help you identify certain types of content. The following table lists these
standards.

x © 2017, MicroStrategy Inc.

 Operations Manager Guide

These standards may differ depending on the language of this manual; some languages have
rules that supersede the table below.

Type Indicates

bold • Button names, check boxes, options, lists, and menus that are the focus of actions
or part of a list of such GUI elements and their definitions
Example: Click Select Warehouse .
italic • Names of other product manuals and documentation resources
• When part of a command syntax, indicates variable information to be replaced by
the user
Example: The aggregation level is the level of calculation for the metric.
Example: Type copy c:\filename d:\foldername\filename

Courier • Calculations
font • Code samples
• Registry keys
• Path and file names
• URLs
• Messages displayed in the screen
• Text to be entered by the user
Example: Sum(revenue)/number of months.

Example: Type cmdmgr -f scriptfile.scp and press Enter.

+ A keyboard command that calls for the use of more than one key (for example,
SHIFT+F1).
A note icon indicates helpful information for specific situations.

A warning icon alerts you to important information such as potential security risks;
these should be read before continuing.

© 2017, MicroStrategy Inc. xi

 1
GETTING STARTED WITH
MICROSTRATEGY
OPERATIONS MANAGER

Introduction
MicroStrategy Operations Manager is a web-based administrative tool that shows you all of
your MicroStrategy environments and lets you monitor them in one place. In Operations
Manager, you can:
• Define thresholds for system usage and performance, and you can have the system
send alerts when those thresholds are met or exceeded.
• View key usage and performance information in charts so you can quickly see the overall
health of an environment.
• View information that Operations Manager collects from the Health Center system for
each of your environments. For more information on Health Center, see the System
Administration Guide.
To set up Operations Manager and see its capabilities, see the following:
• Setting up Operations Manager, page 2
• Accessing Operations Manager, page 2
• Viewing high-level information about your environments, page 3
• Viewing detailed information about an environment, page 8
• Configuring Operations Manager, page 8

© 2017, MicroStrategy Inc. 1

Operations Manager Guide

Setting up Operations Manager

Before you can access Operations Manager:
• It must be deployed in your system. For prerequisites and steps, see the Installation and
Configuration Guide. Operations Manager does not need to be installed on the same
machine as the MicroStrategy Intelligence Server or Web server.
• After Operations Manager is deployed, use the Configuration Wizard to make the
Operations Manager machine the Master Health Agent. If Operations Manager is
installed on a separate machine, configure both the Web server and MicroStrategy
Intelligence Server as Health Agents and the Operations Manager machine as the
Master Health Agent. For steps to configure a machine as a Health Agent or a Master
Health Agent, see the System Administration Guide.
• For any user that administers or monitors Operations Manager, assign the needed
access and privileges. For steps to assign privileges, see the System Administration
Guide.
▫ For the user, assign Monitoring access to the Server Configuration Object:
a In MicroStrategy Developer, from the Administration menu, point to
Server and then select Configure MicroStrategy Intelligence Server.
b In the Server Definition, General category, in the Properties area next to Set
Configuration object properties, click Modify. The Properties dialog box
opens.
c In the Properties list on the left, click Security.
d For any user who will be monitoring Operations Manager, click the Object
column and from the drop-down list, select Monitoring. You may have to add
the user’s name.
e Click OK twice.
▫ Assign the user the privilege of Administer operation manager or Monitor
operation manager in the Operations Manager category. Granting the
Operations Manager privileges automatically grants all other privileges needed.

Accessing Operations Manager

You access MicroStrategy Operations Manager through your web browser.

To log in to Operations Manager

1 In your web browser, go to one of the following, according to the type of application
server you are using for Operations Manager:
• JSP. http://server:port/MicroStrategyOM/servlet/mstrOM
• ASP. http://server:port/MicroStrategyOM/asp

2 © 2017, MicroStrategy Inc.

 Operations Manager Guide

where server:port are the machine name and port number where Operations
Manager is installed and accessible.
2 On the Connect to Environment page, type in your MicroStrategy user name and
password.

If the credentials for all the environments are not the same, when you complete the login
process, Operations Manager will be connected to those environments whose credentials
match what you enter here. You will need to individually connect to all other environments.
See Connecting to or disconnecting from an environment, page 4.

3 Select the authentication mode to use. For information on integrating LDAP with
MicroStrategy, see the System Administration Guide.
4 Click Login. The Landing page of Operations Manager is displayed.
The Operations Manager session does not expire, regardless of how long you leave the
session idle, until you log out of the session or the system is shut down.

Viewing high-level information about your

environments
You can view basic information about each of your environments and servers from a single
screen. From that screen, you can see details about each environment, as well as
configuration information for Operations Manager.
To access the Landing page, from anywhere in Operations Manager, click Operations
Manager at the top left.

Your environments are displayed, sorted by group. To view all the servers in an
environment, expand the environment’s name. The icon next to each server indicates what
kind of server it is:
• The server is an Intelligence Server

• The server is a Web server

• The server is a Mobile Server

© 2017, MicroStrategy Inc. 3

Operations Manager Guide

Searching for a server

To search for a server, use the search box.

Connecting to or disconnecting from an environment

You can connect to or disconnect from an environment:
• To disconnect from an environment, point to the environment and click the Disconnect
icon.

• To connect to an environment, point to the environment and click the Connect icon.
You are prompted to log in.

Displaying counters
Counters indicate the overall health of your servers.
To change which counters are displayed, see Changing the displayed counters, page 5.
For a list of available counters, see List of counters, page 6.
To set the thresholds for counters, see Configuring thresholds for counters, page 7.

Hiding information on the Landing page

To hide groups or unconnected environments, click the View icon and click Groups or
Unconnected Environments. The groups or unconnected environments are displayed
or hidden on the page as you click them.

Refreshing groups and environments

To refresh the information about the groups and environments on the Landing page, click the
Refresh icon . This does not refresh the counters.

Monitoring environments
To see the details for an environment, such as alerts, graphs of server resource usage, how
many jobs are executing, and so on, click the environment name. For information about the
available details, see Viewing detailed information about an environment, page 8.

Managing configuration
To manage your Operations Manager configuration, at the upper right of the Landing Page,
click the Configuration icon . The Environment Configuration page opens. For

4 © 2017, MicroStrategy Inc.

 Operations Manager Guide

information about configuring Operations Manager, see Configuring Operations Manager,

page 8.

Viewing counters for an environment

You can view numeric counters, such as how many alerts or user sessions there are; view
line graph counters at a server level; view colored counters at an environment level; and
customize which counters are displayed. These are explained below.
To see all the available counters, see List of counters, page 6.

Changing the displayed counters

Counters provide basic information about the health of your servers. You can change which
counters are displayed.

To change the counters displayed

1 On the Landing page, click the View icon and select Counters. A list of all counters
displays.
2 To turn a counter on or off, click the counter’s name. Counters are added to or removed
from the Landing page as you click them.
3 When you are finished changing the counters, click anywhere outside the View menu.
The menu closes.

Understanding memory and CPU line graph counters for a server

At the server level, the Machine Memory Used, Machine CPU Used, I-Server Memory Used,
and I-Server CPU Used counters display as line graphs in one of the following colors:
• Red: Usage is at a critical level.
• Orange: Usage is at an adequate level.
• Green: Usage is at an excellent level.
Each line graph represents the memory usage over the past minute, with updates every five
seconds. To see the average percentage of memory usage for one of these counters, point
to the line graph. The average usage displays in a tooltip, as shown below:

© 2017, MicroStrategy Inc. 5

Operations Manager Guide

Understanding memory counters for an environment

At the environment level, memory usage displays as one of the following:
• Red dot : Usage for at least one server in the environment is at a critical level.

• Orange dot : Usage for at least one server in the environment is at an adequate
level; all other servers are at either an adequate level or an excellent level.
• Green dot : Usage for all servers in the environment is at an excellent level.

You can configure the thresholds. For steps, see Configuring thresholds for counters, page
7.
If there is a problem with any one of the servers in an environment, an information icon
displays in the usage columns of the environment row. Point to the icon for details.

List of counters
You can view the following counters:

Counter name Description

Server Status The status of the server: Running, Starting, Stopping, Stopped, or Unknown.
Up Time The percentage of time the server has been up over the past 24 hours.
Alerts The total number of unread alerts for the environment or server. A value
displays for this counter at both the environment level and the server level. At
the environment level, the value is equal to the sum of the values for all the
servers in the environment.

6 © 2017, MicroStrategy Inc.

 Operations Manager Guide

Counter name Description

Machine Memory The real-time memory usage, displayed in graph format.

Used
Machine CPU Used The real-time CPU usage on the server, displayed in graph format.
I-Server Memory The real-time memory used by the Intelligence Server, displayed in graph
Used format.
I-Server CPU Used The real-time CPU usage by the Intelligence Server, displayed in graph format.
Open Sessions The total number of open sessions for the environment. A value displays for
this counter at both the environment level and the server level. At the
environment level, the value is equal to the sum of the values for all the
servers in the environment.
Disk I/O bytes Real-time rate of disk read and write in bytes per second. This is hidden by
default.

Memory Pages I/O Real-time number of pages swapped in and out of memory. This is hidden by
default.
Network I/O Real-time rate of network read and write in bytes per second.
For the Network I/O counter to display information, a simple network
management protocol (SNMP) service agent must be configured and enabled.
For instructions, see your third-party SNMP documentation.
Disk I/O Operation Real-time total number of in and out operations per second. This is hidden by
default.

Configuring thresholds for counters

You can customize a counter's thresholds for Excellent, Adequate, and Critical performance,
which affect the counter's color that is displayed on the Landing page. For example, you may
change a counter to turn red when a the server's memory is at 85 percent rather than the
default 66 percent.
By default, all counters are preset with 33 percent as the Excellent threshold and 66 percent
as the Critical threshold.
You can change the thresholds for the following counters:
• Up Time
• Machine Memory Used
• Machine CPU Used
• I-Server Memory Used
• I-Server CPU Used

© 2017, MicroStrategy Inc. 7

Operations Manager Guide

To change the threshold for a counter

1 On the Landing page, click the Configuration icon .

2 On the left, click the Counter icon . The Counters page opens.

3 Move the threshold markers on the slider to set the boundaries between excellent,
adequate, and critical performance.
If you start making changes to the counter thresholds and then decide you do not want to
save the changes, and you have not yet applied them, you can reset the counters to the
most recent configuration by clicking Revert.
4 Click Apply when you are finished.

Viewing detailed information about an

environment
You can view details for a selected environment, such as alerts, usage information, or
information about jobs and users. Each environment can have one Intelligence Server or
one Intelligence Server cluster, and multiple Web and Mobile Servers.
To view the details for an environment, from the Landing page, click the environment’s
name, then click one of the following on the left:
• Alerts icon : Displays alerts for the environment. You can sort alerts by date, or
group by machine. You can also view alerts for just one server. For additional
information about alerts, see Viewing alerts for an environment, page 43.
• Heartbeat icon : Displays server usage information in graph format, such as how
much of the server's CPU or memory is used, or the job completion rate. For information
about server usage, see Viewing the overall health of an environment, page 44.

• Monitors icon : Displays the various activity monitors for the environment, such as
how many jobs are executing, how many users are connected to a server, and so on.
For information about the available monitors, see Monitoring environment activity, page
48.

Configuring Operations Manager

You can configure the items you work with in Operations Manager, such as when alerts are
triggered, what servers to monitor, and so on. Configuring Operations Manager includes the
following:
• Adding and maintaining environments. For steps to create an environment and manage
it, see Creating and maintaining environments, page 10.

8 © 2017, MicroStrategy Inc.

 Operations Manager Guide

• Creating and maintaining groups. For steps to create and manage your groups, see
Creating and maintaining groups, page 16.
• Setting counter thresholds. For steps, see Configuring thresholds for counters, page 7.
• Configuring alerts. For information on what alerts are available and steps to configure
them, such as setting up a real-time alert to notify you by email when it is triggered, see
Configuring the System to Notify You of Problems, page 18.

To access the Configuration page, click the Configuration icon .

© 2017, MicroStrategy Inc. 9

 2
DEFINING THE SERVERS,
ENVIRONMENTS, AND
GROUPS TO MONITOR
With Operations Manager, you can easily monitor all of your MicroStrategy systems in one
place.
You can allocate your MicroStrategy servers into environments, and monitor each
environment separately. For steps to configure and manage your environments, see
Creating and maintaining environments, page 10. For steps to manage your servers, see
Managing servers, page 14.
A group is a collection of environments that are all related in some way. For example, you
might have a group for all servers on the East Coast and another group for the West Coast.
An environment may be a member of more than one group. To configure and manage your
groups, see Creating and maintaining groups, page 16.

Creating and maintaining environments

An environment is a collection of servers involved in the same MicroStrategy-specific task.
An environment consists of an Intelligence Server, or a cluster of Intelligence Servers,
together with any MicroStrategy Web servers or Mobile Servers that are associated with the
Intelligence Server.
With Operations Manager, you can manage all servers in an environment at once. For
example, a user may have trouble accessing MicroStrategy Web. In Operations Manager,
you can check the status of the user’s MicroStrategy Web servers and Intelligence Server at
the same time.

Managing your environments

You can view the list of your environments in Operations Manager; create, modify, and
delete an environment; and determine whether users can access the usage and job monitors
for an environment.

© 2017, MicroStrategy Inc. 10

Operations Manager Guide

To manage environments, on the Landing page, click the Configuration icon , then click
the Environment icon .

• You can create a new environment by clicking +Create Environment. For steps, see
Creating a new environment, page 11.
• You can display and hide access to usage and job monitor information on the left of the
Environment Details page. For example, if maintenance is being done on a server, you
may want to hide the tabs until the maintenance is complete. You can display or hide the
following:
▫ Heartbeat tab: To display the tab showing usage information on the left of the
Environment Details page, click Disabled. To hide it, click Enabled.
▫ Monitor tab: To display the tab showing job monitor information on the left of the
Environment Details page, click Disabled. To hide the Monitor tab, click Enabled.
• You can modify an existing environment by pointing to the environment, then clicking the
Modify icon . For details, see Modifying an environment, page 13.
▫ You can include an environment in one or more groups. For details, see Selecting
environments for a group, page 17.
▫ You can include a server in an environment. For details, see Selecting servers for an
environment, page 14.
• You can delete an environment, by pointing to the environment’s row, then clicking the
Delete icon .

Creating a new environment

Before you can monitor servers in Operations Manager, first create an environment and
include the servers in the environment.

To create a new environment

1 In Operations Manager, click the Configuration icon . Configuration information is

displayed on the Environments page.
2 Click +Create Environment. The Create Environment dialog box is displayed.
3 In the Environment Name field, type a descriptive name for the environment.
4 In the Intelligence Server Name field, type the hostname or IP address of your
Intelligence Server.
5 In the Port field, type the port to your Intelligence Server.
6 Click Test Connection. The Connect dialog box displays.
7 Enter your MicroStrategy login credentials in the Username and Password fields, and
select the authentication method to use. For information on integrating LDAP with
MicroStrategy, see the MicroStrategy System Administration Guide.

11 © 2017, MicroStrategy Inc.

 Operations Manager Guide

8 Click Login.

To add a MicroStrategy Web server to the environment

9 Follow the appropriate steps below depending on whether you are adding servers to
Operations Manager for the first time, or need to add them to Operations Manager and
then add them to the environment:
• To add a Web server for the first time to Operations Manager and to the
environment:
a In the Web Server Name field, enter the hostname or IP address of the
server hosting MicroStrategy Web.
b In the Application Path field, enter the application path to MicroStrategy
Web. By default, the application path is MicroStrategy, but your installation
may be different.
c In the Port field, enter the port on which MicroStrategy Web runs.
d Select one of the following server types:
— ASP
— JSP
e If communication between the Intelligence Server and your MicroStrategy Web
server is encrypted, select the HTTPS check box.
f Click Add.
g Repeat steps a through f for each additional Web server you add.
• To add a server that is already set up in Operations Manager:
a Click Add from Pool. A list of available Web servers is displayed.
b Select the check box next to each Web server you want to add.
c Click OK.

To add a MicroStrategy Mobile Server to the environment

10 Follow the appropriate steps below depending on whether you are adding servers to
Operations Manager for the first time, or need to add them to Operations Manager and
then add them to the environment:
• To add a Mobile Server for the first time to Operations Manager and to the
environment:
a In the Mobile Server Name field, enter the hostname or IP address of the
server that is hosting MicroStrategy Mobile.
b In the Application Path field, enter the application path to MicroStrategy
Mobile. By default, the application path is MicroStrategyMobile, but your
installation may be different.

© 2017, MicroStrategy Inc. 12

Operations Manager Guide

c In the Port field, enter the port on which MicroStrategy Mobile runs.
d Select one of the following server types:
— ASP
— JSP
e If communication between the MicroStrategy Intelligence Server and the
MicroStrategy Mobile Server is encrypted, select the HTTPS check box.
f Click Add.
g Repeat steps a through f for each additional Mobile Server you add.
• To add a Mobile Server that is already set up in Operations Manager.
a Click Add from Pool. A list of available Mobile Servers is displayed.
b Select the check box next to each Mobile Server you want to add.
c Click OK.
11 When you are finished, click Create. The new environment is saved.

Modifying an environment
You can change the details of an environment, such as the servers in the environment, and
the groups associated with the environment.

To modify an environment

1 In Operations Manager, click the Configuration icon . Configuration information is

displayed on the Environments page.
2 Point to the environment to modify, then click the Modify icon . The Edit Environment
dialog box is displayed.
3 In the Environment Name field, type a descriptive name for the environment.
4 In the Intelligence Server Name field, type the hostname or IP address of your
Intelligence Server.
5 In the Port field, type the port to your Intelligence Server.
6 Click Test Connection. The Connect dialog box displays.
7 Enter your MicroStrategy login credentials, and select the authentication method to use.
For information on integrating LDAP with MicroStrategy, see the System Administration
Guide.
8 Click Login.
9 To modify the MicroStrategy Web servers and Mobile Servers in the environment, see
Selecting servers for an environment.
10 When you are finished, click Save.

13 © 2017, MicroStrategy Inc.

 Operations Manager Guide

Selecting servers for an environment

You can define which MicroStrategy Web and Mobile servers are included in an
environment.

To add or remove MicroStrategy Web or Mobile servers to or from an

environment

1 In Operations Manager, click the Configuration icon . Configuration information is

displayed on the Environments page.
2 Point to the environment’s row, then click the Modify icon . The Edit Environment
dialog box is displayed.

To modify MicroStrategy Web servers

3 For steps to add additional Web servers, see To add a MicroStrategy Web server to the
environment, page 12.
4 To remove a Web server from the environment, click the Delete icon next to the
server you want to remove, then click Yes.
5 To modify a Web server, click the Edit icon next to the server you want to modify,
change the Web server information as needed, then click OK.

To modify MicroStrategy Mobile Servers

6 For steps to add additional Mobile Servers, see To add a MicroStrategy Mobile Server to
the environment, page 12.
7 To remove a Mobile Server from the environment, click the Delete icon next to the
server you want to remove, then click Yes.
8 To modify a Mobile Server, click the Edit icon next to the server you want to modify,
change the Mobile Server information as needed, then click OK.
9 When you are finished, click Save.

Managing servers
You can view the list of servers in an environment, start and stop a server, view the server
status, and configure which servers are included in an environment.
An Operations Manager environment is made up of one or more servers. A server is a
machine that is running a MicroStrategy server component, such as Intelligence Server,
MicroStrategy Web server, or MicroStrategy Mobile Server.

© 2017, MicroStrategy Inc. 14

Operations Manager Guide

• You can view the servers in an environment and check their status. For details, see
Viewing the servers in an environment, page 15.
• You can start, stop, or restart an Intelligence Server. For instructions, see Starting,
stopping, or restarting a server, page 15.
• You can configure which servers are part of an environment. For steps, see Selecting
servers for an environment, page 14.

Viewing the servers in an environment

You can view the servers in an environment, view the type of server (Web server,
Intelligence Server, or Mobile Server), what machine is hosting it, and see the server status.

To view the server status

1 On the Operations Manager Landing page, click the Configuration icon , then click
the Servers icon .

2 From the Environments drop-down list, select the environment. The servers in the
environment are listed with details.
You can start and stop an Intelligence Server. For steps, see Starting, stopping, or restarting
a server.

Starting, stopping, or restarting a server

You can start, stop, or restart an Intelligence Server in an environment. Servers can be in
one of the following states: Started, Stopped, or Starting.

To start, stop, or restart a server

1 In Operations Manager, click the Configuration icon . Configuration information is

displayed on the Environments page.

2 Click the Servers icon .

3 From the environment drop-down list, select the environment that contains the server
you want to start, stop, or restart. The servers and their details are displayed.
4 Point to the server and perform one of the following:

• To start a server click the Start icon .

• To stop a server, click the Stop icon .

• To restart a server, click the Restart icon .
A login dialog box is displayed.

15 © 2017, MicroStrategy Inc.

 Operations Manager Guide

5 Type a username and password for the machine's operating system and click Login.
The server status changes.

Creating and maintaining groups

You can combine your environments into groups so you can easily monitor them in
Operations Manager. For example, you may have a different environment for servers in each
geographic region. In this case, you may create a geographic group that includes all the
region environments. You may also have a different environment for servers that service
requests from each business unit, so you may create a group that includes all the business
unit environments. With those groups, you can see the environments and servers by
geographic region or by business unit.
From the Landing page, you can expand a group and see the underlying environments, then
expand the environments to see the servers.
You can add an environment to more than one group. An environment is not required to be a
group; any environment that is not in a group is displayed as an ungrouped environment on
the Landing page.
For steps to create a group, place environments in a group, and delete a group, see the
following:
• Creating a new group, page 16
• Selecting environments for a group, page 17
• Deleting a group, page 17

Creating a new group

You can create groups to organize your environments. You can then view from one place all
environments and servers that are in the group.

To create a new group

1 In Operations Manager, click the Configuration icon . Configuration information is

displayed on the Environments page.
2 Click the Groups icon .

3 Click Add New Group. The Create Group configuration panel opens.
4 In the Name field, type a name for the group.
5 Select the check box for each environment that you want to include in this group. You
can use the Environments search box to search for the ones you want.
6 Click Save. The group is created.

© 2017, MicroStrategy Inc. 16

Operations Manager Guide

Selecting environments for a group

You can configure which environments are in a group so that you can view from one place
the environments and servers within that group.

To add environments to or remove environments from a group

1 In Operations Manager, click the Configuration icon . Configuration information

displays on the Environments page.
2 Click the Groups icon .

3 Point to the group you want modify, then click the Edit icon . The Edit Group panel
opens.
4 To add an environment to the group, select the environment's check box; to remove it
from the group, clear the check box.
5 Click Save. The changes to the group are saved.

Deleting a group
If you no longer want to use a group, you can delete it. Deleting a group does not delete an
environment that is in the group. Environments are not required to be in a group. If you delete
a group, an environment that was in that group, and is not in any other group, displays in
Operations Manager as an ungrouped environment.

To delete a group

1 In Operations Manager, click the Configuration icon . Configuration information is

displayed on the Environments page.
2 Click the Groups icon .

3 Point to the group you want to delete, click the Delete icon , and then click Yes.

17 © 2017, MicroStrategy Inc.

 3
CONFIGURING THE SYSTEM
TO NOTIFY YOU OF
PROBLEMS
You can configure Operations Manager to notify you of events that need to be addressed.
For example, you may set an alert to warn you when report processing times are too long,
when the CPU usage on a machine becomes too high for a sustained time, or when a
phrase or word you specify appears in a log file. Some alerts can be configured to send email
to a recipient or list of recipients.
For steps on turning alerts on or off, see Turning alerts on or off, page 18.
For steps on configuring alerts, see Configuring alerts, page 19.
For a list of alerts you can configure, by category, see Available alert categories, page 19.

Turning alerts on or off

The steps for turning alerts on or off are below. You can do this for real-time alerts; system
alerts are always on.

To turn alerts on or off

1 On the Landing page, click the Configuration icon . The Configuration page opens.

2 Click the Alerts icon . The Alerts configuration page displays.

3 From the Environment drop-down menu, select the environment you want to turn
alerts on or off for.
4 From the Server drop-down menu, select the server you want to turn alerts on or off for.
5 To list alerts in one category, select the category, such as MicroStrategy Intelligence
Server, from the Category drop-down list.

© 2017, MicroStrategy Inc. 18

Operations Manager Guide

6 To turn on an alert, under the Status column, move the Off slider to On .

• If the Configuration panel opens, provide the necessary configuration values and
click Apply.

7 To turn off an alert, under the Status column, move the On slider to Off .

Configuring alerts
The steps for configuring alerts are below.

To configure an alert

1 On the Landing page, click the Configuration icon . The Configuration page opens.

2 Click the Alerts icon . The Alerts configuration page displays.

3 From the Environment drop-down menu, select the environment you want to
configure alerts for.
4 From the Server drop-down menu, select the server you want to configure alerts for.
5 To list alerts in one category, select the category, such as MicroStrategy Intelligence
Server, from the Category drop-down list.
6 Click the name of the alert you want to configure. The Configuration panel opens on the
right.
7 Make changes to the configuration options. For categories of alerts and details on each
alert’s options, see the appropriate section in Available alert categories, page 19.
8 Click Apply.
9 If the alert is a real-time alert, turn it on to enable it. For steps, see Turning alerts on or
off.

Available alert categories

You can configure and turn on alerts depending on what points of the system are having
problems. For example, if you notice a machine that repeatedly has performance issues, you
can use the alerts in the machine usage and performance category for that machine. Or if
you want to be notified if a Mobile Server becomes unavailable, you can turn on alerts in the
Web and Mobile Server availability category.
Below is the list of alert categories.
• Monitoring machine usage and performance with configuration alerts, page 20

19 © 2017, MicroStrategy Inc.

 Operations Manager Guide

• Monitoring cache and Intelligence Server availability with MicroStrategy 3-tier client
alerts, page 28
• Monitoring Web and Mobile Server availability with MicroStrategy 4-tier client alerts,
page 32
• Monitoring Intelligence Server performance with MicroStrategy Intelligence Server
alerts, page 35
• Monitoring Mobile ASPx with MicroStrategy Mobile ASPx alerts, page 40
• Monitoring Mobile JSP with MicroStrategy Mobile JSP alerts, page 41
• Monitoring Web JSP with MicroStrategy Web JSP alerts, page 42

Monitoring machine usage and performance

with configuration alerts
The configuration alerts monitor the usage and performance of your machines and network.
You can configure the following configuration alerts:
• Memory Usage alerts, page 20
• CPU Usage alerts, page 21
• Logical Disk Free Space alerts, page 23
• Logical Disk I/O alert, page 24
• Memory Pages I/O alert, page 24
• Network Traffic In and Out alerts, page 25
• Network Status alerts, page 26
• Page File Usage alert, page 28

Memory Usage alerts

Sends an alert if memory usage thresholds on a server are exceeded. For example, you can
send an alert when the available memory falls below a certain amount or when memory
usage equals or exceeds a certain amount for a specified time.
You can configure the following thresholds and other options for available and used memory
on a server:

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read
Polling Period Manager polls the server every 5 seconds to get the real-time only
information for these alerts.

© 2017, MicroStrategy Inc. 20

Operations Manager Guide

Option Description Required?

Real Time Counter For MicroStrategy use. Read

Instance only
Available Memory The amount of available memory, in megabytes, that triggers an Yes
Alerting Threshold alert. If the amount of available memory on the server is at or less
(MB) than this amount, an alert is triggered. The default is 20.
Available Memory The number of consecutive polling periods that the Available Yes
Alerting Sustain Memory Alerting Threshold must meet or exceed to trigger an alert.
Interval The default is 12. This number multiplied by the Real Time Counter
Polling Period is the total number of seconds the threshold must
be maintained. For example, if this interval is 12 and the polling
period is 5, the threshold must be maintained for 60 seconds
before an alert is triggered.
Available Memory The minimum number of consecutive polling periods after the last Yes
Alerting Minimum available memory usage alert was triggered before that alert can
Firing Interval be triggered again. The default is 60. This value multiplied by the
Real Time Counter Polling Period must be 300 or more. For
example, the polling period is 5, this interval must be at least 60.
Used Memory The total amount of used memory, in megabytes, that triggers an Yes
Alerting Threshold alert. If the usage amount equals or exceeds this amount, an alert
(MB) is triggered. The default is 20.
Used Memory The number of consecutive polling periods that the Used Memory Yes
Alerting Sustain Alerting Threshold must meet or exceed to trigger an alert. The
Interval default is 12. This number multiplied by the Real Time Counter
Polling Period is the total number of seconds the alerting threshold
must be maintained. For example, if this interval is 12 and the
polling period is 5, the threshold must be maintained for 60
seconds before an alert is triggered.
Used Memory The minimum number of consecutive polling periods after the last Yes
Alerting Minimum used memory usage alert was triggered before that alert can be
Firing Interval triggered again. The default is 60. This value multiplied by the Real
Time Counter Polling Period must be 300 or more. For example,
with the polling period of 5, this interval must be at least 60.

CPU Usage alerts

Sends alerts about CPU usage for a server. For example, you can send an email when a
server's total CPU usage meets or exceeds an amount for a specified time.
You can configure the following thresholds and other options for a server's CPU usage:

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read
Polling Period Manager polls the server every 5 seconds to get the real-time only
information for these alerts.

21 © 2017, MicroStrategy Inc.

 Operations Manager Guide

Option Description Required?

Real Time Counter For MicroStrategy use. Read

Instance only
Alert Email The email addresses the alerts are sent to when the thresholds for No
Recipient this alert are met. Separate multiple addresses with a semicolon
(;).
Total CPU The CPU usage amount that triggers an alert, expressed as a Yes
Percentage Alert percentage of the total available CPU capacity. If the total CPU
Threshold usage is at or above this amount, an alert is triggered. The default
is 20.
Total CPU The number of consecutive polling periods that the Total CPU Yes
Percentage Alerting Percentage Alert Threshold must meet or exceed to trigger an alert.
Sustain Interval The default is 12. This number multiplied by the Real Time Counter
Polling Period is the total number of seconds the alerting threshold
must be maintained. For example, if this interval is 12 and the
polling period is 5, the Total CPU Percentage Alert Threshold must
be maintained for 60 seconds before an alert is triggered.
Total CPU The minimum number of consecutive polling periods after the Yes
Percentage Alerting Total CPU Percentage Alert was triggered before that alert can be
Minimum Firing triggered again. The default is 60. This value multiplied by the Real
Interval Time Counter Polling Period must be 300 or more. For example,
with the polling period of 5, this interval must be at least 60.
Kernel CPU The kernel CPU usage amount that triggers an alert, expressed as Yes
Percentage Alerting a percentage of the total kernel CPU capacity. If the kernel CPU
Threshold usage is at or above this amount, an alert is triggered. The default
is 20.

Kernel CPU The number of consecutive polling periods that the Kernel CPU Yes
Percentage Alerting Percentage Alerting Threshold must meet or exceed to trigger an
Sustain Interval alert. The default is 12. This number multiplied by the Real Time
Counter Polling Period is the total number of seconds the threshold
must be maintained. For example, if this is 12 and the polling
period is 5, the threshold must be maintained for 60 seconds
before an alert is triggered.
Kernel CPU The minimum number of consecutive polling periods after the Yes
Percentage Alerting Kernel CPU Percentage alert was triggered before that alert can be
Minimum Firing triggered again. The default is 60. This value multiplied by the Real
Interval Time Counter Polling Period must be 300 or more. For example, if
this is 60 and the polling period is 5, a new alert may not be
triggered until 300 seconds after the last one was triggered.
User CPU The user CPU usage amount that triggers an alert, expressed as a Yes
Percentage Alerting percentage of the total user CPU capacity. If the user CPU usage is
Threshold at or above this amount, an alert is triggered. The default is 20.
User CPU The number of consecutive polling periods that the User CPU Yes
Percentage Alerting Percentage Alerting Threshold must meet or exceed to trigger an
Sustain Interval alert. The default is 12. This number multiplied by the Real Time
Counter Polling Period is the total number of seconds the threshold
must be maintained. For example, if this is 12 and the polling
period is 5, the User CPU Percentage Alerting Threshold must be

© 2017, MicroStrategy Inc. 22

Operations Manager Guide

Option Description Required?

maintained for 60 seconds before an alert is triggered.

User CPU The minimum number of consecutive polling periods after the User Yes
Percentage Alerting CPU Percentage alert was triggered before that alert can be
Minimum Firing triggered again. The default is 60. This value multiplied by the Real
Interval Time Counter Polling Period must be 300 or more. For example, if
this is 60 and the polling period is 5, a new alert may not be
triggered until 300 seconds after the last one was triggered.

Logical Disk Free Space alerts

Sends alerts about the amount of logical disk free space on a server. For example, you can
send an email when the logical disk free space is at or below a specified amount for a
specified time.
You can configure the following thresholds and other options for a server's logical free disk
space:

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read
Polling Period Manager polls the server every 5 seconds to get the real-time only
information for the alert.
Real Time Counter For MicroStrategy use. Read
Instance only

Alert Email The email addresses the alerts are sent to when the threshold for No
Recipient this alert is met. Separate multiple addresses with a semicolon (;).
Logical Disk Free The logical disk free space amount that triggers an alert, expressed Yes
Space Percentage as a percentage of the total logical disk free space capacity. If the
Alerting Threshold logical disk free space usage is at or above this amount, an alert is
triggered. The default is 20.
Logical Disk Free The number of consecutive polling periods that the Logical Disk Yes
Space Percentage Free Space Percentage Alerting Threshold must meet or exceed to
Alerting Sustain trigger an alert. The default is 12. This number multiplied by the
Interval Real Time Counter Polling Period is the total number of seconds
the threshold must be maintained. For example, if this is 12 and
the polling period is 5, the Logical Disk Free Space Percentage
Alerting Threshold must be maintained for 60 seconds before the
alert is triggered.
Logical Disk Free The minimum number of consecutive polling periods after the Yes
Space Percentage Logical Disk Free Space Percentage alert was triggered before that
Alerting Minimum alert can be triggered again. The default is 60. This value multiplied
Firing Interval by the Real Time Counter Polling Period must be 300 or more. For
example, if this is 60 and the polling period is 5, a new alert may
not be triggered until 300 seconds after the last one was triggered.
Logical Partition or The logical partition or directory from which to gather the logical Yes
directory disk free space information. The default is C:.

23 © 2017, MicroStrategy Inc.

 Operations Manager Guide

Logical Disk I/O alert

Sends an alert about a server's number of logical disk input and output operations per
second. For example, you can send an email when the number of operations per second is
at or above a specified amount for a specified time.
You can configure the following thresholds and other options for a server's logical disk input
and output operations:

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read
Polling Period Manager polls the server every 5 seconds to get the real-time only
information for the alert.
Real Time Counter For MicroStrategy use. Read
Instance only

Alert Email The email addresses the alerts are sent to when the threshold for No
Recipient this alert is met. Separate multiple addresses with a semicolon (;).
Logical Disk IO per The number of logical disk input and output operations per second Yes
Second Alerting that triggers an alert. If the number of logical disk input and output
Threshold operations is at or above this amount, an alert is triggered. The
default is 20.
Logical Disk IO per The number of consecutive polling periods the Logical Disk IO per Yes
Second Alerting Second Alerting Threshold must meet or exceed to trigger an alert.
Sustain Interval The default is 12. This number multiplied by the polling period is
the total number of seconds the threshold must be maintained.
For example, if this is 12 and the polling period is 5, the Logical
Disk IO per Second Alerting Threshold must be maintained for 60
seconds before an alert is triggered.
Logical Disk IO per The minimum number of consecutive polling periods after the Yes
Second Alerting Logical Disk I/O per Second alert was triggered before that alert
Minimum Firing can be triggered again. The default is 60. This value multiplied by
Interval the Real Time Counter Polling Period must be 300 or more. For
example, if this is 60 and the polling period is 5, a new alert may
not be triggered until 300 seconds after the last one was triggered.

Memory Pages I/O alert

Sends alerts about the number of memory pages input/output operations per second on a
server. For example, you can send an email when the number of operations per second on a
server is at or above a specified amount for a specified time.
You can configure the following thresholds and other options for a server's memory page
operations:

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read

© 2017, MicroStrategy Inc. 24

Operations Manager Guide

Option Description Required?

Polling Period Manager polls the server every 5 seconds to get the real-time only
information for the alert.
Real Time Counter For MicroStrategy use. Read
Instance only
Alert Email The email addresses the alerts are sent to when the threshold for No
Recipient this alert is met. Separate multiple addresses with a semicolon (;).
Memory Pages IO The number of pages being swapped in and out of memory per Yes
per Second Alerting second that triggers an alert. If the number of pages is at or above
Threshold this amount, an alert is triggered. The default is 20.
Memory Pages IO The number of consecutive polling periods the Memory Pages IO Yes
per Second Alerting per Second Alerting Threshold must meet or exceed to trigger an
Sustain Interval alert. The default is 12. This number multiplied by the Real Time
Counter Polling Period is the total number of seconds the Alerting
Threshold must be maintained. For example, if this is 12 and the
polling period is 5, the Memory Pages IO per Second Alerting
Threshold must be maintained for 60 seconds before an alert is
triggered.
Memory Pages IO The minimum number of consecutive polling periods after the Yes
per Second Alerting Memory Pages IO per Second alert was triggered before that alert
Minimum Firing can be triggered again. The default is 60. This value multiplied by
Interval the Real Time Counter Polling Period must be 300 or more. For
example, if this is 60 and the polling period is 5, a new alert may
not be triggered until 300 seconds after the last one was triggered.

Network Traffic In and Out alerts

Sends alerts according to the amount of network in and out traffic per second on a server.
For example, you can send an email when the network in traffic reaches a specified amount
for a specified time.
For this alert to work, a simple network management protocol (SNMP) service agent must
be configured and enabled. For instructions, see your third-party SNMP documentation.
You can configure the following thresholds and other options for a server's network in and
out traffic:

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read
Polling Period Manager polls the server every 5 seconds to get the real-time only
information for these alerts.
Real Time Counter For MicroStrategy use. Read
Instance only
Alert Email The email addresses the alerts are sent to when the thresholds for No
Recipient this alert are met. Separate multiple addresses with a semicolon
(;).

25 © 2017, MicroStrategy Inc.

 Operations Manager Guide

Option Description Required?

SNMP Agent Host IP The IP address of the simple network management protocol Yes
Address (SNMP) agent that collects the network traffic in and out. The
default is the IP address on which you are running Operations
Manager.
SNMP Agent Host The port of the SNMP agent that collects the network traffic in and Yes
Port Number out. The default is 161.
SNMP Agent The community settings of the SNMP agent that collects the Yes
Community network traffic in and out. The default is public.
SNMP Agent The agent’s version of SNMP that collects the network in and out Yes
Version traffic. The SNMP version can be 1 or 2. The default is 1.
Network In Alerting The Network In amount, in bytes, that triggers an alert. If the Yes
Threshold (Bytes) amount of data coming into the network equals or exceeds this
amount, an alert is triggered. The default is 20.

Network In Alerting The number of consecutive periods the Network In Alerting Yes
Sustain Interval Threshold must meet or exceed to trigger an alert. The default is
12. This number multiplied by the Real Time Counter Polling Period
is the total number of seconds the threshold must be maintained.
For example, if this is 12 and the polling period is 5, the Network
In Alerting Threshold must be maintained for 60 seconds before
an alert is triggered.
Network In Alerting The minimum number of consecutive polling periods after the Yes
Minimum Firing Network In alert was triggered before that alert can be triggered
Interval again. The default is 60. This value multiplied by the Real Time
Counter Polling Period must be 300 or more. For example, if this is
60 and with the poling period of 5, a new alert may not be
triggered until 300 seconds after the last one was triggered.
Network Out The network out amount, in bytes, that triggers an alert. If the Yes
Alerting Threshold amount of data going out of the network equals or exceeds this
(Bytes) amount, an alert is triggered. The default is 20.
Network Out The number of consecutive periods the Network Out Alerting Yes
Alerting Sustain Threshold must meet or exceed to trigger an alert. The default is
Interval 12. This number multiplied by the Real Time Counter Polling Period
is the total number of seconds the threshold must be maintained.
For example, if this is 12 and the polling period is 5, the Network
Out Alerting Threshold must be maintained for 60 seconds before
an alert is triggered.
Network Out The minimum number of consecutive polling periods after the Yes
Alerting Minimum Network Out alert was triggered before that alert can be triggered
Firing Interval again. The default is 12. This value multiplied by the Real Time
Counter Polling Period must be 300 or more. For example, if this is
60 and with the poling period of 5, a new alert may not be
triggered until 300 seconds after the last one was triggered.

Network Status alerts

Sends alerts that are based on the speed or status of the network. For example, you can
send an email when the network speed is too slow for a specified time.

© 2017, MicroStrategy Inc. 26

Operations Manager Guide

You can configure the following thresholds and other options for the network status:

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read
Polling Period Manager polls the server every 5 seconds to get the real-time only
information for the alert.
Real Time Counter For MicroStrategy use. Read
Instance only
Alert Email The email addresses the alerts are sent to when the thresholds for No
Recipient this alert are met. Separate multiple addresses with a semicolon
(;).
Destination IP The IP address of the machine this computer attempts to contact Yes
Address to test the network conditions.
Network Latency The network latency time, in milliseconds, between the source and Yes
Alerting Threshold destination machines that triggers an alert. If the network latency
meets or exceeds this time, an alert is triggered. The default is 20.
Network Latency The number of consecutive polling periods the Network Latency Yes
Alerting Sustain Alerting Threshold must meet or exceed to trigger an alert. The
Interval default is 12. This number multiplied by the Real Time Counter
Polling Period is the total number of seconds the alerting threshold
must be maintained. For example, if this is 12 and the polling
period is 5, the threshold must be met for 60 seconds before an
alert is triggered.
Network Latency The minimum number of consecutive polling periods after the Yes
Alerting Minimum Network Latency alert was triggered before that alert can be
Firing Interval triggered again. The default is 60. This value multiplied by the Real
Time Counter Polling Period must be 300 or more. For example, if
this is 60 and the polling period is 5, a new alert may not be
triggered until 300 seconds after the last one was triggered.
Network Packet The amount of packet loss that occurs between the source and Yes
Loss Percentage destination machines that triggers an alert, expressed as a
Alerting Threshold percentage of the total packets sent. If the packet loss percentage
meets or exceeds this amount, an alert is triggered. The default is
20.
Network Packet The number of consecutive polling periods that the Network Yes
Loss Percentage Packet Loss Percentage Alerting Threshold must meet or exceed to
Alerting Sustain trigger an alert. The default is 12. This number multiplied by the
Interval Real Time Counter Polling Period is the total number of seconds
the threshold must be met be exceeded. For example, if this is 12
and the polling period is 5, the threshold must be maintained for
60 seconds before an alert is triggered.
Network Packet The minimum number of consecutive polling periods after the Yes
Loss Percentage Network Packet Loss Percentage alert was triggered before that
Alerting Minimum alert can be triggered again. The default is 60. This value multiplied
Firing Interval by the Real Time Counter Polling Period must be 300 or more. For
example, if this is 60, a new alert may not be triggered until 300
seconds after the last one was triggered.

27 © 2017, MicroStrategy Inc.

 Operations Manager Guide

Page File Usage alert

Sends alerts according to the page file usage percentage. For example, you can send an
email when the page file usage percentage on a server meets or exceeds a specified amount
for a specified time.
You can configure the following thresholds and other options for a server's page file usage:

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read
Polling Period Manager polls the server every 5 seconds to get the real-time only
information for this alert.
Real Time Counter For MicroStrategy use. Read
Instance only
Alert Email The email addresses the alerts are sent to when the threshold for No
Recipient this alert is met. Separate multiple addresses with a semicolon (;).
Page File Usage The page file usage amount that triggers an alert, expressed as a Yes
Percentage Alerting percentage. If the page file usage meets or exceeds this amount,
Threshold an alert is triggered. The default is 20.
Page File Usage The number of consecutive polling periods that the Page File Yes
Percentage Alerting Usage Percentage must meet or exceed to trigger an alert. The
Sustain Interval default is 12. This number multiplied by the Real Time Counter
Polling Period is the total number of seconds the Alerting Threshold
must be maintained. For example, if this is 12 and the polling
period is 5, the threshold must be maintained for 60 seconds
before an alert is triggered.

Page File Usage The minimum number of consecutive polling periods after the Yes
Percentage Alerting Page File Usage Percentage alert was triggered before that alert
Minimum Firing can be triggered again. The default is 60. This value multiplied by
Interval the Real Time Counter Polling Period must be 300 or more. For
example, if this is 60 and the polling period is 5, a new alert may
not be triggered until 300 seconds after the last one was triggered.

Monitoring cache and Intelligence Server

availability with MicroStrategy 3-tier client
alerts
You can configure the three-tier client alerts to monitor for report cache and Intelligence
Server availability:
• Cache Availability alert, page 29
• Intelligence Server Availability alert, page 30

© 2017, MicroStrategy Inc. 28

Operations Manager Guide

Cache Availability alert

Sends alerts about whether one or more report caches in a project are unavailable on an
Intelligence Server. For example, if the cache becomes unavailable for a critical report that
key users must have, you can send an email alert.
You can configure the following alert options for monitoring a report's cache availability on
one or more servers and projects:

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read
Polling Period Manager polls the server every 180 seconds to get the real-time only
information for the alert.
Real Time Counter For MicroStrategy use. Read
Instance only

Alert Email The email addresses the alerts are sent to when the thresholds for No
Recipient this alert are met. Separate multiple addresses with a semicolon
(;).
MicroStrategy The hostname of the MicroStrategy Intelligence Server you want to Yes
Intelligence Server monitor cache availability for. Separate multiple server names with
Name(s) a semicolon. The default is the Intelligence Server for the
environment you are configuring the alert for.
If you specify more than one server here, you must specify the
same number of the following settings:
• User Name
• Password
• Authentication Mode
• Port Number
• MicroStrategy Project Name
• Report ID
User Name(s) The MicroStrategy user name for the Intelligence Server. Separate Yes
multiple user names with a semicolon. If the user name has an
internal space or semicolon (;), enclose the entire value within
double quotes. For example, "John Doe". The default is the
user name for the environment you are configuring the alert for.

29 © 2017, MicroStrategy Inc.

 Operations Manager Guide

Option Description Required?

Password(s) The password of the MicroStrategy user for the Intelligence Server. No
Separate multiple passwords with a semicolon. If a password has
an internal space or semicolon (;), enclose the entire value within
double quotes. For example, "pass word". The default is the
password for the environment you are configuring the alert for.
If a user does not have a password, use a space for any
passwordless account. You must specify the same number of
passwords here as entries in the MicroStrategy Intelligence Server
Name field. For example, if you have three servers and the user for
the middle one does not use a password, specify the passwords as
follows:
password1; ;password2
Authentication The authentication mode used for logging in to the MicroStrategy Yes
Mode(s) Intelligence Server. Separate multiple authentication modes with a
semicolon. The default is the authentication mode for the
environment you are configuring the alert for.
Port Number(s) The port number for the MicroStrategy Intelligence Server. Yes
Separate multiple port numbers with a semicolon. The default is
the port of the Intelligence Server for the environment you are
configuring the alert for.
MicroStrategy The name of the MicroStrategy project storing the report that Yes
Project Name Health Center executes when checking the Cache Availability.
Separate multiple project names with a semicolon. If the project
name has an internal space or semicolon (;), enclose the entire
value within double quotes. For example, "Project Name". If it
has a quotation mark in it, escape it with a backslash (\). For
example, if the project name is The “New” Project, type "The
\"New\" project".
Report ID The object ID of the report that Health Center executes when Yes
checking the Cache Availability. To get the object ID, view the
report’s properties. You can specify one report per server. If you are
configuring this alert for multiple servers, separate the IDs with a
semicolon.
Alerting Minimum The minimum number of consecutive polling periods after the Yes
Firing Interval Cache Availability alert was triggered before the alert can be
triggered again. The default is 2. This value multiplied by the Real
Time Counter Polling Period must be 300 or more. With the polling
period of 180, this must be at least 2, and a new alert may not be
triggered until 360 seconds after the last one was triggered.

Intelligence Server Availability alert

Sends an alert if one or more Intelligence Servers are unavailable. For example, you can
send an email when Intelligence Server is consistently unavailable for a specified time.
You can configure the following options for Intelligence Server availability:

© 2017, MicroStrategy Inc. 30

Operations Manager Guide

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read
Polling Period Manager polls the server every 180 seconds to get the real-time only
information for this alert.
Real Time Counter For MicroStrategy use. Read
Instance only
Alert Email The email address that alerts are sent to when the threshold for No
Recipient this alert is met. Separate multiple addresses with a semicolon (;).
MicroStrategy The hostname of the MicroStrategy Intelligence Server you want to Yes
Intelligence Server monitor for availability. Separate multiple server names with a
Name(s) semicolon. The default is the Intelligence Server for the
environment you are configuring the alert for.
If you specify more than one server here, you must specify the
same number of the following settings:
• User Name
• Password
• Authentication Mode
• Port Number
User Name(s) The MicroStrategy user name for the Intelligence Server. Separate Yes
multiple user names with a semicolon. If the user name has an
internal space or semicolon (;), enclose the entire value within
double quotes. For example, "John Doe". The default is the
user name for the environment you are configuring the alert for.

Password(s) The password of the MicroStrategy user for the Intelligence Server. Yes
Separate multiple passwords with a semicolon. If a password has
an internal space or semicolon (;), enclose the entire value within
double quotes. For example, "pass word". The default is the
password for the environment you are configuring the alert for.
If a user does not have a password, use a space for any
passwordless account. You must specify the same number of
passwords here as entries in the MicroStrategy Intelligence Server
Name field. For example, if you have three servers and the middle
one does not use a password, specify the passwords as follows:
password1; ;password2
Authentication The authentication mode used for logging in to the MicroStrategy Yes
Mode(s) Intelligence Server. Separate multiple authentication modes with a
semicolon. The default is the authentication mode for the
environment you are configuring the alert for.
Port Number(s) The port number for the MicroStrategy Intelligence Server. Yes
Separate multiple port numbers with a semicolon. The default is
the port of the Intelligence Server for the environment you are
configuring the alert for.
Alerting Minimum The minimum number of consecutive polling periods after the last Yes
Firing Interval Intelligence Server Availability alert was triggered before that alert

31 © 2017, MicroStrategy Inc.

 Operations Manager Guide

Option Description Required?

can be triggered again. The default is 2. This value multiplied by

the Real Time Counter Polling Period must be 300 or more. For
example, if this is 2 and the polling period is 180, a new alert may
not be triggered until 360 seconds after the last one was triggered.

Monitoring Web and Mobile Server availability

with MicroStrategy 4-tier client alerts
You can configure the four-tier client alerts to monitor for Web and Mobile Server availability:
• Mobile Server Availability alert, page 32
• Web Server Availability alert

Mobile Server Availability alert

Sends an alert if one or more Mobile Servers become unavailable. For example, you can
send an alert when a Mobile Server is unavailable for a specified time.
You can configure the following options for one or more Mobile Servers' availability alerts:

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read
Polling Period Manager polls the server every 180 seconds to get the real-time only
information for this alert.
Real Time Counter For MicroStrategy use. Read
Instance only
Alert Email The email addresses the alerts are sent to when the threshold for No
Recipient this alert is met. Separate multiple addresses with a semicolon (;).
MicroStrategy Web The URL of the MicroStrategy Mobile application you want to Yes
Application URL(s) monitor. Separate multiple URLs with a semicolon. The default is
http://localhost/microstrategymobile/asp/
If you specify more than one URL here, you must specify the same
number of the following settings:
• MicroStrategy Intelligence Server Name
• User Name
• Password
• Authentication Mode
• Port Number
MicroStrategy The hostname of the MicroStrategy Intelligence Server you want to No

© 2017, MicroStrategy Inc. 32

Operations Manager Guide

Option Description Required?

Intelligence Server monitor for availability. Separate multiple server names with a
Name(s) semicolon. The default is the Intelligence Server for the
environment you are configuring the alert for.
User Name(s) The MicroStrategy user name for the Intelligence Server. Separate Yes
multiple user names with a semicolon. If the user name has an
internal space or semicolon (;), enclose the entire value within
double quotes. For example, "John Doe". The default is the user
name for the environment you are configuring the alert for.
Password(s) The password of the MicroStrategy user for the Intelligence Server. No
Separate multiple passwords with a semicolon. If a password has
an internal space or semicolon (;), enclose the entire value within
double quotes. For example, "pass word". The default is the
password for the environment you are configuring the alert for.
If a user does not have a password, use a space for the
passwordless account. You must specify the same number of
passwords here as entries in the MicroStrategy Intelligence Server
Name field. For example, if you have three servers and the middle
one does not use a password, specify the passwords as follows:
password1; ;password2
Authentication The authentication mode used for logging in to the MicroStrategy Yes
Mode(s) Intelligence Server. Separate multiple authentication modes with a
semicolon. The default is the authentication mode for the
environment you are configuring the alert for.
Port Number(s) The port number for the MicroStrategy Intelligence Server. Separate Yes
multiple port numbers with a semicolon. The default is the port of
the Intelligence Server for the environment you are configuring the
alert for.
Alerting Minimum The minimum number of consecutive polling periods after the last Yes
Firing Interval Report Alerting Time alert was triggered before that alert can be
triggered again. The default is 2. This value multiplied by the Real
Time Counter Polling Period must be 300 or more. For example, if
this interval is 2 and the polling period is 180, a new alert may not
be triggered until 360 minutes after the last one was triggered.

Web Server Availability alert

Sends an alert if a Web server you specify becomes unavailable. For example, you can send
an alert when the Web server is consistently unavailable for a specified time.
You can configure the following options for one or more Web servers' availability:

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read
Polling Period Manager polls the server every 180 seconds to get the real-time only
information for the alert.

33 © 2017, MicroStrategy Inc.

 Operations Manager Guide

Option Description Required?

Real Time Counter For MicroStrategy use. Read

Instance only
Alert Email The email addresses the alerts are sent to when the threshold for No
Recipient this alert is met. Separate multiple addresses with a semicolon (;).
MicroStrategy Web The URL of the MicroStrategy Web application you want to monitor. Yes
Application URL(s) Separate multiple URLs with a semicolon. The default is
http://localhost/MicroStrategy/asp/
If you specify more than one URL here, you must specify the same
number of the following settings:
• MicroStrategy Intelligence Server Name
• User Name
• Password
• Authentication Mode
• Port Number
In addition, if you specify a MicroStrategy project name or report ID,
or both, for one server, you must specify a project name or report
ID, or both, for all servers.
MicroStrategy The hostname of the MicroStrategy Intelligence Server you want to No
Intelligence Server monitor for availability. Separate multiple server names with a
Name(s) semicolon. The default is the Intelligence Server for the
environment you are configuring the alert for.

User Name(s) The MicroStrategy user name for the Intelligence Server. Separate Yes
multiple user names with a semicolon. If the user name has an
internal space or semicolon (;), enclose the entire value within
double quotes. For example, "John Doe". The default is the
user name for the environment you are configuring the alert for.
Password(s) The password of the MicroStrategy user for the Intelligence Server. No
Separate multiple passwords with a semicolon. If a password has
an internal space or semicolon (;), enclose the entire value within
double quotes. For example, "pass word". The default is the
password for the environment you are configuring the alert for.
If a user does not have a password, use a space for the
passwordless account. You must specify the same number of
passwords here as entries in the MicroStrategy Intelligence Server
Name field. For example, if you have three servers and the middle
one does not use a password, specify the passwords as follows:
password1; ;password2
Authentication The authentication mode used for logging in to the MicroStrategy Yes
Mode(s) Intelligence Server. Separate multiple authentication modes with a
semicolon. The default is the authentication mode for the
environment you are configuring the alert for.
Port Number(s) The port number for the MicroStrategy Intelligence Server. Yes
Separate multiple port numbers with a semicolon. The default is

© 2017, MicroStrategy Inc. 34

Operations Manager Guide

Option Description Required?

the port of the Intelligence Server for the environment you are
configuring the alert for.
Alerting Minimum The minimum number of consecutive polling periods after the last Yes
Firing Interval Report Alerting Time alert was triggered before that alert can be
triggered again. The default is 2. This value multiplied by the Real
Time Counter Polling Period must be 300 or more. For example, if
this is 2 and the polling period is 180, a new alert may not be
triggered until 360 seconds after the last one was triggered.

Monitoring Intelligence Server performance

with MicroStrategy Intelligence Server alerts
You can configure alerts to monitor an Intelligence Server's performance, such as CPU
usage, how long jobs take to complete, whether certain words or phrases appear in a log file,
and so on. These alerts and options include:
• Intelligence Server (IServer) Performance Counter alerts
• Intelligence Server (IServer) Log Parser alert
• Job Duration alert
• Report Throughput Counter alerts
• Memory Depletion alert

Intelligence Server (IServer) Performance Counter

alerts
Sends alerts about the Intelligence Server performance. For example, you can send an alert
when Intelligence Server CPU usage meets or exceeds a specified percentage for a
specified time.
You can configure the following options about the performance on an Intelligence Server:

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read
Polling Period Manager polls the server every 5 seconds to get the real-time only
information for these alerts.
Real Time Counter For MicroStrategy use. Read
Instance only
Alert Email The email addresses the alerts are sent to when the thresholds for No
Recipient this alert are met. Separate multiple addresses with a semicolon
(;).

35 © 2017, MicroStrategy Inc.

 Operations Manager Guide

Option Description Required?

Port Number The port number of the Intelligence Server. The default is 34952. Yes
CPU Percentage The CPU usage percent that triggers an alert. If the CPU usage Yes
Alerting Threshold meets or exceeds this amount, an alert is triggered. The default is
(%) 95.
CPU Percentage The number of consecutive polling periods that the CPU Yes
Alerting Sustain Percentage Alerting Threshold must meet or exceed to trigger an
Interval alert. This number multiplied by the Real Time Counter Polling
Period is the total number of seconds the threshold must be
maintained. For example, if the polling period is 5 and this is 20,
the threshold must be maintained for 100 seconds before an alert
is triggered. The default is 24.
CPU Percentage The minimum number of consecutive polling periods before the Yes
Alerting Minimum next CPU percentage alert can be triggered. The default is 60. This
Firing Interval value multiplied by the Real Time Counter Polling Period must be
300 or more. For example, with the polling period of 5, this interval
must be at least 60.
Extended CPU The extended CPU usage percent that triggers an alert. If the Yes
Percentage Alerting extended CPU usage meets or exceeds this amount, an alert is
Threshold (%) triggered. The default is 95.
Extended CPU The number of consecutive polling periods that the Extended CPU Yes
Percentage Alerting Percentage Alerting Threshold must meet or exceed to trigger an
Sustain Interval alert. The default is 24. This number multiplied by the Real Time
Counter Polling Period is the total number of seconds the threshold
must maintain. For example, with the polling period of 5 and this
interval is 20, the threshold must meet or exceed for 100 seconds
before an alert is triggered.
Extended CPU The minimum number of consecutive polling periods before the Yes
Percentage Alerting next extended CPU percentage alert can be triggered. The default
Minimum Firing is 60. This value multiplied by the Real Time Counter Polling Period
Interval must be 300 or more. For example, with the polling period of 5,
this interval must be at least 60.
Memory Usage The amount of memory usage for an alert to be triggered. If the Yes
Alerting Threshold memory usage meets or exceeds this amount, an alert is triggered.
(MB) The default is 0.
Memory Usage The number of consecutive polling periods that the Memory Usage Yes
Alerting Sustain Alerting Threshold must meet or exceed to trigger an alert. The
Interval default is 12. This number multiplied by the Real Time Counter
Polling Period is the total number of seconds the threshold must
be maintained. For example, if the polling period is 5 and this is
20, the threshold must be maintained for 100 seconds before an
alert is triggered.
Memory Usage The minimum number of consecutive polling periods before the Yes
Alerting Minimum next memory usage alert can be triggered. The default is 60. This
Firing Interval value multiplied by the Real Time Counter Polling Period must be
300 or more. For example, if the Polling Period is 5, the Minimum
Firing Interval must be at least 60.

© 2017, MicroStrategy Inc. 36

Operations Manager Guide

Option Description Required?

Extended Memory The amount of extended memory usage that triggers an alert. If the Yes
Usage Alerting extended memory usage meets or exceeds this amount, an alert is
Threshold (MB) triggered. The default is 0.
Extended Memory The number of consecutive polling periods that the Extended Yes
Usage Alerting Memory Usage Alerting Threshold must meet or exceed to trigger
Sustain Interval an alert. The default is 12. This number multiplied by the Real Time
Counter Polling Period is the total number of seconds the threshold
must be met. For example, if the polling period is 5 and this is 20,
the threshold must be maintained for 100 seconds before an alert
is triggered.
Extended Memory The minimum number of consecutive polling periods before the Yes
Usage Alerting next extended memory usage alert can be triggered. The default is
Minimum Firing 60. This value multiplied by the Real Time Counter Polling Period
Interval must be 300 or more. For example, if the polling period is 5, this
firing interval must be at least 60.

Intelligence Server (IServer) Log Parser alert

Sends an alert about the contents of the DSSErrors.log file. The DSSErrors.log file is
the primary file in which MicroStrategy records information about its operation. For example,
you could search for 0x8000399A (which finds this type of error message, related to History
List messages, in the log file: 2014-02-14 14:14:26.183+02:00
MsiWorkingSet::ReturnRptInstance: AddMsg() failed, return error
0x8000399A) and if that text occurs in the log file, send an email alert.
You can configure the following options for the log file alert on an Intelligence Server:

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read only
Polling Period Manager polls the server every 60 seconds to get the real-time
information for this alert.
Real Time Counter For MicroStrategy use. Read only
Instance
Alert Email The email addresses the alerts are sent to when the strings for No
Recipient this alert are found. Separate multiple addresses with a semicolon
(;).
Log Entry The string or strings to search for in all fields in the DSSErrors.log Yes
file. Separate multiple strings with a vertical bar (|) which serves
as an OR in this boolean search. Any of the terms found triggers an
alert. No quotation marks are needed.

Job Duration alert

Sends alerts about job duration on the Intelligence Server. For example, you can send an
email when any job duration exceeds a specified time.

37 © 2017, MicroStrategy Inc.

 Operations Manager Guide

You can configure the following options for how long jobs are taking on an Intelligence
Server:

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read only
Polling Period Manager polls the server every 30 seconds to get the real-time
information for this alert.
Real Time Counter For MicroStrategy use. Read only
Instance
Alert Email The email addresses the alerts are sent to when the threshold for No
Recipient this alert is met. Separate multiple addresses with a semicolon (;).
Alerting Threshold The job duration, in seconds, for an alert to be triggered. If a job Yes
takes this long or longer to execute, an alert is triggered.
User Name The MicroStrategy user name for the Intelligence Server. The Yes
default is the user name for the environment you are configuring
the alert for.
Password The password of the MicroStrategy user for the Intelligence Server. No
The default is the password for the environment you are
configuring the alert for.
Authentication The authentication mode for the MicroStrategy Intelligence Server. Yes
Mode The default is the authentication mode for the environment you
are configuring the alert for.
Port Number The port number for the MicroStrategy Intelligence Server. The Yes
default is the port number for the environment you are configuring
the alert for.

Report Throughput Counter alerts

Sends alerts about the report processing speed on the Intelligence Server, such as how long
it is in a queue, and if reports are being submitted at the same rate they are being completed.
For example, you can send an email when the averaged report queue waiting time exceeds
a specified time.
You can configure the following options for report throughput on an Intelligence Server:

Option Description Required?

Real Time Counter The number of seconds between polling times. Operations Read
Polling Period Manager polls the server every 5 seconds to get the real-time only
information for these alerts.
Real Time Counter For MicroStrategy use. Read
Instance only
Alert Email The email addresses the alerts are sent to when the thresholds for No
Recipient this alert are met. Separate multiple addresses with a semicolon
(;).

© 2017, MicroStrategy Inc. 38

Operations Manager Guide

Option Description Required?

Alerting Error The reporting error percentage that triggers an alert. If the Yes
Percentage percentage of report requests that result in errors meets or
Threshold exceeds this percentage, an alert is triggered. The default is 10.
Alerting High Queue The average queue time, in seconds, that triggers an alert. If the Yes
Time Threshold average queue time meets or exceeds this time, an alert is
triggered. The default is 5.
Alerting High The average report response time, in seconds, that triggers an Yes
Response Time alert. If the average report response time meets or exceeds this
Threshold amount, an alert is triggered. The default is 60.
Alerting Throughput The ratio of the report submission rate per minute to the report Yes
Threshold completion rate per minute. When the ratio meets or exceeds the
threshold, an alert is triggered. The default is 2.
Alerting Minimum The minimum number of consecutive polling periods before the Yes
Firing Interval next alert can be triggered. The default is 60. This value multiplied
by the Real Time Counter Polling Period must be 300 or more. For
example, if this is 60 and the polling period is 5, a new alert may
not be triggered until 300 seconds after the last one was triggered.
User Name The MicroStrategy user name for the Intelligence Server. The Yes
default is the user name for the environment you are configuring
the alert for.
Password The password of the MicroStrategy user for the Intelligence Server. No
The default is the password for the environment you are
configuring the alert for.

Authentication The authentication mode for the MicroStrategy Intelligence Server. Yes
Mode The default is the authentication mode for the environment you
are configuring the alert for.
Port Number The port number for the MicroStrategy Intelligence Server. The Yes
default is the port number for the environment you are configuring
the alert for.

Memory Depletion alert

Creates an alert if the Intelligence Server log file includes memory depletion errors.
You can configure the following options for memory depletion on the Intelligence Server:

Option Description Required?

User Name The MicroStrategy user name for the Intelligence Server. The Yes
default is the user name for the environment you are configuring
the alert for.
Password The password of the MicroStrategy user for the Intelligence Server. No
The default is the password for the environment you are
configuring the alert for.

39 © 2017, MicroStrategy Inc.

 Operations Manager Guide

Option Description Required?

Authentication The authentication mode for the MicroStrategy Intelligence Server. Yes
Mode The default is the authentication mode for the environment you
are configuring the alert for.
Port Number The port number for the MicroStrategy Intelligence Server. The Yes
default is the port number for the environment you are configuring
the alert for.
Log file reading How long, in milliseconds, the Health Center attempts to read the Yes
retry period DSSErrors.log file. If the Health Center is unable to read the file, an
alert is triggered. The default is 60000.

Monitoring Enterprise Manager with

MicroStrategy Enterprise Manager alerts
ETL Service Status and Data Load Failure alert
Monitors the Enterprise Manager data load process. If the data load takes longer than the
specified time, an alert appears in the Alert Inbox.

Option Description Required?

Waiting Period How many hours the Enterprise Manager data load process may Yes
(hours) run before it is considered a failed process. If the data load
process is still running and, according to the data load’s begin
time, the process has already run longer than this limit, the
process is considered incomplete and failed. An alert is triggered.
The default and recommended value is 5.

Monitoring Mobile ASPx with MicroStrategy

Mobile ASPx alerts
JVM Maximum Heap Size alert
Checks that the Java Virtual Machine has enough memory available in the virtual directories
for the Mobile Server, Operations Manager, and MicroStrategy Web. You can use these
alerts if your Mobile Server is used with Active Server Pages (ASP).
You can configure the following alert memory options for the Mobile Server used with ASP:

© 2017, MicroStrategy Inc. 40

Operations Manager Guide

Option Description Required?

Filter by last The number of previous days to analyze log files for. The default is Yes
modified date 1.
Collect logs from Whether to monitor out-of-memory errors from the MicroStrategy No
additional IIS virtual Web and Operations Manager virtual directories in addition to the
directories MicroStrategy Mobile virtual directory. The default is No. Typing Yes
starts monitoring for out-of-memory errors from following virtual
directories, in addition to the default MicroStrategy Web
deployment (C:\Program Files
(x86)\MicroStrategy\Web ASPx): Application:
/MicroStrategyOM
Path: C:\Program Files
(x86)\MicroStrategy\Operations Manager ASPx

MicroStrategy The URL to your MicroStrategy Mobile application. Yes

Mobile ASPx URL

MicroStrategy The port for your MicroStrategy Mobile application. The default is 0. Yes
Mobile ASP Port

Monitoring Mobile JSP with MicroStrategy

Mobile JSP alerts
JVM Maximum Heap Size alert
Checks that the Mobile Server machine's Java Virtual Machine maximum heap size, as
specified in the application server configuration file, is not exceeded. You can use this alert if
your Mobile Server is used with Java Server Pages (JSP).
You can configure the following alert memory options for the Mobile Server used with JSP:

Option Description Required?

Application Server The name and version of the application server for MicroStrategy No
Type Mobile JSP.
Application Server The complete path to the folder containing the start-up script for Yes
Configuration Path the application server.
MicroStrategy The path where the MicroStrategy Mobile JSP application is Yes
Mobile JSP deployed.
Deployment Path
Filter by last The number of previous days to analyze log files for. The default is Yes
modified date 1.
Application Server You can change settings, such as the JVM maximum heap size, for No
Configuration File the application server by overriding the default configuration file to

41 © 2017, MicroStrategy Inc.

 Operations Manager Guide

Option Description Required?

Name use. To do this, type the name of the configuration file to use as an
override. For example, for a JOSS application server, you may type
run.conf. For Tomcat on UNIX or Linux, you may type
catalina.sh.

MicroStrategy The URL to your MicroStrategy Mobile application. Yes

Mobile JSP URL
MicroStrategy The port for your MicroStrategy Mobile application. The default is 0. Yes
Mobile JSP Port

Monitoring Web JSP with MicroStrategy Web

JSP alerts
Available Memory for JVM setting alert
Verifies that the machine hosting the MicroStrategy Web server has enough memory
available to start the Web server. The alert checks whether the machine has enough
physical memory to support the JVM Max Heap Size as specified in the application server
configuration file. You can use this alert if Web Universal is used with Java Server Pages
(JSP).
You can configure the following options for the JVM alert:

Option Description Required?

Application Server The name and version of the application server for MicroStrategy No
Type Mobile JSP.
Application Server The complete path to the folder containing the start-up script for Yes
Configuration Path the application server.
Application Server The complete path to the root folder for the MicroStrategy Web JSP Yes
Root Folder Path application server.
Application Server You can change settings, such as the JVM maximum heap size, for No
Configuration File the application server by overriding the default configuration file to
Name use. To do this, type the name of the configuration file to use as an
override. For example, for a JOSS application server, you may type
run.conf. For Tomcat on UNIX or Linux, you may type
catalina.sh.

© 2017, MicroStrategy Inc. 42

 4
MONITORING YOUR
MICROSTRATEGY SYSTEM
You can monitor alerts, usage information, and system activity for each environment.
• Monitor alerts for an environment. See Viewing alerts for an environment, page 43.
• Monitor health and usage information for an environment. See Viewing the overall
health of an environment, page 44.
• Monitor the activity of systems in an environment. See Monitoring environment activity,
page 48.
You can view the high-level information about your environment. For details, see Viewing
high-level information about your environments, page 3.

Viewing alerts for an environment

You can view all alerts from a single screen for a selected environment. To view the alerts,
depending on which page you are on, perform one of the following:
• On the Landing page, click the name of environment you want to see alerts for. Alerts
are displayed by default.

• On the Environment Details page, on the left, click the Alerts icon .

The Alerts Inbox opens to display a list of alerts on the left. To view details about all
occurrences of an alert, click it. The Alert Details display on the right.
You can sort and filter the alerts, mark an alert as read or unread, and delete an alert:
• Filtering and sorting alerts, page 44
• Marking an alert as read or unread, page 44
• Deleting an alert, page 44

© 2017, MicroStrategy Inc. 43

Operations Manager Guide

Filtering and sorting alerts

You can filter alerts to show alerts for a server or a type of alert, or both. You can also sort the
alerts by date or machine.

To filter alerts

1 From the Server Name drop-down list, select the server you want to view alerts for.
2 From the Alert Name drop-down list, select the type of alerts you want to view.

To sort alerts

1 From the Arrange by drop-down list, select one of the following:

• Date: Sorts alerts by date, from newest to oldest.
• Machine Name: Sorts alerts by machine name.

Marking an alert as read or unread

You can mark an unread alert as read, or mark a read alert as unread. Unread alerts display
with a green dot.
To mark an alert as read or unread, in the Alerts Inbox, select the alert to mark, and then
from the Actions drop-down list, select Mark as Read or Mark as Unread.

Deleting an alert
You can delete alerts that you no longer need.
To delete an alert, from the Alert Inbox, select the alert you want to delete, and from the
Actions drop-down list, select Delete.

Viewing the overall health of an environment

You can view the health information such as resource usage, memory use, and job
completion rate for a selected server in an environment. You can see recent trends in the
health because the information is displayed as a line graph for the past five minutes.

To view health information for a server

1 Depending on which page you are on, perform one of the following:
▫ From the Landing page, right-click the environment you want to see the health
information for, and then click Heartbeat. The Heartbeat monitor page opens.

44 © 2017, MicroStrategy Inc.

 Operations Manager Guide

▫ From the Environment Details page, on the left, click the Heartbeat icon . The
Heartbeat monitor page opens.
2 From the drop-down list, select the server you want to view the health information for.
3 On the left, choose the information to view, described below. When you click an option, a
line graph displays to the right.
▫ Total CPU: You can view the total CPU, kernel CPU, and user CPU usage in the
server. This is the default when the page opens. For a sample view of the CPU
heartbeat monitor, see Viewing CPU usage, page 45.
▫ Memory: You can view the server’s total percentage of available memory being
used. For a sample view of the Memory heartbeat monitor, see Viewing memory
usage, page 46.
▫ Memory I/O: You can view the number of pages per second swapped in and out
of memory. For a sample view of the Memory I/O heartbeat monitor, see Viewing
memory I/O usage, page 46.
▫ Logical Disk I/O Bytes: You can view the total kilobytes of disk read and write
operations per second. For a sample view of the Logical Disk I/O Bytes heartbeat
monitor, see Viewing logical disk I/O usage, page 46.
▫ Page File: You can view the percentage of the server’s available virtual memory
being used. For a sample view of the Page File heartbeat monitor, see Viewing
page file usage, page 47.
▫ Job Completion Rate: You can view the average number of jobs per minute that
complete processing on the Intelligence Server. For a sample view of the Job
Completion Rate heartbeat monitor, see Viewing the job completion rate, page 47.
4 You can view details for a point in time by pointing to an area of the graph.

Viewing CPU usage

You can see the CPU usage for a server, as shown in the example below. This is displayed
on the CPU heartbeat monitor.

You can view the total CPU, kernel CPU, and user CPU usage amounts for a point in time
by pointing to the graph.

© 2017, MicroStrategy Inc. 45

Operations Manager Guide

Viewing memory usage

You can view the memory usage for a server, as shown in the example below. This is
displayed on the Memory heartbeat monitor.

You can view the memory usage percentage for a point in time by pointing to the graph.

Viewing memory I/O usage

You can view the number of pages per second swapped in and out of memory on a server,
as shown in the example below. This is displayed on the Memory I/O heartbeat monitor.

You can view the number of pages swapped at a point in time by pointing to the graph.

Viewing logical disk I/O usage

You can view the total kilobytes of disk read and write operations per second on a server, as
shown in the example below. This is displayed on the Logical Disk I/O Bytes heartbeat
monitor.

46 © 2017, MicroStrategy Inc.

 Operations Manager Guide

You can view the detailed total kilobytes in and out per second for a point in time by pointing
to the graph.

Viewing page file usage

You can view the percentage of available virtual memory used for a server as shown in the
example below. This is displayed on the Page File heartbeat monitor.

You can view the detailed percentage of available virtual memory for a point in time by
pointing to the graph.

Viewing the job completion rate

You can view the number of jobs per minute that complete processing on the Intelligence
Server, as shown in the example below. These are displayed on the Job Completion Rate
heartbeat monitor.

© 2017, MicroStrategy Inc. 47

Operations Manager Guide

You can view the detailed number of jobs completed for a point in time by pointing to the
graph.
This monitor is not available for Web or Mobile servers because job processing does not take
place on those servers.

Monitoring environment activity

You can track activity of your MicroStrategy environments in real time and manage them:
• View details about all currently running jobs and cancel selected jobs.
• View all open user sessions and disconnect selected user sessions.
• View cache usage and manage selected caches.
• View open database connections and disconnect selected ones.
• View projects' quick search index status.

To monitor environment activity

1 Depending on which page you are on, perform one of the following:
▫ From the Landing page, right-click the environment you want to see activity for, then
click Monitor.

▫ From the Environment Details page, on the left, click the Monitors icon .

2 From the drop-down list, select the server you want to view the activity for.
3 On the left, choose the information to view, described below. When you click an option,
you can view the information on the right.
▫ Jobs (executing): View the total number of jobs executing on the server, cancel a
selected job, and view details about a job such as who submitted it, how long it has
been running, and so on. For details, see Monitoring and managing currently
running jobs, page 49.

48 © 2017, MicroStrategy Inc.

 Operations Manager Guide

▫ Users (open sessions): View the total number of open user sessions on the
server and cancel a selected user session. For details, see Monitoring and
managing open user sessions, page 51.
▫ Cache Usage: You can view a heat map of the total amount of cache usage on the
server, and you manage a selected cache by deleting it, loading it, unloading it, and
so on. For details, see Monitoring and managing an environment's cache usage,
page 52.
▫ Active Database Instances: View the total number of active database
instances open on the server, and you can disconnect a selected database instance.
For details, see Monitoring and managing open database connections, page 57.
▫ Quick Search Index Creation Status: View the status of the quick search
index creation on the server. For details, see Monitoring the quick search index
status, page 58.

Monitoring and managing currently running jobs

You can monitor the jobs being run on a selected server, and you can view details for a job or
cancel it.
In the top area, you can view the following summary information:
• Completed Reports: Displays the total number of reports that have completed
processing since the server was started.
• Total Report Requests: Displays the total number of report requests that have been
initiated since the server was started.
In the middle area, you can view a line graph of the job submission and job completion rates
for the past five minutes. An example is below.

In the bottom area, you can view a table with all the jobs that are in process on the server.
With options under the Actions column, you can cancel a job or view details for it. For steps,
see Viewing job details, page 50.
• Description: Current state of the job execution.
• Project: The name of the project the job was submitted from.
• Owner: The name of the user who submitted the job.
• Job ID: Numeric identifier assigned to the job.

© 2017, MicroStrategy Inc. 49

Operations Manager Guide

• Start Time: The date and time when the job first entered the server.
• Status: Displays one of the following statuses:
▫ Canceled: The job is being canceled.
▫ Executing: The job is executing.
▫ Ready to execute: The job is in the queue waiting to begin execution.
▫ Error: An error was encountered while processing the job.
▫ Waiting for prompt: The job is held until the user answers a prompt. A prompt
is a question the system presents to a user when a report is executed.
▫ Waiting for children: The job is for a document and is waiting for its component
reports to complete. A document is a container for formatting, displaying, and
distributing multiple reports on the same page, or at the same time within a project.
• Job Duration (sec): How long, in seconds, the job has been executing.

• Actions: You can cancel a job (click the Cancel Job icon ) or view the job details
(click the View Details icon ) for it:

Canceling a job
You can cancel a job on the server by clicking the Cancel Job icon on the row of the job
to cancel, and then clicking Yes.

Viewing job details

You can view a job's details such as its identifier, status, who submitted it, how long it has
been running, and so on. To see the details for an executing job, select a job and click the
View Details icon . You can view the following:

• Job ID: Numeric identifier assigned to the job.

• Creation Time: The date and time when the job first entered the server.
• Description: Current state of the job execution.
• Status: Displays one of the following statuses:
▫ Canceled: The job is being canceled.
▫ Executing: The job is executing.
▫ Ready to execute: The job is in the queue waiting to begin execution.
▫ Error: An error was encountered while processing the job.
▫ Waiting for prompt: The job is on hold until the user answers a prompt. A
prompt is a question the system presents to a user when a report is executed.
• Client Machine: The client machine the job was initiated from.

50 © 2017, MicroStrategy Inc.

 Operations Manager Guide

• Submitted by User: The name of the user who submitted the job.
• Priority: The Intelligence Server priority of the job: low, medium, or high.
• Project ID: ID of the project the job was submitted from.
• Project Name: Name of the project the job was submitted from.
• Duration: How long, in seconds, the job has been executing.
• Filter: The filter used by the job. A filter screens data in your data source to determine
whether the data should be included in or excluded from the calculations of the report
results.
• Template: The template used by the job. A report template (usually simply called a
template) is an object that defines the underlying structure of the report.
• Number of Tasks: The total number of tasks for the job.
• Number of Finished Tasks: The number of tasks that have already completed for
the job.
• SQL: The SQL used by this job.

Monitoring and managing open user sessions

When a user logs in to MicroStrategy, a user session is established. You can view a
summary of the types of sessions (as shown in the example below), the list of all open
sessions, and details about a selected session. You can also disconnect a session.

You can view summary information next to the graph:

• Available Sessions: The total number of available sessions. You can set this number
in the Intelligence Server Configuration Editor. For more information, see the System
Administration Guide.
• Open Sessions: The total number of open sessions.
• Web: The total number of open sessions on MicroStrategy Web.
• Mobile: The total number of open sessions on MicroStrategy Mobile.

© 2017, MicroStrategy Inc. 51

Operations Manager Guide

• Other: The total number of open sessions for other MicroStrategy clients. For example,
these can be Command Manager sessions, Health Center sessions, and so on.
Below the summary, you can view the following details for each open user session:
• User: The name of the MicroStrategy user who owns the session.
• Project: The project the user connection is connected to. If the user connection is not to
a project, <Server> is displayed.
• Client Machine: The machine name or IP address of the machine the session
originated from.
• Time Connected: The date and time the user session was opened.
• Client Type: The type of session, for example, Command Manager, MicroStrategy
Developer, Health Center, and so on.
• First Job Time: The date and time of the first job initiated by the session.
• Last Job Time: The date and time of the most recent job initiated by the session.
• Job Count: The total number of jobs initiated by the session.
• Actions: To disconnect the user session, click the Disconnect icon .

Monitoring and managing an environment's cache

usage
You can view high-level information about report, document, and Intelligent Cube caches on
a selected server, such as how much they are being used and how much size on disk they
are taking up. You can view details about individual report caches. And you can manage
caches by deleting, loading, unloading, and so on.
At the top of the Cache monitor, you can view the following summary information:
• Cache Hits
▫ Reports: The total number of times report caches have been hit since the
Intelligence Server was started. This number includes all projects on the server.
▫ Documents: The total number of times document caches have been hit since the
Intelligence Server was started. This number includes all projects on the server.
• Cache Size on Disk
▫ Report: The total size of all report caches on disk.
▫ Document: The total size of all document caches on disk.
▫ Intelligence Cube: The total size of all Intelligent Cube caches on disk.
Under the summary information, you can view a heat map of the cache information for the
selected project, as shown in the example below:

52 © 2017, MicroStrategy Inc.

 Operations Manager Guide

Understanding the heat map display of the cache information:

• The larger a cache is on the server, the larger it is in the heat map.
• Caches display from left to right in descending size order.
• Caches with the most hits display as orange; caches with the fewest hits display as blue.
• If all caches in the display have the same number of hits, all caches display as blue.
• Caches with hits between the most and the least display as dark orange, gray, or dark
blue.
• When you point to a cache in the heat map, you can view these details in a tooltip:
▫ Cache Name: The name of the cache.
▫ Hit Count: The number of times the cache has been hit since it was loaded to disk.
▫ Cache Size: The size of the cache in kilobytes.
You can filter the types of caches to display in the heat map:
• Select Project: Click to select the project to view cache information for.
• Select Cache Type: Click to select what type of caches to view: Report, Document, or
Intelligent Cube
• Sort Cache By: Works with the Caches Displayed field to limit which caches display in
the heat map. Select one of the following:
▫ All: Displays all caches, regardless of the number in the Caches Displayed field.
▫ Largest Cache: Displays the caches with the largest cache size, limited by the
number in the Caches Displayed field. For example, if you set the Caches Displayed
field to 5, selecting this option changes the heat map to display the five largest
caches.
▫ Smallest Cache: Displays the caches with the smallest cache size, limited by the
number in the Caches Displayed field. For example, if you set the Caches Displayed
field to 7, selecting this option changes the heat map to display the seven smallest
caches.

© 2017, MicroStrategy Inc. 53

Operations Manager Guide

▫ Highest Hit Count: Displays the caches with the most hits, limited by the number
in the Caches Displayed field. For example, if you set the Caches Displayed field to
10, selecting this option changes the heat map to display the 10 caches with the
most hits.
▫ Lowest Hit Count: Displays the caches with the fewest hits, limited by the
number in the Caches Displayed field. For example, if you set the Caches Displayed
field to 3, selecting this option changes the heat map to display the three caches with
the fewest hits.
• Caches Displayed: Type a number to limit the number of caches displayed in the heat
map, in combination with the option you selected for the Sort Cache By option.
Below the heat map, you can view a table with the following information about each cache:
• Cache Name: The name of the cache.
• Size (KB): The size of the cache, in kilobytes.
• Type: One of the following types of cache:
▫ Matching: A cache containing the report results
▫ History: A cache containing information about History List messages relating to
this report.
▫ Matching-History: A matching cache that is referenced by at least one History
List message.
▫ XML: A cache containing the report results and structure, for use by MicroStrategy
Web.
• Status: The status of the cache, which can be any of the following:
▫ R: Ready. The cache is ready to be used.
▫ P: Processed. The cache is being updated.
▫ I: Invalid. The cache has been invalidated either manually or by a change to one of
the objects used in the cached report. It can no longer be used and will be deleted
according to the Cache lookup cleanup frequency specified in the Server Definition
(advanced) category of the Intelligence Server Configuration Editor.
▫ E: Expired. The cache has passed the time limit specified in the Cache Duration in
the Result Caches (maintenance) category of the Project Configuration Editor. It
can no longer be used and will be deleted according to the Cache lookup cleanup
frequency specified in the Server Definition (advanced) category of the Intelligence
Server Configuration Editor.
▫ L: Loaded. The cache is loaded in Intelligence Server memory.
▫ U: Updated. The information in the cache is up to date.
▫ D: Dirty. The cache has been updated in Intelligence Server memory since it was
saved to disk. Caches are saved to disk according to the Backup frequency
specified in the Server Definition (advanced) category of the Intelligence Server
Configuration Editor.

54 © 2017, MicroStrategy Inc.

 Operations Manager Guide

▫ F: Filed. The cache has been created on disk.

• Last Hit: The date and time when the cache was last used, according to the
Intelligence Server machine time.
• Hit Count: The number of times the cache has been used.
• Actions: You can perform the following actions on a cache (see Managing caches,
page 57):

▫ Invalidate Cache: Invalidate the selected cache.

▫ Delete Cache: Delete the selected cache from the project and from the disk.

▫ More Cache Options: Click for a drop-down list with the following options:
— Load: Load the selected cache into memory.
— Unload: Unload the selected cache from memory.
— Details: Select to view additional details about the cache. For descriptions of
the details you can view about a cache, see Viewing cache details, page 55.

Viewing cache details

You can view additional details about any cache in the list, such as its status, size, type, who
created it, and so on.

To view cache details

1 In the Cache monitor, click the More Actions icon in the Actions column for the
cache. A list of options opens.
2 Click Details.... The Cache Details dialog box opens.
When you select to view Cache Details for a cache, you can view the following information:
• Cache Name: The name of the cache.
• Cache ID: The unique 32-digit ID for the cache.
• Report ID: The unique object ID of the report that uses the cache.
• Folder: The folder where the report resides.
• Cache Size (KB): The size of the cache, in kilobytes.
• Status: The status of the cache, as follows:
▫ R: Ready. The cache is ready to be used.
▫ P: Processed. The cache is being updated.
▫ I: Invalid. The cache has been invalidated either manually or by a change to one of
the objects used in the cached report. It will no longer be used and will be deleted

© 2017, MicroStrategy Inc. 55

Operations Manager Guide

according to the Cache lookup cleanup frequency specified in the Server Definition
(advanced) category of the Intelligence Server Configuration Editor.
▫ E: Expired. The cache has passed the time limit specified in the Cache Duration in
the Result Caches (maintenance) category of the Project Configuration Editor. It will
no longer be used and will be deleted according to the Cache lookup cleanup
frequency specified in the Server Definition (advanced) category of the Intelligence
Server Configuration Editor.
▫ L: Loaded. The cache is loaded in Intelligence Server memory.
▫ U: Updated. The information in the cache is up to date.
▫ D: Dirty. The cache has been updated in Intelligence Server memory since it was
saved to disk. Caches are saved to disk according to the Backup frequency
specified in the Server Definition (advanced) category of the Intelligence Server
Configuration Editor.
▫ F: Filed. The cache has been created on disk.
• Cache Type: One of the following types of cache:
▫ Matching: A cache containing the report results.
▫ History: A cache containing information about History List messages relating to
this report.
▫ Matching-History: A matching cache that is referenced by at least one History
List message.
▫ XML: A cache containing the report results and structure, for use by MicroStrategy
Web.
• Hit Count: Number of times the cache has been used.
• Waiting List: The number of reports that are waiting to use this cache.
• Last Hit Time: The date and time when the cache was last used, according to
Intelligence Server machine time.
• Creator: The MicroStrategy user who created the cache.
• Creation Time: Date and time when the cache was created, according to the
Intelligence Server machine time.
• Expiration: The date and time when the cache is set to expire.
• Last Updated Time: The date and time when the cache was last updated.
• Last Load Time: The date and time when the cache was last loaded.
• Prompt Answers: The answers to any prompts used in the report. This information is
available if the Record prompt answers for cache monitoring check box is selected in the
Result Caches (Creation) category of the Project Configuration Editor.
• Database Connection: The database connection used to create the cache. This
information is available if the Create caches per database login check box is selected in
the Result Caches (Creation) category of the Project Configuration Editor.

56 © 2017, MicroStrategy Inc.

 Operations Manager Guide

• Database Login: The user name for the database connection used to create the
cache.
• Cache File Name: Location and file name for this cache on the disk.
• Security Filter ID: ID of the security filter applied to the user who created the cache.
• Language: The language used in the cache.

Managing caches
You can perform the following actions on a cache:
• Invalidate a cache. You can invalidate a cache to keep users from running reports that
are based on the outdated cache data. To do this, click the Invalidate icon in the
Actions column for the cache you want to invalidate, and then click Yes to confirm.
• Delete a cache. You can delete a cache if you want to remove it from the system before it
would automatically be deleted. To do this, click the Delete icon in the Actions
column for the cache you want to delete, then click Yes to confirm.
• Load a cache into memory. If a cache has not been automatically loaded into memory,
you can do it manually. To do this, click the More Actions icon in the Actions column
for the cache you want to load, then click Load.
• Unload a cache from memory. You can unload a cache from memory if you need to free
up memory for other operations on the Intelligence Server machine. To do this, click the
More Actions icon in the Actions column for the cache you want to unload, then
click Unload.

Monitoring and managing open database connections

A data warehouse database connection is initiated any time a user executes an uncached
report or browses uncached elements. You can view the number of busy and cached data
warehouse connections, the name of the database instance, the user who is using the
connection, and the database login being used to connect to the database.
If a database connection is cached, the ODBC connection from Intelligence Server to the
data warehouse remains open. However, if the data warehouse connection surpasses the
connection time-out or lifetime governors (set in the Database Connections dialog box, on
the Advanced tab), the ODBC connection closes and it no longer displays in the Database
Connection Monitor.
To view the open database connections for a server, from the Server drop-down list, select
the server.
You can view information for each open database connection, and you can disconnect a
database connection:
• Connection ID: Numeric identifier for a connection.
• Status: Connections are either Busy processing a job, or Cached and available to
process a job.

© 2017, MicroStrategy Inc. 57

Operations Manager Guide

• Database Instance: The database instance being used to make the connection to the
database.
• Database Connection: The database connection being used to make the connection
to the database.
• User Name: When a connection is busy, you can view the user name of the person
whose job is being executed.
• Database Login: The database login being used to make the connection to the
database.
• Actions: You can disconnect a database connection by clicking the Disconnect
icon, then clicking Yes to confirm.

Monitoring the quick search index status

You can view the status of the quick search index for each project. Quick search is available
in MicroStrategy Web and uses an index to search for objects, so it is faster than the regular
search. Quick search provides ranked search results and suggestions as the user types
search terms. Quick search indexes are managed in MicroStrategy Developer. For
information on managing them, see the System Administration Guide.
To view the quick search index status for all projects on a server, from the Server drop-down
list, select the server.
• Project: The name of the project.
• Index Status: The current status of the quick search index:
▫ No Index: The project has not been indexed for quick search.
▫ Crawling: The quick search index is being created.
▫ Paused: The index creation process is paused.
▫ Complete: The index is complete.
• Percentage Completed: The percentage of the search index that has been created.
• Search Items: The number of items that can be searched in the project.
• Last Real Time Updates: The date and time when the search index was
automatically updated because of a change in the metadata.
• Project ID: The object ID of the project.

58 © 2017, MicroStrategy Inc.

 1
INDEX

A sorting 44
alert 18 turning off 18
cache availability 28 turning on 18
categories of 19 viewing 43
configuration 20 alert inbox 43
configuring 19 filtering 44
deleting 44
C
Enterprise Manager data load
process 40 cache
filtering 44 deleting 57
Intelligence Server availability 28 invalidating 57
machine usage and performance 20 loading into memory 57
marking as read 44 managing 55, 57
marking as unread 44 monitoring availability with an alert 28
MicroStrategy Mobile memory 40-41 unloading from memory 57
MicroStrategy Web Server viewing details 55
availability 32
cache monitor 52
MicroStrategy Web Server
memory 42 counter

Mobile Server availability 32 available 5

server performance 35 choosing 5

displaying 4

© 2017, MicroStrategy Inc. 59

Operations Manager Guide

setting thresholds 8 J
CPU usage 45 job
canceling 50
D
monitoring 49
database connection
viewing details 50
disconnecting 58
job completion rate 47
monitoring 57
L
E
landing page 3
environment 10
displaying counters on 5
adding servers to 14
logical disk I/O usage 46
configuring 10
connecting 4 M
creating 11 memory I/O usage 46
deleting 11 memory usage 46
disconnecting 4 monitor 48
modifying 13 caches 52
removing servers from 14 database connections 57
environment details 8 environment 43
jobs 49
G
quick search index 58
group 16
users 51
adding environments 17
Monitor tab 11
creating 16
deleting 17 O
removing environments 17 Operations Manager 10
accessing 2
H
configuring 8
heartbeat
introduction 1
accessing 44
landing page 3
Heartbeat tab 11
prerequisites 2
setting up 2

60 © 2017, MicroStrategy Inc.

 Operations Manager Guide

P
page file usage 47

Q
quick search index monitoring 58

S
server 14
managing 14
monitoring availability using an
alert 28
performance alert 35
restarting 15
searching for 4
starting 15
stopping 15
viewing 15

U
user monitoring 51
user session
details 52
disconnecting 52

V
viewing a server 15

© 2017, MicroStrategy Inc. 61

Operations Manager Guide

62 © 2017, MicroStrategy Inc.