In order to monitor MicroStrategy Intelligence Server, we have two options:

Let's start with MicroStrategy monitors. We should open MicroStrategy Developer, where we can find Project monitors:

These monitors are very useful and can give a quick overview of what is going on with our MicroStrategy server. For example, one of the most useful is User Connections, which helps to understand who is logged on now. In addition, if we have enough rights, we can kill the session of a particular user. Another one is Jobs - this shows us reports that are executing or in a queue waiting to execute. On our small training server, there isn't lots of information, but if you have a production MicroStrategy, you can get lots of insights from these monitors.

One of the main new features of MicroStrategy 10 is MicroStrategy Operations Manager, which is a web-based tool for administrative tasks. It allows us to monitor all environments in one place. For example, Operations Manager allows us to:

There is detailed guide available about Operations Manager at https://community.microstrategy.com/mxret26282/attachments/mxret26282/351/13236/1/OperationsManager.pdf.

Let's set up Operations Manager for our server. In order to run Operations Manager, we should:

In Chapter 1, Getting Started with MicroStrategy we deployed both WAR files for Operations Manager and Web. However, if we try to access Operations Manager now via its link, we get a message that we need JRE version 1.7 and higher. Let's check what Java version we have on the Linux machine:

# java -version
java version "1.6.0_38"

It's not the required Java version. Let's try to upgrade it:

# cd /opt/
# wget --no-cookies --no-check-certificate --header "Cookie: 
    gpw_e24=http%3A%2F%2Fwww.oracle.com%2F;
    oraclelicense=accept-securebackup-cookie" 
    "http://download.oracle.com/otn-pub/java/jdk/8u77-b03/
    jdk-8u77-linux-x64.tar.gz"
# tar xzf jdk-8u77-linux-x64.tar.gz
# cd /opt/jdk1.8.0_77/
# alternatives --install /usr/bin/java java /opt/jdk1.8.0_77/bin/java
# alternatives --config java

Choose a new version of Java:

# java -version
java version "1.8.0_77"

The next step is to restart Tomcat in order to use new Java.

Now, when we go to the link, we can see that Operations Manager is working. In order to create a new environment, we should install MicroStrategy Master Health Agent on the same machine where we have Tomcat. Let's do it:

# cd /mstr10/microstrategy_home/bin
# ./mstrcfgwiz

In the Configuration Wizard:

As a result, we set up Master Health Agent. Now we can go to Operations Manager and create a new environment:

Now we are using Master Health Agent for Intelligence Server and Operations Manager because we deployed Tomcat (MicroStrategy Web, Operations Manager) and Intelligence Server on one physical machine. However, in the production environment, we should split the web server from the MicroStrategy server. In this case, we should install Master Health Agent on the machine where we deploy Operations Manager and Health Agent on the machine where we deploy Intelligence Server. There is a very good explanation of how to do it in Linux or Windows at https://community.microstrategy.com/t5/Server/TN32554-How-to-Configure-a-MicroStrategy-Health-Center-system/ta-p/183413.

As a result, we add our environment to the Operations Manager. Now we are able to monitor performance and create alerts. Moreover, we can add other environments, for example, if we have a MicroStrategy cluster or just want to have one place for monitoring multiple environments such as Test, Development, and so on. In addition, we can connect Enterprise Manager to the Operations Manager.