Documents
Product Categories
Manageengine Application Manager
Product Categories
Manageengine Application Manager
Manageengine Application Manager
Jun 28, 2024.bin -i console
For example, if the name of the file is ''ManageEngine_ApplicationsManager.bin'', then the command
should be as follows:
./ManageEngine_ApplicationsManager.bin -i console
Execution of the above command would take you through the installation process. However, to execute
.bin type of files, users should require Execute permission.
When installing Applications Manager in a Linux machine, make sure that the installation is done using a
non-root user account with admin privileges.
Troubleshooting an Installation process
In case of problems during installation in a Linux system, follow the steps given below to produce the logs files:
Create a text with the same name as that of the installer and with extension as ".sp". i.e, For .bin,
create a text file named .sp. For example, if the file name is
ManageEngine_ApplicationsManager.bin, create a text file named
ManageEngine_ApplicationsManager.sp
Open the ".sp" text file in an editor, add is.debug=1 as the content.
Save the ".sp" text file in the same directory where the binary file resides.
Change to the directory where the binary file is present by executing cd command
Invoke the installer as ./.bin -is:javaconsole -is:log log.txt
The above command will create the log file named log.txt. Mail the log file to appmanager-
support@manageengine.com.
Note
If the execution of the installation command throws an error such as "there may not be enough temporary space
available in the temp folder", then execute the file with the argument as
For Windows: .exe -is:tempdir $DIRNAME
For Linux: ./.bin -is:tempdir $DIRNAME
where $DIRNAME is the absolute path of any existing directory.
Troubleshoot: For more Installation Troubleshooting, refer Troubleshooting page on our website.Uninstalling Applications Manager
Windows
Shut Down Applications Manager (Make sure that the ManageEngine ApplicationsManager service is stopped
if installed as a Windows service)
Open a command prompt as an administrator [ Command Prompt → right click → Run as administrator], go to
Applications Manager Home directory and execute the following commands:
shutdownApplicationsManager.bat
shutdownApplicationsManager.bat -force
Exit out of the command prompt and close all files, folders opened in the
directory
Click Start → Programs → ManageEngine Applications Manager → Uninstall Applications Manager
Also from Control Panel → Add/Remove Programs.
Linux
From the command line, go to Applications Manager Home directory ( by default it is
/opt/ManageEngine/AppManager ) and execute the below commands:
sh shutdownApplicationsManager.sh
sh shutdownApplicationsManager.sh -force
Exit out of the command prompt and close all files, folders opened in the Applications Manager Home
directory
Execute the command ./uninstaller.bin from the AppManager/_uninst directory.
Note
You can uninstall Applications Manager via Command Line also. Type the following command in the
command prompt:
./uninstaller.bin -console
Execution of this command would take you through the uninstallation process.
Here''s how you can manually uninstall Applications Manager
Frequently Asked Questions (FAQs)
Question: How can perform a "Silent Installation" of Applications Manager?
Solution: To perform silent installation of Applications Manager, refer to the following links:
For Windows OS, refer here.
For Linux OS, refer here.
Question: I downloaded the .bin file to install Applications Manager in my Linux machine. When I tried to
execute the file I got a dialog box displaying "Could not display the file. File is of an unknown format".
Solution: You must change the permission for the downloaded file. To do so, execute the following command to
provide the permission for executing the downloaded file:
chmod +x .bin
Example: chmod +x ManageEngine_ApplicationsManager_64bit.bin
After executing the above command, you will be able to install Applications Manager in Linux machine.
Note:
By default, Applications Manager will not store installation logs. To enable installation logs, do the following:
Create a file named APMBinFileName.sp (ManageEngineApplicationsManager.sp) in the location where
the .bin folder of Application Manager is downloaded.Inside the file, type (is.debug=1) and save it.
Then start the installation using below options:
./bin -is:log log.txt along with the options that are given in the solution.
Troubleshooting
For troubleshooting tips on installation and setup, go to our support portal.
Licensing Applications Manager
When you have purchased the registered license file, you need to apply the license file over the existing version.
This section explains the procedure to apply the new license file.
Applying the New License File from the Web Client
A quick way to apply the new license file is from the web client.
In the web client, click on the Settings tab link provided at the top right-hand corner.
Click Product License link in the menu
A Register Applications Manager pop-up is displayed.
Click Browse button and locate the file (License.xml) in your local machine.
Click Register.
Your existing version is now changed to Professional Edition - Registered.
Note: For Enterprise Edition, it is sufficient that you apply the license in Admin Server alone, the managed
servers will be taken care automatically. The Product License link on top will disappear once you have applied
the registered license. If the registered customers, want to upgrade their license further, they can use the
Product License link under Applications Manager Server Settings in the Admin tab.
Applying the New License File using License Manager
The license manager comes handy when your license has already expired and you are not able to access the web
client.
Invoke the updateLicense.bat/.sh file located in the /bin directory (For
Windows use ''Run as Administrator'' option). The License Manager UI is displayed.
Click Browse button and locate the file (License.xml) in your local machine.
Click Next and then Click Finish.
Re-start the Applications Manager server.
Note: To invoke License Manager via Command Line, use the following command
Applying a license in a plugin build
Users must apply the OpManager license in the OpManager console to register the Applications Manager plugin
(you need not apply the OpManager license file on APM plugin license tool).
Please contact us at appmanager-support@manageengine.com for any technical query.
Using Update Manager
Overview
Update Manager is a tool which is used for installing the service packs (.ppm file) over Applications Manager. The
service pack may contain certain bug fixes and new feature additions. This document explains about how to use
the Update manager to install service packs over Applications Manager.
Note: The Update Manager also has some useful validation incorporated. This validation includes
compatibility checks. You cannot use update manager to install an incompatible service pack. For example,you cannot install a service pack of another product in Applications Manager or a service pack of one version of
Applications Manager in another version.
Installing Service Pack using Update Manager
Execute the updateManager.bat/sh file located in the /bin directory or invoke
through Start → Programs → ManageEngine Applications Manager 15 → Update Manager in Windows (For
Windows, use ''Run as Administrator'' option). The Update Manager tool is displayed. Click Update.
Provide the service pack (.ppm) file by clicking the Browse button. Only compatible service pack file will be
opened. Once the file is specified, other buttons such as Readme and Install are enabled.
Click the Readme button and the Readme file related to the service pack is displayed in a separate window.
Click Install. This opens a new panel where the installation process is displayed. On completion, a message
"Service Pack installed successfully" is displayed and the service pack is listed in the Installed Patches section
To uninstall the service pack, click the Uninstall button. To know the service pack details, click the Details button
in Update Manager.
Installing Service Pack using Update Manager (Command Line
Option)
To invoke Update Manager, navigate to /bin directory and execute the
following command:
For Windows: updateManager.bat -c
For Linux: sh updateManager.sh -c
To force quit Applications Manager, execute the following command:
For Windows: shutdownApplicationsManager -force
For Linux: shutdownApplicationsManager.sh -force
Using this command line option, you can install or uninstall a service pack or view its details. Press ''i'' to install and
specify the absolute path of the service pack file in your machine.
Troubleshooting
For troubleshooting steps, go to our Support Portal.
Starting and Shutting Down Applications
Manager
Starting Applications Manager
Once installation is successful, you can start the Applications Manager by following the instructions provided for
different operating systems.
To start Applications Manager
In Windows
Click Start → Programs → ManageEngine Applications Manager XX → Applications Manager Start (or)
Invoke the batch file startApplicationsManager.bat located in the directory.
Once the server is initialized, a tray icon is placed in the Windows system tray . After the server is started
completely the icon changes to and a message "Server Ready for Monitoring!" is displayed over the icon. Right-
click on the Applications Manager tray icon to connect to the web client or stop Applications Manager.
Starting Applications Manager as a Windows Service:
In Windows, you can start Applications Manager as a service. With this feature you can start the Applications
Manager server automatically when the Windows system starts.By default, during product installation, you can choose to install it as a service (More on Installation). If you have
not enabled it then, use the following option to setup Applications Manager as a service.
Go to /bin directory, execute the installservice.bat file. On executing this file,
''ManageEngine Applications Manager'' service is added in Windows Services and the startup type is set as
''Automatic'', by default. (To ensure if it is installed as a service, check for the ''Services'' under ''Windows
Administrative Tools'').
Note: For installing Applications Manager as service, you need to have administrative privileges in that
system.
Now, when you start Windows system, Applications Manager is automatically started. You can swap between
Automatic and Manual modes.
To uninstall this service, go to /bin directory and execute the uninstallservice.bat
file.
In Linux:
From the command line, go to directory (by default, it is
/opt/ManageEngine/AppManager) and execute the below command to start the product:
nohup sh startApplicationsManager.sh &
To start Applications Manager as a service in Linux, refer here.
Troubleshoot: Having trouble starting Applications Manager? Refer to the online troubleshooting section.
Shutting Down Applications Manager
To shutdown Applications Manager
In Windows
Click Start → Programs → ManageEngine Applications Manager XX → Applications Manager Shutdown (or)
In Applications Manager''s Settings tab, under Tools, click on Shut Down Applications Manager icon (or)
Invoke shutdownApplicationsManager.bat file located in the directory (or)
Right-click on the Applications Manager tray icon and click Stop Applications Manager (or)
Go to Start → Run → services.msc → opens up Services console → stop ManageEngine Applications Manager.
[If Applications Manager is running as service]
In Linux
Use shutdownApplicationsManager.sh script located in the directory to
shutdown Applications Manager.
You can also use the Shut Down Applications Manager tool under Settings tab in Applications Manager.
Compare our Editions
Meet your specific monitoring and business objectives by choosing the right edition of ManageEngine
Applications Manager. Applications Manager is available in these editions - Free, Professional and Enterprise.
Features Free Professional Enterprise
Supports integrated
Supports monitoring up to Supports large
performance monitoring
5 apps or servers. There is deployments with its
Out-of-the-box support for for a heterogeneous set of
no time limit on the free distributed monitoring
80+ applications applications. Ideal for
edition - you can use it capability. Ideal for large
small to medium
forever. enterprises.
enterprises.
Server Monitoring
Monitor open source apps
& servers
Monitor commercial apps
& servers (For Five Monitors)Features Free Professional Enterprise
Application Server
Monitoring
MySQL, Oracle, MS SQL,
PostgreSQL, Memcached,
Database Monitoring
Cassandra, MongoDB and
Redis.
Website / Web Services
Monitoring
SLA Management
Exchange Server
Monitoring
Virtualization monitoring VMware Monitoring Only
Cloud monitoring
WebSphere MQ Series
monitoring
MS Office SharePoint
monitoring
AS400 monitoring
ERP monitor
Web transactions
monitoring for J2EE and
.Net (APM Insight)
Web transactions
monitoring for Ruby on
Rails(APM Insight)
Integration with Site 24x7
End user monitoring (EUM)
URL monitoring/multi-
step URL sequence
monitoring
User administration,
network discovery, custom
dashboards
ManageEngine
OpManager Connector
ServiceDesk Plus
Integration
Anomaly detection
Admin tools: Downtime
scheduler, Trap Listener,
Scheduling, enabling,
disabling reports.
Updates and patches
Technical support E-mail Support (30 days)
Failover support
High scalability
Distributed architecture
Supported Operating
Windows, Linux Windows, Linux Windows, Linux
Systems for Installation
Starts @ $395 for 10 Starts @ $9,595 for 250
Price Free
monitors monitors
Verifying build integritySHA256 checksum verification helps verify integrity of files you download. It helps identify if the downloaded file
has been corrupted.
After you have downloaded Applications Manager binaries, you should ensure that its SHA256 checksum matches
the one provided in the Applications Manager download pages.
Steps to verify SHA256 Checksum:
Open command prompt with administrator privileges.
Navigate to the directory in which the downloaded file exists.
Based on the OS you are using, execute the command mentioned. (The sample output is mentioned below
each command)
Windows:
C:\Users\Downloads> CertUtil -hashfile ManageEngine_ApplicationsManager_64bit.exe SHA256
SHA256 hash of ManageEngine_ApplicationsManager_64bit.exe:
3a4a903b80f75618698c6ba66aca0b298ab861f75ae0b2322a661a593cae2a51
CertUtil: -hashfile command completed successfully.
Linux:
$> sha256sum ManageEngine_ApplicationsManager_64bit.bin
$> fc8881646e23053ad42548782243af1ef8ae675d0386d5a8753041a7dbdf2e95
ManageEngine_ApplicationsManager_64bit.bin
MAC:
$> shasum -a 256 ManageEngine_ApplicationsManager_64bit.exe
$> 3a4a903b80f75618698c6ba66aca0b298ab861f75ae0b2322a661a593cae2a51
ManageEngine_ApplicationsManager_64bit.exe
After executing the command, verify that the returned checksum value matches the SHA-256 value mentioned
in the Applications Manager''s download page. If the values do not match, download the file again and repeat
this procedure.
Security Best Practices
With the digital era evolving and expanding rapidly, the frequency of cyber attacks is also increasing at an
alarming rate. Hence, it is critical to follow guidelines and best practices as a first line of defense against potential
threats. Below is a list of recommended guidelines that will help us achieve our common goal of enhancing
security and preventing possible intrusions.
Disable HTTP
By default, Applications Manager can be accessed via both HTTP and HTTPS ports. To ensure a secure
connection between Applications Manager server and the browser/client, it is recommended to disable HTTP
access. Show me how.
Use Third Party SSL Certificate
Applications Manager comes with a self-signed SSL certificate for HTTPS to work. However, to enhance
security it is recommended that you apply your own CA signed SSL certificate. Show me how.
Disable TLSv1 and TLSv1.1 protocols for HTTPS port
Applications Manager supports TLSv1, TLSv1.1 and TLS v1.2 by default. It is recommended that you disable old
TLS v1/1.1 protocols. Show me how.
Enable Security response headers
Security response headers act as an added layer of security that helps browsers to detect and mitigate certain
types of attacks. It is recommended that you enable these headers to prevent click-jacking, cross-site
scripting, and MIME type sniffing attacks.
To enable security response headers, navigate to Settings -> Security Settings -> Enable Security response
Headers
To learn more about this, click here.
Setup complex passwords and enforce account locks
By default, Applications Manager''s password policy enforces password encryption by default. It mandates you
to set complex passwords to enhance security and make it less vulnerable to cyber attacks. It is alsorecommended that you change the Super admin''s password after installation of the product.
To defend against password-guessing attacks, it is recommended that you enforce account locks in case of
consecutive failed login attempts. Show me how.
Implement role-based access control (RBAC)
Applications Manager provides you the ability to manage users and roles for your enterprise, with roles
assigned to users and different permissions associated to each role. This enforces controlled access to the
product thereby ensuring effective authorization.
It is recommended that you add users and associate them with the required roles to prevent unwanted access
and changes. Show me how.
Enable LDAPS when configuring domain
Applications Manager provides domain configuration options and also lets you import users from those
domains. It is recommended that you enable LDAPS while configuring domains to ensure secure
communication with domain controllers. Show me how.
Enable Data Protection
To ensure that report data is accessed more securely, it is recommended that you enable data protection in
security settings. Applications Manager enforces password protection for reports in all formats (PDFs, HTML
files, and CSVs).
To enable Data Protection, go to Settings -> Security Settings -> Data Protection.
Disable file upload
The Applications Manager UI has an option that allows admins to upload files into the Applications Manager
directory. As a measure to avoid harmful files from being uploaded accidentally, it is recommended to disable
this option. You can enable it whenever required.
To disable file upload, navigate to Settings -> Security Settings -> Disable file upload.
Enable read-only database user connection for Query Tool
Applications Manager has a query tool that lets the super admin obtain data from the database by executing
custom queries. To prevent accidental change in the database that might likely impact the functioning of the
entire application, it is recommended to enable read-only database user connection for Query tool.
To enable read-only database user connection for Query Tool, go to Settings -> Security Settings -> Enable
read-only database connection for query tool.
Upgrade to the latest version of Applications Manager
Ensure that you frequently upgrade to the latest version of Applications Manager to experience the latest
features and to ward off possible vulnerabilities. Also, periodically back up application data and database.
Refer this link to upgrade to the latest version.
Other options:
IP Whitelist/Blacklist: Grant access to specific IP addresses to access Applications Manager.
Server Information Headers (Banner): Disable information about the underlying hosting environment.
Session Timeouts: Configure browser session idle time for inactivity.
Common Best Practices
Subscribe to the Applications Manager security advisory mailing list. (Navigate to Admin -> Privacy settings -
> Breach notification)
Ensure that you always have the latest host operating system, browser, and network security update installed.
Ensure that you do not expose Applications Manager on the public Internet.
If you must enable outbound internet access from Applications Manager servers, create a strict allow list and
block all other traffic.
Disable unnecessary ports, protocols, and services on your host operating system. See Security/Firewall
Requirements of Applications Manager.
Only authorized users should have access to the machine where you install Applications Manager server.
Ensure that the credentials you provide in Applications Manager for monitoring/integration purpose must
follow the principle of least privilege.
Getting StartedWhen Applications Manager is started in Windows, the default browser as configured in your system is invoked and
the login screen is displayed. Login by specifying the authentication details. The default user name and password
are "admin" and "admin" respectively. To know more about the different types of user access to the product, refer
to the User Administration section of Performing Admin Activities.
In Windows, if you do not want the client to open by default, follow the steps given below to disable it.
Edit AMServer.properties file located in the /conf directory.
Set the value of am.browser.startup as false (by default, it is true).
After this configuration, when you restart the server the next time, the web client will not be invoked automatically.
In Linux, by itself, the client will not open by default..
To login to Web Client, when it is not opened by default
Connect to the Applications Manager through any browser with the host name and port number, say
http://localhost:9090, where 9090 is the default port number.
In Windows, go to Program Files → ManageEngine Applications Manager → Applications Manager Web
Console.
Right-click the Applications Manager tray icon and click Start Web Client.
Then log in to the Applications Manager by filling in the User Authentication details.
In case you forgot the password for your user account, you can reset the password from the login page using the
Reset Password option. To do so, follow the steps given below:
Click over the Reset Password link available in the login page.
Enter the username and the email ID configured for the user and click Reset Password.
An email containing the link for password reset will be sent if the given user details are correct. Click over the
Reset Password link mentioned in the mail.
On clicking the link, you will be redirected to the Password Reset page. Enter the new password to be
configured for the user account and submit.
Once password reset is successful, you can login using the new password configured from the login page.
Note:
Reset Password option is not supported for Plugin and SSO-enabled Enterprise Edition setup.
You can also use the startWebConsole.bat or sh file available at the
directory that opens a default browser of the localhost and connect to the Applications Manager at
http://localhost:9090. Ensure that the Applications Manager is started before executing this file.
Browse through the following topics which would help you understand Applications Manager better and work with
it easily.
Understanding Applications Manager
Prerequisites for Applications Manager
Working with Applications Manager
You can also refer our Best Practices Guide for more help on getting started with Applications Manager.
Note
User management is not supported for the Applications Manager plugin build over OpManager. At present,
there are only two types of roles available for plugin users - Administrator and Read-Only User. Operator,
Delegated Admin and Manager role is not supported. Applications Manager Plugin users cannot assign
monitors to the any specific users in the Apps tab. They can view all the default monitors only.
Prerequisites for Applications Manager
Discussed below are the prerequisites for managing the various monitors:
Application Servers
GlassFish
JBoss
Oracle Application ServerTomcat
WebLogic
WebSphere
Java Runtime Monitor
Resin Server
Jetty Server
Apache Geronimo
Database Servers
IBM Informix Server
MS SQL DB Servers
MongoDB Servers
MySQL DB Servers
Oracle Database Servers
Oracle Pluggable Database (PDB)
PostgreSQL
SAP ASE / Sybase SQL Server / Sybase ASE
SAP HANA
SAP MaxDB
SQL Anywhere
IBM DB2
Cloud Apps
Microsoft Azure
Azure Virtual Machines
Azure SQL Database
Azure Kubernetes Service (AKS)
Microsoft 365
AWS Monitoring
Amazon EC2 Instances
Amazon RDS Instances
Amazon DynamoDB
Amazon Billing
Amazon Elastic Load Balancer
Amazon SNS
AWS Lambda
AWS Elastic Beanstalk
Amazon SQS
AWS ECS
AWS EKS
Google Cloud Platform
Oracle Cloud Infrastructure
Oracle Autonomous Database
OpenStack
ERP
Oracle EBS
SAP Server, SAP CCMS
Microsoft Dynamics CRM / 365 (On-Premise)
Microsoft Dynamics AX
SAP Business OneServers
Windows
Linux
IBM i
Services
JMX Applications
Ceph Monitor
Hadoop Monitor
Apache Zookeeper
Active Directory
Istio
Network Policy Server (Radius Server)
Mail Servers
Exchange Server
Java / Transactions
APM Insight
Middleware / Portal
IBM WebSphere MQ
IBM Websphere Message Broker
WebLogic Integration Server
Microsoft Office SharePoint Server
Microsoft Message Queue (MSMQ)
Microsoft BizTalk Monitoring
Azure Service Bus
Apache ActiveMQ
Virtualization
VMware Horizon View Connection Broker
Docker
Web Server / Services
IIS Server
PHP
Apache
Nginx
HAProxy
Real Browser Monitoring
Webpage Analyzer
Real User Monitor
ManageEngine ADManager Plus
ManageEngine ServiceDesk Plus
ManageEngine OpManager
Converged Infrastructure
Cisco UCS
Application Servers
GlassfishWhile monitoring Glassfish application servers, make the following changes in the domain.xml file and then restart
it:
Change the "accept-all" property to "true" for the "jmx-connector" node : /server/default/deploy/http-invoker.sar/META-INF/jboss-service.xml file.
JBoss Version 5x
To monitor JBoss 5.x version, jbossagent.sar should be deployed in JBoss server. To deploy, follow the steps below:
Copy jbossagent.sar from location /working/resources and paste
under /server/default/deploy
If you are running JBoss in different domain like all, then deployment target folder would
be /server/all/deploy.
JBoss Version 6.x
Note: JBOSS 6 EAP should be added as JBoss 7
To monitor JBoss 6.x version, jbossagent.sar should be deployed in JBoss server. To deploy, follow the steps below:
Copy jbossagent.sar from location /working/resources and paste
under /server/default/deploy
If you are running JBoss in different domain like all, then deployment target folder would
be /server/all/deploy.
Provide the rmiRegistryPort which is available
in /server//conf/bindingservice.beans/META-INF/bindings-jboss-
beans.xml file. The default port is 1090.
Example:
jboss.remoting:service=JMXConnectorServer,protocol=rmi
1090
RMI/JRMP socket for connecting to the JMX MBeanServer
JBoss Version 7.x and above
To add a new monitor for JBoss Version 7.x and above you must provide a management port. The default port is
9990.
JBoss WildflyChange the Management port binding to use the network accessible interface:
In the JBoss config file (i.e. \standalone\configuration\standalone-full.xml) change
jboss.bind.address.management:127.0.0.1 to jboss.bind.address.management 0.0.0.0
Restart the service
Add a JBoss administration user for monitoring:
/bin/add-user.bat ManagementRealm -silent
Oracle Application Server
Applications Manager uses the Dynamic Monitoring Service (DMS) provided by Oracle Application Server to
monitor the same. For this reason, the DMS Servlet has to be made accessible to the system where the
Applications Manager is running.
To enable the access, please follow the instructions provided below
[The instructions are referred from the Oracle website:
http://docs.oracle.com/cd/B14099_19/core.1012/b14001/monitor.htm]
By default, the dms0/AggreSpy URL is redirected and the redirect location is protected, allowing only the
localhost (127.0.0.1) to access the AggreSpy Servlet.
To view metrics from a system other than the localhost you need to change the DMS configuration for the system
that is running the Oracle Application Server that you want to monitor by modifying the file
$ORACLE_HOME/Apache/Apache/conf/dms.conf on UNIX, or%ORACLE_HOME%\Apache\Apache\conf\dms.conf
on Windows systems.
The following example shows a sample default configuration from dms.conf. This configuration limits AggreSpy to
access metrics on the localhost (127.0.0.1). The port shown, 7200, may differ on your installation.
Example: Sample dms.conf File for localhost Access for DMS Metrics
# proxy to DMS AggreSpy
Redirect /dms0/AggreSpy http://localhost:7200/dmsoc4j/AggreSpy
#DMS VirtualHost for access and logging control
Listen 127.0.0.1:7200
OpmnHostPort http://localhost:7200
ServerName 127.0.0.1
By changing the dms.conf configuration to specify the host that provides, or serves DMS metrics, you can allow
users on systems other than the localhost to access the DMS metrics from the location
http://host:port/dms0/AggreSpy.
Caution: Modifying dms.conf has security implications. Only modify this file if you understand the security
implications for your site. By exposing metrics to systems other than the localhost, you allow other sites to
potentially view critical Oracle Application Server internal status and runtime information.
To view metrics from a system other than the localhost (127.0.0.1), do the following:
Modify dms.conf by changing the entries with the value for localhost "127.0.0.1" shown in Example to the name
of the server providing the metrics (obtain the server name from the ServerName directive in the httpd.conf
file, for example tv.us.oracle.com).
Find below a sample updated dms.conf that allows access from a system other than the localhost (127.0.0.1)
Example: Sample dms.conf File for Remote Host Access for DMS Metrics:
# proxy to DMS AggreSpy
Redirect /dms0/AggreSpy http://tv.us.oracle.com:7200/dmsoc4j/AggreSpy
#DMS VirtualHost for access and logging control
Listen tv.us.oracle.com:7200
OpmnHostPort http://tv.us.oracle.com:7200
ServerName tv.us.oracle.com
Restart, or stop and start the Oracle HTTP Server using Application Server Control Console or using the Oracle
Process Manager and Notification Server opmnctl command.
For example,
%opmnctl restartproc process-type=HTTP_Server
or%opmnctl stopproc process-type=HTTP_Server
%opmnctl startproc process-type=HTTP_Server
After performing the above steps, please ensure that you are able to access the URL
http://:7200/dmsoc4j/AggreSpy from the Applications Manager system.
To check if a user has select privilege:
We suggest you to execute the below query directly in your Oracle machine and check if a connected user has
select privilege or not :
select TABLE_NAME,PRIVILEGE from user_tab_privs_recd where table_name in
(''ALL_SCHEDULER_JOB_RUN_DETAILS'',''V_$RMAN_BACKUP_JOB_DETAILS'',''ALL_SCHEDULER_JOBS'',''ALL_SC
HEDULER_RUNNING_JOBS'');
If there is no row selected or privilege column does not have select value for the above table_name columns, then
the user doesn''t have privilege to access the table.
To grant Privilege:
Use the following query:
grant select on to ;
Example: grant select on V_$RMAN_BACKUP_JOB_DETAILS to monitoruser;
Note: As above, you have to give grant permission on all the tables mentioned in the above query.
Tomcat
Applications Manager agent has to be deployed in Tomcat Servers 3.x and 4.x. More
Tomcat 3.x and 4.x needs no user name and password. In case of Tomcat 5.x and above, an application named
Manager must be running in it for Applications Manager to monitor the Tomcat server. By default, this application
will be running in the server.If you have customized the manager application (Eg., \qamanager), then you can use
the option "Tomcat Manager Application URI" in the client, for Applications Manager to monitor the Tomcat server.
For Tomcat Versions 5.x & 6.x and 7.x:
The user role to access the server must be manager (versions 5.x & 6.x) / manager-jmx (version 7.x).
To add a role as "manager" (versions 5.x & 6.x) / "manager-jmx" (version 7.x) for any of the users such as
tomcat, role1, or both, you need make changes in tomcat-users.xml file located in the /conf
directory.
Example:
Default configurations in tomcat-users.xml in Tomcat Server:
After adding the roles for the "tomcat" user, the modified entries will be as follows:
On making the configuration, restart the Tomcat Server.
Now, when adding a new Tomcat (5.x and above) monitor, specify the username/password as tomcat/tomcat
when discovering the Tomcat Server.
[Click the link to view an example tomcat-users.xml for versions 5.x / 6.x and tomcat-users.xml for versions 7.x]
For Tomcat 7 and above:
Remote access to Applications Manager is restricted, by default.
Include the IP address of Applications Manager-installed host machine in
CATALINA_HOME/webapps/manager/META-INF/context.xml file (under ''allow ='' ).
:/manager/status (Provide manager user credentials).
2) If the application is not accessible, add the following entry in server.xml, under ''Engine'' context:
/weblogic61/server/lib directory. From there,
copy Weblogic.jar to \working\classes\weblogic\version6 directory in the
machine where Applications Manager is running.
To monitor WebLogic 7.x:
You should set the weblogic.disableMBeanAuthorization and
weblogic.management.anonymousAdminLookupEnabled variables to true for enabling data collection. Follow
the steps given below:
Edit startWLS.cmdsh present in the /server/bin directory and add the following arguments
-Dweblogic.disableMBeanAuthorization=true
-Dweblogic.management.anonymousAdminLookupEnabled=true Click here for Sample
startWLS.cmd/shRestart the WebLogic Server for the changes to take effect
In the remote WebLogic server, navigate to /weblogic70/server/lib directory. From there,
copy Weblogic.jar to \working\classes\weblogic\version7 directory in the
machine where Applications Manager is running.
To monitor WebLogic 8.x:
You should set the weblogic.disableMBeanAuthorization and
weblogic.management.anonymousAdminLookupEnabled variables to true for enabling data collection. Follow
the steps given below:
Edit startWLS.cmdsh present in the /server/bin directory and add the following arguments
-Dweblogic.disableMBeanAuthorization=true
-Dweblogic.management.anonymousAdminLookupEnabled=true Click here for Sample
startWLS.cmd/sh
Restart the WebLogic Server for the changes to take effect
In the remote WebLogic server, navigate to /weblogic81/server/lib directory. From there,
copy Weblogic.jar to \working\classes\weblogic\version8 directory in the
machine where Applications Manager is running.
To monitor WebLogic 9.x:
In the remote WebLogic server, navigate to /weblogic92/server/lib directory. From there, copy
Weblogic.jar to \working\classes\weblogic\version9 directory in the machine
where Applications Manager is running.
To monitor WebLogic 10.x , 11g:
In the remote WebLogic server, navigate to /wlserver/server/lib directory. From there,
copy Weblogic.jar, wlclient.jar, wljmsclient.jar, wlthint3client.jar to \working\classes\weblogic\version10 directory in the machine where Applications Manager is running.
To monitor WebLogic 12.x and above:
In the remote WebLogic server, navigate to /wlserver/server/lib directory. From there,
copy wlclient.jar and wljmxclient.jar to \working\classes\weblogic\version12 directory in
the machine where Applications Manager is running.
Note:
refers to the WebLogic installation directory.
After replacing the jar files, Applications Manager has to be restarted.
For SSL support over WebLogic:
WebLogic certificate has to be imported to /working/jre/lib/security/cacerts file.
This certificate can be imported through /bin/WeblogicCertificate.bat/sh files.
Syntax:
WeblogicCertificate.bat [import] [Full path of weblogic server certificate] [alias name]
Example:
C:\Program Files\ManageEngine\AppManager\bin> WeblogicCertificate.bat import
"C:\Oracle\Middleware\Oracle_Home\user_projects\domains\MyDomain\root.cer" mykey
Note:
* If customer is monitoring all three versions of weblogic (10.x, 11g, 12C), then get the jars from latest version of
WebLogic (Version 12c).
* SSL option is enabled in the UI only for version 9 and above.
The ports that need to be opened when the Weblogic Monitor is behind the firewall: Two-way communication
between WebLogic listening port (default : 7001) and Applications Manager web server port (default : 9090).
Sample commands for WebLogic 7.x, 8.x:"%JAVA_HOME%\bin\java" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%" -
Dweblogic.Name=%SERVER_NAME% -Dbea.home="C:\WebLogic\WL7.0" -
Dweblogic.disableMBeanAuthorization=true -
Dweblogic.management.anonymousAdminLookupEnabled=true -
Dweblogic.management.username=%WLS_USER% -Dweblogic.management.password=%WLS_PW% -
Dweblogic.management.server=%ADMIN_URL% -Dweblogic.ProductionModeEnabled=%STARTMODE% -
Djava.security.policy="%WL_HOME%\server\lib\weblogic.policy" weblogic.Server
goto finish
:runAdmin
@echo on
"%JAVA_HOME%\bin\java" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%" -
Dweblogic.Name=%SERVER_NAME% -Dbea.home="C:\WebLogic\WL7.0" -
Dweblogic.disableMBeanAuthorization=true -
Dweblogic.management.anonymousAdminLookupEnabled=true -
Dweblogic.management.username=%WLS_USER% -Dweblogic.management.password=%WLS_PW% -
Dweblogic.ProductionModeEnabled=%STARTMODE% -
Djava.security.policy="%WL_HOME%\server\lib\weblogic.policy" weblogic.Server
WebSphere Application Server
Prerequisites for WebSphere Versions 8.x and below
Prerequisites for WebSphere Version 9.x
Prerequisites for WebSphere Versions 8.x and below
For base deployment:
You have to modify the Performance Monitor Interface (PMI) Specification Level from "None" to "Standard". Then
deploy the perfServletApp.ear file, which uses the PMI infrastructure to retrieve the performance information from
WebSphere Application Server, in the WebSphere. Restart WebSphere Application Server.
For Network deployment:
You have to modify the PMI Sepcifictaion Level from "None"to "Standard" in all the WebSphere Servers in Network
Deployment. Then deploy theperfServletApp.ear file, which uses the PMI infrastructure to retrieve the performance
information from WebSphere Application Server, in any one of the WebSphere Servers in the Network Deployment.
Restart WebSphere Application Server.
Note: Steps to check whether WebSphere monitor has been correctly set
To modify PMI specification level:
Connect to the Admin console - http://:/admin/
On the left-side tree, expand the Servers node.
Click on Application Servers link. This will display the list of servers running in the node.
Click on the server for which data collection has to be enabled.
In the Additional Properties table, click on Performance Monitoring Service.
Change the Initial specification level to "Standard" and then apply the changes. Also enable (select) Startup.
To deploy perfServletApp.ear:
Open the Admin console
Go to Applications then Application Types, then WebSphere Enterprise Applications.
Click Install and select local system.
Browse the perf servlet application then click ok.
The Default Path is //installableApps/PerfServletApp.ear
Accept all default options and select Next until finish then click Save.
After successfully installed this application, restart the node server once in order to work the perf servlet work
correctly.
Make sure that a WebSphere Admin User is added to the monitor group of the perfservletApp, if global security
is enabled in Websphere. To do so, go to WebSphere Admin console → Applications → Installed Applications →Choose perfservletapp → Security role to user group mapping → Choose Monitor Role → Associate the admin
user → Save directly to the master configuration.
To check the perf servlet output, open the following url from your browser:
http://localhost:/wasPerfTool/servlet/perfservlet?connector=SOAP&port=8880 - 9080 (Default)
Steps to Check whether Websphere monitor has been correctly set
For Base Deployment:
To ensure whether the PMI & perfServletApp are configured properly in WebSphere, invoke the below URL &
check whether the data is returned in XML format.
http://WebSphereHost:Port/wasPerfTool/servlet/perfservlet?connector=SOAP&port=SOAP-PORT
where
WebSphere Host - Host in which WebSphere Application Server is running
WebSphere Port - HTTP Transport port of the WebSphere Application server [How to locate HTTP Port]
SOAP Port - SOAP Port of WebSphere [How to locate SOAP Port]
For Network Deployment:
To ensure whether the PMI & perfServletApp are configured properly in WebSphere, invoke the below URL &
check whether the data is returned in XML format.
http://WebSphereHost:Port/wasPerfTool/servlet/perfservlet?connector=SOAP&port=NetworkDeployerSOAP-
PORT&HOST=NetworkDeployerHost
where
WebSphere Host - The host of the websphere application server in which the perf servlet application is
installed
Websphere Port - HTTP Transport port of the Websphere server in which the perf servlet application is
installed [How to locate HTTP Port]
NetworkDeployer SOAP PORT - The SOAP port of the Deployment manager (DMGR) [How to locate SOAP Port]
Network Deployer Host - The host in which the Deployment manager is running.
Note: Also check whether WebSphere admin user is added to the monitor group of the perfservletApp.
How to locate SOAP Port?
1. Login to Admin console
2. Expand the server link on left side tree. Click on Application Servers
3. In Base mode, various WebSpheres will be listed down. Click on the WebSphere''s name- > Under Additional
Properties, click on End Points link -> click on SOAP connector address. You can get the SOAP port from there.
4. In Network Deployment mode, Click DMGR - > Under Additional Properties, click on End Points link -> click on
SOAP connector address - You can get the SOAP port from there.
How to find the HTTP Transport port?
1. Login to Admin console
2. Expand the Server link on left side tree, Click on Application Servers
3. Various WebSpheres will be listed down. Click on the WebSphere''s name- > Under Additional Properties, click
on Web Container link -> click on HTTP Transports link. You can get the HTTP port from there.
Prerequisites for WebSphere Versions 9:
Enable Performance Monitoring Infrastructure (PMI) in application server (for base mode), and in all
application servers and the node agents ( in ND mode ) which you want to monitor.
Go to Websphere Console, then Servers and All servers.
Click on the server name, then "Performance Monitoring Infrastructure (PMI)" under "Performance" tab.
Check the box "Enable Performance Monitoring Infrastructure".
Click Apply, Save and Restart the server.
If global security is enabled, provide username and password of user with adminitrative role.
Go to the Websphere Console, System Administration then Node agents
Click on the node agent, then "Performance Monitoring Infrastructure (PMI)".
Check the box "Enable Performance Monitoring Infrastructure".Click Apply, Save and Restart the server.
For Network deployment mode, enable Global security
Go to the Websphere Console, go to Security then Global Security.
Under "Administrative security", check "Enable administrative security".
Click Apply, Save and Restart the server.
SSL certificates has to be added to APM incase SSL is enabled or Global security is enabled.
Steps: https://pitstop.manageengine.com/portal/kb/articles/how-to-import-certificates-for-monitoring-
websphere-application-server-with-ssl-authentication
Resin Server
JMX MBeans are used to monitor Resin Application server''s activity. To enable JMX, open Resin.XML and add the
below JVM arguments or start Resin.exe with the below JVM arguments
-Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
Replace 1099 with the actual port number of the JMX agent
Jetty Server
JMX MBeans are used to monitor Jetty server''s performance. To enable JMX,
Add the below JVM arguments on Jetty start up:
-Dcom.sun.management.jmxremote.port=9999
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote
Replace 9999 with the actual port number of the JMX agent
Add the following line in start.ini file --module=jmx
Apache Geronimo
To monitor Apache Geronimo Server, add the following java runtime options to the startup file of your application:
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=1999
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
Replace 1999 with the any free port available.
You can find the startup file here : /bin
Database Servers
IBM Informix ServerJDBC Driver:
To monitor IBM Informix DB, make sure that the ifxjdbc.jar file is present in the location:
\working\classes directory. The jar file can be copied from the IBM Informix installation location,
\jdbc\lib\jar. Restart Applications Manager after copying the file.
User Privileges:
To add an Informix DB monitor, a user requires Connect database-level privileges and he should be able to access
sysmaster database.
Microsoft SQL Database Server
For monitoring a Microsoft SQL database server, the SQL user account used for monitoring should have access to
MASTER, MSDB and DISTRIBUTION databases. User should have the following roles:
sysadmin server role : Go to SQL Server Management Studio → Go to Logins → Choose the respective user and
open properties → Go to ''Server roles'' and select sysadmin role → Save the option and proceed with adding the
SQL monitor in Applications Manager.
(OR)
1. Provide VIEW SERVER STATE permission on the server to the respective SQL user.
To grant VIEW SERVER STATE, you can use any of the following methods :
i) Execute the following query:
GRANT VIEW SERVER STATE TO username;
ii) In SQL Management Studio for user Choose Properties → Securables → Click Add ( under Securables ) →
Choose ''All objects of the Types...'' → Choose Servers → Choose Grant for ''View server state'' permission.
2. Provide the following DB roles:
DB Role required for all databases: public, db_datareader (To see key metrics in all databases)
DB Role required for msdb database: public, db_datareader, SQLAgentReaderRole,
SQLAgentOperatorRole (For SQL Jobs monitoring/Log Shipping monitoring/Replication monitoring)
DB Role required for distribution database: public, db_datareader (For SQL Replication monitoring)
DB role required for monitoring DBCC CHECKDB & DBCC DBREINDEX/INDEXDEFRAG commands:
db_writer
To monitor AlwaysOn Availability Groups in Applications Manager, the admin must provide view any definition
permission on the server to the respective SQL user. To do so, you can use any of the following methods:
(i) Execute the following query:
GRANT VIEW ANY DEFINITION TO username;
(ii) In SQL Management Studio, for user, choose Properties → Securables → click Add ( under Securables )
→ choose ''All objects of the Types...'' → Choose Servers → Choose Grant for ''view any definition'' permission.
MongoDB Servers
Supported Versions: MongoDB 4.2 and older versions. We support mongod services and mongos services
If the MongoDB instance is authenticated, the User should have ''clusterMonitor'' role to fetch performance
metrics of MongoDB.
To monitor OpLog details, add the Mongo client (mongo.exe/mongo) file under /working/classes directory. For Linux installation, execute the command : sudo apt install mongodb-
clients and grant executable permission to the Mongo client using CHMOD command.
To download the mongo client, click on any of the following links for respective operating systems:
Older versions of Windows from 2008 to 8
Windows 10
Ubuntu 16.04
Ubuntu 18.04
For other operating systems, refer here.
Note: MongoDB of versions 3.4 & above is not supported in 32-bit Windows and Linux OS.MySQL Database Servers
MySQL monitor requires MySQL Java Connector to be present in the Applications Manager classpath. You can
verify this by following these steps:
Check /working/mysql/MMMySQLDriver/ directory for the file
mysql_connector.jar
If the .jar file is not present, you can download it from here (for MYSQL versions older than 5.6) or here(for
MYSQL version 5.6 and newer).
If you are using multiple MySQL servers with various versions, then you must download the new jar file.
Note: If any MySQL server is enabled with ''SSL Configuration'' or MySQL server is hosted on any cloud
platform, then please use the latest mysql_connector jar file.
Extract the downloaded zip file.
Find mysql-connector-java-3.0.10-stable-bin.jar or mysql-connector-java-5.1.46.jar file and rename the file
as mysql_connector.jar
In the machine, where Applications Manager is running, copy the downloaded mysql_connector.jar to
/working/mysql/MMMySQLDriver/ directory.
Restart Applications Manager.
Privileges Required :
While monitoring a MySQL database server, ensure that you assign a username that has permission to access the
MySQL database from the host where Applications Manager is running. An alternate way is to add a relevant user
who has the privileges to do the same. The user should have privileges to execute SELECT, SHOW DATABASES,
REPLICATION commands in the MySQL server.
For enabling these privileges, execute the following commands in the remote MySQL Server:
If MySQL version is below 5.7:
To create a new user in mysql database:
USE mysql;
INSERT INTO user (Host,User) VALUES('''','''');
Granting privileges required for DB-user to monitor MySQL DB-sever:
GRANT SELECT,SHOW DATABASES,REPLICATION CLIENT,REPLICATION SLAVE ON *.* TO
''''@'''';
FLUSH PRIVILEGES; (Use the host name - Applications Manager machine).
If MySQL version is 5.7:
To create a new user in mysql database:
USE mysql;
CREATE USER @''%'' IDENTIFIED BY ''password'';
Granting privileges required for DB-user to monitor MySQL DB-sever:
GRANT SELECT,SHOW DATABASES,REPLICATION CLIENT,REPLICATION SLAVE ON *.* TO
''''@'''';
FLUSH PRIVILEGES; (Use the host name - Applications Manager machine).
If MySQL version is 8.0 and above:
To create a new user in mysql database:
USE mysql;
CREATE USER ''''@'''' IDENTIFIED WITH mysql_native_password BY ''password'';
Granting privileges required for DB-user to monitor MySQL DB-sever:GRANT SELECT,SHOW DATABASES,REPLICATION CLIENT,REPLICATION SLAVE ON *.* TO
''''@'''';
FLUSH PRIVILEGES; (Use the host name - Applications Manager machine).
For MariaDB:
GRANT SELECT,SHOW DATABASES,REPLICATION SLAVE ADMIN,REPLICATION MASTER ADMIN ON *.* TO
''''@'''';
FLUSH PRIVILEGES; (Use the host name - Applications Manager machine)
Prerequisites for MySQL SSL sever monitoring:
User account requires tls_option.
ALTER USER ''''@'''' REQUIRE ; [ tls_option: { SSL | X509 | CIPHER ''cipher''
| ISSUER ''issuer'' | SUBJECT ''subject'' } ]
Add the client certificates and its root certificates in apm.keytore file under /working/cert/ directory.
Add the monitor by enabling ''SSL'' option in Add New Monitor page. If the monitor is already added, update
the ''SSL'' option in Edit Monitor page.
Oracle Database Servers
A user with CONNECT and SELECT_CATALOG_ROLE roles are required for Oracle monitoring in Applications
Manager. Configure a user with these permissions and use the credentials in Applications Manager
Prerequisites for monitoring Oracle Alert Log metrics
Login as SYS user and run the following queries:
Create or replace view v_$appman_alertlog_ext as select * from x$dbgalertext
Create or replace public synonym v$appman_alertlog_ext for sys.v_$appman_alertlog_ext
Grant select on v$appman_alertlog_ext to [USERUSEDFORORACLEDBSERVERMONITOR]
For Oracle versions 12c & above:
Create or replace view appman_alertlog_vw as select * from x$dbgalertext
Create or replace public synonym appman_alertlog_view for sys.appman_alertlog_vw
Grant select on appman_alertlog_view to [USERUSEDFORORACLEDBSERVERMONITOR]
Note: Oracle DB Alert Log monitoring is supported for version Oracle 11g and above only.
Prerequisites for monitoring Oracle Redo Log metrics
Login as SYS user and run the following queries:
Create or replace view v_$appman_redolog_cp_ext as select * from x$kcccp
Create or replace public synonym v$appman_redolog_cp_ext for sys.v_$appman_redolog_cp_ext
Grant select on v$appman_redolog_cp_ext to [USERUSEDFORORACLEDBSERVERMONITOR]
Create or replace view v_$appman_redolog_le_ext as select * from x$kccle
Create or replace public synonym v$appman_redolog_le_ext for sys.v_$appman_redolog_le_ext
Grant select on v$appman_redolog_le_ext to [USERUSEDFORORACLEDBSERVERMONITOR]
For Oracle versions 12c & above:
Create or replace view appman_redolog_cp_vw as select * from x$kcccp
Create or replace public synonym appman_redolog_cp_view for sys.appman_redolog_cp_vw
Grant select on appman_redolog_cp_view to [USERUSEDFORORACLEDBSERVERMONITOR]
Create or replace view appman_redolog_le_vw as select * from x$kccle
Create or replace public synonym appman_redolog_le_view for sys.appman_redolog_le_vw
Grant select on appman_redolog_le_view to [USERUSEDFORORACLEDBSERVERMONITOR]Prerequisites for monitoring Oracle Data Guard metrics
Following are the prerequisites to monitor Oracle Data Guard metrics under RPO tab:
Database Role should be either PRIMARY or PHYSICAL STANDBY or LOGICAL STANDBY.
For PRIMARY database role, the Switch Over Status should not be as NOT ALLOWED.
The Database Role and Switch Over Status can be found by executing the following query:
SELECT database_role,switchover_status FROM v$database
Prerequisites for monitoring Oracle Pluggable Database (PDB) metrics
SYS or SYSTEM or Common user with CONNECT and SELECT_CATALOG_ROLE roles is required to monitor
Oracle PDBs.
If Common user is chosen for monitoring, then the below privilege has to be provided by connecting to the
CDB container with SYS user:
alter user set container_data=all container = current;
For example,
alter user C##APM set container_data=all container = current;
The C##APM user has now been given the SELECT role privilege to access all the objects.
PostgreSQL
If PostgreSQL is in remote server, it should allow connections from Applications Manager server. For this follow the
steps given below:
Allowing remote connection from Applications Manager in PostgreSQL
Open postgresql.conf file under /data
Check value of configuration parameter listen_addresses.If it is using the default value localhost, it must be
changed to TCP/IP address(es) on which the PostgreSQL has to listen for connections from Applications
Manager. You can change it to *(corresponds to all available IP interfaces) like below:
listen_addresses = ''*''
Click here for more details on configuring postgresql.conf file.
Open pg_hba.conf file under /data
Add the following new line to allow all PostgreSQL user remote connections from Applications Manager server:
host all all 0.0.0.0/0 md5
host all all ::0/0 md5
Click here for more details on configuring pg_hba.conf file.
User privileges required
Applications Manager uses PostgreSQL''s subsystem statistics collector & some built-in views such as pg_class,
pg_database, pg_indexes, pg_locks, pg_namespace, pg_proc, pg_replication_slots, pg_stat_statements,
pg_tables, pg_trigger, pg_user to monitor PostgreSQL server activity. The user provided for monitoring should have
at least read-only access to statistics collector and above mentioned views.
For PostgreSQL versions below 10:
Create a user with following privileges:
CREATE USER WITH PASSWORD '''';
GRANT SELECT ON pg_stat_database TO
To monitor replication metrics, the database user is required to have Replication privilege (if replication is
configured). Execute the below query to update the DB user with Replicationprivilege:
ALTER USER WITH Replication;
To list out configuration-related metrics & WAL file count, the database user is required to have Superuser
privilege. Execute the below query to update the DB user with Superuserprivilege: (optional)
ALTER USER WITH Superuser;
For PostgreSQL versions 10 and above:
To monitor all the metrics, execute the following query:CREATE ROLE WITH LOGIN NOSUPERUSER NOCREATEDB NOCREATEROLE INHERIT
REPLICATION CONNECTION LIMIT -1 PASSWORD ''xxxxxx'';
GRANT pg_monitor TO ;
GRANT EXECUTE ON FUNCTION pg_ls_dir(text) TO ;
Extensions to be enabled in PostgreSQL server:
To monitor top queries by CPU, include the below lines in postgresql.conf file:
shared_preload_libraries = ''pg_stat_statements''
pg_stat_statements.track = all
Then execute the below query in PostgreSQL:
CREATE EXTENSION pg_stat_statements;
After implementing the above steps, restart the PostgreSQL server.
Note: After implementing the above steps, a restart of the PostgreSQL server is required for the changes to
take effect.
Limitations in PostgreSQL Replication monitoring:
Replication is not monitored for PostgreSQL server version 9.0 & 9.1.
Master server and slave server should be on different machines.
More than one slave shouldn''t run on same machine.
Connections to any server (i.e either master or slave) via Unix socket cannot be monitored.
SAP ASE / Sybase SQL Server / Sybase ASE
Supported Versions: Applications Manager supports monitoring of Sybase ASE 12.5.3 and above.
To monitor a Sybase ASE database monitor, the minimum privileges required by the user are as follows:
There are select privileges for few tables in master database. They are:
master.dbo.systransactions
master.dbo.spt_values
master.dbo.sysprocesses
master.dbo.sysdatabases
master.dbo.syslogins
master.dbo.monProcessStatement
master.dbo.monProcessSQLText
master.dbo.monOpenDatabases
User with mon_role, to execute a system procedure named as "sp_monitorconfig"
To provide the privileges mentioned above, use the following commands in Sybase ASE database:
exec sp_role ''grant'', ''mon_role'', ; (login-name assigned to the user)
grant select on master.dbo.systransactions to ;
grant select on master.dbo.spt_values to ;
grant select on master.dbo.sysprocesses to ;
grant select on master.dbo.sysdatabases to ;
grant select on master.dbo.syslogins to ;
exec sp_configure ''enable monitoring'', 1
exec sp_configure ''statement statistics active'', 1
exec sp_configure ''per object statistics active'', 1
Note: Execute the above commands in the Sybase SQL shell.SAP HANA
Copy the ngdbc.jar file into the location /working/classes. ngdbc.jar can be
copied from installed SAP HANA Client folder. Click here to download SAP HANA Client
If HANA is running On-demand, in addition to the above, SAP Cloud Platform SDK is needed. However, this is
not needed for HANA On-premise. Click here to download SAP Cloud Platform SDK. The downloaded zip should
be extracted under /working/hanacloud folder. After extracting, verify whether
/working/hanacloud/tools folder is available.
Restart Applications Manager after performing the above steps.
Provide the below privileges for SAP HANA DB User.
System privilege CATALOG READ.
Object privilege SELECT on the schema _SYS_STATISTICS.
To grant the above privileges, execute the below statements in SAP HANA SQL console.(Replace USER_NAME
with actual HANA DB Username)
GRANT MONITORING to < USER_NAME >
CALL GRANT_ACTIVATED_ROLE (''sap.hana.admin.roles:Monitoring'',''< USER_NAME >'')
SAP MaxDB
Following are the prerequisites to be implemented to monitor SAP MaxDB in Applications Manager:
X-Server should be running.
sapdbc.jar file should be copied to \working\classes folder. By default, this jar
will be available in SAP MaxDB installation folder under \runtime\jar\ directory.
SQL Anywhere
Applications Manager supports the monitoring of SQL Anywhere from version 17. We use system procedures for
monitoring the SQL Anywhere server.
To monitor SQL Anywhere server, the DB user must have the following privileges:
Privilege to manage any DBspace.
Any one of the following roles: Monitor or Server Operator or Drop connection
To know more about system privileges, click here.
Note: Only databases that can be accessed with the given user credentials will be monitored.
IBM DB2
A DB2 user with SYSMON instance level authority is required for monitoring DB2 server.
Long Running Queries (Available from version 9.7 & above):
To monitor ''Long Running Queries'', the user must have the following authorization:
SELECT privilege on the MON_CURRENT_SQL administrative view
Session details (Available from version 9.7 & above):
To monitor ''Session details'', the user must have any one of the following authorizations:
Execute privilege on the routine ''SYSPROC.MON_GET_CONNECTION''
Minimum User Privileges:
For monitoring IBM DB2 v.8 and v.9, the user should be able to access the SYSPROC procedures.
For monitoring IBM DB2 v.10 & above, the user should be able to access the SYSIBMADM functions and
SYSPROC procedures.
Granting a privilege to user:
Login to DB2 command line processor and execute below statement:GRANT ON DATABASE TO USER
where, can be any one of the following: CONNECT, LOAD
To learn how to grant a privilege to a user, refer here.
CLOUD APPS
Microsoft Azure
Microsoft Azure Monitor can be added using 3 methods,
AD Application & Service Principal – Mode 1
Azure Organizational Account (Powershell) – Mode 2
OAuth mode – Mode 3
Discovery using AD Application & Service Principal – Mode 1
For Microsoft documentation, refer https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-
group-create-service-principal-portal
1. Create Active Directory Application:
Log in to Azure Portal (https://portal.azure.com) using the credentials of Microsoft account (@outlook.com or
@live.com) using which the subscription was created.
Select Azure Active Directory.
Select App registrations.
Select New registration.
After entering relevant details, click Register.
2. Getting Tenant ID, Client ID and Client Secret(Application Key):
Tenant ID:
Select Azure Active Directory.
From App registrations in Azure AD, select your application.
Copy the value given as Directory (tenant) ID. This is your Tenant ID.
Client ID:
Select Azure Active Directory.
From App registrations in Azure AD, select your application.
Copy the value given as Application (client) ID. This is your Client ID.
Client Secret(Application Key):
Select Azure Active Directory.
From App registrations in Azure AD, select your application.
Select Certificates & secrets.
Select Client secrets -> New client secret.
Provide a description of the secret, and a duration. (Preferrably 24 months)
select Add.
Credential will be updated for the same AD Application and copy the new Client Secret Value and this is
the Client Secret(Application Key).
To know more about creating the Client Secret, refer here.
3. Assign a role to the application:
Select Subscriptions from he home page.
Select the particular subscription to assign the application to.Select Access control (IAM).
Select Add > Add role assignment to open the Add role assignment page.
Select the role you wish to assign to the application.
Select the role as Owner or Contributor and click Next.
Select User, group, or service principal in Assign access to option.
In Members option, click on Select Members and search for the name of your application and select it.
Select Review + Assign to finish assigning the role.
To know more about assigning a role to the application, refer here.
4. Provide the Client ID, Tenant ID and Application Key(Client Secret) in the Azure new monitor page of
Applications Manager.
Discovery using Azure Organizational Account (Powershell) – Mode 2
1. Installing the Powershell module on Applications Manager server:
For Applications Manager versions 15170 onwards, you must install the Az Powershell module.
To install the Az Powershell module, follow the below steps:
Open Powershell prompt with Administrator privileges. Run the following commands:
# Install the Az module from the PowerShell Gallery
Install-Module -Name Az -RequiredVersion 6.2.1
To check if the modules are installed successfully:
Open Powershell prompt with Administrator privileges. Run the following command,
Connect-AzAccount
If this opens a pop-up asking for Azure credentials, this means the required modules are installed successfully.
For further troubleshooting regarding installing the module, refer https://docs.microsoft.com/en-
us/powershell/azure/install-az-ps?view=azps-6.2.1
Note:
If you already have the AzureRM Powershell installed, you will have to uninstall it before you install the Az
Powershell module using the below command:
Uninstall-AzureRm
If you face any problems, kindly refer this link.
For Applications Manager versions till 15160, you must install the AzureRM Powershell module.
To install the AzureRM Powershell module, follow the below steps:
Open Powershell prompt with Administrator privileges. Run the following commands:
# Install the Azure Resource Manager modules from the PowerShell Gallery
Install-Module AzureRM
In case if you get the following error upon executing the above command, then install the downloader from
http://aka.ms/webpi-azps
Install-Module: The term ‘Install-Module’ is not recognized as the name of a cmdlet, function, script file or
operable program
To check if the modules are installed successfully:
Open Powershell prompt with Administrator privileges. Run the following command,
Login-AzureRmAccount
If this opens a pop-up asking for Azure credentials, this means the required modules are installed successfully.
2. Create an Organizational account using Microsoft Azure administrator permissionsLog in to Azure Portal (https://portal.azure.com/) using the credentials of Microsoft account (@outlook.com or
@live.com) using which the subscription was created.
Select Active Directory.
Select the default directory
Select Users, and then select New user.
On the User page, enter required information for this user - Username, First name, Last name, Groups, and
Role.
Note down the Email ID and the password of your user (Autogenerated in the Password box after entering the
above details).
Select Create.
3. Assign the Global administrator role to your organizational account
Log in to Azure Portal (https://portal.azure.com/).
Search for and select Active Directory.
Select Users.
Select the user for which Global administrator role needs to be assigned.
On the User Profile page, select Assigned Roles and then click on Add assignment.
Search for and select the role Global administrator.
After selecting the role, click on Add button.
The Global administrator role will be assigned to the required user.
After performing all the above steps,
Sign out of the current account.
Sign in using the newly created Email address and temporary password
You will be prompted to change the password, when logging in for the first time
Change and note down the new password
Provide this Email ID to ‘User Email’ field and Password to ‘Password’ field in the New monitor page, while using
the mode ‘Azure Organizational Account (Powershell) of Applications Manager.
OAuth mode – Mode 3
For Microsoft documentation, refer https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-
group-create-service-principal-portal1. Create Active Directory Application:
Log in to Azure Portal (https://portal.azure.com) using the credentials of Microsoft account (@outlook.com or
@live.com) using which the subscription was created.
Select Azure Active Directory.
Select App registrations.
Select New registration.
After entering relevant details, click Register.
2. Getting Tenant ID, Client ID and Client Secret:
Tenant ID:
Select Azure Active Directory.
From App registrations in Azure AD, select your application.
Copy the value given as Directory (tenant) ID. This is your Tenant ID.
Client ID:
Select Azure Active Directory.
From App registrations in Azure AD, select your application.
Copy the value given as Application (client) ID. This is your Client ID.
Client Secret:
Select Azure Active Directory.
From App registrations in Azure AD, select your application.
Select Certificates & secrets.
Select Client secrets -> New client secret.
Provide a description of the secret, and a duration. (Preferrably 24 months)
select Add.
Credential will be updated for the same AD Application and copy the new Client Secret Value and this is
the Client Secret.
To know more about creating the Client Secret, refer here.
3. Assign a role to the application:
Select Subscriptions from he home page.
Select the particular subscription to assign the application to.
Select Access control (IAM).
Select Add > Add role assignment to open the Add role assignment page.
Select the role you wish to assign to the application.
Select the role as Owner or Contributor and click Next.
Select User, group, or service principal in Assign access to option.
In Members option, click on Select Members and search for the name of your application and select it.
Select Review + Assign to finish assigning the role.
To know more about assigning a role to the application, refer here.
4. Provide the Client ID, Tenant ID and Client Secret in the Azure new monitor page of Applications Manager.
4. App Registration Permissions
Select your created application under Azure Active Directory → App Registration.
In the application''s Overview page, click on ''API Permissions'' available on the left pane.
Click on ''Add a Permission'' option, select ''Azure Service Management'' and choose ''Delegated Permissions''.
Select the ''user_impersonation'' permission and then click on ''Add Permissions''.
Finally, click on ''Grant admin consent for APM'' button.Steps to create an OAuth Provider for Azure monitor:
In Applications Manager, go to Settings → OAuth Provider and select Add OAuth Provider. (Make sure you
are logged in from a fully qualified domain name as in the help card)
Copy the Redirect URL from the Add OAuth Provider window.
In the Microsoft Azure console, go to Azure Active Directory from the left pane, select App Registrations and
click on the required application.
In the application''s Overview page, click on the link available under Redirect URIs and paste the Redirect
URL copied from the Add OAuth Provider window. Click Save.
Now copy the App ID, Client Secret and Tenant ID obtained in the above steps and fill in the Add OAuth
Provider window.
Fill the required details as mentioned below:
Grant Type - Authorization Code
Authorization Endpoint URL - https://login.microsoftonline.com//oauth2/authorize
Token endpoint URL - https://login.microsoftonline.com//oauth2/token
Token request method - Post request body
Request body:
Name - resource
Value - https://management.azure.com/
Authenticated request method - Basic Authentication
Note: Remaining fields should remain as default.
Click Authorize button and authorize using the account to login to Azure.
Once created, verify whether both Access token and Refresh token are generated.
Use this OAuth Provider in the Microsoft Azure''s New Monitor page.
Azure Virtual Machines
Enabling Diagnostic Extension for Windows and Linux VMs
Enabling Guest OS monitoring
Enabling Diagnostics Extension for Windows & Linux VMs
Steps to Enable Diagnostics Extension for Windows VMs:
Log in to Azure Portal (https://portal.azure.com) using the credentials of ''Administrator''
Navigate to your virtual machine.
Click on ''Diagnostics settings'' on the vertical pane. Select ''Agent'' tab and click on ''Remove'' at the bottom, as
shown in the below image.
Under ''Overview'' tab, click on ''Enable guest level monitoring'' and click Save as shown in the image below.In Performance counters tab, all the Basic metrics are chosen by default, and the metrics monitored in
Applications Manager are included in it. If the user wants to enable diagnostics only for the monitored
metrics, select Custom and select the below-listed metrics and click Save.
Metric Name in Azure Portal Metric Name in Applications Manager
\\Processor Information(_Total)\\% User Time User Time
\\Processor Information(_Total)\\% Privileged Time Privileged Time
\\Processor Information(_Total)\\Processor Frequency Processor Frequency
\\System\\Processes Process Count
\\System\\Context Switches/sec Context Switches/sec
\\Process(_Total)\\Thread Count Thread Count
\\Process(_Total)\\Handle Count Handle Count
\\Memory\\Committed Bytes Committed Bytes
\\Memory\\Available Bytes Available Bytes
\\Memory\\% Committed Bytes In Use Committed Bytes In Use
\\Memory\\Page Faults/sec Page Faults/sec
\\Memory\\Pool Paged Bytes Pool Paged Bytes
\\Memory\\Pool Nonpaged Bytes Pool Nonpaged Bytes
Restart the VM
Steps to Enable Diagnostics Extension for Linux VMs:
Log in to Azure Portal(https://portal.azure.com) using the credentials of ''Administrator''
Navigate to your virtual machine.
Click on ''Diagnostics settings'' on the vertical pane under ''Monitoring''.
To uninstall the old diagnostic agent and reinstall again, go to ''Agent'' and click ''Remove'' to remove the
current diagnostic agent. On the same page, now choose a storage account from the dropdown and then click
''Enable guest-level monitoring'' to enable the VM diagnostic.
To reduce the amount of data stored in Storage Account tables, configure only the required diagnostics
instead of all.
Once the diagnostic settings are updated successfully, in the same pane, click ''Metrics'' and then click ''Custom''
and remove the unwanted metrics. Refer to the below image to view the required metrics and their configuration.Also, set the aggregation intervals to 1 minute (Choose only ''PT1M'' and remove other intervals like ''PT1H'', ''PT5M'',
etc.) and finally click ''Save'' to save the configuration.
Note:
In Applications Manager, we retrieve the VM diagnostics only from the PT1M tables.
Configuring only the required metrics and setting the aggregation to 1 minute is mainly to reduce your
Azure Storage cost by avoiding unwanted storage. In addition, it removes the old tables from the
configured Storage Account to minimize the Storage cost.
Metric Name in Azure Portal Metric Name in Applications Manager
/builtin/disk/averagereadtime Average Read Time
/builtin/disk/averagewritetime Average Write Time
/builtin/memory/availablememory Available Memory (MB)
/builtin/memory/percentusedswap Used Swap memory (%)
/builtin/memory/usedmemory Used Memory (MB)
/builtin/memory/percentavailablememory Available Memory (%)
/builtin/processor/percentidletime Idle Time
/builtin/processor/percentiowaittime IO Wait Time
/builtin/processor/percentprocessortime Processor Time(Linux)
To check whether the diagnostic agent is working properly by storing the diagnostic metrics in the configured
Storage Account:
In the Azure portal, go to Virtual Machine and click ''Metrics'' under ''Monitoring'' in the left pane.
Make sure the ''Scope'' is pointing to the respective Virtual Machine and choose ''Guest (Classic)'' in ''Metric
Namespace'' dropdown.
Choose any one metric, let us check by choosing ''CPU idle time'' in ''Metric'' dropdown and check the data
points for the current timestamp as below:
GENERAL BEHAVIOUR
Under the tab ‘Disk’, below ‘Disk spacing’ section, the disk size will be shown as 0, if disk size is not
configured for the virtual machine in portal.
To set disk size in portal, refer https://blogs.msdn.microsoft.com/madan/2016/09/28/resize-azure-resource-
manager-arm-vm-os-data-disk-using-azure-portal/
Note: In case if you change the resource group of any Virtual machine in Azure portal, then provide the updated
details (Virtual Machine ResourceID and Resource Group Name) in the Edit monitor page of that Virtual
machine in Applications Manager for data collection to happen.
Enabling Guest OS monitoring:
Metrics monitored when Guest OS monitoring is enabled
Disk UtilizationDisk IO Statistics
Network Interface
Service Monitoring
Note: Guest OS metrics will be available only in Windows installations of Applications Manager for Windows
VMs alone.
1. Perform the below steps in Azure Portal.
Log in to Azure Portal.
Open Azure Cloud Shell.
Execute the following command
Enable-AzVMPSRemoting -Name ''vm-hostname'' -ResourceGroupName ''vm-resourcegroupname'' -Protocol
https -OsType Windows
Where you need to replace ''vm-hostname'' and ''vm-resourcegroupname'' with the Name and Resource group
name of the VM for which the Guest OS metrics need to be monitored.
This enables PowerShell remoting for the respective VM with HTTPS protocol. To know more, click here.
2. Run Applications Manager with administrator privilege.
3. Perform the below steps in Applications Manager Server to enable Powershell Remoting (To collect metrics
by remoting into Azure VMs).
Open Powershell prompt with Administrator privileges.
Execute the following commands:
Set-ExecutionPolicy Unrestricted
If the above cmdlet produces an Error as below, you can configure Powershell Script Execution via Group
Policy Editor:
#To configure Windows PowerShell for remoting, type the following command:
Enable-PSRemoting -force
#To configure the TrustedHosts setting to ensure that appmanager can trust the connections from other
servers :
Set-Item wsman:\localhost\client\trustedhosts *
#To increase the maximum number of concurrent shells that a user can remotely open:
Set-Item WSMan:\localhost\Shell\MaxShellsPerUser -value 25 -WarningAction SilentlyContinue
#To set idle timeout value for sessions : Determines how long the session stays open if the remote computer
does not receive any communication from the local computer, including the heartbeat signal. When the
interval expires, the session closes:
Set-Item WSMan:\localhost\Shell\IdleTimeout -value 60000 -WarningAction SilentlyContinue
#Restart the WinRM service for changes to take effect:
Restart-Service WinRM
Configure Powershell Script Execution via Group Policy Editor
Open the Group Policy Editor from Control Panel→ Edit Group Policy (or) run gpedit.msc from Start menu.
To configure, navigate under Computer Configuration to Policies\Administrative Templates\Windows
Components\Windows PowerShell.
You should see a setting called Turn on Script Execution like in the following image:Double-click the setting. You will want to enable it and select an option from the drop down.
Set it to “Allow All Scripts”.
Click Apply and OK.
Microsoft Azure SQL Database
Following are the prerequisites to monitor Database Query Statistics in Azure SQL Database monitor:
Firewall rule configuration in portal:
In Azure portal, navigate to the Azure SQL database to be monitored -> Click on Overview -> Select Set
Server Firewall -> Add your Client IPs to the list. Client should add all his public IPs under the firewall
settings in SQL server.
Refer link for setting server firewallAllowing outgoing access on port 1433:
For Applications manager to access and monitor the Azure SQL database, ensure that the firewall on your
network and Applications Manager installed server allows outgoing communication on TCP port 1433.
Azure Kubernetes Service (AKS)
Install AzureCLI: Install the Azure CLI on any Applications Manager-installed machine (Windows or Linux) to
configure cluster with kubectl for monitoring. Learn more
Install Kubectl: Install the latest Kubectl utility executable (kubectl.exe) file by executing the following
command in command prompt:
az aks install-cli --client-version [client-version]
where, [client-version] refers to the compatible client-version to be installed.
If kubectl is already installed, make sure to find out the version of the kubcetl using the command kubectl
version --short --clientin command prompt. If the version is incompatible, then install the latest version
as stated above in Step 2.
Note: Choose the supported kubectl version for your AKS cluster by using one minor version older or
newer of kubectl relative to your cluster''s Kubernetes version (kube-apiserver), consistent with the
Kubernetes support policy for kubectl. The cluster''s Kubernetes version can be found in the Azure
portal itself.
Alternatively, you can add kubectl to the system environment path by adding the kubectl installed
directory in system path under Environment Variables → System → Path. However, you can ignore this
step either if you have already specified your kubectl installed directory in system path of environment
variable or have installed kubectl under \workingdirectory in Windows.
Note: Make sure to restart Applications Manager after configuring the environmental variable to run
kubectl commands.
Configure Container Insights: To fetch metrics from Container Insights, you can do so using the az aks
addoncommands. Execute the following command to enable/disable Container Insights:
To enable Container Insights: az aks addon enable
To disable Container Insights: az aks addon disable
Enable Cluster Autoscaler: To fetch Cluster Autoscaler metrics, you need to enable and configure the cluster
autoscaler on the node pool of the AKS cluster. You can enable the cluster autoscaler either while creating acluster or for an existing cluster via Azure CLI. Learn more
Microsoft 365
Prerequisites for adding the monitor
Prerequisites for enabling Service Health monitoring
Prerequisites for adding the monitor:
The Microsoft 365 work or school account that you use for these procedures needs to be a member of an
Microsoft 365 admin role. For more information, see About Microsoft 365 admin roles. The Microsoft 365
admin account used for monitoring must be assigned the below roles: Exchange administrator, SharePoint
administrator, or Microsoft Teams administrator.
Limitation: Accounts with multi factor authentication are not supported.
You can use the following 64-bit versions of Windows:
Windows 10
Windows 8.1 or Windows 8
Windows Server 2019
Windows Server 2016
Windows Server 2012 R2 or Windows Server 2012
Windows Server 2008 R2 SP1*
* You need to have the Microsoft .NET Framework 4.5 or higher version installed and Windows Management
Framework 5.1 installed. For more information, see Installing the .NET Framework and download the latest version
of Windows Management Framework.
You need to use a 64-bit version of Windows because of the requirements for the Microsoft 365 modules.
PowerShell version 4 or above.
To check the PowerShell version installed, open up a PowerShell prompt and execute the below command:
>$PSVersionTable
Check for the PSVersion attribute from the output to find out the version.
You need to install the following modules to monitor Microsoft 365:
Microsoft Online Service Sign-in Assistant for IT Professionals RTW (Needed for Windows Server 2012 &
below) Learn more
Windows Azure Active Directory Module for Windows PowerShell
SharePoint Online Powershell Module
Exchange Online PowerShell V2 module (EXO V2 module)(Optional)
Note: For huge mailbox data, we prefer the optimized EXO module to connect and fetch data. In that
case, enable ''Use Exchange Online Powershell V2 Module'' check-box in Exchange Online Edit
Monitor page and install the EXO module for collecting Exchange Online Mailbox statistics.
Microsoft Teams PowerShell module: (for Applications Manager versions 15110 & above)
Open PowerShell window in Admin mode and execute the below command:
Install-Module MicrosoftTeams -RequiredVersion 2.3.1
If error occurs and asks to use -AllowClobber, then execute the below command:
Install-Module MicrosoftTeams -RequiredVersion 2.3.1 -AllowClobber
Once done, execute the below command to install the Preview version:
Install-Module PowerShellGet -Force -AllowClobber
Once done, close the PowerShell window. Then open a new window and execute the below
command:
Install-Module MicrosoftTeams -AllowPrerelease -RequiredVersion "1.1.9-preview"Windows PowerShell needs to be configured to run scripts for data collection. To do this, execute the
following command in an elevated Windows PowerShell session (a Windows PowerShell window you open by
selecting Run as administrator).
To configure Windows PowerShell for remoting, type the following command:
Enable-PSRemoting -force
Configure the TrustedHosts setting on Applications Manager machine, so that remote computers can trust
it:
Set-Item wsman:\localhost\client\trustedhosts *
Set Execution Policy:
Set-ExecutionPolicy Unrestricted
Restart the Windows Remote Management (WinRM) so the new settings will take effect:
Restart-Service WinRM.
Enable TLS 1.2:
Using TLS 1.2 with Office Online Server requires strong cryptography in .NET Framework 4.5 or higher. To enable
strong cryptography in .NET Framework 4.5 or higher, add the following registry keys:
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\.NETFramework\\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\.NETFramework\\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
To add the above registry keys via cmd prompt:
Open command prompt -> Run as administrator :
Enter the below :
REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 /v
SchUseStrongCrypto /t REG_DWORD /d 1
REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v
SchUseStrongCrypto /t REG_DWORD /d 1
Prerequisites for enabling Service Health Monitoring
Go to https://portal.azure.com/ and login with the Microsoft 365 admin credentials.
Go to App Registrations and choose New Registration
Enter a name and click Register.
In the Overview page of the application, copy the Directory (Tenant) ID and Application (Client) ID
Go to API Permissions → choose Add a permission
Select Microsoft Graph → Application permissions → ServiceHealth → ServiceHealth.Read.All and click
Add permission.
Choose Add a permission and select Microsoft Graph → Application permissions → Reports →
Reports.Read.All and click Add permission.
Now grant Admin access for the tenant.
Go to Certificates & Secrets → New Client secret
Add a name in Description, select Expires as Never and click Add.
Copy the value of that Client Secret.
Now paste all the copied values into their respective textboxes in the Add Monitor page and proceed.
AWS Monitoring
In Applications Manager, we require AWS Access keys [Access key & Secret Access key] to authenticate and
retrieve key performance metrics from AWS portal. Click here to know more about access keys.
In addition to secret keys, we also require ''List'' and ''Read'' action type Amazon APIs permissions. Furthermore, we
require ''Write'' action type APIs permissions for Amazon EC2 actions [Start, Stop, Reboot] actions alone.
By default, AWS users with administrator privileges have access to all the AWS Services APIs. If the user wishes to
grant admin access privileges, he can provide the admin user access keys to configure AWS monitor. If the user
however, wishes to provide limited permissions access keys, then he needs to create a separate policy with the
required APIs and attach this policy to an IAM user. This can be done directly or can be attached to the ''Group'' in
which the IAM user is associated.
Click here to know the steps involved in creating a policy and attaching it to the IAM user. There are two ways
to create a policy.In "Create Policy" page: If you choose "Visual Editor" tab, you can refer the columns "Service Name in AWS
Portal" and "List of APIs" in the below table, to identify the respective APIs for each AWS Service.
In "Create Policy" page: If you choose "JSON" tab, then you can copy & paste the policy content given below to
create the policy.
List of APIs required for each AWS Service supported in Applications Manager:
APM Service List of APIs
monitor/Category Name in
Name AWS Portal
STS
AWS monitor (Security
GetCallerIdentity
authentication/addition Token
Service)
To collect performance
metrics from CloudWatch GetMetricData, GetMetricStatistics
CloudWatch
Cost
Billing statistics Explorer GetCostAndUsage, GetCostForecast
Service
DynamoDB DynamoDB ListTables, DescribeTable, DescribeLimits, DescribeStream
EC2 (Elastic Compute DescribeVolumes, DescribeInstances, DescribeRegions,
EC2
Cloud) DescribeInstanceAttribute
EC2 Actions (start, stop
EC2 StartInstances , StopInstances, RebootInstances
& reboot instances)
Elastic DescribeEnvironments, DescribeEnvironmentResources,
Elastic Beanstalk
Beanstalk DescribeEvents
EC2 Auto
Elastic Beanstalk DescribeAutoScalingGroups
Scaling
Elastic DescribeClusters, DescribeContainerInstances, DescribeServices,
ECS (Elastic Container
Container DescribeTasks, ListClusters, ListContainerInstances, ListServices,
Service)
Service ListTasks
ELB (Elastic Load DescribeLoadBalancers, DescribeTargetGroups,
ELB v2
Balancing) DescribeTargetHealth
Lambda Lambda ListFunctions, GetFunction
RDS (Relational
RDS DescribeDBInstances, DescribeDBClusters
Database Service)
S3 (Simple Storage
S3 ListAllMyBuckets, ListBucket, GetBucketLocation
Service)
SQS (Simple Queue
SQS ListQueues, GetQueueAttributes
Service)
SNS (Simple
SNS ListTopics, ListSubscriptionsByTopic
Notification Service)
Elastic
EKS (Elastic Kubernetes ListFargateProfiles, DescribeNodegroup, ListNodegroups,
Kubernetes
Service) DescribeFargateProfile, DescribeCluster, ListClusters
Service
Policy content in JSON Format:
{ "Version": "2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": [
"eks:DescribeFargateProfile", "ec2:DescribeInstances", "cloudwatch:GetMetricData",
"dynamodb:ListTables", "ec2:DescribeRegions", "sns:ListTopics", "ce:GetCostAndUsage", "s3:ListBucket",
"ecs:ListServices", "elasticbeanstalk:DescribeEnvironmentResources",
"elasticloadbalancing:DescribeLoadBalancers", "eks:DescribeNodegroup",
"elasticbeanstalk:DescribeEnvironments", "ec2:StartInstances", "dynamodb:DescribeTable", "ecs:ListTasks",
"autoscaling:DescribeAutoScalingGroups", "ec2:DescribeVolumes", "rds:DescribeDBInstances",
"ecs:DescribeServices", "ecs:DescribeContainerInstances", "ecs:DescribeTasks","dynamodb:DescribeLimits", "ecs:ListClusters", "ec2:RebootInstances", "sqs:ListQueues",
"eks:ListNodegroups", "sns:ListSubscriptionsByTopic", "lambda:ListFunctions", "lambda:GetFunction",
"sqs:GetQueueAttributes", "dynamodb:DescribeStream", "cloudwatch:GetMetricStatistics",
"ec2:StopInstances", "ecs:DescribeClusters", "ce:GetCostForecast", "eks:ListFargateProfiles",
"s3:ListAllMyBuckets", "elasticbeanstalk:DescribeEvents", "elasticloadbalancing:DescribeTargetHealth",
"elasticloadbalancing:DescribeTargetGroups", "eks:DescribeCluster", "ecs:ListContainerInstances",
"eks:ListClusters", "sts:GetCallerIdentity", "s3:GetBucketLocation", "rds:DescribeDBClusters",
"ec2:DescribeInstanceAttribute " ], "Resource": "*" }]}
Note: You can refer to the screenshots below for your reference.
Using the Visual Editor to add a policy:
Using JSON format to add a policy:
Amazon EC2 Instances
To collect operating system-level metrics like Memory and Disk, you must deploy the Cloud-Watch Agent inside
EC2 instance. The agent will send your data to Cloud-Watch from where Applications Manager fetches and
displays it in the console. Click here to know more about how you can collect metrics from Amazon ec2 instances
and on-premises servers with the Cloud-Watch Agent.
AWS account users are required to use their AWS Access Key and Secret Access Key to add an AWS monitor in
Applications Manager. By default, AWS users have administrator privileges and can access AWS Service APIs.
However, if your AWS user account has limited permission, here is the list of APIs used to collect metrics from the
respective AWS services and performance metrics from CloudWatch:
EC2 - DescribeVolumes, DescribeInstances, DescribeRegions, DescribeInstanceAttributeEC2 actions - StartInstances , StopInstances, RebootInstances
The common API call - ''GetMetricStatistics'' is used for all the metrics that we collect from Cloudwatch.
Amazon RDS Instances
AWS account users are required to use their AWS Access Key and Secret Access Key to add an AWS monitor in
Applications Manager. By default, AWS users have administrator privileges and can access AWS Service APIs.
However, if your AWS user account has limited permission, here is the list of APIs used to collect metrics from the
respective AWS services and performance metrics from CloudWatch:
DescribeDBInstances
DescribeDBClusters
The common API call - ''GetMetricData'' is used for all the metrics that we collect from Cloudwatch.
Amazon S3 Buckets
Following are the list of APIs used to collect metrics from CloudWatch:
ListAllMyBuckets
ListBucket
GetBucketLocation
The common API call - ''GetMetricData'' is used for all the metrics that we collect from Cloudwatch.
Amazon DynamoDB Monitoring
AWS account users are required to use their AWS Access Key and Secret Access Key to add an AWS monitor in
Applications Manager. By default, AWS users have administrator privileges and can access AWS Service APIs.
However, if your AWS user account has limited permission, here is the list of APIs used to collect metrics from the
respective AWS services and performance metrics from CloudWatch:
ListTables
DescribeTable
DescribeLimits
DescribeStream
The common API call - ''GetMetricStatistics'' is used for all the metrics that we collect from Cloudwatch.
Amazon Billing
AWS account users are required to use their AWS Access Key and Secret Access Key to add an AWS monitor in
Applications Manager. By default, AWS users have administrator privileges and can access AWS Service APIs.
However, if your AWS user account has limited permission, here is the list of APIs used to collect metrics from the
respective AWS services and performance metrics from CloudWatch:
GetCostAndUsage - To retrieve cost and usage metrics for your Global Account
GetCostForecast - To retrieve a forecast for how much Amazon Web Services predicts that you will spend over
the forecast time period that you select, based on your past costs.
Amazon Elastic Load Balancer (ELB)
Application Load Balancers APIs:
DescribeLoadBalancers
DescribeTargetGroups
DescribeTargetHealth
The common API call - ''GetMetricData'' is used for all the metrics that we collect from Cloudwatch.
Amazon SNSAmazon Simple Notification Service APIs:
ListTopics - API to retrieve the list of SNS topics in an account
ListSubscriptionsByTopic - API to retrieve the list of subscriptions in a SNS topic
The common API call - ''GetMetricStatistics'' is used for all the metrics that we collect from Cloudwatch.
AWS Lambda
AWS Lambda Service APIs:
ListFunctions - API to fetch list of Lambda functions. Click here for more info.
GetFunction - API to fetch the configuration and information about the Lambda function. Click here for more
info.
The common API call - ''GetMetricData'' is used for all the metrics that we collect from Cloudwatch.
AWS Elastic Beanstalk
AWS Elastic Beanstalk APIs:
DescribeEnvironments - API to fetch environments and its meta-data. Click here for more info.
DescribeEnvironmentResources - API to fetch resources used by the environment. Click here for more info.
DescribeAutoScalingGroups - API to fetch meta-data of the AutoScaling Group. Click here for more info.
DescribeEvents - API to fetch events occurred in the environment. Click here for more info.
The common API call - ''GetMetricData'' is used for all the metrics that we collect from Cloudwatch.
To enable enhanced monitoring for Beanstalk environment, follow the steps mentioned below. Learn more
In the AWS console, select ElasticBeanstalk under Services.
Select the environment that needs the metrics to be enabled.
Click Configuration on the left side menu.
Choose Monitoring → click Edit → select Enhanced → select all the metrics for environment and instance.
Click Apply.
Amazon SQS
Amazon SQS Service APIs:
ListQueues - API to list the queues in AWS. Click here for more info.
GetQueueAttributes - API to get the metrics of the specified SQS Queue. Click here for more info.
The common API call - ''GetMetricData'' is used for all the metrics that we collect from Cloudwatch.
AWS Elastic Container Service (ECS)
Amazon Elastic Container Service (ECS) APIs:
ListClusters - API to list the existing clusters in AWS. Click here for more info.
DescribeClusters - API to fetch meta-data of clusters in AWS. Click here for more info.
ListContainerInstances - API to list ECS container instances in the cluster. Click here for more info.
DescribeContainerInstances - API to fetch meta-data of ECS container instances in the cluster. Click here for
more info.
ListServices - API to list the services that are running in the cluster. Click here for more info.
DescribeServices - API to fetch meta-data of specified services running in the cluster. Click here for more
info.
ListTasks - API to list the tasks in the cluster. Click here for more info.
DescribeTasks - API to fetch meta-data of tasks in the cluster. Click here for more info.
The common API call - ''GetMetricData'' is used for all the metrics that we collect from Cloudwatch.To enable Container Insights on an existing Amazon ECS cluster, enter the following command. You must
be running version 1.16.200 or later of the AWS CLI for the following command to work. Learn more
aws ecs update-cluster-settings --cluster --settings
name=containerInsights,value=disabled
To deploy the CloudWatch agent to collect instance-level metrics from Amazon ECS clusters hosted on
EC2 instance, download the JSON file, save it and then execute the following command in CLI. Learn more
aws cloudformation create-stack --stack-name CWAgentECS-- --template-
body file://.json --parameters ParameterKey=ClusterName,ParameterValue=
ParameterKey=CreateIAMRoles,ParameterValue=True --capabilities
--region
AWS Elastic Kubernetes Service (EKS)
Check if you have given access for the following APIs to the IAM user whose credentials are being used for
monitoring EKS:
ListFargateProfiles
DescribeNodegroup
ListNodegroups
DescribeFargateProfile
DescribeCluster
ListClusters
GetMetricData
GetMetricStatistics
Download and install the AWS CLI (Windows or Linux) to configure cluster with kubectl for monitoring. Learn
more
Windows: Execute the downloaded file to open the Installation wizard and complete the installation.
Linux: Execute the below commands to unzip the downloaded file, execute the program and
complete the installation. Learn more
unzip awscliv2.zip
sudo ./aws/install
Note: AWS CLI is used only for AWS EKS monitoring. Uninstall AWS CLI if no longer needed.
Download the latest Kubectl utility executable file (Windows or Linux). Learn more
Windows: Place the downloaded executable file under \working\ directory
(or) add kubectl to the system environment path.
Linux: Execute the following commands (or) add kubectl to the system path.
chmod +x ./kubectl
mkdir -p $HOME/bin && cp ./kubectl $HOME/bin/kubectl && export PATH=$PATH:$HOME/bin
To fetch metrics from Container Insights, implement the prerequisites for container insights. However, to
execute the commands specified in the prerequisites, AWS CLI and kubectl should be configured.
To configure AWS CLI, execute the below command and provide the necessary credentials:
aws configure
To configure kubectl, execute the below command:
aws eks --region {region} update-kubeconfig --name {cluster_name} --kubeconfig .
Nodes (EC2 instances) should have the policy CloudWatchAgentServerPolicy to send container insights
metrics to CloudWatch.
Google Cloud PlatformPrerequisites:
Login to the GCP console with Owner access to the Project to be monitored.
Go to GCP Console → APIs & Services → Library, to enable the following APIs :
Cloud Resource Manager API
Cloud Asset API
Compute Engine API
Stackdriver API
Stackdriver Monitoring API
Cloud Storage
Google Cloud Storage JSON API
Cloud Filestore API
Kubernetes Engine API
Follow the below mentioned steps to create an OAuth provider to monitor a GCP project.
Once an OAuth provider is created, verify if it has an Access Token and Refresh Token.
You can use OAuth provider to add multiple projects under the same account, but ensure that the APIs are
enabled in each project before adding a monitor in AppManager.
Steps to create an OAuth Provider for GCP:
In Applications Manager, go to Settings → OAuth Provider and select Add OAuth Provider. (Make sure you
are logged in from a fully qualified domain name as in the help card)
Copy the Redirect URL from the Add OAuth Provider window.
Go to GCP Console → APIs & Services → OAuth consent screen.
Select User Type as External and click Create to register an app. Provide the desired App Information and
under Authorised domain, enter the domain name from the Redirect URL and press the enter key. If the app is
already present then click the Edit App option and under Authorised domain, enter the domain name from the
Redirect URL and press the enter key. Now click Save and Continue.
Go to GCP Console → APIs & Services → Credentials.
Select Create Credentials → OAuth Client ID.
Select Web Application and enter the copied Redirect URI in the Authorised redirect URIs section and press
the Enter key.
Now click Create button.
The generated Client ID and Client secret will be displayed. Copy it and fill in the Add OAuth Provider
window.
Fill the following as below:
Grant Type - Authorization Code
Authorization Endpoint URL - https://accounts.google.com/o/oauth2/auth
Scope - https://www.googleapis.com/auth/cloud-platform
Query parameters:
Name - access_type
Value - offline
Token endpoint URI - https://oauth2.googleapis.com/token
Token request method - Post request body
Authenticated request method - Basic Authentication
Note : Remaining fields should remain as default.
Click Authorize button and authorize using the account to login to GCP.
Once created, verify whether both Access token and Refresh token are generated.
Use this OAuth Provider in the Google Cloud Platform''s New Monitor page.
Oracle Cloud Infrastructure
To obtain data into Applications Manager, the user must have appropriate policies/permissions assigned by the
administrator. To do so, follow the steps given below:
Login as administrator into the Oracle Cloud Infrastructure console. Under Governance and Administration
section, go to Identity → Groups option and click on Create Group button.
Create a new group with the required group name (say ''AppManager'') and add the required user to this newly-
created group.Under Identity → Policy option, click on Create Policy button and create a new policy with the following
policy statement:
ALLOW GROUP to use all-resources IN TENANCY
Example:
ALLOW GROUP AppManager to use all-resources IN TENANCY
Make sure that you are in the ''root'' compartment while creating the above policy.
Note : Using this policy, the user can only read and cannot perform create and delete operations. (Refer here
for more info.)
Oracle Autonomous Database
To obtain data for TableSpace, Sessions, Processes and Jobs in Applications Manager, you must configure the
Oracle Wallet credentials in the Oracle Autonomous DB monitor. To do so, follow the steps given below:
Go to Monitor Actions → Edit Monitor available on right-side of the Oracle Autonomous DB monitor
dashboard page.
Download the Oracle Wallet credentials. (Click here to learn how to download the Oracle Wallet credentials)
After downloading, unzip the Wallet_databasename.zip file to a secured location.
Copy the location path of that file and provide as input in the Wallet File Path field.
Now open the tnsnames.ora file (obtained after unziping Wallet_databasename.zip file) in any text editor.
This file contains the predefined services identifiable as high, medium, and low. Each service has its own TNS
alias and connection string. Copy any one of the alias names (based on severity) and provide the same as
input in the TNS Alias Name field. (Refer here to learn more)
Enter the username and password details of the autonomous database.
Click Update.
OpenStack
Prerequisites:
Policy defaults enable only users with the administrative role to perform below operations (Access to below APIs).
User can provide the required permissions through the policy.json file.
Hypervisors: /os-hypervisors
Cinder Services: /v3/{project_id}/os-services
Nova/Compute Services: /os-services
Neutron Agents: /v2.0/agents
Authentication API: /v3/auth/tokens
Computes: /servers/detail
Images: /v2/images
ERP
Oracle EBS
Applications Manager uses the Dynamic Monitoring Service (DMS) to monitor performance and availability of
Oracle E-Business Suite. You can access performance metrics using servlets from the following URLs for different
versions of EBS from Applications Managers:
EBS R11 - http://:/dms0/AggreSpy
EBS R12.0 - http://:/dms0/Spy
EBS R12.2.0 - http://:/dms/Spy
For Oracle E-Business Suite Version R11i, the DMS Servlet has to be made accessible to the system where
Applications Manager is running. For Versions R12.0 and R12.2.0, the DMS Servlet should be accessible by default.
It is recommended that you test to ensure that the Servlet is accessible to the Applications Manager system. [The
instructions given below are referred from the Oracle website.]For Oracle E-Business Suite R11i:
By default, the dms0/AggreSpy URL is protected, allowing only the localhost (127.0.0.1) to access the AggreSpy
Servlet. To view metrics from a system other than the localhost, you need to change the DMS configuration for the
system running the Oracle EBS that you want to monitor by modifying the trusted.conf file. This can be done as
follows:
Open the trusted.conf file under $ORACLE_HOME/Apache/Apache/conf on a UNIX system,
or%ORACLE_HOME%\Apache\Apache\conf\ on a Windows system.
Add the Applications Manager Hostname and IPaddress in the Allow from list as shown in the following
example:
Order deny,allow
Deny from all
Allow from localhost
Allow from
Now open the httpd.conf and httpd_pls.conf files and check if the trusted.conf file is included. The Files are
present under$ORACLE_HOME/Apache/Apache/conf on a UNIX system, or
%ORACLE_HOME%\Apache\Apache\conf\ on a Windows system. If the trusted.conf file is not included, add
the following lines in both the files and save:
# Include the trusted.conf file
include $ORACLE_HOME/Apache/Apache/conf/trusted.conf
Restart Oracle E-Business Suite and ensure that you are able to access the URL http://:
/dms0/AggreSpy from the Applications Manager system.
For Oracle E-Business Suite R12.0:
Ensure that you are able to access the URL http://:/dms0/Spy (Hostname = Hostname with domain
name, Port number = OAS listening port) from the Applications Manager system.
For Oracle E-Business Suite R12.2.0:
Ensure that you are able to access the URL http://:/dms/Spy (Hostname = Hostname with domain
name, Port number = Weblogic Admin Server listening port) from the Applications Manager system. Users must
enter the credentials of their Weblogic Admin server in their Oracle E-Business Suite to access the URL.
Caution: Modifying trusted.conf has security implications. Modify this file only if you understand the security implications for
your site. By exposing metrics to systems other than the localhost, you allow other sites to potentially view critical Oracle EBS
Server internal status and runtime information.
SAP Server, SAP CCMS
SAP Server Monitoring and SAP CCMS Monitoring requires SAP JavaConnector ( JCo) to be present in Applications
Manager''s classpath.
Note: The user name provided while adding SAP monitor should have sufficient privileges to access CCMS and
Background job metrics. To check this, the user can execute RZ20 transaction in the SAP GUI and see if the
CCMS monitor sets can be displayed.
Applications Manager build 14270 and above
For Windows:
Download and unzip the SAP JavaConnector [SAP JCo 3.1.x] from here. Depending on the hardware
architecture of host machine where Applications Manager is running, make sure you download the respective
zip file.
In the machine, where Applications Manager is running,
copy sapjco3.jar and sapjco3.dll and sapjco3.pdb under AppManager_home/working/lib directory.
If Applications Manager is installed on Windows, as mentioned in SAP Note 2786882 on Windows platforms,
JCo 3.1 requires the Visual Studio 2013 C/C++ runtime libraries to be installed on the system. To verify, check
for the presence of the "Microsoft Visual C++ 2013 Redistributable" package in ControlPanel -> Program and
Features. If not present, download and install the "Visual C++ 2013 Redistributable Package" from the
Microsoft knowledge base article https://support.microsoft.com/en-us/help/4032938 and choose the
package, which corresponds to the used Locale and JVM bit-width (x64 for 64-bit or x86 for 32-bit).
Restart Applications Manager.Note: Do not copy the sapjco3.dll neither into the {windows-dir}/system32 nor into the {windows-
dir}/SysWOW64 directory. This will break the operability of other JCo versions that are already installed on
the same system. Furthermore you would risk that the current installation also would not work anymore, if
the sapjco3.dll gets replaced in the respective Windows system directory in the future.
For Linux:
Download and unzip SAP JavaConnector[SAP JCo 3.1.x] from here. Depending on the hardware processor of
the host machine where Applications Manager is installed. make sure you download the respective zip file.
In the machine, where Applications Manager is running,
copy sapjco3.jar and libsapjco3.so under AppManager_home/working/lib directory.
Restart Applications Manager.
Applications Manager build below 14270
For Windows:
Download and unzip the SAP JavaConnector [SAP JCo 3.0.x] from here. Depending on the hardware
architecture of host machine where Applications Manager is running, make sure you download the respective
zip file.
In the machine, where Applications Manager is running, copy sapjco3.jar and sapjco3.dll and sapjco3.pdb
under AppManager_home/working/lib directory.
If Applications Manager is installed on Windows, as mentioned in SAP Note 1077727 JCo 3.0 requires the
Microsoft Visual Studio 2005 C/C++ runtime libraries (version 8.0.50727.6195) to be installed on the system. To
verify, check for the presence of the "Microsoft redistributable runtime DLLs VS2005 SP1" in ControlPanel ->
Program and Features. If not present, download and install the "Visual C++ 2005 SP1 Redistributable Package"
from the Microsoft website https://www.microsoft.com/en-us/download/details.aspx?id=26347 and choose
the package, which corresponds to the used JVM bit-width and processor architecture (x64 for 64-bit, x86 for
32-bit and ia64 for Itanium processors).
Restart Applications Manager.
Note: Do not copy the sapjco3.dll neither into the {windows-dir}/system32 nor into the {windows-
dir}/SysWOW64 directory. This will break the operability of other JCo versions that are already installed on
the same system. Furthermore you would risk that the current installation also would not work anymore, if
the sapjco3.dll gets replaced in the respective Windows system directory in the future.
For Linux:
Download and unzip SAP JavaConnector[SAP JCo 3.0.x] from here. Depending on the hardware processor of
the host machine where Applications Manager is installed. make sure you download the respective zip file.
In the machine, where Applications Manager is running, copy sapjco3.jar and libsapjco3.so under
AppManager_home/working/lib directory.
Restart Applications Manager.
Microsoft Dynamics CRM / 365 (On-Premise)
To monitor a Microsoft Dynamics CRM / 365 application, use an Administrator user account with permission to
execute WMI queries on ''root\CIMV2'' namespace of the Dynamics CRM / 365 Server.
The following software must be installed and running on your computer before you try to execute WMI queries:
Microsoft .Net framework 3.5
Microsoft .Net framework 4.7
Firewall access for monitoring:
Ports required for monitoring via WMI.
Windows Management Instrumentation (WMI) (default : TCP 445)
Remote Procedure Call (RPC) (default :TCP 135)
Target server uses random port above 1024 by default to respond back for remote communication (DCOM)
(default : TCP 1025 to 1030)Powershell – Enable Script Execution:
Powershell script execution must be enabled on Applications manager server for data collection. Here is how you
can do it:
Execute the below cmdlet from an administrator powershell window:
Set-ExecutionPolicy Unrestricted
If the above cmdlet produces an Error as below, you can configure Powershell Script Execution via Group Policy
Editor:
Configure Powershell Script Execution via Group Policy Editor
Open the Group Policy Editor from Control Panel→ Edit Group Policy (or) run gpedit.msc from Start menu.
To configure, navigate under Computer Configuration to Policies\Administrative Templates\Windows
Components\Windows PowerShell.
You should see a setting called Turn on Script Execution like in the following image:
Double-click the setting. You will want to enable it and select an option from the drop down.Set it to “Allow All Scripts”.
Click Apply and OK.
Microsoft Dynamics AX
Supported versions of Microsoft Dynamics AX: Microsoft Dynamics AX 2012, Microsoft Dynamics AX 2012 R2,
Microsoft Dynamics AX 2012 R3
The following software must be installed and running on your computer before you try to execute WMI queries:
Microsoft .Net framework 3.5
Microsoft .Net framework 4.7
To monitor a Microsoft Dynamics AX application, use an Administrator user account which has the permission
to execute WMI queries on ''root\CIMV2'' namespace of the AX Server.
Firewall access for monitoring- Ports required for monitoring via WMI:
Windows Management Instrumentation (WMI) (default : TCP 445)
Remote Procedure Call (RPC) (default : TCP 135)
Target server uses random port above 1024 by default to respond back for remote communication
(DCOM) (default : TCP 1025 to 1030)
SAP Business One
Integration Framework should be launched for SAP Business One.
Servers
Windows
Currently windows hardware performance monitoring is supported in SNMP and WMI monitoring mode:
SNMP Mode of monitoring:
Monitoring Dell hardware status:
Dell OpenManage Server Administrator and make sure SNMP agent is enabled.
Installation steps http://www.dell.com/downloads/global/power/ps2q06-20050112-Lou-OE.pdf.
Monitoring HP hardware status:
HP System Insight Manager (SIM v6.2 or higher is recommended) and make sure SNMP agent is enabled
Installation steps
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00293378/c00293378.pdf
Determine if SNMP responds for the OID properly. Below are the correct OID''S for each vendor:
For HP: 1.3.6.1.4.1.232.2.2.2.1.0
For Dell: 1.3.6.1.4.1.674.10892.1.300.10.1.8.1
WMI mode of monitoring:
The following conditions must be met before you can proceed troubleshooting WMI nodes:
The node has successfully been added via WMI.
WMI is working properly on the remote server.
HP System Insight Manager (SIM v6.2 or higher is recommended) is installed on the remote server and
running.
Dell OpenManage Server Administrator is installed on the remote server and running.
If WMI, execute the below cmdlet from Powershell prompt with Administrator privileges:
Set-ExecutionPolicy UnrestrictedThis is to allow execution of powershell scripts, which handle proper process termination during Datacollection
For WMI Mode of Monitoring:
In Windows Server 2008 and later versions, and in Windows Vista and later versions, use the following
dynamic port range:
Start port: 49152
End port: 65535
If your computer network environment uses only Windows Server 2012, Windows Server 2008 R2, Windows
Server 2008, Windows 8, Windows 7, or Windows Vista, you must enable connectivity over the high port range
of 49152 through 65535.
For Windows 2000, Windows XP, and Windows Server 2003 use the following dynamic port range:
Start port: 1025
End port: 5000
If your computer network environment uses Windows Server 2012, Windows Server 2008 R2, Windows Server
2008, Windows 8, Windows 7, or Windows Vista together with versions of Windows earlier than Windows
Server 2008 and Windows Vista, you must enable connectivity over both the following port ranges:
High port range: 49152 through 65535
Low port range: 1025 through 5000
Linux
Prerequisites for monitoring Cron jobs:
Curl must be installed in the remote Linux machine.
Script linked to the cron job must have executable permission.
The machine where Applications Manager is installed should be reachable from the remote Linux machine via
SSL port without any proxy server.
The remote machine where the cron job is running must be synced with the correct time zone.
Cron job interval should be a minimum of five minutes.
Cron job uses HTTPs protocol to send responses to the machine where Applications Manager is installed and
is validated using the admin user''s Rest API key. If the admin user''s API key is regenerated, then update the
latest API key for all the cron job(s) on the remote Linux machine using the crontab -e command.
Linux cron is supported only in SSH and TELNET mode of monitoring.
IBM i
To connect to IBM i server from Applications Manager, ensure that the ports mentioned under "Port Non-SSL"
column in the link are not blocked in firewall. Also check out: https://www.ibm.com/support/pages/ports-
must-be-open-make-odbc-data-transfer-ole-db-adonet-or-jdbc-connection-through-firewall
It is recommended to use an account having a *QSECOFR permission on the server. If using the *QSECOFR
user profile is not possible, then use an account of user class *USER with additional permissions as follows:
The user should be permitted to access QMPGDATA/QPFRDATA(used to collect disk details) and
QGPL(used to collect problem details) libraries and permitted to execute the command CRTPFRDTA and
DSPPRB.
Consider the following special authorities when you use an account of user class *USER such as *ALLOBJ,
*SAVSYS , *JOBCTL, *SPLCTL to retrieve all data and perform IBM i admin actions from Applications
Manager.
Services
JMX Applications
To monitor a JMX Applications, the following java runtime options are to be added to your applicationDcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099
Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false
Replace 1099 with the actual port number of the agent
Example:
To enable JMX Applications in JBoss:
Edit the run.sh/bat under JBoss home/bin.
Append the following command to JAVA_OPTS,
JAVA_OPTS =-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 -
Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false
%JAVA_OPTS%
To enable JMX Applications in JBoss 7 and above:
Copy the jboss-client.jar from /bin/client/ and place it under /working/classes/jboss/as7 directory.
To enable JMX Applications in Tomcat:
JAVA_OPTS =-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 -
Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false
%JAVA_OPTS%
To enable SSL for JMX applications
-Dcom.sun.management.jmxremote.ssl=true
To enable authentication, use of authentication is recommended. If you do not want to use authentication, you
should change the value to false.
-Dcom.sun.management.jmxremote.authenticate=true
If you are using authentication, specify the location of the password file
-Dcom.sun.management.jmxremote.password.file=c:\jmxremote.password
If you are using authentication, specify the location of the access file
-Dcom.sun.management.jmxremote.access.file=c:\jmxremote.access
Refer Oracle documentation in this regard:
http://docs.oracle.com/javase/1.5.0/docs/guide/management/agent.html#remote
Note: To know more about monitoring a JMX Application if your application is behind a firewall, check out this
blog post. Also please note that the ping/telnet/nslookup should be working for the remote JMX:
telnet hostname port
ping hostname
ping IPAddress
nslookup hostname
nslookup IPAddress
Ceph Storage Monitor
Ceph status command is used to collect performance stats of Ceph Storage Monitor. The user given, should have
read privileage to ceph.keyring file. Ensure the ceph.keyring file has appropriate permissions set (e.g., chmod
644) on your client machine.
Hadoop Monitor
1. To monitor Hadoop via REST API:
No Authentication:
URL http://:/jmx should be able to accessed from the Applications Manager machine for
both Namenode and Jobtracker/ResourceManager
Simple Authentication:URL http://:/jmx?user.name= should be able to access from the
Applications Manager machine for both Namenode and Jobtracker/ResourceManager
2. To monitor Hadoop via JMX:
Add the following java runtime options to ''HADOOP_NAMENODE_OPTS''; ''HADOOP_JOBTRACKER_OPTS'' in
Hadoop-env.sh with unique port.
-Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -
Dcom.sun.management.jmxremote.port=8004
Apache Zookeeper
Prerequisites for monitoring Apache Zookeeper:
Remote JMX should be enabled.
To ensure that please open the ZKServer file under bin folder and check the below following:
JMXPORT =
ZOOMAIN="-Djava.rmi.server.hostname= -Dcom.sun.management.jmxremote -
Dcom.sun.management.jmxremote.port=$JMXPORT -
Dcom.sun.management.jmxremote.authenticate=$JMXAUTH -
Dcom.sun.management.jmxremote.ssl=$JMXSSL -Dzookeeper.jmx.log4j.disable=$JMXLOG4J
org.apache.zookeeper.server.quorum.QuorumPeerMain"
Note: Replace with JMXPORT and with IP address of the machine.
Java/Transactions
APM Insight
APM Insight includes a remote monitoring agent which has to be deployed in your application instances. Know
more about APM Insight Agent.
Java Runtime Monitor
To monitor a JDK1.5 JVM and above, add the following JVM arguments to your application:
-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 -
Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false
To monitor IBM JDK1.5 JVM and above, add the following JVM arguments to your application:
-Djavax.management.builder.initial= -Dcom.sun.management.jmxremote -
Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.ssl=false -
Dcom.sun.management.jmxremote.authenticate=false
Note: Port number ''1099'' can be replaced with the actual port number of the JMX agent.
To enable Java Runtime Monitor in JBoss:
Edit the run.sh/bat under JBoss home/bin. Append the following command to JAVA_OPTS
JAVA_OPTS =-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 -
Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false
%JAVA_OPTS%
To enable Java Runtime Monitor in JBoss 7 and above:
Copy the jboss-client.jar from /bin/client/ and place it under /working/classes/jboss/as7 directory.
To enable Java Runtime Monitor in Tomcat do the following:
Edit the catalina.sh/bat under Tomcat home/bin. Append the following command to JAVA_OPTS
JAVA_OPTS =-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 -
Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false
%JAVA_OPTS%To enable SSL over JMX, use the following JMX parameters in addition to the above, and restart the server.
JMX Parameters:
-Dcom.sun.management.jmxremote.ssl=true
-Djavax.net.ssl.keyStore="E:/APMBuilds/certificates/jmx.keystore"
-Djavax.net.ssl.keyStorePassword=password
-Djavax.net.ssl.trustStore="E:/APMBuilds/certificates/jmx.truststore"
-Djavax.net.ssl.trustStorePassword=password
Additionally, import the server certificate to "\working\jre\lib\security\cacerts" file and restart the server.
Syntax:
keytool -import -alias -file -
keystore "\working\jre\lib\security\cacerts" -storepass changeit
-noprompt
Example:
keytool -import -alias jmxcert -file "E:\APMBuilds\certificates\ssloverjmx.cer" -keystore
"C:\Program Files (x86)\AppManager14\working\jre\lib\security\cacerts" -storepass changeit -
noprompt
In the Tomcat Environment:
Make sure the catalina-jmx-remote.jar file is present in the $TOMCAT_HOME/lib location. This jar file can be
downloaded for your version of Tomcat from the Apache website from the extras section (sample link:
http://archive.apache.org/dist/tomcat/tomcat-7/v7.0.55/bin/extras/catalina-jmx-remote.jar).
Enable JMX in WebLogic
Open the startWebLogic.bat file in a text editor.
Find the JAVA_OPTS line and add the following:
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=8888
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
Restart WebLogic.
Active Directory
To monitor an Active Directory Service, the user must have "Administrator" privileges. To add an Active Directory
Service, follow the below given steps:
Install the latest .NET Framework on your Applications Manager machine.
Enable .NET Framework 3.5:
To know how to enable .NET 3.5 in Windows Server 2008, click here.
To know how you can enable .NET 3.5 other Windows Servers, click here.
Firewall access for monitoring:Following are the list of ports required for monitoring:
Windows Management Instrumentation (WMI) (Default : TCP 445)
Remote Procedure Call (RPC) (Default :TCP 135)
Target server uses random port above 1024 by default to respond back for remote communication (DCOM)
(Default : TCP 1025 to 1030)
PowerShell Remoting (Default: TCP 5985 and 5986)
Install the latest Windows Management Framework in both Applications Manager machine and AD Server.
Check whether both machines have PowerShell version 5.0 or above. Click here for Powershell prerequisites
Using CredSSP Authentication
Enable the Use CredSSP Authentication option only when the monitored AD Server is a non-primary Domain
Controller and is present in a different domain other than that of the Applications Manager server domain. Learnmore about the prerequisites for using CredSSP authentication
Istio
Istio metrics are collected via kubectl, istioctl, curl, grep commands, so all the CLI tools mentioned should be
installed on that machine where Istio is installed.
Mesh traffic metrics collected by prometheus as running with ClusterIP, so prometheus should be deployed
with Istio.
Network Policy Server (Radius Server)
To monitor Network Policy Server (Radius Server), the user must have "Administrator" privileges. To add an
Network Policy Server (Radius Server), follow the below given steps:
Install the latest .NET Framework on your Applications Manager machine.
Enable .NET Framework 3.5:
To know how to enable .NET 3.5 in Windows Server 2008, click here.
To know how you can enable .NET 3.5 other Windows Servers, click here.
Firewall access for monitoring:Following are the list of ports required for monitoring:
Windows Management Instrumentation (WMI) (Default : TCP 445)
Remote Procedure Call (RPC) (Default :TCP 135)
Target server uses random port above 1024 by default to respond back for remote communication (DCOM)
(Default : TCP 1025 to 1030)
To use a non-admin user for monitoring, follow the steps mentioned in this link.
Mail Servers
Exchange Server
Monitoring of Exchange Server is possible only if Applications Manager is running in a Windows System. Exchange
Monitoring supports two Modes of Monitoring.
Using WMI - If WMI is enabled in the remote machine in which Exchange Server is running.
Using Windows PowerShell technology - To use Powershell for data collection, make sure the proper steps
have been followed to enable and use remote commands in Windows PowerShell both in the Applications
Manager server and the remote server.
Ports required for monitoring:
Windows Management Instrumentation (WMI) (default : 445)
Remote Procedure Call (RPC) (default : 135)
PowerShell remoting - TCP 5985 and 5986
Exchange PowerShell session - TCP 80 and 443
Creating User Accounts, adding users and assigning roles
User Account Used for Monitoring:
The User Account used to add the monitor should be a member of View-Only Organization Management group.
Make sure that the group has the following Roles assigned - Mailbox Search & Monitoring.
For Exchange View-Only Administrators:
This role allows read access only to Exchange organization container and containers with Exchange recipients in
AD. They can verify settings, but can not change or add any settings. Only Powershell "Get-" can be
executed.
Adding Users and Assigning Roles
Adding Users to the View-Only Organization Management group and assigning roles in:
Exchange 2010/2013/2016Open Exchange Mangement Console in the Exchange Server.
To check if the user is already under View-Only Organization Management role group: Get-
RoleGroupMember "View-Only Organization Management" | where-object {$_.Name -eq ""}
If the user is not under the specified role group,execute the below cmdlet to add the user: Add-
RoleGroupMember "View-Only Organization Management" -Member
Next Add the two roles for View-Only Organization Management role group
New-ManagementRoleAssignment -SecurityGroup "View-Only Organization Management" -Role
"Monitoring"
New-ManagementRoleAssignment -SecurityGroup "View-Only Organization Management" -Role
"Mailbox Search"
Exchange 2007:
Open Exchange Management Shell.
Execute the following cmdlet: Add-ExchangeAdministrator –Identity –Role ViewOnlyAdmin
Enabling CredSSP authentication
Enable the Use CredSSP Authentication option only if you want to fetch Exchange Queues metrics for non-
mailbox roles in versions 2010 and above where the Applications Manager and Exchange server are in different
domains. Check the prerequisites for using CredSSP authentication here
Configuring ConnectionURI for Powershell Remoting
The ConnectionURI is used to establish a connection to a remote computer using the URI address of the related
HTTP or HTTPS endpoint.These connections are made over TCP port 80 for HTTP and TCP port 443 for HTTPS. By
default,the connection URI is of the form http:///powershell and uses Kerberos
authentication.
With Kerberos Authentication: When the machine running Exchange Server is joined to the same domain as
the machine running Applications Manager, either HTTP or HTTPS can be used with Kerberos Authentication.
If Kerberos Authentication is not supported , or the machine is in another domain, the other option is to
configure Basic Authentication for powershell virtual directory. To configure basic authentication in Exchange
2013, 2010 or 2007 using IIS Manager:
Open IIS Manager.
In the Connections pane, expand Default Web Site, and then click PowerShell.
Click Authentication in the results pane and enable Basic Authentication.
Note: If you decide to use Basic Authentication, HTTPS should be used as mode of connection for
connectionURI. If the connectionURI should be customized it can be done so by clicking the "Customize
ConnectionURI" option in new monitor page. To provide a different port for the connectionUri provide it in the
following format: /Powershell: (or) /Powershell:
For Example: http://win-exchange13/Powershell:4444
Middleware/Portal
IBM WebSphere MQ Monitor
To monitor IBM Websphere MQ Series, the following jar files must be added to the respective locations:
For IBM
Websphere Location in
Jar files to be added Location in Applications Manager
MQ Series Websphere MQ
version
Version Download the Copy the jar files to
com.ibm.mq.jar
5.x/6.x supportpac MS0B \working\jre\lib\ext
com.ibm.mq.pcf-6.x.jar
WebSphere MQ directory.
connector.jar
Java classes for
PCF, the
com.ibm.mq.pcf-
6.1.jarfile for
version 6 and older
versions.The jar files can be
found under
\Java\lib
directory.
connector.jar All the jar files can
com.ibm.mq.jar be found under
Copy the jar files to
com.ibm.mq.pcf.jar \working\jre\lib\ext
com.ibm.mq.jmqi.jar Home
directory.
com.ibm.mq.headers.jar Directory>\Java\lib
com.ibm.mq.commonservices.jar directory.
com.ibm.mq.jar
com.ibm.mq.pcf.jar
All the jar files can
com.ibm.mq.jmqi.jar
be found under
com.ibm.mq.headers.jar and Copy the jar files to
Version 8 \working\jre\lib\ext
and above Home
directory.
(OR) Directory>\Java\lib
directory.
com.ibm.mq.allclient.jar and
com.ibm.mq.pcf.jar
Note: The username & password length should be less than or equal to 12.
To monitor Queue statistics, make sure MONQ value is set to MEDIUM or HIGH for all queues. You can check the
current MONQ status using
DISPLAY QSTATUS(Q1)
To modify,
ALTER QL(Q1) MONQ(MEDIUM)
where Q1 is the queue.
To monitor Channel statistics, make sure MONCHL value is set to MEDIUM or HIGH for all channels. You can check
the current MONCHL status using
DISPLAY CHANNEL(QM1.TO.QM2)
To modify,
ALTER CHL(QM1.TO.QM2) CHLTYPE(SDR) MONCHL(MEDIUM)
where QM1.TO.QM2 is the channel name and SDR is its type.
IBM WebSphere Message Broker
To discover Message Broker, the following jars are required:
ConfigManagerProxy.jar located at \classes directory.
ibmjsseprovider2.jar located at \jre\lib directory.
Copy the two jar files to \working\jre\lib\ext directory.
Note: Copy these jar files to \jre\lib\ext directory if external JDK is configured for AppManager.
Restart Applications Manager and try adding the monitor.
For IBM Integration Bus(MessageBroker 10.x):
The following jars are required to monitor IIB:
IntegrationAPI.jar
jetty-io.jar
jetty-util.jar
websocket-api.jar
websocket-client.jar
websocket-common.jar
IntegrationAPI.jar located at \common\classes directory.
jetty-io.jar, jetty-util.jar, websocket-api.jar, websocket-client.jar, websocket-common.jar located at
\common\jetty\lib directory.Copy the jar files to \working\jre\lib\ext directory.
Note: Copy these jar files to \jre\lib\ext directory if external JDK is configured for AppManager.
Restart Applications Manager and try adding the monitor.
WebLogic Integration Server
Note: WebLogic Integration Server needs some additional configuration and conditions to be followed for
monitoring.
For monitoring WebLogic Integration Server 8.x, you should set the weblogic.disableMBeanAuthorization
andweblogic.management.anonymousAdminLookup system variable to true for enabling data collection.
Follow the steps given below:
Edit startWLS.cmd\sh present in the /server/bin directory and add the following argument
-Dweblogic.disableMBeanAuthorization=true and -
Dweblogic.management.anonymousAdminLookupEnabled=true (click on the link to view the sample
startWLS.cmd\sh file)
Restart the WebLogic Integration Server for the changes to take effect.
Copy weblogic.jar from folder /weblogic81/server/lib in Remote WebLogic server version 8 and place it
under \working\classes\weblogic\version8 folder in the machine where
Applications Manager is running.
Microsoft Office SharePoint Server
For SharePoint Standalone Server:
WMI Mode:
WMI access to remote server is required.
PowerShell Mode:
PowerShell remoting should be enabled. For more information, check enable and use remote commands in
Windows PowerShell.
For SharePoint Farm Server:
Enable PowerShell remoting on both, AppManager and Remote Server.
Perform the following steps on the SharePoint server(s):
In the Server Manager, add the user account used for adding the Sharepoint to the following Groups:
Remote Desktop Users
WinRMRemoteWMIUsers__
WSS_ADMIN_WPG
Open the Sharepoint Management shell as an administrator and execute the below commands one by one:
Enable-PSRemoting -Force
Enable-WSManCredSSP –Role Server
winrm set winrm/config/winrs ''@{MaxShellsPerUser="25"}''
[This is Optional].
winrm set winrm/config/winrs ''@{MaxMemoryPerShellMB="600"}''
[This is Optional].
Get-SPShellAdmin
[This command will return all the users who have the SharePoint_Shell_Access role].
Get-SPDatabase | Add-SPShellAdmin DOMAIN\UserName
[Replace Domain\Username with the user used to add the SharePoint Server].
Get-SPShellAdmin
[The added user should be listed.]Set-PSSessionConfiguration -Name Microsoft.PowerShell32 –ShowSecurityDescriptorUI
[This command will open up a dialog box. Add the user(s) with Read and Execute permissions then
click OK].
Run the above command again to ensure the permissions were applied correctly.
Using CredSSP Authentication
To monitor the SharePoint Farm server, CredSSP authentication should be used. To do so, enable the Use CredSSP
Authentication and refer the prerequisites for using CredSSP authentication. Then, perform the following steps on
the Applications Manager Server:
Open Windows PowerShell as Administrator.
Execute the below commands in the Administrator PowerShell:
$cred=get-Credential
$s=new-PSsession “SharePointServerName” -authentication credssp -credential $cred
[Replace SharePointServerName with the FQDN of the SharePoint server].
Invoke-Command -Session $s -ScriptBlock {Add-PSSnapin Microsoft.SharePoint.PowerShell;}
Invoke-Command -Session $s -ScriptBlock {get-SPContentDatabase}
[This will return all the content databases in your SharePoint farm and ensure you have access].
Invoke-Command -Session $s -ScriptBlock {get-spserviceinstance}
[This will return the SharePoint service instances and ensure you have access].
Enter-PSSession -session $s
[You will now see the servers name in [ ] PS: c:\users\\documents].
Exit-PSSession
If there are any errors related to permissions issue while executing the above commands, resolve the same.
For any issues related to Add-SPShellAdmin, check the following link: https://technet.microsoft.com/en-
us/library/ff607596.aspx
Microsoft Message Queue (MSMQ) Server
Below are the prerequisites for monitoring MSMQ server in Applications Manager:
WMI Mode: WMI access to remote server is required.
PowerShell Mode: PowerShell remoting should be enabled. For more information, check enable and use
remote commands in Windows PowerShell.
Microsoft BizTalk Monitoring
To monitor a Microsoft BizTalk Server, the user must have Administrator privileges. To use Powershell for data
collection, make sure the proper steps have been followed to enable powershell remoting.
Azure Service Bus
To add an Azure Service Bus Namespace in Applications Manager, a .pfx file (which contains the cryptographic
information of private keys) of the certificate uploaded in Azure Management certificates is required.
In the console, execute the script /bin/exportCertificateToAppManager.sh/bat file to export the
managed certificate of your account to Applications Manager.
To know more about creating certificates and uploading in Windows Azure portal, Click here.
Example:
/bin/exportCertificateToAppManager.bat [testCertificate.pfx] [password]
Apache ActiveMQ
Using JMX to monitor Apache ActiveMQ
Apache ActiveMQ has extensive support for JMX to allow you to monitor and control the behavior of the broker via
the JMX MBeans.
You can enable/disable Remote JMX support as follows:
For WindowsIn Service Mode: Add the following entries in wrapper.conf file.
/bin/win64/wrapper.conf (if 64-bit)
/bin/win32/wrapper.conf (if 32-bit)
wrapper.java.additional.13=-Dcom.sun.management.jmxremote
wrapper.java.additional.14=-Dcom.sun.management.jmxremote.port=1099
wrapper.java.additional.15=-Dcom.sun.management.jmxremote.authenticate=false
wrapper.java.additional.16=-Dcom.sun.management.jmxremote.ssl=false
wrapper.java.additional.17=-Djava.rmi.server.hostname=
In Non-Service Mode: Add the following lines in apachemq.bat file (located under
/bin/ directory) before ACTIVEMQ_CLASSPATHis set.
set ACTIVEMQ_SUNJMX_START=-Dcom.sun.management.jmxremote -
Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.ssl=false -
Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=
Replace with hostname/IP of ActiveMQ-installed machine.
For Linux
Add the following lines in apachemq.sh file (located under /bin/ directory) under invoke_start()
function:
ACTIVEMQ_SUNJMX_START="-Dcom.sun.management.jmxremote -
Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.ssl=false -
Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname="
Replace with hostname/IP of ActiveMQ-installed machine.
Virtualization
VMware Horizon View Connection Broker
Prerequisite for adding the Connection Broker monitor in the Applications Manager host:
VMware Horizon View Connection Broker monitor uses Windows PowerShell technology. Follow these steps to
enable Windows PowerShell Remoting in the Applications Manager server and the remotely monitored Horizon
View server:
Enable and Use Remote Commands in Windows PowerShell
Horizon View''s Domain Server and its components should be accessible (able to ping ) from the Applications
Manager server.
Docker
Docker and Docker Container metrics are collected via their REST API, so Docker''s REST API should be enabled to
add a Docker Monitor.
To enable remote API:
Open etc\default\docker file
Add the below option
DOCKER OPTS=''-H tcp://0.0.0.0:4243-H=unix:///var/run/docker.sock''
Save the file.
Restart Docker.
Web Server / Services
IIS Server
To add an IIS monitor
URL for IIS server (http(s)://[Host/IP]:[PORT]) should be accessible from Applications Manager-installed
server as we check for the Server header in the response.
Monitoring IIS Website and Application Pool statistics:For Applications Manager versions till 15110, we use the relevant server monitor credential to fetch data
from the remote server. So adding Server monitor is mandatory to fetch IIS Website and Application Pool
statistics.
From Applications Manager versions 15120 onwards, IIS server credential should be provided while
adding/editing the IIS monitor itself. This is mandatory to monitor Website and Application Pool
statistics.
Mode of Monitoring:WMI access to remote server is required. Following are the list of ports that are required
for monitoring through WMI:
Windows Management Instrumentation (WMI) (Default : TCP 445)
Remote Procedure Call (RPC) (Default : TCP 135)
For remote communication (DCOM), target server uses random port above 1024 by default to respond.
(Default : TCP 1025 to 1030)
To collect IIS Website Statistics
User must have the permission to execute WMI queries on ''root\CIMV2'' namespace of the IIS Server.
To collect IIS Application Pools Statistics
For Applications Manager versions till 15110, user must have the permission to access ''root\MicrosoftIISv2'' and
''root\WebAdministration'' WMI namespaces.
From Applications Manager versions 15120 onwards, user must have permission to access
''root\WebAdministration'' WMI namespace alone.
For ''root\WebAdministration'' namespace: Install the IIS WMI provider by selecting the IIS Management
Scripts and Tools component under Management Tools (or Web Management Tools).
For ''root\MicrosoftIISv2'' namespace: To enable IIS v6 Management Compatibility tools, follow steps 3 & 4
as mentioned in this link.
Troubleshooting: In case you encounter with issues in IIS server monitoring, refer here.
PHP
Place the phpstats.php file in the webserver''s document root. The phpstats.php can be found in /working/resourcesdirectory.
Apache
Enabling the Server status and the Extended-status will give additional information for the Apache server.
To enable the Server Status, follow the steps given below:
In Apache''s httpd.conf file, locate "Location /server-status" tag.
Remove the comment in the Location/Server-status tag, to Enable SetHandler server-status.
Change the attribute "deny from all" to "Allow from all".
Remove the comment in "LoadModule status_module modules/mod_status.so".
Save the conf file and restart the Apache Server.
To enable the Extended-status, follow the steps given below:
Locate "ExtendedStatus" Attribute in httpd.conf file.
Remove the comment to enable the status.
Save the conf file and restart the Apache Server.
HAProxy
To monitor a HAProxy instance:
Open the ''stats'' port for collecting the metrics.
To enable metrics collection, add the following content at the bottom of the file /etc/haproxy/haproxy.cfg:
listen stats :9000
mode httpstats enable
stats hide-version
stats realm Haproxy\ Statistics
stats uri /
stats auth Username:Password
Restart the HAProxy instance. This will open up the stats in the port ''9000'' (we have specified 9000 as the
port in this configuration). You can further add the same HAProxy for monitoring using the hostname and port.
Note:
* You can change the port (9000 by default) to any free port that you wish to use.
* The line number 7 is for setting up basic authentication for this stats url. A user can provide his own username
and password.
* We use the following URL to collect metrics: http://[HOSTNAME]:[PORT]/;csv
(Replace [HOSTNAME] and [PORT] with the respective hostname of the HAProxy instance and port which is
mentioned in the above configuration).
Nginx
To Enable the Nginx Server Status, follow the steps given below:
Configure the location /server_status method in /conf/nginx.conf file, to enable server_status.
The value of stub_status attribute should be "on".
Change the attribute "deny all" to "Allow all".
Save the conf file and restart the Nginx Server.
Real Browser Monitoring (RBM)
RBM requires network connectivity between the EUM agent and the Applications Manager server. This network
connectivity can be ensured with the help of the VPN or NAT or by assigning an direct IP Address to the
Applications Manager server. In the case where an agent is deployed within the local network and another one in a
remote site, a dual NIC or any one of the above means would be required to ensure this connectivity.
Note:
Playback using Microsoft Edge WebDriver is supported only in the End User Monitoring (EUM) Agent
installed on Windows Server with Microsoft Edge (versions 17 & above) support.
Playback using Google Chrome WebDriver is supported only in the End User Monitoring (EUM) Agent
installed on Server with Google Chrome (versions 65 & above) support.
For any further support please contact appmanager-support@manageengine.com. You can visit Troubleshooting
details.
Webpage Analyzer
Following the steps to be done for setting up Webpage Analyzer monitor :
Download the add-on for Webpage Analyzer.
After downloading, extract the zip file contents into /working directory.Following are the components that can be found in the ZIP file of the add-on, which are required for data collection
in Webpage Analyzer:
Mozilla Firefox v81: Used as the browser in which the webpage is loaded.
Gecko Driver: Used as a proxy that is used to communicate with Firefox.
PageSpeed Insights: Used to retrieve PageSpeed results.
Extension: Used to capture various performance metric data.
Note:
Without the add-on, Webpage Analyzer monitors webpage similar to that of the HTTP URL monitor, with
the exception that only the main URL will be monitored and not the underlying page components.
To install PageSpeed Insights in Linux, open the terminal from /working/wpaAddons/PageSpeedInsights directory and execute the following command:
chmod a+x pagespeed_bin
Real User Monitor
To learn how to set up Real User Monitoring in Applications Manager, refer here.
ManageEngine ADManager Plus
Mode of Monitoring: Remote JMX
Prerequisites for monitoring ManageEngine ADManager Plus:
1. Add below entries in wrapper.conf (D:\ManageEngine Products\ADManager Plus\conf\wrapper.conf) or
run.bat (D:\ManageEngine Products\ADManager Plus\bin\run.bat) file:
#Enable Remote JMX
wrapper.java.additional.16=-Dcom.sun.management.jmxremote
wrapper.java.additional.17=-Dcom.sun.management.jmxremote.port=1999
wrapper.java.additional.18=-Dcom.sun.management.jmxremote.ssl=false
wrapper.java.additional.19=-Dcom.sun.management.jmxremote.authenticate=false
2. To monitor PGSQL DB, implement the following changes:
D:\ManageEngine Products\ADManager Plus \pgsql\data\postgresql.conf
Uncomment and update ip address: listen_addresses = ''172.22.168.171''
D:\ManageEngine Products\ADManager Plus \pgsql\data\pg_hba.conf
# IPv4 local connections:
#host all all 127.0.0.1/32 trust
host all all 0.0.0.0/0 trust
D:\ManageEngine Products\ADManager Plus\conf\database_params.conf
Update the hostname/ipaddress instead of localhost .
For PGSQL/MSSQL database, Statistics will be collected by connecting to the database.
ManageEngine ServiceDesk Plus
Prerequisites:
To monitor PGSQL DB, implement the following changes:
C:\ManageEngine\ServiceDesk\pgsql\data\postgresql.conf
Uncomment and update ip address: listen_addresses = ''172.22.168.171''
C:\ManageEngine\ServiceDesk\pgsql\data\pg_hba.conf
# IPv4 local connections:
#host all all 127.0.0.1/32 trust
host all all 0.0.0.0/0 trust
Update the hostname/ipaddress instead of localhost in
\ServiceDesk\server\default\deploy\postgres-ds.xml file.ManageEngine OpManager
Mode of Monitoring: Remote JMX
For PostgreSQL DB, statistics will be collected by connecting to the database.
Prerequisites for monitoring ManageEngine OpManager:
For Windows:
In Service Mode:
1. Add below entries in wrapper.conf file.
C:\ManageEngine\OpManager\conf\wrapper.conf
# Enable Remote JMX
wrapper.java.additional.16=-Dcom.sun.management.jmxremote
wrapper.java.additional.17=-Dcom.sun.management.jmxremote.port=1999
wrapper.java.additional.18=-Dcom.sun.management.jmxremote.ssl=false
wrapper.java.additional.19=-Dcom.sun.management.jmxremote.authenticate=false
wrapper.java.additional.20=-Dcom.sun.management.jmxremote.rmi.port=1999
wrapper.java.additional.21=-Djava.rmi.server.hostname=
In Non-Service Mode:
Append the following parameters to JAVA_OPTS:
set JAVA_OPTS= %JAVA_OPTS%
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=1999
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.rmi.port=1999
-Djava.rmi.server.hostname=
For Linux:
Add the following entry in run.sh:
JAVA_OPTS="$JAVA_OPTS
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=1999
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.rmi.port=1999
-Djava.rmi.server.hostname="
2. To monitor PostgreSQL DB, do the following changes:
Open postgresql.conf file under /data directory.
Check the value of the configuration parameter listen address. It should be "*". Click here for more details on
configuring postgresql.conf
Open pg_hba.conf under /data
Add a new line ''host all all 0.0.0.0/0 trust'' to allow all the machines with proper password authentication to
acces PostgreSQL database server. Click here for more details on configuring pg_hba.conf file.
Open C:\ManageEngine\OpManager\conf\database_params.conf file.
Update the hostname/ipaddress instead of localhost.
Converged Infrastructure
Cisco UCS
Cisco UCS Manager should be installed and running while adding a Cisco UCS monitor.Configuring Cisco UCS Manager:
Refer to the following links to learn more about configuring Cisco UCS Manager.
https://www.cisco.com/c/en/us/products/servers-unified-computing/ucs-manager/index.html
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-manager/GUI-User-
Guides/Getting-Started/4-
1/b_UCSM_Getting_Started_Guide_4_1/b_UCSM_Getting_Started_Guide_4_1_chapter_0100.html
https://www.cisco.com/c/en/us/products/collateral/servers-unified-computing/ucs-
manager/whitepaper_c11-697337.html
aks
Understanding Applications Manager
Applications Manager is a web-based monitoring tool that manages the performance of applications, servers,
databases, systems, services, websites, and JMX/SNMP-based custom applications in a complex IT infrastructure.
You can find seven module tabs at the top which are explained as follows:
Intro Introduction Page of Applications Manager. It gives an overview of the working of Applications
Manager.
Home Has four views: Summary, Business View, Availability and Performance
Summary: Has a dashboard that shows the health and availability of all the Monitor Groups in a
snapshot . Lists all the Monitor Groups created and their details and graphical representation of
the Monitor Group with most critical alarms. Recent 5 alarms can be also be viewed.Business
View: The business view provides you a graphical snapshot of the entire business infrastructure
which is being monitored. This view displays the various Monitors associated to Monitor Groups
along with its health and availability.Availability: Gives the Availability history of the Monitors/
Monitor Groups in a snapshot. You can get the data for either the last 24 hours or the last 30
days.Performance: Gives the Health history and events of Monitor/Monitor Groups in a
dashboard. You can get the data for either the last 24 hours or the last 30 days (excluding
today).Custom Dashboards: Apart from the already available dashboards, you can create your
own custom dashboards by using different widgets.
Monitors Lists all the Monitor Typessupported and provides the number of Monitor being discovered in the
network. You can also click on the Monitor Types to view information of their Monitors. On clicking
the Monitor Types, you can view the Availability Dashboard, Performance Dashboard and the List
View that shows the performance attributes of the Monitor in detail.
Alarms Lists the alarms generated by the Monitor and their attributes, based on predefined thresholds.
The view is customizable such that you can view alarms for all or for particular application or
Monitor Type, list 10/25/50/75/100/125 entries in a single view, etc.
Reports Lists the Monitor Groups and the different Monitor Types for which the reports are generated.
Reports can be viewed based on attributes listed for the corresponding Monitor Type.
Support Provides information on getting assistance from the Applications Manager Technical center. It
also provides monitoring information on Applications Manager which monitors itself.
Admin Lists the admin operations such as creating new application, new Monitor, etc. to be performed
for monitoring.
The left frame consists of links for easy navigation and the top frame consists of links such as Talk back, Help,
Personalize etc. common in all the screens. To know more details on these links and icon representation, refer to
the Web Clientsection. The various tables in the web client can be dragged and arranged as per your requirement
Note: Have a look at Getting Started - How to Demosfrom Website.
Monitor Views
Under Monitor tab, you can see all the monitors listed down in the Select View drop-down menu in the right-hand
corner. There are eight different views:
Bulk Configuration View
Category View
Plasma View
Monitor Group ViewWorld Map View
Icon View
Table View
Business View
Bulk Lists all the details of the monitors that are monitored. From this view you can carry out bulk
Configuration admin operations like updating user name and passwords across monitors. Refer Bulk
View Configurationfor further details.
Category View Lists the monitors according to the various categories like Applications Servers, Database
Servers etc.
Business View In this view, the Monitors will be arranged in an default order.You can re-arrange the
Monitors and click on the floppy disk icon to save the view. You can also zoom in and out of
the view, and save the zoom level which is optimal for your viewing. Business View has the
following properties.You can edit the view by clicking on Settings icon and selecting the
Edit View from the menu to open a Customizable Business View page: View Properties
Update Monitor - This setting allows you to refresh the status of the Monitors and
Monitor Groups automatically by fixing some limited time (in minutes).
Reload Interval - This setting is similar to Update Monitor except that it will reload the
entire view after the given time. The recommended interval would be 15 minutes.
Check the Show Label for Monitors checkbox to show the labels for various monitors.
Associated Monitor Groups - This setting allows you to add various Monitor Groups to
your view. This is only available for the "Customizable Business View".
Under View Properties, by selecting Show only Monitor Groups and Sub Groups
allows you to include the Monitor Groups and Sub Groups in the selected view.
By selecting Show only Critical Monitors you can show only critical Sub Groups and
Monitors inside the selected view.
By selecting Show only Monitor Groups Status you can show the status of top level
Monitor Groups (that are selected via Associated Monitor Groups) in the selected view.
You can create multiple views for a Monitor Group. Click on the Settings icon in the business
view and select Create New View. By providing various details like Update Monitor time
interval, Reload interval, opting to select Monitor and Monitor Groups and Sub Groups you
can create a custom view. In addition, you can also edit its apperance of the view . Go to the
Display Properties tab and provide the following details:
Background color
Line Color
Label Color
Line Thickness
Line Transperancy
Publishing the View: Applications Manager allows you to embed these Business View in
intranet/internet portals by selecting the menu option ''Publish The View'' from Settings and
copy the iframe details and pasting it in the webpages.
World Map View Applications Manager, integrated with online map services, provides network traffic
information at a geographical dimension. By using online map API features, Applications
manager provides different levels of abstraction in the network data visualization.Refer to
World Map View for further details.
Icon View Lists all the monitors using icons, shows the host and the monitors assosciated with it
symbolically
Table View Lists the monitors within the host in a tabular format.
Plasma View The plasma view enables you to have a snapshot of what is happening with the monitors, at
one glance. The view can be put up on a plasma screen, and you can have a look even when
you are not in front of the monitor.The ''Customize View'' option available in the top right hand
corner, gives you the option to customize the layout. By checking the option “Play sound
alarm for critical events”, you can get notified/ warned of the critical events by sound
alarms.
Monitor Group Lists all Monitor Groups and the Sub-Groups available. You can associate Monitors, Copy
View Paste Monitor, configure alarms through this Monitor Group View itself. (as like Bulk Config
view). In addition, you can enable or disable actions via this view itself, i.e, even if you have
already configured actions like sending EMail, through ''disable action'' you can prevent
EMail action.
Working with Applications Manager
The following are the steps involved in monitoring:
Create a new Monitor Group: Create a new Monitor Group by grouping one or more Monitors.
Create new Monitor: Discover Monitors in the network and start collecting data (performance metrics,
availability etc) for the same.
Create new Monitor Type: Create new monitor type for monitoring custom applications.
Associate Monitor with Monitor Group: Add the discovered monitors to the Monitor Group.
Create threshold profile: Create thresholds to identify the status of a specific attribute.
Create actions: Specify what action needs to be taken in the event of an alarm.
Associate threshold and action with the attributes: Associate the thresholds and action to generate alarms and
perform action based on the threshold definition.
Configuring dependencies: Dependencies specify the rule based on which the severity of health and
availability is determined. For example, Health of a Tomcat Server may depend on the overall response time of
the server or on the response time of each of the web applications deployed on the server etc. By configuring
dependencies, you can determine the attribute, based on which the severity of health changes.
Note: Have a look at Working with Applications Manager - How to Demos from the website.
Please go through Working with Monitor Group and Configuring Alarms for detailed information on the above.
See Also
Best Practices Guide
Working with Monitor Groups
Monitor Groups are a logical group of one or more monitors that provides a holistic view of your business
environment.
For example, the health of an online Web application depends on various factors, such as the health of the
application server hosting the Web application, the availability of the Web server for accessing the Web
applications, the database server for storing or getting the required information, etc. These web applications and
services can be grouped together and monitored as a single Monitor Group.
Troubleshoot: For any monitoring-related troubleshooting, refer to the online Troubleshooting section.
Browse through the following topics to work with Monitor Groups:
Creating Monitor Groups
Creating Web Application Groups
Creating New Monitor
Associating Monitors to Monitor Groups
Deleting Monitor from Monitor Groups
Editing and Deleting a Monitor Group
VMware Virtual Infrastructure Groups
Associating Monitors to Monitor Groups
To associate a Monitor/Process/Service/Database to a Monitor Group, follow the steps given below:Click on the Monitor Group (from Home tab).
Under Monitor Group Information, click Associate Monitors link.
A list of discovered Monitors/Processes/Services/Databases that are available for associating and those that
have already been associated with that Monitor Group is displayed.
Note : The status of Monitor Group would remain unknown, until you associate at least one monitor to it.
Select the check box of the corresponding monitor from Monitors not present in this Monitor Group list and
click Add. You can also remove a monitor which has already been associated with the Monitor Group by
selecting the check box of Monitor(s) under Monitors present in this Monitor Group and clicking Remove.
Note :
In order to add Processes, Services and Databases to Monitor Groups, go to Admin → Server Settings →
Monitor Group Settings tab and enable appropriate monitor options (Process/Service/Database) prior to
performing the action. On disabling these options, the Processes/Services/Databases associated
previously can only be removed manually from the Monitor Group.
When a Process, Service or Database is down, the RCA for the Monitor Group will display the
Process/Service/Database name along with the Server Display name.
Creating Monitor Groups
This section explains how you can create a new Monitor Group. A monitor Group is particularly useful for grouping
the resources of a location say the resources available in sales office or for grouping the resources used by a
business application.
Applications Manager provides two types of monitor groups - Monitor Group and Web Application Group. The
steps to create a Monitor group are explained below. To create a web application group, refer this link.
To create a new Monitor Group, follow the steps given below:
Click New Monitor Group.
Provide a Monitor Group Name. This is mandatory and only alphanumeric characters, dashes (-), underscores
(_), periods (.), and spaces ( ) are allowed.
Provide any Description, if required.
Under Advanced Options, Select the Owner from the list of users created. Refer User Administration topic for
more information on the different roles of users.
Note:
Operator if associated as an owner will have Read Only Access to that particular Monitor Group alone.
Admin user is a super user and will be able to see all Monitor Groups.
Manager if associated will be able to view this Monitor Group in Manager Console. Using this option,
Restricted Monitor Groups alone can be shown in Manager Console. [By default, if the Manager is not
explicitly associated to a Monitor Group, the Manager will be able to access all the Monitor Groups in the
Manager Console]
Select the location for associating the monitor group to World Map Business View. Clicking on Add Location
will open up the world map wherein you can select and add custom locations. You can also delete or edit the
added locations, if required.
Note: Delete and edit location options are applicable only for Admin users.
Click Finish to create the Monitor Group and to add Monitors later.
How To Demos: Have a look at our demo on creating Monitor Group in our website.
Creating a Sub-Group within a Monitor Group
By using this option, you can create a Monitor Sub-Group within a Monitor Group (a Monitor Group within a Monitor
Group). Sub-Groups help better organization of your resources. With Sub-Groups, you can capture advanced
dependencies in your infrastructure. You can group clustered databases or servers and create complex groups. For
eg., A huge banking application Monitor Group may contain 100 monitors (application servers, systems,
databases, URLs, etc.,). All the database monitors can be grouped under a Sub-Group for effective monitoring.
To create a sub group, follow the steps given below:
Inside the Monitor Group Details page, click on the Monitor Group Actions button in the top right-hand
corner.
Click the New Sub-Group option under Monitor Group Actions.
Give the Sub-Group name and the description.Set a group type and the location of the group. (optional)
Click on Create Sub-Group.
Then you can associate the desired monitors to the Sub-Group.
Note: You can create up to six levels of sub-groups in a Monitor Group, by default.
Creating New Web Application Group
Once you create a web application group, you can view the health of the sub groups and know how each individual
sub group is performing. If there is a problem in the web application group, you can drill down and identify which
component is having a problem.The details page shows the health of all the tiers as components giving you a
better perspective of the Application''s Performance and Availability. You can also configure dependencies and
powerful alarm rules for intelligent alert correlation.
To create a new web application group, follow the steps given below:
Click New Monitor Group and select Web Application Group from the drop-down menu.
Provide a Name for the Monitor Group. This is mandatory and only alphanumeric characters, dashes (-),
underscores (_), periods (.), and spaces ( ) are allowed.
Provide a Description, if required.
Select the Owner from the list of users displayed. Refer User Administration topic for more information on the
different roles of users.
Note:
Operator if associated as an owner will have Read Only Access to that particular Monitor Group alone.
Admin user is a super user and will be able to see all Monitor Groups.
Manager if associated will be able to view this Monitor Group in Manager Console. Using this option,
Restricted Monitor Groups alone can be shown in Manager Console. [By default, if the Manager is not
explicitly associated to a Monitor Group, the Manager will be able to access all the Monitor Groups in the
Manager Console]
Select Web Application Group as the group type.
Select the Application Components from the options displayed. The components available are End User
Transaction (URL) group, Network devices group, Edge Devices group, Web Server Group, Application Server
Group, Database Group and Server Group. The components that you select will be automatically added as sub
groups within the web application group.
Select the Location for associating the monitor group to World Map Business View under Advanced section.
Otherwise, click the ''Add Location'' link and select custom locations from the google map that opens up.
Click Create Monitor Group button to create the Web Application Group. You can add monitors any time using
the Associate Monitors option.
Note: You can convert a web application group to a monitor group or vice versa by changing the Group Type.
Click Monitor Group Options link from the web application group page and select the Edit option. This will take
you to the Modify Monitor Group section. You can modify the Group Type values from this screen.
Creating a Sub-Group within a Web Application Group
If you have selected ''Application Components'' while creating the web application group, the sub groups will be
automatically created based on the options you have selected. You can also add sub groups later on by following
the steps given below.
Click the Monitor Group Actions->New Sub-Group option inside the Web Application Group Details page.
Provide the Sub-Group Name, Description and select the Owner from the list of users.
Select the Group Type from the dropdown box.
Select the Location for associating the sub group to from the drop-down box. You can also use the ''Add
Location'' option to specify custom locations from google map.
Click the Create Sub-Group button to create the sub group.
You can then associate the desired monitors to the Sub-Group.
Note: You can create up to six levels of sub groups for a web application group, by default.
Deleting Monitor from Monitor Groups
To delete a monitor from a Monitor Group,Click on the Home tab to display the list of Monitor Groups created.
Click over the Monitor Group from which the Monitor has to be deleted.
Data of all Monitors in that Monitor Group is displayed graphically. Click Remove from Group.
This deletes the monitor only from the Monitor Group but its monitoring will not stop.
Deleting monitor from Applications Manager
To delete a monitor from getting monitored by Applications Manager itself, follow the below given steps:
Click over the Monitors tab.
From Select View combo box, select Bulk configuration view. All the Monitor Types are listed.
Select the check box of the monitor to be deleted and click Delete.
Editing and Deleting a Monitor Group
To edit a Monitor Group,
Click the Home module tab to display the list of Monitor Groups created.
Click the Monitor Group to be edited.
On the Left-side Monitor Group Links, click Edit.
By editing the monitor group, you can change the Name, Description, Owners and the Country (location)
associated.
To delete a Monitor Group,
Click the Home module tab to display the list of Monitor Groups created.
Click the Monitor Group to be deleted.
On the Left-side Monitor Group Links, click Delete.
Note:
In simple layout, the left side links will not be persent. In this case, move to Monitors tab, under Select View
drop down box, select Monitor Group view. Select the Monitor Groups you want to delete, then select the
Delete action from the dropdown.
However, the Monitor pertaining to the corresponding Monitor Group will not be deleted. You will still be
able to view the details of the Monitor that was associated with the Monitor Group. To delete the Monitor,
refer to the Deleting Monitor from Applications Manager section.
VMware Virtual Infrastructure Groups
Applications Manager can discover your entire VMware virtual infrastructure through the vCenter server and
provide dependency mapping of its components. The ‘VMware Virtual Infrastructure Group’ allows you to quickly
discover all your virtual resources and model them the same way they are configured in the vCenter server. The
VMware infrastructure will be automatically categorized into components such as Datacenter, Cluster, ESX/ESXi
hosts, VMs, etc. Once you discover the virtual infrastructure, you can easily track the availability, health and
performance metrics of its various components.
The VMware virtual infrastructure group is different from monitor groups due to the fact that you have to manually
map all the resources to a monitor group. In the VMware virtual infrastructure group, the virtual resources in your
network are automatically discovered through the vCenter server and the components mapped accordingly. When
combined with the out-of-the-box support for 50+ applications, servers, databases, and transactions spanning
physical, virtual and cloud infrastructures along with auto-provisioning of virtual systems, the VMware virtual
infrastructure group becomes even more powerful.
Creating a New VMware Virtual Infrastructure Group
Follow the steps given below to create a VMware Virtual Infrastructure group:
Click New Monitor Group and select VMware Virtual Infrastructure from the drop-down menu. The ‘Discover
Virtual Infrastructure through vCenter’ screen will be displayed.
Provide a Display Name for the monitor group.
Specify vCenter Hostname/IP Address.
Specify the Port at which vCenter is running.
Enter the authentication credentials of the vCenter server such as User Name and Password.Specify the Polling Interval in minutes.
Select the VM Discovery option based on which the virtual machines present under the vCenter Virtual
Infrastructure should be discovered and monitored. The available options are Do not discover, Discover VM
but do not monitor metrics, and Discover and Monitor VM metrics.
For Discover VM but do not monitor metrics and Discover and Monitor VM metrics options, you can also
specify the Discovery Filter Regex based on which the virtual machines are to be discovered and monitored.
Learn more
If you are adding a new monitor from an Admin Server, select a Managed Server.
Click Fetch ESX Hosts button to start the virtual infrastructure discovery.
For more information on the performance metrics provided by the VMware virtual infrastructure group, refer this
topic.
Performance Metrics
Browse through the below topics to learn about monitoring performance metrics in Applications Manager:
Creating a new monitor
Viewing Performance Metrics
Creating a New Monitor
Once a new Monitor Group is created, the Monitors such as WebLogic Server, JBoss Server, Tomcat Server,
WebSphere Server, MySQL DB Server, Oracle DB Server, Mail Server, etc. must be created. This discovers the
Monitor from the network and starts collecting data for monitoring.
You have to create a Monitor to discover it from the network and monitor it. This can be done by following any of the
options given below:
All Monitors in a host.
A specific Monitor in a host.
All Monitors in a network
Note:
The displayname of the monitor can have any alphanumeric characters except for the following:
The following reserved characters:
< (less than)
> (greater than)
: (colon)
" (double quote)
'' (single quote)
/ (forward slash)
\ (backslash)
? (question mark)
% (percentage)
* (asterisk)
` (backtick)
Integer value zero, sometimes referred to as the ASCII NUL character.
If there is a problem while creating new monitors, click on Diagnose link to troubleshoot the problem.
All Monitors in a Host
To discover all Monitors running on a host, create them using the All Monitors option. Follow the given steps for
discovering the Monitor:
Select New Monitor.
Choose All Services.Provide the hostname, where all the monitors running on this host will be discovered. You can also discover
monitors in multiple hosts by providing the hostname, separated by commas. (Note: This will start discovering
in the default port of the Monitor.)
Enter the Subnet Mask of the network.
Click Add Monitor(s).
Note: Adding any service will also automatically add that server and other applications in the default port in
that server.
How To Demos: Have a look at our demo on creating Monitors in our website.
Viewing Performance Metrics
Applications Manager is used to monitor different types of applications and services of Monitor running in your
system/ network. Monitoring is an activity that checks the performance of your monitors by collecting and
analyzing the data at regular intervals. These monitoring capabilities are performed by different types of Monitor
Types.
This chapter lists the different types of Monitor Types supported by Applications Manager and the parameters
monitored by them.
Monitor Types
Applications Manager supports the following Monitor Types:
Application Servers
Microsoft .NET
JBoss Servers
Jetty Servers
GlassFish Servers
Oracle Application Servers
Resin Application Server
SilverStream
Tomcat Servers
VMware vFabric tc Servers
WebLogic Servers
WebSphere Servers
Apache Geronimo
Cloud Apps
Amazon
Amazon Elastic Compute Cloud (Amazon EC2)
Amazon Relational Database Service (Amazon RDS)
Amazon Simple Notification Service (Amazon SNS)
Amazon DynamoDB
Windows Azure
Open Stack
Microsoft 365
Oracle Cloud Infrastructure (OCI)
Google Cloud Platform (GCP)
Database Servers
Cassandra Servers
CouchBase Servers
IBM DB2 ServersIBM Informix Servers
Memcached Servers
MongoDB Servers
MS SQL Servers
MySQL/MariaDB Servers
Oracle Servers
PostgreSQL Servers
Redis Servers
Sybase ASE/SAP ASE/Sybase SQL Server
Oracle NoSQL
SAP HANA DB Servers
Middleware / Portal
Microsoft BizTalk
Microsoft Message Queue (MSMQ)
Microsoft Office SharePoint
Oracle Tuxedo
VMware vFabric RabbitMQ
WebLogic Integration Servers
IBM Websphere Message Broker
IBM WebSphere MQ
Microsoft Skype for Business Server
Azure Service Bus
Apache Kafka
Apache ActiveMQ
Servers
Windows
Linux
Solaris
IBM AIX
IBM i
HP Unix
Tru64 Unix
Free BSD
Mac OS
Novell
Windows Cluster
Services
JMX Applications
Ping Monitor
Service Monitoring
SNMP / Network Device
Telnet
Hadoop Monitor
Active Directory
DNS Monitor
FTP / SFTP MonitorLDAP Monitor
Ceph Storage
Apache Zookeeper
Oracle Coherence Servers
Mail Servers
Exchange Server
Mail Server
Web Server / Services
Apache Server
IIS Server
Nginx
Real Browser Monitor
PHP
Web Services
Web Server
HTTP(s) URL Monitors and HTTP(s) URL Sequence (Record & Playback)
Elasticsearch
ServiceDesk Plus
ManageEngine OpManager
ERP
SAP
SAP CCMS
Oracle E-Business Suite
Microsoft Dynamics CRM / 365 (On-Premise)
Virtualization
Microsoft Hyper-V Servers
VMware ESX/ESXi servers
VMware Horizon View Connection Broker
Citrix XenApp
Citrix Xenserver
Docker
Custom Monitors
JMX / SNMP Dashboard
File System Monitor
Windows Performance Counters
Script Monitor
Database Query Monitor
Web Transactions Monitors
JavaRuby on Rails
.NET
Others
Java Runtime Monitor
Monitor Types
Applications Manager supports monitoring for the following monitor types:
Application Servers
Cloud Apps
Custom Monitors
Database Servers | NoSQL Database Servers
ERP
Mail Servers
Middleware/Portal
Servers
Virtualization
Converged Infrastructure
Web Server/Services
Services
Application Servers
Application Servers are designed to develop web services and applications, and in real time, the productivity and
performance of such servers get affected due to failure of diagnosing any problem in the services/application
running in the server.
Applications Manager enables high performance business process management by detecting and diagnosing
problems of application servers and their services faster. The following are the application servers supported:
Microsoft .NET
GlassFish Servers
JBoss Servers
Jetty Servers
Resin Servers
Oracle Application Servers
SilverStream
Tomcat Servers
VMware vFabric tc Server
WebLogic Servers
WebSphere Servers
Apache Geronimo Servers
Please browse through the different application servers that provide the server information and their parameters
being monitoring.
Java Runtime Monitors
Java Runtime Monitoring - Overview
Java Runtime Monitor provides out-of-the-box remote monitoring and management on the Java platform and of
applications that run on it. It monitors performance metrics like Memory (JVM), Garbage Collection (GC) andThread Statistics. Thresholds can be associated and alarms generated. Further, operations such as Automated
Thread dump, Heap dump and PerformGC for management are also supported. The different JVM vendors
supported by Applications Manager are Sun JVM, IBM JVM and Oracle JRockit JVM.
In this help document, you will learn how to get started with Java monitoring along with the list of parameters that
are monitored using Applications Manager.
Creating a new Java Runtime monitor
Prerequisites for Java Runtime Monitor: Know more about the JVM arguments to add to your application for Java
Runtime Monitoring
Using the REST API to add a new Java Runtine monitor: Click here
Click New Monitor. Choose Java Runtime.
Enter the IP Address or hostname of the host in which the Monitor is running.
Enter the SubNetMask of the network.
Provide the port number in which JDK is running (default: 1099). Also, you can provide multiple ports separated
by commas.
You can enter your own credential details or select preconfigured credentials details in Credentials Manager. If
you wish to enter your own credentials, specify username and password details for this monitor.
Enter the JNDI name. For example, /jmxrmi.
To enable customized JMX URL, check the Enable JMX URL checkbox and enter the JMX URL. (The URL should
be of the format service:jmx:rmi:///jndi/rmi://HOST:PORT/jmxrmi. For example, a jboss customized jmx URL
can be - service:jmx:remoting-jmx://HOST:PORT/ and a websphere customized jmx URL -
service:jmx:wsrmi://HOST:PORT/)
If Authentication is enabled, enter the username and password.
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group, to which you want to associate the Monitor (optional). You can choose multiple
groups to associate your monitor.
Click Add Monitor(s). This discovers the Monitors from the network and starts monitoring them.
Note:
Support is available for JRE1.5 and above for Java Runtime. Support for Heap dump operation is available
if HotSpotDiagnostic MBean is present in the JVM.
Support given for JDK 1.8 : When monitoring with JDK 1.8 MetaSpace, Applications Manager monitors and
displays new memory space called MetaSpace and Compressed Class Space instead of the former
Permanent Generation (Non-Heap).
In case you are unable to add the monitor even after enabling JMX, try providing the below argument:
-Djava.rmi.server.hostname=[YOUR_IP]
Monitored Parameters
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Java Runtime Monitor checks the availability, response time, connection time (time taken by the Applications
Manager to look up the JMX agent on the remote JVM) of the monitor, along with many other parameters listed
below.
Overview
Garbage Collection
Threads
Configuration
Overview
Parameter Description
Monitor Information
Name Name of the JavaRuntime monitor.
Health Specifies the health (Clear, Warning, Critical) of the JavaRuntime monitorType Specifies the type you are monitoring.
Host Name Specifies the host at which the Java virtual machine is running.
Port Specifies the port number at which the Java virtual machine is running.
Host OS Specifies the OS of the host where the JavaRuntime monitor is running.
JVM Specifies the Java virtual machine name and version.
Vendor Specifies the Java virtual machine Vendor Name.
Processor Count Specifies the number of processors available to the Java virtual machine.
Last Polled at Specifies the time at which the last poll was performed.
Next Poll at Specifies the time at which the next poll is scheduled.
Availability Shows the current status of the JavaRuntime monitor - available or not available.
Connection Time Time taken to connect to the Java virtual machine.
Memory Pool
Eden Space (Heap Memory) The pool from which memory is initially allocated for most objects.
Survivor Space (Heap
Pool containing objects that have survived GC of eden space.
Memory)
Tenured Generation (Heap
Pool containing objects that have existed for some time in the survivor space.
Memory)
Java Heap Space where the JVM stores the objects.
Permanent Generation Holds all the reflective data of the virtual machine itself, such as class and method
(Non-Heap) (for versions objects. With JVMs that use class data sharing, this generation is divided into read-
older than JDK 1.8) only and read-write areas.
The Native memory space for the representation of class metadata is called
MetaSpace (for JDK 1.8) Metaspace. MetaSpace use native memory to store meta-data and that grows
automatically.
Compressed Class
Compressed Class Space contains only class metadata.
Space (for JDK 1.8)
Code Cache (Non-Heap) Memory used for compilation and storage of native code.
JIT Code Cache Memory that is converted to assembler and stored for running at higher speed.
Nursery Separate space for newly allocated objects.
Class Loading
Classes loaded Number of classes loaded
Classes Unloaded Number of classes unloaded
JVM Statistics
Specifies the percentage of load on the machine caused by the JVM.
CPU Load
0 indicates no load is created and 100 indicates all load is created by the JVM
CPU Usage This indicates the CPU usage of the JVM on the server.
Max file descriptor Maximum permissible open file descriptor. Available only for UNIX.
Host Memory
Total Physical Memory Total amount of physical memory in Megabytes.
Free Physical Memory The amount of free physical memory in Megabytes.
Total Swap Space Total amount of swap space in Megabytes.
The amount of virtual memory that is guaranteed to be available to the running
Committed Virtual Memory
process in Megabytes.
Garbage Collection
Parameter Description
Garbage Collector
Time Spent/Min Approximate collection elapsed time in milliseconds.
Collections/Min Total number of collections that have occurred.
Thread Count Number of threads used for Garbage Collector.Last Start Time Start time of this GC.
Last End Time End time of this GC.
Memory usage before GC Memory usage of all memory pools at the beginning of this GC.
Memory usage after GC Memory usage of all memory pools at the end of this GC.
GC time Time taken to perform garbage collection.
Compile time Time spent in just-in-time (JIT) compilation.
Threads
Parameter Description
Thread Parameters
Total threads
Total number of threads created and also started since the Java virtual machine started.
started
Peak Threads Peak live thread count since the Java virtual machine started or peak was reset.
Live Threads Number of live threads currently running.
Daemon Threads Number of daemon threads currently running.
Runnable Threads A thread executing in the Java virtual machine is in this state.
Blocked Threads A thread that is blocked waiting for a monitor lock is in this state.
A thread that is waiting indefinitely for another thread to perform a particular action is in this
Waiting Threads
state.
Timed waiting A thread that is waiting for another thread to perform an action, for up to a specified waiting
Threads time is in this state.
Deadlocked Number of threads that are in deadlock waiting to acquire object monitors.
Configuration
Parameter Description
Configuration Information
Uptime The uptime of the Java virtual machine.
Java Virtual Machine The Java virtual machine implementation name.
Vendor The Java virtual machine implementation vendor.
The process identifier is a number used by some operating system kernels to uniquely
Process ID
identify a process.
Name The name representing the running Java virtual machine.
The input arguments passed to the Java virtual machine which does not include the
VM arguments
arguments to the main method.
Class path The Java class path that is used by the system class loader to search for class files.
Library path The Java library path.
Boot class path The boot class path that is used by the bootstrap class loader to search for class files.
JIT compiler The name of the Just-in-time (JIT) compiler
Objects Pending for
The approximate number of objects for which finalization is pending.
finalization
Operating System The name of the operating system.
Architecture The operating system architecture.
Processors The number of processors available to the Java virtual machine.
The maximum metaspace containing all other large class metadata including methods,
Max Metaspace
bytecode ,constant pool etc.
Max Non Heap = Commit Non Heap + free Physical Memory.
Max non-heap Note: In case of Virtual Memory also, we consider only Free Physical Memory to
calculate Max Metaspace value.The table below lists the different JVM vendors supported by Applications Manager and the major parameters
monitored by them.
Parameters Monitored Sun JVM IBM JVM JRockit JVM
Connection Time
Memory Usage
CPU Usage
CPU Load
System Memory
Process Memory
Heap Memory
Non Heap Memory
VM Statistics
Total Physical Memory
Free Physical Memory
Total Swap Space
Free Swap Space
Committed Virtual Memory
Garbage Collector- Summary
Garbage Collector - View impact for specific collector
Total Threads Started
Peak Threads
Live Threads
Runnable Threads
Blocked Threads
Waiting Threads
Timed Waiting Threads
Daemon Threads
Deadlocked
Configuration Details
JVM Actions
View Thread Dump
There is an option to view the thread dump history under ''Threads'' tab. Click the ''View Thread Dump'' link in the
threads tab. The Thread Dump screen will open up in a new window and you will be able to view the current thread
dump details. Once you close this window, the thread dump details will be moved under the Thread
Historysection. You can view this information any time you want from this section.
Reports
We provide the option to view both realtime and historical data of any of the attributes present in the ''Configuration
Information'' section in the Configuration tab. Click on any attribute under the Configuration tab. This will open up a
new window named ''History Data'' that provides more information about these attributes.
There are two tabs in the History Data window - History Report and Global View
History Report: This tab provides historical reports of the attribute selected based on time period chosen. You can
also use the Select Attribute drop-down box and view reports for other attributes.
Global View: This tab displays the current values of the attribute selected, across multiple monitors. To view
information about other attributes present in the monitor, use the Select Attribute drop-down box and change the
attribute.
If you want to view data of multiple attributes, click the Customize Columns link present at the top left corner of the
window. This will take you to the Edit Global Viewscreen. In this screen, you can change the monitor type using
the Filter by Monitor Type drop-down box, select the metrics to be displayed, and show monitors on a monitor
basis or a monitor group basis. After you select your options, click the Show Report button to view those
information in the Global View tab.Note: If jmx connection is not being established in the machine where Applications Manager is installed, use
this key and restart your application:
-Djava.rmi.server.hostname=YOUR_IP
Help Links for Reference
Tuning Garbage Collection with the JVM
FAQ About the Java HotSpot VM
FAQ about Garbage Collection in the Hotspot JVM
Java Performance Documentation
Microsoft .NET Monitoring
Creating a new .NET monitor
To create Microsoft .NET Monitor
Click on New Monitor link.
Select Microsoft .NET Monitor.
Enter the IP Address or hostname of the host where .NET runs.
Enter the SubNetMask of the network.
Set the Polling Interval.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Enter the User Name / Domain Name and Password of the system.
Choose the Monitor Group from the combo box with which you want to associate .NET Monitor (optional). You
can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers .NET from the network and starts monitoring them.
Monitored Parameters
Microsoft .NET is monitored based on the attributes such as Heap Size, Threads etc. Data collection happens
through WMI. The monitoring details of Microsoft .Net are represented graphically and that helps to understand
the parameters with ease. You can also configure thresholds to the attributes monitored by the .Net, based on
these details.
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Parameter Description
Availability Shows the current status of the .NET - available or not available.
Threads
Shows the number of native OS threads created and owned by the CLR
Physical Threads
to act as underlying threads for .NET thread objects.
Logical Threads Shows the number of current .NET thread objects in the application.
Memory
Heap Size Shows the current memory allocated(MB)
Shows the percentage of elapsed time that was spent in performing a garbage
collection (GC) since the last GC cycle. This counter is usually an indicator of the work
% Time in GC
done by the Garbage Collector on behalf of the application to collect and compact
memory
Locks
Queue Length Refers to the total number of threads currently waiting.
Refers to the rate at which threads in the runtime attempt to acquire a managed lock
Contentions/Min
unsuccessfully.
Exceptions
Exceptions/Min Refers to the number of exceptions per Minute
SecurityTotalRuntimeChecks/Min Refers the total number of runtime Code Access Security (CAS) checks performed per
minute.
JIT
Refers to the percentage of elapsed time spent in JIT compilation since the last JIT
% Time In JIT
compilation phase.
.NET Applications Details
Name Name of the .NET Application.
Active Sessions Refers to number of sessions that are active currently
Requests/Min Refers to number of Requests executed per minute
.NET Applications Details
Clicking on the Names of the .NET applications, you can see their performance based on their parameters. The
various .NET application''s parameters that are monitored are:
Parameter Description
Request Statistics
Requests/Min Refers to number of Requests executed per minute
Errors/Min Refers to rate of errors occured
Requests Timeout/Min Refers to number of Requests Timeout per minute
Queued Requests Refers to number of Queued Requests
Transactions
Transactions/Min Refers to number of Transactions started per minute
Abandoned
Refers to number of Transactions aborted per minute
Transactions/Min
Pending Transactions Refers to number of Transactions in progress
Sessions
Active Sessions Refers to number of sessions that are active currently
Network Traffic
Bytes Sent/Min Bytes Received/Min
Refers to the number of
Refers to the number of Bytes received per minute
Bytes sent per minute
GlassFish Servers
Creating a new GlassFish monitor
Prerequisites for monitoring GlassFish metrics: Click here
Using the REST API to add a new GlassFish monitor: Click here
Follow the steps given below to create a new GlassFish application server monitor:
Click on New Monitor link.
Select GlassFish.
Enter the Display name.
Enter the HostName of the host where GlassFish runs.
Enter the Port
Enter the credential details like user name and password for authentication, or select the required credentials
from the Credential Manager list by enabling the Select from Credential list option.
Enter the JNDI path.
Specify the Polling Interval in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which you want to associate GlassFish Monitor (optional).
You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers GlassFish Servers from the network and starts monitoring them.
Note:
In case you are unable to add the monitor even after enabling JMX, try providing the below argument:
-Djava.rmi.server.hostname=[YOUR_IP]Monitored Parameters
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configuration.
GlassFish servers are monitored based on the attributes such as memory, thread, etc. The monitoring details of
GlassFish server are represented graphically that helps to understand the parameters with ease. You can also
configure thresholds to the attributes monitored by the server based on these details.
Click on the individual monitors listed to view the following information:
Monitor Information
Performance Overview
Monitor Information
Parameter Description
Name Name of the Server
Availability Shows the current status of the server - available or not available.
Last Polled at Specifies the time when the monitoring of the server was recently done
Next Poll at Specifies the next polling time for monitoring the server
Performance Overview
Parameter Description
RESPONSE TIME:
Response Time Refers to time required for the Glass Fish server to respond while monitoring
MEMORY DETAILS:
Used Memory Refers to JVM heap used in KB
Total Memory Refers to the JVM total heap size
THREAD DETAILS:
Thread Count Total number of Threads in JVM in which GlassFish is running
Running Refers to the state of totals thread that are in runnable state in the JVM
Waiting Refers to the total no. of threads that are waiting for a monitor lock in the JVM
Blocking Refers to no. of total threads that are blocked waiting for a monitor lock
Deadlocked Refers to the no. of total threads that are blocked forever in the JVM
Refers the total threads that are waiting for another thread to perform
Timed Waiting
an action for up to a specified waiting time
Webapp Monitoring:
WebAppName Name of the Web Application
Session High Count Maximum number of concurrently active sessions
Session Current Count List of currently active sessions in the Web Application
Total Sessions Rejected Total number of rejected sessions
JDBC Pool Monitoring:
Jdbc Pool Name Name of the JDBC pool
Max Pool Size Maximum size of pool
Connections Currently in Use Number of connections that are currently in use
Connections Used % Number of connections used (in percentage).
Free Connections Number of free connections
Potential Leaked Connections Number of unauthenticated connections
Wait Queue Length Size of wait queueConnections Timed Out Number of connections which were timed out
JBoss Server Monitoring
Creating a new JBoss monitor
Supported versions of JBoss Server: 3.2.x, 4.x, 4.0.x, 5, 5.1, 6.0, 7.x, Wildfly_8.x
Prerequisites for monitoring JBoss server metrics: Click here
Using the REST API to add a new JBoss monitor: Click here
To create a JBoss server monitor, follow the steps given below:
Click on New Monitor link.
Select JBoss.
Enter the IP Address or hostname of the host where JBoss runs.
Choose the JBoss version.
Enter the port number for eg., 8080.
Check the Is Domain option if the JBoss operating mode is in managed domain. For managed domain,
provide the HOST and PORT of domain controller. All the servers in the managed domain is identified and
automatically added as monitors. This option is available for version 7.x and above.
Enable Filter: Choose this option to filter the addition of monitors for servers in the managed domain.
Filter Condition: Select the option include/exclude and provide the filters in the following format:
HostController1:server1,server2,server3 ; HostController2:server1,server2,server3;...
Choose SSL option , if SSL is enabled in JBoss server.
Enter the User Name and Password , if JBoss has authentication information.
Set the Polling Interval.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which you want to associate JBoss Server Monitor
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers JBoss server from the network and starts monitoring them.
For Applications Manager to monitor JBoss, it should be able to access the host where JBoss server runs and
vice versa. For more information, refer to online Troubleshooting section.
Monitored Parameters
Performance data is collected by deploying an agent automatically from Applications Manager to the JBoss server
that needs to be monitored. JBoss servers are monitored based on the attributes such as JVM heap usage, JDBC
pool usage, JMS Queue, the different web applications and EJB deployed in the server. The monitoring details of
JBoss server are represented graphically that helps to understand the parameters with ease. You can also
configure thresholds to the attributes monitored by the server based on these details.
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configuration.
Click on the individual monitors listed, to view the following information:
Overview
JVM
Deployments
Statistics
JDBC
Web
Transactions
JMS
Configuration
Custom attributes
OverviewParameter Description
SERVER RESPONSE TIME
Response time Response time of JBoss server (in ms).
JVM Usage
This metric gives the current amount of free, used and committed memory in the JVM heap in megabytes as well
as in percentage.
Parameter Description
Memory Usage
Type of the memory pool i.e, (Heap memory , Non-Heap Memory, Code cache
Type
etc.)
Used Memory in MB The amount of memory used by the Java Virtual Machine (in MB).
Free Memory in MB The amount of memory free for the Java Virtual Machine (in MB).
The amount of memory guaranteed to be available for use by the Java Virtual
Committed Memory in MB
Machine (in MB).
Total Memory in MB The total amount of memory allocated for the Java Virtual Machine (in MB).
Used Memory % The amount of memory used by the Java Virtual Machine (in percentage).
Free Memory % The amount of memory free for the Java Virtual Machine (in percentage).
JVM USAGE
JVM Heap Size JVM heap size of JBoss server (in bytes).
Maximum Free Memory (MB) Maximum amount of free memory available (in MB).
Maximum Free Memory Maximum amount of free memory available (in percentage).
THREAD USAGE
Live Threads Number of threads that are currently in use.
Daemon Threads Number of daemon threads available.
Peak Thread Count The maximum number of threads in use at any point of time.
Total Threads Started Total number of threads started.
CLASS LOADING
Class Loaded The number of classes currently loaded in the Java virtual machine.
The total number of classes loaded since the Java virtual machine has started
Total Class Loaded
execution.
Class Unloaded The number of classes unloaded since the Java virtual machine has started.
Object Pending Finalization The approximate number of objects for which finalization is pending.
Deployments
Parameter Description
Deployments
Name Name of the deployment/war file.
Context Context name of the web application.
Enabled Indicates whether the deployment is enabled or not. (true or false)
Runtime Name Runtime name of the deployment.
Status The status of the deployment.
Sub-Deployments The number of sub-deployments.
Servlets The number of servlets present for the deployment.
Web Applications
Name Name of the web application.
Context Context name of the web application.
Active Sessions Number of sessions currently open/active.Created Sessions Number of sessions created.
Expired Sessions Number of sessions expired.
Rejected Sessions Number of sessions rejected.
Duplicated Sessions Number of sessions duplicated.
Session Alive Time (Avg) The average alive time of sessions (in ms).
Statistics
This tab contains the EJB statistics and Servlet details of the JBoss server. The name, type and module of the EJB
along with the number of instance created and removed, instances in passivated state, pooled state, ready state
are being captured. The servlet details specify the number of times the servlet was invoked and the execution time
for the servlet.
Parameter Description
EJB Statistics
Name Name of the EJB appended with the web module name.
EJB Name of the EJB.
Web Module Name of the web module.
Type of EJB. (Any one of the following - "Stateless Session Bean", "Stateful
Type
Session Bean", "Entity Bean", "Message Driven Bean")
Create count Number of EJB bean created.
Removed count Number of EJB bean removed.
Passive count Total number of beans that have been passivated.
Ready count The number of bean instances in ready state.
Method ready count The number of bean methods in ready state.
Pooled count Number of EJBs available in the pool.
Servlet Details
Name Name of the servlet appended with web module name.
Servlet Name of the servlet.
Web module Name of the web module.
The total number of times the servlet has been invoked since Jboss server was
Invocation count
started.
The average amount of time (in ms) all invocations of the servlet have
Exec. Time (Total)
executed since it was most recently deployed.
The average amount of time (in ms) the single longest invocation of the servlet
Exec. Time (High)
has executed since it was most recently deployed.
The average amount of time (in ms) the single shortest invocation of the
Exec. Time (Low)
servlet has executed since it was most recently deployed.
The average amount of time (in milliseconds) it took to execute all invocations
Exec. Time (Avg)
of the servlet since it was most recently deployed.
Connections
Name Name of the session/connection.
Sessions Opened The global number of sessions opened since last poll.
Sessions Closed The global number of sessions closed since last poll.
Connections Requested The global number of connections asked by the sessions since last poll.
Percentage Closed Percentage of session closed.
Statistics Enabled Indicates whether statistics are enabled or not. (true or false)
Transactions
Name Name of the transaction.
The global number of transactions known to have completed since the
Completed
statistics were reset.
The global number of transactions known to have been successful since the
Successful
statistics were reset.Successful Transactions Percentage of successful transactions.
Queries
Name Name of the query.
Query Put Count The global number of cacheable queries put in cache since last poll.
The global number of cached queries successfully retrieved from cache since
Query Hit Count
last poll.
Query Miss Count The global number of cached queries not found in cache since last poll.
Query Hit Ratio The percentage of queries cache hit.
Query Execution Count The global number of queries executed since last poll.
Max-time taken to execute The amount of time taken by the slowest recorded query since last poll.
Slow Query The query that is the slowest.
Second level Cache
Name Name of the cache.
The global number of cacheable entities/collections put in the cache since
Put Count
last poll.
The global number of cacheable entities/collections successfully retrieved
Hit Count
from cache since last poll.
The global number of cacheable entities/collections not found in the cache
Miss Count
and loaded from the database since last poll.
Hit Ratio The percentage of second level cache hit.
JDBC
JDBC Connection Pool details are displayed through this metric. The number of connections that are available,
active, created, timed out and destroyed are listed. Also available are the metrics pertaining to the prepared
statement cache of the database connection in the pools.
Parameter Description
Pool Usage
Name Name of the JDBC pool.
Available The number of available connections in the pool.
The number of active connections. Each of the connections is either in use by
Active
an application or available in the pool.
Created The number of connections created.
Destroyed The number of connections destroyed.
Wait The number of requests that had to wait for a connection.
Maximum Used The maximum number of connections used.
Total Blocking Time(ms) The total time spent waiting for an exclusive lock on the pool (in milliseconds).
Total Creation Time(ms) The total time spent creating connections (in milliseconds).
Timed Out The number of timed out connections.
Idle Time Out in Mins Amount of time (in minutes) after which unused connections are closed.
The percentage of active connections.
Active Connections(%)
Active Connections (%) = (Active / Pool Size) * 100
The percentage of maximum used connections.
Maximum Connections Used(%)
Maximum Connections Used(%) = (Max Used / Pool size ) * 100
Prepared Statement Cache
Name Name of the cache.
The number of prepared and callable statements currently cached in the
Current Size
statement cache.
Hit Count The number of times that statements from the cache were used.
Miss Count The number of times that a statement request could not be satisfied with a
statement from the cache.Hit Ratio The percentage of prepared statement cache hit.
Web
Parameter Description
Web Metrics
Name Connector name of the global request processor.
Request Count Number of requests served by this global request processor since last poll.
Error Count Number of error request received since last poll.
Maximum time taken by the global request processor to process a request (in
Maximum Time
ms).
Time taken by this global request processor to process the requests since last
Processing Time
poll (in ms).
Bytes Sent Per Second Average number of bytes sent per second.
Bytes Received Per Second Average number of bytes received per second.
Requests Failed Percentage of failed requests.
Transactions
Parameter Description
TRANSACTIONS
Total The total number of transactions created, including nested since last poll.
Committed The number of committed transaction since last poll.
Aborted The number of aborted transactions since last poll.
The number of transactions that have rolled back due to timeout since last
TimedOut
poll.
Nested The total number of nested transactions created since last poll.
Heuristics The number of transactions in a heuristic state since last poll.
The number of transactions which have begun but not yet terminated since
Inflight
last poll.
The number of failed transactions, including timeouts, whose failure origin
Application rollbacks
was an application since last poll.
The number of failed transactions whose failure origin was a resource since
Resources rollback
last poll.
Percentage of successful commits.
Successful commits
Successful commits = (Committed / Total) * 100
Percentage of aborted transactions.
Aborted transactions
Aborted transactions = (Aborted / Total) * 100
Percentage of timedout transactions.
TimedOut transactions
Timeout transactions = (Timeout / Total) * 100
JMS
The JMS tab provides an overview of the metrics related to the JMS Queues and Topics. Queues details include
metrics like messages in queue, messages added, scheduled, paused along with current delivery percentage.
Metrics with respect to topics tracked are message count, messages added, durable and non-durable message
count,etc.
Parameter Description
QUEUES
Name Name of the queue.
Is paused Indicates whether the JMS Queue is paused or not.Messages in Queue The number of messages currently in this queue.
The number of messages that this queue is currently delivering to its
In Delivery
consumers.
Messages Added The number of messages added to this queue since it was created.
Messages Scheduled The number of scheduled messages in this queue.
Number of Consumer The number of consumers consuming messages from this queue.
Percentage of message currently delivering.
Currently Delivering
Currently Delivering = (In Delivery / Messages in Queue) * 100.
TOPICS
Name Name of the topic.
Messages in Topic The number of messages currently in this topic.
No of Durable Messages The number of messages for all durable subscribers for this topic.
No of Non-Durable Messages The number of messages for all non-durable subscribers for this topic.
Subscriptions The number of durable and non-durable subscribers for this topic.
No of Durable Subscribers The number of durable subscribers for this topic.
No of Non-Durable Subscribers The number of non durable subscribers for this topic.
Percentage of durable messages.
Durable Messages
Durable Messages = (No of Durable Messages / Messages in Topic) * 100
Percentage of non-durable messages.
Non-Durable Messages
Non-Durable Messages = (No of non Durable Messages / Messages in Topic) *
100
Configuration
Parameter Description
SERVER CONFIGURATION
Launch Type Launch type of the JBoss server.
Host Name / IP Address Hostname/IP address on which the JBoss server is running.
Process Type The process type of JBoss server.
JBoss Version Version of JBoss running.
Release Codename Release codename of the JBoss server.
Server State Current state of the server.
Running Mode The mode in which the JBoss server is currently running.
Available Processors Number of processors available for the JBoss server.
Operating System Operating system on which the JBoss server is running.
Product Name Name of the JBoss product.
Server Name Name of the server hosting the JBoss application.
Is Master Indicates whether the JBoss server is the master or not.
Host Controller Name Name of the host controller.
Server Group Name of the server group.
Custom attributes
You can view the custom attributes of the JBoss Server here. Click Add Attributes to add custom MBean attributes
and associate MBean actions. For information on adding Custom Monitors, refer to Custom Monitors topic. Below
is the detailed list of parameters monitored and the various versions of the server supported:
Monitored Parameters JBoss 3.2.x JBoss 4.0.x, JBoss 5,5.1 JBoss 6.0 JBoss 7.0
4.2.2 GA
Memory Usage[Used (MB), Free(MB),
Commited(MB),
Maximum(MB), Used(%),
Free(%)]
* Metrics for non-heap
memory is supported in
JBoss 6&7 only
Thread Usage
[Live Thread count, Daemon
Thread count, Peak Thread
Count, Total Thread Started]
Class Loading
[Class loaded, Class
Unloaded, Total Loaded,
Object Pending Finalization
count]
Deployments
[Name, Context, Enabled, [sub- [sub- [sub- [sub-
[servlets
Runtime Name, Status, Sub- deployment deployment deployment deployment
count not
Deployments, Servlets count not count not count not count not
available]
Count] available] available] available] available]
Web Applications
[Active Sessions, Sessions
Created, Expired, Rejected,
Duplicated and Session Alive
Time]
[instances in
EJB Statistics passive
state, ready
[WebModule,Type,Instances
state, pooled
Created, Removed,
state,
Instances in Passive State,
message
Ready State, Pooled State,
count,
Message Count, Method
method
Ready Count]
ready count
not
available]
Servlet Details
[Invocation Count, Execution
Time Total, Execution Time
High,Execution Time
Low,Execution Time
Average]
Persistence Units
[Connections, Transactions,
Queries, Second Level
Cache]
Connection Pool Usage
[Connections - Available,
Active , Created, Destroyed,
Maximum used, Timed out,
Active Connections(%), Max
Connections Used (%)]Prepared Statement Cache
[Current size, Hit count, Miss
count, HitRatio]
Web Metrics
[Request Count, Error Count,
Processing time(ms),
Maximum time(ms), Bytes
Sent, Bytes Received ,
Request Failed(%)]
[transactions
Transactions
aborted, [transactions [transactions
[Total Transacations, timedout, aborted, aborted,
Commited, Aborted, nested, timedout, timedout,
TimedOut, Nested, heuristics, nested, nested,
Heuristics, Inflight, inflight, heuristics, heuristics,
Applications Rollbacks, applications inflight, inflight,
Resource Rollbacks, rollbacks, applications applications
Successful Commits] resource rollbacks, rollbacks,
rollbacks not resource resource
available] rollbacks not rollbacks not
available] available]
JMS-Queues
[Name, Message Count, In
Delivery, Messages Added,
Messages Scheduled,
Consumer Count, Is Paused,
Delivering Percentage]
JMS-Topics
[Name, Message Count, In
Delivery, Messages Added,
Durable Message Count,
Non- Durable Message
Count, Subscriptions,
Durable Subscribers Count,
Non-Durable Subscribers
Count,Current Delivering (%),
Durable Message(%), Non-
Durable Message(%)]
Custom Attributes and
Server Configuration Details
Jetty Server Monitoring
Overview
Jetty, the lightweight open-source project hosted by the Eclipse foundation, is a full-fledged HTTP server and
Servlet container that can be easily configured to serve static and dynamic content. Unlike most Web Servers, Jetty
is often used for machine to machine communications, usually within larger software frameworks.
Applications Manager allows you to monitor your Java applications running on the Jetty HTTP server and Servlet
container, track critical performance indicators of Jetty App server like CPU usage and be notified of thread pool
exhaustion. Applications Manager also provides an in-depth view of the memory usage - heap and garbage
collection information, real-time memory utilization and even object instance information within the JVM and Jetty
server.
Creating a new Jetty server monitor
Supported versions of Jetty Server: Jetty 3.1 and above.Prerequisites for monitoring Jetty Server: Click to know about the user previleges and other necessary
prerequisites to monitor Jetty Server.
To create a Jetty monitor, follow the steps given below:
Click on New Monitor link.
Select Jetty Server under Application Servers.
Give the Display name.
Enter the Hostname of the server where Jetty Server is running.
Enter the JMX Port. For default installations of Jetty, the JMX port number is 9999.
You can enter your own credential details or select preconfigured credentials from details in Credentials
Manager. If you wish to enter your own credentials, specify enter the JMX User Name and Password of Jetty
Server. If no authentication is required, then leave the fields blank.
Enter the JNDI path. For example:- JNDIPATH for default installations of Jetty is /jmxrmi.
Set the Polling interval.
Choose the Monitor Group from the combo box with which, you want to associate Jetty Server Monitor
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers your Jetty Server from the network and starts monitoring it.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Jetty Server under the Applications
Servers Table. Displayed is the Jetty Server bulk configuration view distributed under three tabs:
Availability tab, gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations
Click on the monitor name to see all the server details listed under the following tabs:
Performance Overview
Thread
WebApps
Configuration
Performance Overview
Parameter Description
CPU Details
Available Processors The number of processors available to the JVM.
CPU Usage Percentage The percentage of CPU usage of the JVM on the server.
Uptime The uptime of the Java virtual machine.
Class Loading Details
Loaded Class Count The number of classes currently loaded in the JVM.
Unloaded Class Count The number of classes unloaded since the JVM started execution.
Heap Memory
The pool containing objects that have survived the garbage collection of the
PS Survivor Space
Eden space.
PS Eden Space The pool from which memory is initially allocated for most objects.
This pool contains tenured and virtual (reserved) space and will be holding
PS Old Gen those objects which survived after garbage collection from young generation
space.
Non Heap Memory
The Permanent Generation holds all the reflective data of the virtual machine
PS Perm Gen itself, such as class and method objects. With JVMs that use class data sharing,
this generation is divided into read-only and read-write areas.
The Code cache is the memory used for compilation and storage of native
Code Cache
code.
Heap Memory DetailsTotal Memory The total memory is the memory that is currently allocated to the JVM. It is the
combination of used memory currently occupied by objects and free memory
available for new objects. It varies over time.
Free Memory (MB) The total free memory available to the JVM for new objects.
Used Memory (MB) The space that is currently occupied by Java objects.
Max Allocated Memory (MB) The currently allocated memory in MB.
Committed Memory (MB) The currently used memory in MB.
Non Heap Memory Details
The total memory is the memory that is currently allocated to the JVM. It is the
Total Memory combination of used memory currently occupied by objects and free memory
available for new objects. It varies over time.
Free Memory (MB) The total free memory available to the JVM for new objects.
Used Memory (MB) The space that is currently occupied by Java objects.
Max Allocated Memory (MB) The currently allocated memory in MB.
Committed Memory (MB) The currently used memory in MB.
Garbage Collector Details
Name The Garbage Collector Name.
Valid The Garbage Collector Status.
Live JVM statistics about garbage collector activity like the time spend
Collection Time (MS)
collecting objects.
The Live JVM statistics about garbage collector activity like the number of
Collection Count
collected objects.
Note:
Java8 Update: When monitoring with JDK 1.8 MetaSpace, Applications Manager monitors and displays new
memory space called MetaSpace instead of the former Permanent Generation (Heap and Non-Heap memory).
The main difference is that Metaspace re-sizes dynamically i.e., It can expand at runtime. Java Metaspace
space: unbounded (default)
Thread
Parameter Description
JVM Threads
Live Threads The current live thread count.
Daemon Total number of Daemon Threads. A daemon thread is one that does not prevent the JVM from
Threads exiting when the program finishes but the thread is still running.
Peak Thread
The peak live thread count since the Java virtual machine started or peak was reset.
Count
Threads
started per The number of threads started per sec.
sec
Thread Pool Details
Name The name of the thread pool.
Thread Count The total number of threads currently in the pool.
Busy Threads The number of currently busy threads in the thread pool.
Idle Threads The number of currently idle threads in the thread pool.
The maximum number of threads in the thread pool simultaneously tasked with some work to
Max Threads
process.
Thread
The percentage of threads used by the java process.
Utilization
Queue size The size of the job queue
State The lifecycle state for this instance.
Low on This value is true if the pools is at maxThreads and there are not idle threads than queued jobs.Threads
Webapps
Parameter Description
Webapps
Name The name of the Session.
Id The session Id.
Active Sessions The number of currently active sessions.
State The current lifecycle state.
Configuration
Parameter Description
Server Info
VM Name The Java virtual machine implementation name.
VM Vendor The Java virtual machine implementation vendor
VM Version The Java virtual machine Version
Name The name representing the running Java virtual machine.
Version The operating system version
OS Name The operating system name.
Start Time The timestamp at which the Java virtual machine was started.
Jetty Version The Version of Jetty server.
Resin Application Server Monitoring
Creating a new Resin server monitor
To create a new Resin server monitor, follow the steps given below:
Click on New Monitor link.
Select Resin Server under Application Servers.
Give the Display name.
Enter the Hostname of the server where Resin Application Server is running.
Enter the JMX Port. For default installations of Resin, the JMX port number is 9999.
You can enter your own credential details or select preconfigured credentials from details in Credentials
Manager. If you wish to enter your own credentials, specify enter the JMX User Name and Password of Resin
Server. If no authentication is required, then leave the fields blank.
Enter the JNDI path. For example, JNDIPATH for default installations of Resin is /jmxrmi.
Set the Polling interval.
Choose the Monitor Group from the combo box with which, you want to associate Resin Server Monitor
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers your Resin Server from the network and starts monitoring it.
Resin is a fast and reliable Java EE integrated high-performance application server that features load balancing for
increased reliability. Built-in Resin features include clustering for high scalability, distributed caching to reduce
reliance on traditional databases and adaptive health monitoring. Applications Manager increases the reliability of
your Resin Application Server by monitoring all of the key performance indicators like thread details, connection
pool usage, session details and memory resources.
Resin Server - Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Resin Server under the Application
Servers Table. Displayed is the Resin Server bulk configuration view distributed into three tabs:
Availability tab, gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.Click on the monitor name to see all the server details listed under the following tabs:
Performance Overview
Threads
Memory
Web Applications
Connection Pools
Configuration
Performance Overview
Parameter Description
JVM Statistics
JVM Memory The current total amount of memory available for the JVM, in MB.
Free JVM Memory The current free amount of memory available for the JVM, in MB.
JVM Memory Used The current used amount of JVM memory, in MB.
State The current lifecycle state.
Sever Request Throughput
Request Serviced/Sec The total number of requests serviced by the server per sec.
Bytes Read/Sec The total number of bytes that requests serviced by this server have read.
Bytes Written/Sec The total number of bytes that requests serviced by this server have written.
Transcation Manager
Commited Transactions/Sec The total number of committed transactions/Sec.
Failed Commited Transactions/Sec The total number of failed committed transactions/Sec.
Rollback Transactions/Sec The total number of rolledback transactions/Sec.
In-Progress Transactions The count of in-progress transactions.
CPU Details
Available Processors Number of processors available to the JVM.
CPU Usage Percentage The CPU usage of the JVM on the server in Percentage.
Uptime The uptime of the Java virtual machine.
Class Loading Details
Loaded Class Count The Number of classes loaded.
Unloaded Class Count The Number of classes unloaded.
Garbage Collector Details
Name Garbage Collector Name.
Valid Garbage Collector Status.
Collection Time Time taken to perform garbage collection in ms.
Collection Count Total number of collections that have occurred.
Threads
Parameter Description
Total Threads Total Thread count.
Total Threads Started Total number of threads started.
Active Resin Threads The current number of active resin threads.
Idle Resin Threads The current number of idle resin threads.
Resin Threads waiting The current number of wait threads.
Max Resin Threads The configured maximum number of threads.
Total Resin Threads The current number of managed threads.Memory
Both Heap memory and Non-Heap memory details can be viewed in this tab along with their sub-memory types.
Heap memory types include Eden, Survivor and Tenured memories, and Non-Heap memory types include
CodeCache and PermGen memories respectively.
Parameter Description
Total Memory Total memory of various storage arrays with used memory and free memory split-up.
Free Memory Free memory in MB.
Used Memory Used memory in MB.
Max allocated Memory Max allocated Memory in MB.
Committed Memory Committed memory in MB.
Used Memory % The percentage of used memory.
Web Applications
Parameter Description
Name Name of the Web Application.
Active Sessions The current number of active sessions.
Invalidated Sessions The total number of sessions that have been invalidated.
Session Max The configured maximum number of sessions in memory.
Session Utilization Percentage of session''s used by the webapp.
Requests/Sec The number of requests served by the web-app per sec.
Bytes Received/Sec The total number of bytes received in client requests.
Bytes Sent/Sec The total number of bytes sent to clients.
500 Errors The total number of 500 status errors.
State The current lifecycle state.
Connection Pools
Parameter Description
Name The Name of the Connection Pool.
Active Connections The current number of active connections.
Idle Connections The current number of idle connections.
Total Connections The current number of idle and active connections.
Failed Connections The current number of failed connections.
Max Connections The configured maximum number of connections.
Pool Utilization Percentage of connection pool used.
Configuration
Parameter Description
VM Name The Java virtual machine implementation name.
VM Vendor The Java virtual machine implementation vendor.
VM Version The Java virtual machine Version.
Name The name representing the running Java virtual machine.
Boot Classpath The boot class path that is used by the bootstrap class loader to search for class files.
ClassPath The Java class path that is used by the system class loader to search for class files.
Library Classpath The Java library path.
Version The operating system version.
OS Name The operating system name.
Start Time The start time of the Java virtual machine in milliseconds.Oracle Application Servers
Creating a new Oracle monitor
Supported Versions: Applications Manager supports monitoring of Oracle Application Servers 10g.
Prerequisites: Applications Manager uses the Dynamic Monitoring Service (DMS) provided by Oracle
Application Server to monitor the same. For this reason, the DMS Servlet has to be made accessible to the system
where the Applications Manager is running. Refer Prerequisites section.
To create a Oracle Application server monitor, follow the steps given below:
Click on New Monitor link.
Select Oracle AS.
Enter the IP Address or hostname of the host where Oracle Application Server runs.
Enter the SubNetMask of the network.
Enter the Port number for eg., 7200.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which, you want to associate Oracle Application Server
Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers Oracle Application Server from the network and starts monitoring them.
Monitored Parameters
Oracle Application servers are monitored based on the attributes listed below. The monitoring details of Oracle
Application server are represented graphically that helps to understand the parameters with ease. You can also
configure thresholds to the attributes monitored by the server based on these details.
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the individual monitors listed, to view the following information:
Parameter Description
Monitor Information
Port The port at which the Oracle Application server listens.
Last Polled at Specifies the time when the monitoring of the server was started.
Availability Shows the current status of the server - available or not available.
Request Throughput
Throughput Number of requests processed per unit of time in the server.
Current Active Connection Shows the current active connections
Average Connection Process Time Gives the average processing time of the connections
Current Active Request Shows the number of requests that are active currently
Server Response Time
Response Time Refers to the time required for the server to respond while monitoring.
Data Throughput Refers to how much data is transferred per unit time
Data Processed Refers to how much data is processed per request
Servlets Total number of servlets
OPMN Process Memory Stats (Memory statistics of the OPMN processes like dcm-daemon, WebCache,
WebCache Admin, HTTP_Server, home)
Used Memory Gives the total physical memory used by the process
Status Gives the availability status of the process
oc4j JVM Statistics
Active Thread Groups Shows the number of Active Thread groups in the JVM
Active Threads Shows the number of Active Threads in the JVM
Heap Usage Shows current heap memory usage of the processJDBC Connections Gives the total number of JDBC Connections
Transactions Gives the total number of open, committed and aborted JDBC transactions
Web Applications
Servlets Total number of servlets in the web application
Throughput Number of requests processed per unit of time in the web application
Process Request Time taken to process the request
Active Request Current number of active requests for the web application
Active Session Number of active sessions of the web application
Session time Total time for which the sessions have been active
JMS Attributes
Deque Avg Average time to deque messages
Enque Avg Average time to enque messages
Pending Message Total number of message waiting to be processed
Message Dequeued Total number of messages dequeued
Message Enqueued Total number of messages enqueued
Message Count Number of messages in the JMS Destination
EJB Statistics
EAR Name Name of the Enterprise Application Resource
Process Name of the oc4j process to which the EJB belongs to
Type Gives the type of the EJB
Create Count Number of EJBs created
Active Count Number of active EJBs
Passive Count Number of passive EJBs
Pooled Count Number of pooled EJBs
Response Summary Gives the count for the various HTTP responses
Tomcat Servers
Supported Versions
The supported versions of Tomcat Servers are 3.x, 4.x, 5.x, 6.x, 7.x and above. For Tomcat Server 3.x and 4.x,
agent has to be deployed for Tomcat monitoring.
Note: You can check whether the Agent is deployed, by connecting to the following URL in Tomcat Server.
http://:/adventnet/DataServlet
To deploy the agent for Tomcat Server 3.x
Download the Tomcat3Agent.Zip from /working/classes directory.
Unzip it in the directory of the host in which the Tomcat server is running.
Restart the Tomcat Server.
To deploy the agent for Tomcat Server 4.x
Download the Tomcat4Agent.Zip from the /working/classes directory
Unzip it in the directory of the host in which the Tomcat server is running.
Add the following tag in server.xml file located in the /conf directory (below the Engine tag).
/working/classes directory
Unzip it in the directory of the host in which the Tomcat server is running.Add the following tag in server.xml file located in the /conf directory (below the Engine tag).
/conf directory.
For Tomcat 8:
Remote access to Application Manager is restricted, by default.
Add the IP address of APM in CATALINA_HOME/webapps/manager/META-INF/context.xml (under ''allow ='' )
After adding the roles for the "tomcat" user, the modified entries will be as follows:
On making the configuration, restart the Tomcat Server.
Now, when adding a new Tomcat (5.x and above) monitor, specify the username/password as tomcat/tomcat
when discovering the Tomcat Server.
[Click the link to view an example tomcat-users.xml for versions 5.x / 6.x and tomcat-users.xml for versions 7.x]
Note:
After adding the Manager role in tomcat-users.xml, you should be able to access the manager
application - :/manager/status (Provide manager user credentials).
If the application is not accessible, add the following entry in server.xml, under ''Engine'' context:
\deploy\jbossweb-
tomcat50.sar\ROOT.war\WEB-INF folder
"
Status Servlet
/manager/status
Status Servlet
/manager/
Status Servlet
/manager/status/
"
Restart the JBoss server.
Configure a tomcat monitor by clicking New Monitor --> Select Tomcat Server in the combo box.
Select the version as 5.x and create the monitor. This will create a monitor for the Tomcat webserver
running in JBoss3.2.5.
Configurations based on Tomcat Server Deployment
Monitoring of Tomcat Server depends on its deployment. This section explains the possible deployment scenarios
of Tomcat. Your configuration of host name and the port depends on these scenarios.
1. Standalone Tomcat Server
This is a general scenario wherein you have a Tomcat server which has the HTTP (apache) within its deployment. In
this case, when configuring a tomcat monitor, specify the host name of the Tomcat server and the port of the HTTP.
2. One Tomcat Server (with HTTP) and one external instance of Apache
There is one Tomcat server with HTTP (apache) instance running in it and another external Apache running outside.
Example: Tomcat server name: Tomcat A; HTTP (in Tomcat server) port: 8080; External Apache server port: 80In this case, while configuring for a Tomcat monitor, specify the host name as ''Tomcat A'' and specify the port of the
HTTP that runs with the Tomcat and not the external Apache, i.e., specify the port as 8080 and not 80.
3. One Tomcat Server (without HTTP) and one external instance of Apache
There is one Tomcat server without HTTP in it and another external Apache running.
Example: Tomcat server name: Tomcat A; HTTP (in Tomcat server) port: Not available; External Apache server
port: 80
In this case, while configuring for a Tomcat monitor, specify the host name as ''Tomcat A'' and specify the port of the
external Apache, i.e., 80.
4. Multiple Tomcat Server (with HTTP instances in each of these servers) and one external instance of Apache
There are multiple Tomcat servers, say 3, with HTTP instances in each of them and another external Apache
running.
Example: Tomcat Server names: Tomcat A, Tomcat B, Tomcat C; HTTP (in Tomcat servers)
port: 8070, 8080, 8090 respectively; External Apache server port: 80
In this case, you need to create tomcat server monitor individually for Tomcat A, Tomcat B, and Tomcat C and
specify their ports as 8070, 8080, and 8090 respectively.
5. Multiple Tomcat Server (without HTTP instances in these servers) and one external instance of Apache
There are multiple Tomcat servers, say 3, without HTTP instances in them and another external Apache running.
Example: Tomcat Server names: Tomcat A, Tomcat B, Tomcat C; HTTP (in Tomcat servers) port: Not available;
External Apache server port: 80
You can monitor only one of the instances in this case. Please contact appmanager-
support@manageengine.com if you would like to have it added.
Monitored Parameters
Tomcat Servers are monitored based on the parameters or the attributes listed below. These attributes provide
information about the functioning of the Monitors of Tomcat server. You can also configure thresholds to the
numerical attributes monitored by the server based on these details.
Availability tab, gives the Availability history for the past 24 hours or 30 days. Performance tab gives the Health
Status and events for the past 24 hours or 30 days. List view enables you to perform bulk admin configurations.
Click on the individual monitors listed, to view the following information.
Overview
Memory
Thread
JDBC
Web
Web Applications
Servlets
Overview
Parameters Description
Availability Shows the current status of the server - available or not available.
The time taken for the tomcat server to respond while monitoring in
Response Time
milliseconds
Average Processing Time The average processing time taken to process a request in milliseconds
Requests Per Minute The average number of requests received by the server in one minute
Average Bytes Per Minute The average bytes send per minute
Successful Requests The number of requests served successfully
Errors The number of error request received
Requests Failed percentage Percentage of requests failed.
Class Loaded The number of classes currently loaded in the java virtual machine.Class Unloaded The number of classes unloaded since the java virtual machine has
started
The total number of classes loaded since the java virtual machine has
Total Class Loaded
started execution.
Daemon Threads The number of live daemon threads
Live Threads Current number of live threads
The total number of threads started since the java virtual machine
Total Threads Started
started.
Memory
Parameters Description
Name The memory pool name
Type Memory pool type. i.e, (Heap memory , Non-Heap Memory)
Used Memory in MB Used memory in MB
Free Memory in MB Free memory in MB
Committed Memory in MB Committed memory in MB
Maximum Memory in MB Maximum memory allocated in MB
Used memory in % Percentage of memory used
Free memory in % Percentage of memory free
Name Garbage collector name
Number of collections per Minute Number of garbage collections occurred per minute
Collection Time per Minute Collection time in milliseconds.
Thread
Parameters Description
Connector Name The thread pool connector name
Busy Threads Number of threads currently busy
Current Threads Number of threads currently created
Maximum Threads The maximum number of active threads can present in this pool
Percentage Used Percentage of threads used
Percentage Free Percentage of threads free
JDBC
Parameters Description
JNDI Name The JNDI name of the datasource
Context The web application context name
Active
Number of active connections to the data source
Connections
Idle Connections Number of idle connections to the data source
Active Percentage of active connections (not applicable if maximum active connection is
Connections in % unlimited i.e. configured as -1)
Idle Connections Percentage of idle connections (not applicable if maximum idle connection is unlimited
in % i.e. configured as -1)
Web
Parameters Description
Connector Name Connector name of the global request processor
Request Count Number of requests served by this global request processor
Error Count Number of error request receivedProcessing Time Time taken by this global request processor to process the requests in milliseconds
Bytes Send Per Second Average bytes send per second
Bytes Received Per Second Average bytes received per second
Successful Request (%) Percentage of successful requests
Failed Request (%) Percentage of failed requests
Web Applications
Parameters Description
Context Web application''s context name
Status Status of the web application such as STARTED, STOPPED
Processing Time (ms) The processing time taken to process the requests in milliseconds
Successful Requests Number of successful request served for this web application
Failed Requests Number of error request for this web application
Average Response Time (ms) Average response of this web application in milliseconds
Average Request Per Minute Average requests for this web application per minute
Average Bytes Per Second Average bytes send per second
No.of Open Sessions Number of sessions currently open / active
No.of Expired Sessions Number of sessions expired
No.of Rejected Sessions Number of sessions rejected
Servlets
Parameters Description
URL The name of the servlet
Context Web application''s context name
Processing Time (ms) The processing time in milliseconds
Successful Requests Number of successful request
Failed Requests Number of error request
Average Response Time (ms) Average response time in milliseconds
Average Requests Per Minute Average requests served per minute
SilverStream Servers
To create a SilverStream Server Monitor
Click on New Monitor link.
Select SilverStream.
Give the Display name.
Enter the Hostname of the host where SilverStream Server runs.
Enter the Port number.
Set the Polling interval.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which, you want to associate SilverStream Server Monitor
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers SilverStream Server from the network and starts monitoring them.
Monitored ParametersSilverStream servers are monitored based on the attributes such as memory, thread, etc. The monitoring details of
SilverStream server are represented graphically that helps to understand the parameters with ease. You can also
configure thresholds to the attributes monitored by the server based on these details.
Availability tab, gives the Availability history for the past 24 hours or 30 days. Performance tab gives the Health
Status and events for the past 24 hours or 30 days. List view enables you to perform bulk admin configurations.
Click on the individual monitors listed, to view the following information.
Parameter Description
Monitor Information
Name The name of the server
Health The health of the server
Availability The availability status of the server
Last Polled at The time at which last poll happened
Next Poll at The time at which next poll has been scheduled
Memory Details
Free Memory Available Memory in MB for the JVM
Total Memory Total Memory used by JVM
GC Count No. of time Garbage Collection happened
Request Details
Minimum Response Time The least time taken to process a request
Average Response Time Average time taken to process a request
Maximum Response Time The maximum time taken to process a request
Thread Details
Free Threads No. of free threads
Idle Threads No. of threads that are waiting for a task
Total Threads Total number of threads available
Load Details
Requests No.of requests processed by the server
Current Load Load on the SilverStream Server
Bytes No. of bytes transferred by the server
Session Details
Idle Sessions No.of sessions in idle state
Total Sessions Total number of sessions
License Details
Used Licenses Total number of licenses used
Total Licenses Total number of licenses available
VMware vFabric TC Server Monitoring
Overview
Applications Manager monitors the VMware vFabric tc Server and the Spring applications deployed on the server
to detect any performance problems. This monitoring is carried out by tracking critical components of the vFabric
tc Server such as memory, thread, throughput, garbage collector, etc.
Creating a new VMware vFabric tc server monitor
Supported Versions: The supported versions of VMware vFabric tc Server are 2.6 to 2.9
To create a new VMware vFabric tc Server monitor, follow the steps given below:
Click on New Monitor link.
Select VMware vFabric tc Server.
Provide the Display name of the monitor.
Enter the Host Name in which the vFabric tc Server is running.Enter the Port number in which the JMX Agent is running (6969 by default). The port in which JMX agent is
running; is defined in the ''catalina.properties'' file.
Enter the User Name and Password of the vFabric tc Server.
Specify the JNDIPath. For example, JNDIPath for default installations of vFabric tc Server is /jmxrmi.
Specify the Polling Interval in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which you want to associate vFabric tc Server Monitor
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the vFabric tc Server from the network and starts monitoring it.
Note:
To enable JMX in the tc Server, you have to define a JMX port in the ''catalina.properties'' file and then give an
entry in ''server.xml'' file. For more information on setting values for JMX variables, refer here.
Monitored Parameters
The Availability tab shows the availability history of the vFabric tc Server for the past 24 hours or 30 days. The
Performance tab shows some key performance indicators of the vFabric tc Server such as CPU utilization,
throughput and garbage collection rate. This tab also shows the health status and events for the past 24 hours or
30 days.
The List view lists all the vFabric tc Servers monitored by Applications Manager along with their overall availability
and health status. It enables you to perform bulk admin configurations. Click on the individual monitors listed to
view detailed performance metrics.
To view detailed performance metrics of a vFabric tc Server, click on the monitor name listed in the Availability or
List View tabs. The performance metrics have been categorized into 6 different tabs:
Overview
Web Applications
Throughput
Cache
Transaction
Threads
Configuration Details
Overview
This tab provides a high-level overview of the health and performance of the vFabric tc Server along with
information pertaining to the throughput, thread and garbage collection.
Parameters Description
Memory Details
Memory Used The amount of memory used by the JVM
Memory available The amount of physical memory available.
Used Heap The percentage of heap memory space used.
Total Memory Total amount of physical memory available to the operating system.
CPU Usage
CPU Usage The CPU utilization of the VM.
Throughput>
Bytes Received Per
The average bytes received per second.
Second
Bytes Sent Per Second The average bytes sent per second.
Error Count The number of error request received.
Processing Time The processing time taken to process the requests in milliseconds.
Request Count The number of requests served by this global request processor.
Thread Details
Total number of threads created and also started since the Java virtual machine
Thread Count
started.Threads in Running Total number of threads executing in the Java virtual machine in running state.
State
Threads in Waiting
Total number of threads in the Java virtual machine in waiting state.
State
Blocked Threads A thread that is blocked waiting for a monitor lock is in this state.
A thread that is waiting for another thread to perform an action, for up to a specified
Timed Waiting Threads
waiting time is in this state.
Deadlock Threads Number of threads that are in deadlock waiting to acquire object monitors.
Heap Memory
Eden Space The pool from which memory is initially allocated for most objects.
Tenured Gen The pool containing objects that have existed for some time in the survivor space.
Survivor Space The pool containing objects that have survived GC of eden space.
Non Heap Memory
Perm Gen, Perm Gen Holds all the reflective data of the virtual machine itself, such as class and method
[shared-rw], Perm Gen objects. With JVMs that use class data sharing, this generation is divided into read-
[shared-ro] only and read-write areas.
Code Cache Memory used for compilation and storage of native code.
Garbage Collector
GC Rate The rate of garbage collection.
Average GC Time (ms) Time taken to perform garbage collection.
You can use the Custom Fields option in the ''Monitor Information'' section to configure additional fields for the
monitor.
Support given for JDK 1.8:
When monitoring with JDK 1.8 MetaSpace, Applications Manager monitors and displays new memory space
called MetaSpace and Compressed Class Space instead of the former Permanent Generation (Non-Heap).
Web Applications
This tab provides the details of the various applications running in the vFabric tc Server.
Parameters Description
Context The various applications running.
Active Sessions The number of sessions currently in active state.
Session Creation Rate The number of sessions created per second.
Average Response Time The average response time taken for a particular application.
You can also disable, enable or delete a particular application by using the Actions option and also compare
performance reports of different applications using theCompare Reports option.
Throughput
This tab displays information pertaining to the number of requests received and sent per second in the server.
Parameter Description
Global Request Processor
Name The name of the instances.
Bytes Received Per Second The number of requests received per second in the server.
Bytes Sent Per Second The number of requests sent per second from the server.
Error Count The number of requests, not processed.
Processing Time ms The time taken for a request to be processed in milliseconds.
Request Count The total count of requests.
Cache
This tab contains metrics related to cache memoryParameters Description
Cache The applications running in the server.
Access Count The number of times the application is accessed.
Hits Count The number of times the application is accessed from the cache.
Cache Hit Ratio % The ratio of Hits Count to Access Count.
Transactions
This tab shows information pertaining to the database.
Parameters Description
Transaction Manager- Commits The commit rate transactions per second and failed commits transactions.
Transaction Manager- Resumes The resume rate transactions per second and failed resumes transactions.
Transaction Manager- Rollbacks The rollback rate transactions per second and failed rollbacks transactions.
Transaction Manager- Suspends The suspend rate transactions per second and failed suspends transactions.
Threads
Parameters Description
Thread Details
Total Threads The total number of threads started since the java virtual machine started.
Busy Threads The number of threads currently busy.
Executor Details
Active Threads The number of Active Threads in the JVM.
Max Threads The maximum number of Threads in the JVM.
Pool Size The number of objects in the pool (entity and stateless).
Requests Queue Size The number of requests in the Request Queue.
Configuration Details
Parameters Description
Name The Java virtual machine implementation name.
Version The Java virtual machine Version.
JVM Vendor The Java virtual machine implementation vendor.
Classpath The Java class path that is used by the system class loader to search for class files.
Library
The Java library path.
Classpath
Boot
The boot class path that is used by the bootstrap class loader to search for class files.
Classpath
OS Name The operating system name.
Total Memory
The amount of memory used by this VM.
(MB)
Maximum
The maximum Native memory space for the representation of class metadata is called
Metaspace
Metaspace.MetaSpace use native memory  to store meta-data and that grows automatically.
(MB)
WebLogic Servers
Creating a new WebLogic server monitor
Supported Versions: Following versions of WebLogic Servers can be monitored by Applications Manager:
WebLogic 6.1
WebLogic 7.xWebLogic 8.x
WebLogic 9.x
WebLogic 10.x (WebLogic 11g)
WebLogic 12.x
WebLogic 14.x and above
Prerequisites for setting up WebLogic server monitoring: Click here
Using the REST API to add a new WebLogic monitor: Click here
To create a new WebLogic monitor, follow the steps given below:
Click on New Monitor link.
Select WebLogic Server.
Enter a Display Name for the monitor.
Enter the IP Address/ hostname of the host.
Select the version of your Weblogic Server from drop-down menu.
From the box, select whether SSL is enabled or not.
Enter the port number in which WebLogic is running.
You can enter your own credential details or select preconfigured credentials from details in Credentials
Manager. If you wish to enter your own credentials, specify WebLogic version, username and password
details for this monitor.
Select the action you want to perform on deleted resources using the Action on Deleted Resources field.
Choose one of the following from Discover Clusters and Servers option:
Do not discover: Clusters and managed servers will not be discovered.
Discover but do not monitor metrics: Clusters and managed servers will be discovered and added as
separate monitors, but will be in unmanaged state.
Discover and monitor metrics: Clusters and managed servers will be discovered, added as separate
monitors and metric data will be collected.
Note: Clusters are added as Cluster Monitor type.
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Provide the monitor-specific authentication information, such as user name and password.
Choose the Monitor Group from the combo box with which you want to associate WebLogic Server Monitor
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers WebLogic server from the network and starts monitoring them.
Note:
The ports that need to be opened when the Weblogic Monitor is behind the firewall: Two-way
communication between WebLogic listening port (Default : 7001) and Applications Manager web server
port (default : 9090).
Having trouble in monitoring WebLogic server? Refer to the online Troubleshooting section.
Monitored Parameters
WebLogic servers are monitored based on a few parameters or the attributes. These attributes provide information
about the functioning of the Monitors of WebLogic server and you can also receive alarms based on the thresholds
configured on the numerical attributes of the server.
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations. Click on the individual monitors listed, to view the
following information.
Click on the monitor name to see all the server details listed:
JVM Heap Usage
JDBC
Thread pool
Web Applications
Java Message ServiceSAF
Custom Attributes
JVM Heap Usage
Parameters Description
Minimum
The minimum amount of heap memory that was used by the WebLogic server. (KB)
Heap Size
Maximum
The maximum amount of heap memory that was used by the WebLogic server. (KB)
Heap Size
Average
The average amount of heap memory that was used by the WebLogic server. (KB)
Heap Size
Total Heap
The total amount of heap memory allocated to the WebLogic server. (KB)
Size
Current
The amount of heap memory currently available in the WebLogic server. (KB)
Heap Size
Current
Heap Size The percentage of the amount of heap memory currently available in the WebLogic server. (%)
(%)
Server Response Time
Server Response Time is the time the server takes to respond to a user request. Here, it is
Server
calculated as the time that the Weblogic Server takes to establish a connection with and respond
Response
to a request from Applications Manager. You can also track the minumum, maximum, average and
Time
current response time of your Weblogic Servers.
JDBC
Parameters Description
Name of the database connection pools that enables caching of database connection in the
Name
monitor easier through pools.
Threads waiting
Mentions the number of threads waiting for the connection.
for connection
JDBC Active
Mentions the number of active connections made to the monitor.
Connections
Total
Specifies the number of database connection pool.
Connections
Pool State Specifies the state of the pool Running/Suspended
JDBC
There can be some problems in connections that are checked out from the connection pool but
Connection
are not returned back to the pool and they are specified using the parameter.
Leak Count
JDBC Active
Amount of active connections in %
Connection in %
Thread Pool
Parameters Description
Idle Threads Count Specifies the threads that are idle or not used.
Total Threads Refers to the total count of threads assigned in this thread queue.
Pending Request Total Count Specifies the number of requests that are pending in the queue.
Threads In Use Specifies the threads that are currently in use.
Web Applications
Parameters Description
Name Name of the Web Application.
Session Opened Total Refers to the total number of sessions that were opened since deployment of anApplication.
Number of Active Sessions Specifies the number of sessions that are currently active in the Application.
Maximum Number of
Refers to the highest number of sessions that were open for an Application.
Sessions
Number of Servlets Refers to the total number of servlets of a web application
Java Message Service
Parameters Description
Name The name of JMS server.
Current The current number of messages stored on this JMS server.
The current number of messages pending (unacknowledged or uncommitted) stored on this JMS
Pending
server.
Received/Min The number of messages received on this destination since the last reset per minute.
SAF Details (Conversations & Remote End Points)
Parameters Description
Name Name of SAF Agent in Weblogic.
Current
The current number of conversations.
Conversations
Conversations/Minute The total number of conversations per minute since the last reset.
Current Remote The current number of remote endpoints to which this SAF agent has been storing and
EndPoints forwarding messages.
EndPoints/Minute The rate at which this SAF agent has been storing and forwarding messages per minute.
Custom Attributes
You can also view the custom attributes of the WebLogic Server in the same page. Click Add Attributes to add
custom WebLogic attributes. For information on adding Custom Monitors, refer to Custom Monitors topic.
WebSphere Server Monitoring
Create a New Monitor
The supported versions of WebSphere Servers are 5.x, 6.x, 7.x, 8.x and 9.x
Prerequisites for Websphere Monitoring:
For Applications Manager to collect data from WebSphere Application Server, configurations are required at
the Performance Monitoring Infrastructure (PMI) specification level. Refer Prerequisites Section for
configuration details.
To create a WebSphere Server Monitor
Click on New Monitor link.
Select WebSphere Server.
Select the Deployment Mode as Base or Network Deployment.
For Base Mode, Enter the Host name/IP Address of the host in which websphere application server is running.
For Network Deployment, enter the Host name/IP Address of the websphere application server in which the
perf servlet is installed. This will automatically discover all the WebSphere servers in Network Deployment.
Enter the SubNetMask of the network.
Enter the HTTP Transport Port (9080 by default).
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Select the version of the WebSphere to be monitored - 5.x, 6.x, 7.x, 8.x and 9.x
Enter the port number of the SOAP Connector (8880 by default).
If you want to monitor WebSphere through SSL mode, select the SSL is enabled checkbox.
Enter the User Name and Password, if Global Security is enabled.
In Network Deployment Mode, Enter the Network Deployer''s Host and SOAP Port (Default : 8879).Choose the Monitor Group from the combo box with which you want to associate WebSphere Server Monitor
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers WebSphere server from the network and starts monitoring them.
Note:
Applications Manager has been tested for WebSphere versions of English, German, Japanese and Chinese
languages. In the Network Deployment mode, the child monitors which are automatically discovered cannot
be deleted from the list view. If a user tries to delete a child monitor, it will get added again in next poll of the
Parent monitor. Child monitors will be deleted only if the parent monitor is deleted. If they want to stop data
collection(don''t want to monitor) for child monitors, they need to mention those child monitors in Exclude list of
the parent monitor in edit monitor page. If they mentioned it in exclude list of parent monitor page, then those
child monitors will be unmanaged and data collection stops for those monitors.
Monitored Parameters
The Availability tab, gives the Availability history for the past 24 hours or 30 days. Performance tab gives the Health
Status and events for the past 24 hours or 30 days. List view enables you to perform bulk admin configurations.
Click on the individual monitors listed, to view the following information
WebSphere servers are monitored based on the attributes listed under the following tabs:
Monitor Information
Overview
Web
EJB
JDBC
JMS - Queues, Topics
Thread
The monitoring details of the server are represented graphically that helps to understand the parameters with
ease. You can also configure thresholds to the attributes monitored by the server based on these details.
Monitor Details
Parameters Description
The deployment mode of the WebSphere server. You can choose either Base or Network
Deployment.If you select:
Base Mode, enter the Host Name/IP Address of the host in which the WebSphere
Deployment
application server is running.
Mode
Network Deployment, enter the Host name/IP Address of the WebSphere Application
server in which the perf servlet is installed. This will automatically discover all the
WebSphere servers in Network Deployment.
WebSphere
Denotes the version of the WebSphere server monitor.
Version
Port Refers to HTTP Transport port.
Subnet Mask The subNetMask of the WebSphere server.
Do not resolve If you have multiple system IP addresses configured with a single DNS name, select the ‘Do
DNS name not resolve DNS name’ option under‘Advanced’ section.
Network
Deployer Host,
If you have chosen the ‘Network Deployment’ mode, specify the Network Deployer Host and
Network
Network Deployer SOAP Port values. The default SOAP port is 8879.
Deployer SOAP
Port
SSL is enabled If you want to monitor WebSphere through SSL mode, select the ‘SSL is enabled’ checkbox.
If you want to monitor selected app servers running in the WebSphere server, select the
App Servers to
‘Advanced Options’ checkbox and specify the app servers in the ‘App Servers to Monitor’ field.
Monitor
If you want to monitor all the app servers in the WebSphere server, leave this field empty.
OverviewParameters Description
State Refers to different states of the Websphere server such as running and down.
HTTP Port Refers to HTTP Transport port.
Transaction Specifies Global Commit Duration, Committed Transactions, Transactions Rolled Back and
Details Transactions Optimized.
Server Response
Specifies Minimum, Maximum, Average and Current Response Time.
Time
Availability Specifies the status of the WebSphere server - available or not available.
JVM Memory
Specifies the total memory in JVM run time.
Usage
Specifies the average system CPU utilization taken over the time interval since the last
CPU Utilization
reading.
Free Memory Specifies the amount of real free memory available on the system.
Average CPU
Specifies the average percent CPU Usage that is busy after the server is started
Utilization
Session Details of Web Applications
Parameters Description
Invalidated
Specifies the total number of sessions that were invalidated.
Sessions
Session
Creation The rate per minute at which session objects were created by the server.
Rate/Min
Affinity The total number of requests received for sessions that were last accessed from other Web
Breaks/Min applications. This value can indicate failover processing or a corrupt plug-in configuration.
Live Sessions The number of local sessions that are currently cached in memory
Total
The total number of requests that a web application processed
Requests/Min
Error
Total number of errors in a servlets or JavaServer Page (JSP).
Count/Min
Concurrent
The number of requests that are concurrently processed.
Requests
EJB Details
Parameters Description
Mentions the names of the different EJB present in the WebSphere server with JAR and EAR
Name
name. Move the mouse pointer over the EJB name to view the JAR and EAR name.
Denotes the different types of the bean such as entity, stateless session, stateful session, and
Type
message driven.
Concurrent Lives Specifies the number of concurrent live beans.
Total Method
Specifies the total number of method calls.
Calls
Average Method
Specifies the average time required to respond to the method calls.
Response Time
Pool Size Specifies the number of objects in the pool (entity and stateless).
Specifies the average time in milliseconds that the total bean is activated for that particular
Activation Time
Bean container, including the time at the database, if any.
Specifies the average time in milliseconds that the total bean is passivated for that particular
Passivation Time
Bean container, including the time at the database, if any.
Current JDBC Connection Pool Details
Parameters Description
Name The name of the current JDBC Connection pool.Pool Type The type of the connection pool.
Create Count The total number of connections created.
Pool Size The size of the connection pool.
Concurrent Waiters The number of threads that are currently waiting for a connection.
Faults The total number of faults in the connection pool such as timeouts.
Average Wait Time The average waiting time, in milliseconds, until a connection is granted.
Percent Maxed The average percent of the time that all connections are in use.
JMS Queues
Parameters Description
Queue Depth The number of messages available for a queue''s consumption
Uncommitted The number of messages locked or uncommitted. This means messages that have been added
Transactions or removed but the transaction has not yet been committed.
Produced
The total number of messages produced per second to this queue.
Count/Sec
Consumed
The total number of messages consumed per second from this queue
Count/Sec
Number of
The number of currently attached local producers.
Producers
Number of
The number of currently attached local consumers.
Consumers
Message Wait
Maximum time spent by messages on this queue at consumption in seconds.
Time(sec)
Oldest
Message The longest time any message has spent on this queue in seconds.
Age(sec)
Jms Topics
Parameters Description
Durable The number of subscriptions that can be used to preserve messages published on a topic
Subscriptions while the subscriber is not active.
Non-durable
The number of non-durable subscriptions.
Subscriptions
Incomplete
The number of publications not yet received by all current subscribers.
Publications
Oldest Publication
The longest time any publication has spent on this topic space.
Age
Number of
The number of local publishers to topics in this topic space.
Publishers
Number of
The number of local subscriptions to topics in this topic space.
Subscriptions
Number of
The total number of publications to this topic space.
Publications
Thread Pool Details
Parameters Description
Name Mentions the name of the thread pool.
Thread Creates Specifies the total number of threads created.
Thread Destroys Specifies the total number of threads destroyed.
Active Threads Specifies the number of concurrently active threads.
Pool Size Specifies the average number of threads in pool.Percent Used The average percentage of the pool in use.
Free Pool Size The number of free connections in the pool.
Percent Maxed Specifies the average percent of the time that all threads are in use.
Note:
In Network Deployment mode, Network Deployer will be listed in the WebSphere Monitors list. Clicking on it,
will give server information and the custom attributes. Further, the individual WebSpheres within the Network
Deployment would also be listed. Clicking on those servers would bring up each of those server''s details.
Monitoring Apache Geronimo
Apache Geronimo - An Overview
Monitoring Apache Geronimo - What we do
Adding a new Apache Geronimo Monitor & Demo
Monitored Parameters
Apache Geronimo - An Overview
Apache Geronimo is an open source J2EE/Java EE 5 web application server that integrates open source projects to
create Java/OSGi server runtimes that meet the needs of enterprise developers and system administrators.
Geronimo can host a variety of server applications and boasts a large base of users. It comes equipped with a
relational database server and message broker, enabling you to immediately deploy your enterprise applications.
With all this potential, monitoring Apache Geronimo can be a daunting task.
Monitoring Apache Geronimo - What we do
Applications Manager aims to help administrators implement performance management of their Apache
Geronimo application servers and the business-critical applications running on them. Let’s take a look at what you
need to see to optimize your Apache Geronimo servers and the performance metrics that you can gather with
Applications Manager:
Resource utilization details - Discover Apache Geronimo servers, monitor memory and CPU utilization and
get alerted of changes in resource consumption.
JVM and Thread Details - Track thread usage with metrics like Daemon, Peak and Live Thread Count. Ensure
started threads don’t overload the server''s memory.
Web and Data Source details - Get an overview of sessions where you can see all session details for each
web application – active, expired, duplicate, rejected and more. Collect information on the number of
requests, concurrent connections, requests duration etc.
EJB and ActiveMQ data - Automatically collect and visualize ActiveMQ queue data like memory usage,
average message size, average enqueue time and broker metrics all in one place. Analyze topic details
including memory consumed by each topic, average message size, blocked sends, health of each topic etc.
and make informed decisions. Correlate subscriber metrics with their respective topic metrics to diagnose
issues.
Juddi Stats and Cache details - Track Failed and Successful API Queries stats of the UDDI Registry. Monitor
the cache size of an Apache Geronimo Environment and the number of access count.
Fix Performance Problems Faster - Maintain configurations for high availability and scalability, and be
alerted automatically of potential issues with the components of your Apache Geronimo server. Become
aware of performance bottlenecks and take quick remedial actions before your end users experience issues.
Adding a new Apache Geronimo monitor
Supported Versions of Apache Geronimo: Version 2.1.3 to 3.0.1
Prerequisites to monitor Apache Geronimo metrics: Click here
Using the REST API to add a new Apache Geronimo monitor: Click here
To create an Apache Geronimo Monitor, follow the steps given below:
Click on New Monitor link. Choose Apache Geronimo.
Specify the Display Name of the Apache Geronimo monitor.
Enter the HostName or IP Address of the host where Apache Geronimo runs.
Enter the JMX Port of the Apache Geronimo. By default, it will be 1191.Enter the credential details like JMX user name and password of Apache Geronimo server or select
credentials from a Credential Manager list.
Enter the polling interval time in minutes.
Click Test Credentials button, if you want to test the access to Spark server.
Choose the Monitor Group from the combo box with which you want to associate Spark Monitor (optional). You
can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers Spark from the network and starts monitoring
Note:
In case you are unable to add the monitor even after enabling JMX, try providing the below argument:
-Djava.rmi.server.hostname=[YOUR_IP]
Demo
How to add Apache Geronimo monitor?
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the Apache Geronimo Server monitors
under the Application Servers Table. Displayed is the Apache Geronimo Server bulk configuration view
distributed into three tabs:
Availability tab displays the Availability history for the past 24 hours or 30 days.
Performance tab displays the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the server details listed under the following tabs:
Monitor Information
Overview
JVM
Web
Data Sources
EJB
ActiveMQ
JUDDI
Cache
Configuration
Monitor Information
Field Description
Display Name The display name of Apache Geronimo monitor.
Host Name / IP Address* The name or Ip address of the host where Apache Geronimo is running.
Port The Port in which Apache Geronimo server is running.
JMX Port The JMX port of the server.
Username The Username of Apache Geronimo instance.
Password The password of Apache Geronimo instance.Field Description
JNDI Path The JNDI Path of the server
Overview
Parameter Description
Server Response Time The response time of the Geronimo server.
Used heap memory percentage The percentage of heap memory used.
Free heap memory percentage The percentage of heap memory free.
Used non-heap memory percentage The percentage of non heap memory used.
Free non-heap memory percentage The percentage of non heap memory free.
THREAD USAGE
Daemon Thread Count The number of live daemon threads.
Peak Thread Count The peak count of active threads in the system.
Live Thread Count The current number of live threads.
The total number of threads started since the java
Total Thread Started
virtual machine started.
TRANSACTIONS
Active Count The number of active transactions.
Total Commits The total number of transaction commits.
Total Rollbacks The total number of transaction rollbacks.
JVM
Parameter Description
Class Loading
Loaded class count The number of classes currently loaded in the java virtual machine.
Unloaded class count The number of classes unloaded since the java virtual machine has started.
The total number of classes loaded since the java virtual machine has started
Total Class count
execution.
Garbage Collector
PC Scavenge Collection count
The number of garbage collections carried out by the PC Scavenge
rate
PC Scavenge Collection time
The time taken to collect garbage by PC Scavenge
rate
PC MarkSweep Collection time
No. of garbage collected by MarkSweep
rate
PC MarkSweep Collection time
Time taken to collect garbage by MarkSweep
rate
Memory Details
Name Heap Memory/ Non- Heap Memory usage in MB.
Committed Current allocated memory in MB.
Max Max allocated memory in MB.
Used Current used memory in MB.
Free Current free memory in MB.
Free% The percentage of currently free memory.
Used% The percentage of currently used memory.
Buffer Pool
Direct Buffer Connection Count The total connections to Direct Buffer pool.
Direct Buffer Space Used The total space used in the Direct Buffer pool.
Direct Buffer Total Space The total space in the Direct Buffer pool.Parameter Description
Mapped Buffer Connection
The total connections to Mapped Buffer pool.
Count
Mapped Buffer Space Used The total space used in the Mapped Buffer pool.
Mapped Buffer Total Space The total space in the Mapped Buffer pool.
Buffer Pool: A direct buffer is a chunk of memory typically used to interface Java to the OS I/O subsystems, for
example as a place where the OS writes data as it receives it from a socket or disk, and from which Java can read
directly. The mapped buffer pool is all the memory used by Java for its FileChannel instances.
Web
Parameter Description
Web apps
Context Web application''s context name
Active Sessions Number of active sessions at this moment
Duplicate Sessions Number of duplicated session ids generated
Expired Sessions Number of sessions that expired.
Rejected Sessions Number of sessions we rejected due to maxActive being reached
Session Average Alive Time Average time an expired session had been alive.
Session Max Alive Time Longest time an expired session had been alive.
Session Create Rate Session creation rate in sessions per minute.
Session Expire Rate Session expiration rate in sessions per minute.
Global Request Processor
Connector Name Connector name of the global request processor.
Request Count Number of requests served by this global request processor.
Error Count Number of error request received.
Time taken by this global request processor to process the requests in
Processing Time
milliseconds.
Bytes Sent Per Second Average bytes sent per second.
Bytes Received Per Second Average bytes received per second.
Successful Request (%) Percentage of successful requests.
Failed Request (%) Percentage of failed requests.
Data Sources
Parameter Description
Name Name of the data source.
Active Connections Number of active connections to the data source.
Idle Connections Number of idle connections to the data source.
EJB
Parameter Description
EJP Pool
Name Name of the EJB Pool
Active Instances The no. of active instances
Idle Instances The no. of idle instances.
Initializing Instances The no. of initializing instances.
Pooled Instances The no. of pooled instances.
Access Timeouts The no. of times, access timeouts occurred.
Aged The no. of aged instances.Parameter Description
Flushed The no. of times, the pool is flushed.
Garbage Collected The no. of times, the garbage collection occurred.
ActiveMQ
Parameter Description
Apache ActiveMQ Broker
Name Name of the Active MQ Broker.
Memory Usage Percentage The percentage of the memory limit .
Dequeue Count Number of messages that have been acknowledged on the broker.
Enqueue Count Number of messages that have been sent to the broker.
Consumer Count Number of message consumers subscribed to destinations on the broker.
Message Count Number of unacknowledged messages on the broker.
Temp Usage Percentage Percent of temp limit used.
Store Usage Percentage Percent of store limit used.
Apache ActiveMQ Topic
Name Name of the Active MQ queue.
Number of messages in the destination which are yet to be consumed.
Queue Size
Potentially dispatched but unacknowledged.
Number of messages that have been acknowledged (and removed from) from
Dequeue Count
the destination.
Enqueue Count Number of messages that have been sent to the destination.
Number of messages that have been delivered (but potentially not
Dispatch Count
acknowledged) to consumers.
Expired Count Number of messages that have been expired.
Number of messages that have been dispatched to, but not acknowledged by,
InFlight Count
consumers.
Consumer Count Number of consumers subscribed to this destination.
Producer Count Number of producers publishing to this destination.
Max Enqueue Time The longest time a message has been held this destination.
Min Enqueue Time The shortest time a message has been held this destination.
Avg Enqueue Time Average time a message has been held this destination.
Memory Usage Percentage The percentage of the memory limit used
JUDDI
The Universal Description, Discovery and Integration (UDDI) protocol is one of the major building blocks required
for successful Web services. UDDI creates a standard interoperable platform that enables companies and
applications to quickly, easily, and dynamically find and use Web services over the Internet (or Intranet).
Parameter Description
Name Name of the JUDDI implementation.
Failed API Queries Count of API queries failed.
Successful API Queries Count of successful API queries.
Total API Queries Total number of API queries performed.
Cache
Parameter Description
Name Name of the cache.
Cache Max Size Max size of the cache.Parameter Description
Cache Size Current cache size.
Access Count Number of times the cache is accessed.
Hit Count Number of cache hits.
Note: Geronimo provides built-in caches for Active MQ, juddi, open-ejb server and system-database.
Configuration
Parameter Description
HostName/IP Address Host name or IP address of the server.
Port The port geronimo is running
Geronimo Installation Directory The file directory where geronimo installed.
Geronimo Version The version of the geronimo server.
Host OS The operating system where the server is running.
JVM Vendor Vendor of the virtual machine.
JVM version Version of the virtual machine.
Cloud Application Monitoring
Cloud computing services help organizations to improve the flexibility and scalability of IT services delivered to
their end users. Many IT organizations are moving a portion of their IT infrastructure to the cloud in order to improve
flexibility and scalability of IT services delivered to end users. Public cloud service providers make it easy for
companies to rent virtual computers on which to run their own applications and services.
Nevertheless, it is important to continuously monitor these cloud hosted applications in order to ensure they
perform at expected levels at all times, and also to ensure cloud resources are being effectively utilized. Cloud
monitoring solutions from Applications Manager''s Cloud performance monitor enables you to ensure that your
public cloud computing services perform their best at all times and that cloud resources are being effectively
utilized.
Cloud monitoring services from Applications Manager''s Cloud monitoring software enables high performance
business process management by detecting and diagnosing problems of cloud applications faster. Following are
the list of cloud monitoring services that are supported by Applications Manager''s Cloud performance monitor:
Amazon Web Services (AWS)
Microsoft Azure
Microsoft 365
Oracle Cloud
Google Cloud
OpenStack
Google Cloud Platform Monitoring
Google Cloud Platform - An Overview
Google Cloud Platform Monitoring - What we do
Creating a new Google Cloud Platform monitor
Monitored Parameters
Troubleshooting
Google Cloud Platform - An Overview
Google Cloud is Google''s in-built cloud platform that provides a series of cloud services including computing,
data storage, data analytics, and machine learning. Google Cloud Platform provides infrastructure as a service,
platform as a service, and serverless computing environments.
Google Cloud Platform Monitoring - What we doApplications Manager''s Google cloud platform monitoring tool will give you complete visibility into every
component of your Google cloud environment thereby allowing you to optimize the performance of business
critical Google cloud services. With our root cause analysis capabilities, you can easily identify the root cause of
performance issues and troubleshoot them quickly.
Our Google cloud monitoring capabilities will allow you to:
Effortlessly monitor compute elements of your Google Cloud Platform.
Collect and monitor key metrics like CPU usage, disk I/O, memory utilization, etc.
View network status and understand performance trends.
Creating a new Google Cloud Platform monitor
Prerequisites for monitoring Google Cloud metrics: Click here
Using the REST API to add a new Google Cloud Platform monitor: Click here
Follow the steps given below to create a new Google Cloud Platform monitor:
Click on New Monitor link. Select Google Cloud Platform under Cloud Apps category.
Specify the Display Name of the Google cloud application.
Enter the GCP Services you want to monitor.
Specify the Project ID to be monitored.
Specify OAuth Provider name.
If you choose the Advanced Settings option, input the action you want to perform on deleted resources.
Enable Stop discovery if you want to stop discovering resources under a particular service.
Specify the Polling interval in minutes.
If you are adding a new monitor from Admin server, select a Managed server.
Choose the Monitor Group with which you want to associate the Google Cloud Platform monitor with, from the
combo box. You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the Google Cloud and starts monitoring it.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Google Cloud Platform under the Cloud
Apps section. Displayed is the Google Cloud bulk configuration view distributed into three tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configuration.
On clicking a monitor from the list, you''ll be taken to the Google Cloud dashboard. It has 3 tabs —
Overview
Compute
Storage
Overview
INVENTORY
Parameter Description
Compute Engine Instances Total number of Compute Engine instances available.
Cloud Storage Buckets Total number of Storage buckets available.
Cloud Filestore Instances Total number of Filestore instances available.
Kubernetes Engine Clusters Total number of Kubernetes Engine clusters available.
App Engine Applications Total number of App Engine applications available.
Cloud Functions Total number of Cloud Functions available.
Cloud Pub/Sub Topics Total number of Cloud Pub/Sub topics available.
Cloud Dataflow Jobs Total number of Cloud Dataflow jobs available.Bigtable Instances Total number of Bigtable instances available.
BigQuery Instances Total number of BigQuery instances available.
Cloud SQL Instances Total number of Cloud SQL instances available.
Quotas
Parameter Description
Metric name Name of the resource.
Limit Total quotas allocated.
Used Number of quotas used.
Available Number of quotas available.
Note: Quota metrics are mapped under performance polling. To change the polling interval, go to Admin →
Performance polling → Optimize data collection and choose ''Google Cloud Platform'' for ''Monitor Type'' and
''Quotas'' for the ''Metric name'' and change the ''Default Polling Status''.
Compute
Kubernetes Engine
Parameter Description
Name Name of the Kubernetes cluster.
Location Name Location of the Kubernetes cluster.
Status Current status of the cluster.
Endpoint IP address of this cluster''s master endpoint.
Current Node Count Total number of nodes currently present in the cluster.
User Pods Count Total number of pods currently present in the cluster.
By clicking over the cluster name, you will be redirected to the Google Kubernetes Engine monitoring dashboard.
Compute Engine
Parameter Description
Name Name of the Compute Engine Instance.
Instance ID ID of the Compute Engine Instance.
Status Status of the Compute Engine Instance.
Zone Zone in which the instance is available.
External IP Address External IP Address of the instance.
OS Platform Operating System of the Compute Engine Instance.
By clicking over the instance name, you will be redirected to the Google Compute Engine monitoring dashboard.
Storage
Cloud Storage
Parameter Description
Name The name of the bucket in the Google Cloud instance.
Location The location of the bucket.
Location Type The type of location that the bucket resides in.
Storage Class The storage type of the bucket.
Bucket Size The size of the bucket (in GB).
Number of Objects Total number of objects available in the bucket.
By clicking over the bucket name, you will be redirected to the Google Cloud Storage monitoring dashboard.
Cloud FilestoreParameter Description
Name The name of the Filestore in the Google Cloud instance.
Location Name The name of the region where the instance is created.
Fileshare Name The name of the file share.
Instance Tire The service tier of the instance.
Total Storage Total storage capacity of the Filestore instance (in TB).
Storage Utilization The amount of storage utilized in the Filestore instance (in percentage).
Current IP Address Current IP address of the Filestore.
By clicking over the Filestore name, you will be redirected to the Google Cloud Filestore monitoring dashboard.
Troubleshooting
1. Authentication Failed. Request has invalid authentication credentials.
In AppManager, go to Admin → OAuth Provider and check if the provider used in the GCP monitor has Valid
Access Token and Refresh Token.
Verify if the provider is created for the project being monitored.
Verify if the prerequisites are fulfilled.
2. Access denied. Cloud resource manager API disabled.
Go to GCP Console → APIs & Services → Library. Check if the Cloud Resource Manager API is enabled.
If you enabled this API recently, wait a few minutes for the action to propagate and retry.
3. Authentication failed while connecting to Stackdriver API.
Go to GCP Console → APIs & Services → Library and ensure Stackdriver API and Stackdriver Monitoring API
are enabled.
Check if the arguments of the selected OAuth Provider are valid.
4. Unable to fetch instances (or) Error fetching instances.
Go to GCP console → APIs & Services → Library, and check if Compute Engine API is enabled.
Note: Make sure you have a working internet connection to add or fetch data from the cloud services. If your
environment requires the use of a proxy server to excess external websites, you can configure the proxy
settings under the ''Admin'' tab.
Google Compute Engine
Overview
Monitored Parameters
Troubleshooting
Overview
Google Cloud Compute Engine is an Infrastructure as a Service (IaaS) offering that provides a scalable number of
virtual machines (VMs) to serve as large compute clusters.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Google Cloud under the Cloud Apps
section. Displayed is the Google cloud bulk configuration view distributed into three tabs:Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
On clicking a monitor from the list, you''ll be taken to the Google Cloud dashboard. Under the parent monitor, you
have 3 tabs. The child monitor has 4 tabs -
Performance
Network
Disk
Configuration
Performance
Parameter Description
CPU:
CPU Utilization Activity level from CPU. Expressed as percentage.
Total CPUs Nmber of CPUs in usage
CPU Usage CPU Usage for all cores, in seconds
Memory:
Memory Utilization Space currently in use. Expressed as a percentage.
Total Memory Overall memory available
Used Memory Amount of memory used
Free Memory Amount of memory free
Network
Parameter Description
Input Traffic Bytes received from the network expressed in KBps.
Output Traffic Bytes sent over the network expressed in KBps.
Input Traffic - Packets Count of packets received from the network
Output Traffic - Packets Count of packets sent over the network
Firewall dropped - Bytes Incoming bytes dropped by firewall expressed in KBps.
Firewall dropped - Packets Count of incoming packets dropped by firewall
Disk
Parameter Description
Disk Utilization:
Disk Label Name of the disk allocated
Used Amount of disk used
Free Amount of disk available
Disk Performance:
Disk Name Name of the disk
Disk Status Status of the disk
Disk Size Size of the disk expressed in GB
Disk Reads Bytes read from disk expressed in KB/sec
Disk Writes Bytes written to disk expressed in KB/sec
IO Read Operations Count of disk read IO Operations
IO Write Operations Count of disk write IO Operations
Disk Throttling:Parameter Description
Disk Name Name of the disk
Bytes in throttled read operations expressed in KB/sec (Throttle reason: Per
Throttled Disk Reads Per GB
GB limit)
Bytes in throttled write operations expressed in KB/sec (Throttle reason: Per
Throttled Disk Writer Per GB
GB limit)
Throttled IO Read Operations Per
Count of throttled disk read operations (Throttle reason: Per GB limit)
GB
Throttled IO Write Operations Per
Count of throttled disk write operations (Throttle reason: Per GB limit)
GB
Bytes in throttled read operations expressed in KB/sec. (Throttle reason: Per
Throttled Disk Reads Per VM
VM limit)
Bytes in throttled write operations expressed in KB/sec. (Throttle reason: Per
Throttled Disk Writes Per VM
VM limit)
Throttled IO Read Operations Per
Count of throttled read operations (Throttle reason: Per VM limit)
VM
Throttled IO Write Operations Per
Count of throttled write operations (Throttle reason: Per VM limit)
VM
Configuration
Parameter Description
Instance name Name of the instance
Instance ID Unique ID of the instance
Project ID Unique ID of the project
Zone Zone in which the instance is created
Status Current status of the instance (Running, terminated,...)
Machine Type Virtualized hardware resources available to the instance
External IP IP Address of the instance
CPU Platform Base platform of the instance
OS Platform Operating system running in the instance
Start Restricted Restriction on the instance to perform start operation (True/False)
Deletion Protection Restriction on the instance to perform delete operation (True/False)
Troubleshooting
1. Data unavailable for performance metrics
When an instance is started and polled immediately, data might not be collected for some of the performance
metrics. Wait for some time and then poll the monitor to get the data.
If the data is still not populated, go to Stackdrive Console and check if data is available.
If data is available in Stackdriver and is not getting populated in AppManager, reach out to our support with
the latest SIF generated with print all logs enabled.
2. Data unavailable for memory and disk utilization metrics
Install Stackdriver Monitoring Agent in the instance, to get memory and disk utilization metrics.
Click here for information on installing the Stackdriver agent.
When an instance is started and polled immediately, data might not be collected for some of the performance
metrics. Wait for some time and then poll the monitor to get the data.
Google Cloud StorageGoogle Cloud Storage - Overview
Google Cloud Storage is a storage platform that provides high-performance object storage services and offers
excellent scalability, data availability, durability, and security. It allows you to store objects and access any
amount of data instantly from any storage classes, integrate storage into your applications with a single unified
API, and optimize price and performance easily.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the Storage instance available under
Google Cloud in the Cloud Apps section. Displayed is the Google Cloud Storage bulk configuration view
distributed into three tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
By clicking a monitor from the list, you''ll be taken to the Google Cloud Storage dashboard. It has 5 tabs:
Overview
Requests
Network
Objects
Configuration
Overview
Parameter Description
NUMBER OF OBJECTS:
Number of Objects Total number of objects present in the Google Storage instance.
BUCKET SIZE:
Bucket Size The size of the bucket (in GB).
REQUESTS:
Total Requests/Min The total number of requests processed by the bucket per minute.
NETWORK TRAFFIC:
Total Incoming Traffic Total amount of data received over the network between two polls (in KB/sec).
Total Outgoing Traffic Total amount of data sent over the network between two polls (in KB/sec).
Requests
Parameter Description
READ REQUESTS:
Get Object Requests/Min The total number of Get object requests made in a bucket per minute.
Get Bucket Requests/Min The total number of Get Bucket requests made in a bucket per minute.
Read Object Requests/Min The total number of Read object requests made in a bucket per minute.
List Objects Requests/Min The total number of List object requests made in a bucket per minute.
WRITE REQUESTS:
Write Object Requests/Min The total number of Write object requests made in a bucket per minute.
Delete Object Requests/Min The total number of Delete object requests made in a bucket per minute.
Update Object Requests/Min The total number of Update object requests made in a bucket per minute.
Clone Object Requests/Min The total number of Clone object requests made in a bucket per minute.
Rewrite Object Requests/Min The total number of Rewrite object requests made in a bucket per minute.
NetworkParameter Description
READ INCOMING TRAFFIC:
Get Object Incoming Traffic Amount of data received over the network for the Get Object method (in KB/sec).
Get Bucket Incoming Traffic Amount of data received over the network for the Get Bucket method (in KB/sec).
Amount of data received over the network for the Read Object method (in
Read Object Incoming Traffic
KB/sec).
List Object Incoming Traffic Amount of data received over the network for the List Object method (in KB/sec).
READ OUTGOING TRAFFIC:
Get Object Outgoing Traffic Amount of data sent over the network for the Get Object method (in KB/sec).
Get Bucket Outgoing Traffic Amount of data sent over the network for the Get Bucket method (in KB/sec).
Read Object Outgoing Traffic Amount of data sent over the network for the Read Object method (in KB/sec).
List Object Outgoing Traffic Amount of data sent over the network for the List Object method (in KB/sec).
WRITE INCOMING TRAFFIC:
Amount of data received over the network for the Write Object method (in
Write Object Incoming Traffic
KB/sec).
Delete Object Incoming Amount of data received over the network for the Delete Object method (in
Traffic KB/sec).
Update Object Incoming Amount of data received over the network for the Update Object method (in
Traffic KB/sec).
Amount of data received over the network for the Clone Object method (in
Clone Object Incoming Traffic
KB/sec).
Rewrite Object Incoming Amount of data received over the network for the Rewrite Object method (in
Traffic KB/sec).
WRITE OUTGOING TRAFFIC:
Write Object Outgoing Traffic Amount of data sent over the network for the Write Object method (in KB/sec).
Delete Object Outgoing
Amount of data sent over the network for the Delete Object method (in KB/sec).
Traffic
Update Object Outgoing
Amount of data sent over the network for the Update Object method (in KB/sec).
Traffic
Clone Object Outgoing Traffic Amount of data sent over the network for the Clone Object method (in KB/sec).
Rewrite Object Outgoing
Amount of data sent over the network for the Rewrite Object method (in KB/sec).
Traffic
Objects
Parameter Description
Top Objects by Size:
Object Name (Top) Name of the object that is of higher size.
Top Object Size Size of the object that is of higher size (in MB).
Created Time (Top) Time at which the object of higher size was created.
Recently Uploaded Objects:
Object Name (Recent) Name of the object that was recently uploaded.
Recently Uploaded Object Size Size of the object that was recently uploaded (in MB).
Created Time (Recent) Time at which the recently-uploaded object was created.
Category Wise Details:
Category Category of the object.
Count by Category Number of objects available in that category.
Size by Category Total size of objects available in that category (in MB).
Configuration
Parameter DescriptionParameter Description
BUCKET INFORMATION:
Project ID Unique identifier of the project in which the bucket was created.
Location The location of the bucket.
Location Type The type of location that the bucket resides in.
Storage Class The storage type of the bucket.
Creation Time The creation time of the bucket.
Last Updated Time Time at which the bucket was last updated.
Bucket Policy Enabled Indicates whether Bucket level Policy is enabled for the bucket.
Uniform Bucket Level Access Enabled Indicates whether Uniform Bucket level Access is enabled for the bucket.
Google Cloud Filestore
Google Cloud Filestore - Overview
Google Cloud Filestore is a managed file storage service from Google that provides high-performance file storage
for applications requiring a file system interface and a shared file system for data. It facilitates users in setting up
their managed Network Attached Storage (NAS) systems with their Google Compute Engine and Kubernetes
Engine instances, leading to predictably faster performance for file-based workloads.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the Filestore instance available under
Google Cloud in the Cloud Apps section. Displayed is the Google Cloud Filestore bulk configuration view
distributed into three tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
By clicking a monitor from the list, you''ll be taken to the Google Cloud Filestore dashboard. It has 3 tabs:
Overview
Disk
Configuration
Overview
Parameter Description
USAGE:
Total Storage Total storage capacity of the Filestore instance (in TB).
Used Storage Amount of storage utilized in the Filestore instance (in TB).
Reserved Storage Amount of storage reserved in the Filestore instance (in TB).
Free Storage Remaining amount of storage available in the Filestore instance (in TB).
Storage Utilization Amount of storage capacity utilized in the Filestore instance (in percentage).
Procedure Call Counts:
Procedure Name Name of the procedure call.
Count Number of procedure calls occurred.
Disk
Parameter Description
I/O THROUGHPUT:
Read Throughput Rate at which data is read from the disk (in MB/sec).Parameter Description
Write Throughput Rate at which data is written to the disk (in MB/sec).
I/O OPERATIONS:
Read Ops Number of read operations occurred on the disk (in Ops/sec).
Write Ops Number of write operations occurred on the disk (in Ops/sec).
I/O LATENCY:
Read Latency Amount of time taken to perform disk read operations (in millisecond).
Write Latency Amount of time taken to perform disk write operations (in millisecond).
Configuration
Parameter Description
BUCKET INFORMATION:
Location Name The name of the region where the instance is created.
Project ID Unique identifier of the project in which the bucket was created.
State Indicates the state of the instance. (CREATING, READY, REPAIRING, DELETING, ERROR)
Creation Time Time at which the bucket was created.
Fileshare Name The name of the file share.
Instance Tire The service tier of the instance.
Authorized Network The name of the Google Compute Engine VPC network to which the instance is connected.
Reserved IP Range The range of IP addresses reserved for this instance.
Current IP Address Current IP address of the instance.
Google Kubernetes Engine
Google Kubernetes Engine - Overview
Google Kubernetes Engine is an enterprise-grade platform for containerized applications, including stateful and
stateless, AI and ML, Linux and Windows, complex and simple web apps, API, and backend services. It aids you in
providing automatic application deployment, scaling and management of Nodes, Pods and Containers.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the Kubernetes Engine instance
available under Google Cloud in the Cloud Apps section. Displayed is the Google Kubernetes Engine bulk
configuration view distributed into three tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
By clicking a monitor from the list, you''ll be taken to the Google Kubernetes Engine dashboard. It has 4 tabs:
Overview
Nodes
Pods
Configuration
Overview
Parameter Description
CLUSTER USAGE DETAILS
Average Cluster CPU Utilization Average amount of CPU used by all nodes in the cluster (in percentage).
Average Cluster Memory Utilization Average amount of memory used by all nodes in the cluster (in percentage).PODS
Pod Utilization Amount of pods used by the cluster (in percentage).
Maximum Pods Count Maximum number of pods that can be created.
Used Pods Count Number of pods that are currently being used.
NODE
Cluster Node Count Total number of nodes that are currently present in the cluster.
Nodes
Parameter Description
Node Pool Details
Pool Name Name of the node pool.
Version Kubernetes version of the node pool.
Machine Type Name of the Google Compute Engine machine type used for the nodes.
Status Status of the nodes in this pool instance.
Disk Size Size of the disk attached to each node (in GB).
Image Type The image type to use for this node.
Disk Type Type of the disk attached to each node.
Max Pods Per The constraint on the maximum number of pods that can be run simultaneously on a node in
Node the node pool.
Auto Scaling
Indicates whether Auto Scaler configuration is enabled for this node pool.
Enabled
Node Pool
On clicking the required node pool, you can view detailed information about the performance of nodes available
under that node pool.
Parameter Description
Node Details
Node Name Name of the node.
Pool Name The name of the pool to which the node belongs.
CPU Total Cores Total number of CPU cores on the node.
CPU Allocatable Cores Number of allocatable CPU cores on the node.
CPU Usage Time Cumulative CPU usage time of all cores used on the node (in milliseconds).
CPU Utilization Amount of CPU ulitized by the node (in percentage).
Total Memory Total memory allocated on the node (in GB).
Memory Usage Amount of memory used by the node.
Memory Utilization Amount of memory utilized by the node (in percentage).
Input Traffic Amount of data received by the node over the network (in KB/Sec).
Output Traffic Amount of data transmitted by the node over the network (in KB/Sec).
Top 5 Nodes by CPU Utilization - Provides a graphical representation of the CPU utilization of top 5 nodes (in
percentage).
Top 5 Nodes by Memory Utilization - Provides a graphical representation of the Memory utilization of top 5
nodes (in percentage).
Pods
Parameter Description
Pod CPU Details
Pod Name Name of the pod.
Number of Containers Total number of containers present in the pod.
Namespace Name of the namespace.Parameter Description
CPU Limit Cores Number of CPU cores limited by the pod.
CPU Request Cores Number of CPU cores requested by the pod.
Pod CPU Usage Time Cumulative CPU usage of the pod (in milliseconds).
CPU Limit Utilization Amount of CPU limit that is currently in use (in percentage).
CPU Request Utilization Amount of CPU request that is currently in use (in percentage).
Top 5 Pods by CPU Details - Provides a graphical representation of the CPU utilization of top 5 pods with respect
to CPU Request and CPU Limit (in percentage).
Top 5 Pods by Memory Details - Provides a graphical representation of the Memory utilization of top 5 pods with
respect to Memory Request and Memory Limit (in percentage).
Pod Memory and Network Details
Pod Name Name of the pod.
Pod Input Traffic Amount of data received by the pod over the network (in KB/Sec).
Pod Output Traffic Amount of data transmitted by the pod over the network (in KB/Sec).
Memory Limit Total memory limit of all the containers in this pod (in MB).
Memory Request Total memory request of all the containers in this pod (in MB).
Pod Used Memory Total memory used by all the containers in this pod (in MB).
Memory Limit Utilization Amount of memory limit that is currently in use (in percentage).
Memory Request Utilization Amount of memory request that is currently in use (in percentage).
Pod Volume and Ephemeral Storage Details
Pod Name Name of the pod.
Total Volume Total amount of disk volume allocated to the pod (in MB).
Used Volume Amount of disk volume used by the pod (in MB).
Volume Utilization Amount of disk volume that is currently being used by the pod (in percentage).
Ephemeral Storage Limit Local ephemeral storage limit (in MB).
Ephemeral Storage Request Local ephemeral storage request (in MB).
Ephemeral Storage Used Local ephemeral storage usage (in MB).
Container Details
Container Name Name of the container.
Pod Name Name of the pod in which the container is present.
Restart Count Number of times the container has restarted.
Namespace Name of the namespace.
Configuration
Parameter Description
CONFIGURATION DETAILS
Project ID Unique identifier of the project in which the cluster was created.
Location Name Location of the cluster.
Creation Time Creation time of the cluster.
Status Current status of the cluster.
Endpoint IP address of the cluster''s master endpoint.
Subnetwork Name of the Google Compute Engine subnetwork to which the cluster is connected.
Cluster IPv4 CIDR Range IP address range of the container pods in the cluster expressed in CIDR notation.
Services IPv4 CIDR IP address range of the Kubernetes services in this cluster expressed in CIDR
Range notation.
Oracle Cloud Infrastructure MonitoringOracle Cloud - An Overview
Oracle Cloud Monitoring - What we do
Creating a new Oracle Cloud Monitor
Monitored Parameters
Oracle Cloud - An Overview
Oracle Cloud is Oracle''s in-built cloud platform that helps you build and run a wide range of applications and
services in a highly available hosted environment. Oracle cloud services such as IaaS, PaaS, SaaS, and DaaS are
used to build, deploy, integrate, and extend applications in cloud.
Oracle Cloud Monitoring - What we do
Applications Manager''s Oracle Cloud Infrastructure monitoring tool will give you complete visibility into every
component of your Oracle Cloud environment thereby allowing you to optimize the performance of business
critical Oracle cloud services. With our root cause analysis capabilities, you can easily identify the root cause of
performance issues and troubleshoot them quickly.
Our Oracle cloud monitoring capabilities will allow you to:
Effortlessly monitor compute elements of your Oracle cloud infrastructure.
Collect and monitor key metrics like CPU usage, disk I/O, memory utilization, etc.
Keep tabs on critical parameters like boot volume, block volume, etc.
View network status and understand performance trends.
Creating a new Oracle Cloud monitor
Prerequisites for setting up Oracle Cloud monitoring : Click here
Rest API for adding a new monitor : Click here
Follow the steps given below to create a new Oracle Cloud monitor:
Click on New Monitor link.Select Oracle Cloud under Cloud Apps category.
Specify the Display Name of the Oracle cloud application.
Enter the Services you want to monitor.
Specify the Regions you have subscribed to.
Specify the Tenancy OCID and User OCID.
Provide the PEM file path. Follow these instructions to generate API signing key.
Enter the Fingerprint of the public key.
If you choose the Advanced Settings option, input the number of compartments you want to monitor.
Enable Stop discovery if you want to stop discovering resources under a particular service.
Select the Action you want to perform on the terminated resources.
Specify the Polling interval in minutes.
Click Add Monitor(s). This discovers the Oracle cloud and starts monitoring it.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Oracle Cloud under the Cloud Apps
section. Displayed is the Oracle cloud bulk configuration view distributed into three tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
By clicking a monitor from the list, you will be taken to the Oracle Cloud dashboard. It has 4 tabs -
Overview
Compute
Storage
Database
OverviewParameter Description
TENANCY DETAILS:
Total number of compartments Total number of compartments present in the tenancy.
Total Number of Subscribed Regions Total number of regions that are subscribed by the tenancy.
INSTANCE:
Total Oracle Cloud Instances Number of Oracle Cloud instances present.
Total Oracle Cloud Instances Running Number of Oracle Cloud instances that are running.
STORAGE:
Total Number of Buckets Total number of buckets present in Oracle Cloud Storage.
Total Number of File Systems Total number of file systems present in Oracle Cloud Storage.
Total Number of Mount Targets Total number of mount targets present in Oracle Cloud Storage.
DATABASE:
Total Number of Autonomous Databases Total number of databases present in Oracle Autonomous Database.
Compute
Parameter Description
Instances:
Name Name of the Oracle Cloud Instance.
Status Status of the Oracle Cloud Instance.
Compartment name Name of the compartment.
Public IP Address Public IP Address of the instance.
Operating System Operating System of the Oracle Cloud Monitor.
Region Region where the Oracle Cloud Instance is running.
You can perform the following admin actions on the required Compute instance(s):
Delete: Deletes the selected Compute monitor instance(s) from the Applications Manager console alone.
Start Instances: Starts the selected Compute instance(s) from Applications Manager.
Stop Instances: Stops the selected Compute instance(s) from Applications Manager.
By clicking over the instance name, you will be redirected to the Oracle Cloud Compute monitoring dashboard.
Storage
Parameter Description
Buckets:
Bucket Name The name of the bucket in the Oracle Cloud instance.
Storage Tier The storage tier of the bucket in the Oracle Cloud instance.
Compartment Name Name of the compartment.
Region Region where the bucket is located.
Number of Objects The number of objects available in the bucket.
Bucket Size The size of the bucket (in GB).
Visibility Denotes the visibility assigned to the bucket.
File Systems:
File System Name Name of the file system in the Oracle Cloud instance.
Region Region where the file system is located.
Compartment Name Name of the compartment.
Utilization The amount of memory utilized by the file system (in GB).
Life Cycle State The current state of the file system.
Created Time The date and time at which the file system was created.Parameter Description
Availability Domain The availability domain of the file system.
Last Snapshot Name Name of the snapshot that was last taken.
Backup Age The number of days that have elapsed since the last backup.
Mount Targets:
Mount Target Name Name of the mount target in the Oracle Cloud Instance.
Life Cycle State The current state of the file system.
Compartment Name Name of the compartment.
Region Region where the mount target is located.
IP Address The IP address of the mount target.
Availability Domain The availability domain of the mount target.
By clicking over the bucket name, you will be redirected to the Oracle Cloud Storage monitoring dashboard.
Databases
Parameter Description
Autonomous Databases:
Autonomous DB Name User-friendly name of the autonomous database.
Life Cycle State The current state of the autonomous database.
Compartment Name Name of the compartment.
Region Region where the autonomous database instance is running.
Database Name Actual name of the autonomous database.
Workload Type The workload type of the autonomous database.
CPU Core Count The number of CPU cores to be made available for the autonomous database.
Dedicated Deployment Indicates whether the autonomous database uses the dedicated deployment type.
You can perform the following admin actions on the required Autonomous Database(s):
Delete: Deletes the selected Autonomous database(s) monitor instance from Applications Manager console
alone.
Start Databases: Starts the selected Autonomous database(s) from Applications Manager.
Stop Databases: Stops the selected Autonomous database(s) from Applications Manager.
By clicking over the DB name, you will be redirected to the Oracle Autonomous Database monitoring dashboard.
Oracle Cloud Compute
Overview
Oracle Cloud Infrastructure Compute offers significant price-performance and control improvements compared to
on-premises data centers, while providing elasticity and cost savings of the public cloud. It lets you provision and
manage compute hosts, known as instances. It offers both bare metal and virtual machine instances.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Oracle Cloud under the Cloud Apps
section. Displayed is the Oracle Cloud bulk configuration view distributed into three tabs:
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
On clicking a monitor from the list, you''ll be taken to the Oracle Cloud dashboard. Under the parent monitor, you
have 3 tabs. The child monitor has 6 tabs:Performance
Boot Volume
Block Volume
Network
Configuration
Performance
Parameter Description
CPU:
CPU Utilization Activity level from CPU. Expressed as percentage of total time.
Memory:
Memory Utilization Space currently in use. Expressed as a percentage of used pages.
Disk:
Disk Read Read throughput expressed as bytes read per interval.
Disk Write Write throughput expressed as bytes written per interval
Disk Read IOPS Activity levels from I/O reads expressed as bytes read per interval.
Disk Write IOPS Activity levels from I/O writes expressed as bytes written per interval.
Network:
NetworksBytesIn Network recieved throughputs expressed in bytes.
NetworkBytesOut Network transmitted throughput expressed in bytes.
Boot Volume
Parameter Description
Boot Volume Read throughput Read throughput expressed in bytes
Boot Volume Write throughput Write throughput expressed in bytes
Boot Volume Read operations Activity level from I/O reads expressed in bytes
Boot Volume Write operations Activity level from I/O writes expressed in bytes
Block Volumes
Oracle Block volumes add storage capacity to an instance and enables you to dynamically provision and manage
data.
Parameter Description
Block Volume Details:
Volume OCID Oracle Cloud ID for the block volume.
Block Volume
A user-friendly name for the volume.
Name
Size In GB The size of the volume in GBs.
Life Cycle State The current state of a volume.
Specifies whether the cloned volume''s data has finished copying from the source volume
Is Hydrated
or backup.
Block Volume I/O Statistics:
Volume OCID Oracle Cloud ID of the block volume.
Read
The average number of bytes read from the block volume per second.
Throughput(MB)
Write
The average number of bytes written to the block volume per second.
Throughput(MB)
Read Operations Number of read operations occurring in this block volume.
Write Operations Number of write operations occurring in this block volume.Network
Track the Virtual Network Interface Cards (VNICs) to determine how an instance connects with endpoints inside
and outside a Virtual Cloud Network (VCN).
Parameter Description
Attached VNICs:
VNIC OCID Oracle Cloud ID for the VNIC.
VNIC Name A user-friendly name for the VNIC.
Public IP Address The public IP address of the VNIC.
Private IP Address The private IP address of the primary VNIC.
Primary Indicates whether the VNIC is primary or not.
Life Cycle State The current state of the VNIC.
MAC Address The MAC address of the VNIC.
Skip Source Destination Check Indicates Whether the source/destination check is disabled or not.
VNIC Performance Metrics:
VNIC OCID Oracle Cloud ID for the VNIC.
Egress Packets Dropped by Security Number of packets sent from the VNIC dropped due to security
List violations.
Ingress Packets Dropped by Security Number of packets received from network dropped due to security
List violations.
Packets from Network Number of packets received by the VNIC after drops.
Packets to Network Number of packets sent from the VNIC before drops.
Input Traffic Rate at which data is received by the VNIC after drops (in KBps).
Output Traffic Rate at which data is sent from the VNIC before drops (in KBps).
Configuration
Parameter Description
INSTANCE INFORMATION:
Instance Name Name of the instance
Instance OCID Oracle Cloud ID of the instance.
Status State of the instance.
Compartment OCID Oracle Cloud ID for the compartment.
Shape Shape of the instance.
Region Localized geographic region of the instance.
Public IP Address Public IP Address of the instance.
Private IP Address Private IP Address of the instance.
Availability Domain Availability domain of the instance.
Fault Domain Fault domain of the instance.
Launch Mode Specifies the configuration mode for launching virtual machine (VM) instances.
Time Created The date and time during which the instance was created.
Time Maintenance Reboot
The date and time during which the instance is expected to reboot.
Due
OS INFORMATION:
Operating System Name of the operating system used by the image.
Operating System Version Version of the operating system used by the image.
Boot Volume Size The boot volume size for an instance launched from this image. (MB)
Image Name A user-friendly name for the image.
Base Image ID The OCID of the image originally used to launch the instance.Parameter Description
Determines whether instances launched with this image can be used to create new
Create Image Allowed
images.
Image ID The Oracle Cloud ID of the image.
Launch Mode Specifies the configuration mode for launching virtual machine (VM) instances.
Life Cycle State State of the image.
Boot Volume OCID Oracle Cloud ID of the boot volume.
Oracle Cloud Storage
Oracle Cloud Storage - Overview
Oracle Cloud Storage is a storage platform that provides high-performance object and file storage services
and offers excellent scalability, data availability, durability, and security. It allows you to store objects and access
any amount of data instantly from anywhere and is ideal for storing unlimited amount of unstructured data such as
images, media files, logs, backups, etc.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the Storage instance available under
Oracle Cloud in the Cloud Apps section. Displayed is the Oracle Cloud Storage bulk configuration view
distributed into three tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
By clicking a monitor from the list, you''ll be taken to the Oracle Cloud Storage dashboard. It has 4 tabs:
Overview
Requests
Objects
Configuration
Overview
Parameter Description
NUMBER OF OBJECTS:
Number of Objects The number of objects present in the Oracle Storage instance.
BUCKET SIZE:
Bucket Size The size of the bucket (in GB).
TOTAL REQUESTS:
Total Requests The total number of requests processed by the bucket.
LATENCY:
First Byte Latency The per-request time measured from the time Object Storage receives the complete
Time request to when Object Storage returns the first byte of the response.
Overall Latency The per-request time from the first byte received by Object Storage to the last byte sent
Time from Object Storage.
ERRORS:
Client Side Error
The total number of client-side errors made in the bucket.
Count
INCOMPLETE MULTIPART UPLOAD SIZE:
Incomplete
The size of any multipart upload parts that have not been discarded (aborted) or
Multipart Upload
committed.
SizeRequests
Parameter Description
READ REQUESTS:
GetObject Request
The total number of Get object requests made in a bucket.
Count
HeadObject
The total number of Head object requests made in a bucket.
Request Count
ListObjects Request
The total number of List object requests made in a bucket.
Count
WRITE REQUESTS:
DeleteObject
The total number of Delete object requests made in a bucket.
Request Count
PutObject Request
The total number of Put object requests made in a bucket.
Count
RenameObject
The total number of Rename object requests made in a bucket.
Request Count
PostObject Request
The total number of Post object requests made in a bucket.
Count
CopyObject Request
The total number of Copy object requests made in a bucket.
Count
ArchiveObject The total number of Archive object requests made in a bucket. To archive objects, you
Request Count must configure an Object Lifecycle policy.
REQUESTS THROUGHPUT:
Get Requests/Min The number of Get request made per minute.
Put Requests/Min The number of Put request made per minute.
Objects
Parameter Description
Top Objects by Size:
Object Name (Top) Name of the object that is of higher size.
Top Object Size Size of the object that is of higher size (in MB).
Created Time (Top) Time at which the object of higher size was created.
Recently Uploaded Objects:
Object Name (Recent) Name of the object that was recently uploaded.
Recently Uploaded Object Size Size of the object that was recently uploaded (in MB).
Created Time (Recent) Time at which the recently-uploaded object was created.
Category Wise Details:
Category Category of the object.
Objects Count Number of objects available in that category.
Category Size Total size of objects available in that category (in MB).
Configuration
Parameter Description
BUCKET INFORMATION:
Compartment Name Name of the compartment.
Region Region where the bucket is located.
Storage Tier The storage tier of the bucket.
Created Time The date and time at which the bucket was created.
Visibility Denotes the visibility assigned to the bucket.Parameter Description
Object Level Audit Mode Specifies whether the audit logs are enabled for the objects in the bucket.
Entity Tag The Entity Tag (or ETag) header value assigned to the bucket.
Oracle Autonomous Database
Oracle Autonomous Database - Overview
An autonomous database is a fully managed, pre-configured cloud database environment that uses machine
learning and Internet of Things (IoT) to perform tasks without any human intervention. It automates tasks
associated with database tuning, security, backups, updates, etc. that are traditionally performed by database
administrators (DBAs) and helps you in creating the database and performs maintenance tasks such as backing
up, patching, upgrading and tuning the database with ease.
Monitored Parameters
Prerequisites for monitoring Oracle Autonomous DB metrics: Click here
Go to the Monitors Category View by clicking the Monitors tab. Click on the Autonomous Database instance
available under Oracle Cloud in the Cloud Apps section. Displayed is the Oracle Autonomous Database bulk
configuration view distributed into three tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
On clicking a monitor from the list, you''ll be taken to the Oracle Autonomous Database dashboard. It has 6 tabs:
Overview
Tablespace
Session
Process
Scheduled Jobs
Configuration
Overview
Parameter Description
UTILIZATION:
CPU Utilization Amount of CPU utilized by the autonomous database (in percentage).
Storage Utilization Amount of storage capacity utilized by the autonomous database (in percentage).
CONNECTION STATISTICS:
DB Connection
Time taken to connect to the database (in seconds).
Time
SESSION DETAILS:
Sessions The number of sessions running in the autonomous database.
Current Logons The number of successful logons occurred during the selected time interval.
The combined number of logons, parses, and execute calls during the selected time
User Calls
interval.
QUEUED STATEMENTS THROUGHPUT:
Running
The number of running SQL statements aggregated across all consumer groups.
Statements
Queued
The number of queued SQL statements aggregated across all consumer groups.
Statements
TRANSACTIONS:
Execute Count The number of user and recursive calls that executed SQL statements.Parameter Description
Total Parse Count The number of hard and soft parses occurred.
Transaction Count The combined number of user commits and user rollbacks.
FAILED LOGONS & CONNECTIONS THROUGHPUT:
Failed Connections The number of failed database connections occurred.
Failed Logons The number of failed logons occurred.
Tablespace
Parameter Description
Tablespace Details:
Tablespace Name Name of the tablespace.
Allocated Bytes Allocated size of the tablespace (in GB).
Total Allocated Bytes The total allocated size of the tablespace (in GB).
Used Bytes The amount of storage that have been used in the tablespace (in GB).
Free Bytes The remaining amount of storage that is free in the tablespace (in GB).
Used Bytes (%) The amount of storage that have been used in the tablespace (in percentage).
Free Bytes (%) The remaining amount of storage that is free in the tablespace (in percentage).
Allocated Blocks The number of data blocks allocated to the tablespace.
Free Blocks The number of free data blocks available in the tablespace.
Tablespace Status:
Tablespace Name Name of the tablespace.
Tablespace Status The status of the tablespace. (ONLINE, OFFLINE or INVALID)
Data Files The number of data files available in the tablespace.
Read Rate Number of read operations that have occurred in the tablespace per minute.
Write Rate Number of write operations that have occurred in the tablespace per minute.
Read Time Time taken for a single read from the tablespace (in seconds).
Write Time Time taken for a single write to the tablespace (in seconds).
Performance of DataFiles:
DataFile Name Name of the data file along with its location.
Tablespace Name Name of the tablespace.
Status The status of the data file.
AutoExtend Denotes whether AutoExtend is enabled for this data file or not.
Created Bytes The size of the data file (in MB).
Reads Number of reads occurred from the data file.
Writes Number of writes occurred to the data file.
Average Read Time The average time taken for read operations to occur. (in millisecond)
Average Write Time The average time taken for write operations to occur. (in millisecond)
Objects Approaching MAX Extents:
Owner Owner name of the table space.
Tablespace Name Name of the tablespace.
Segment Name Name of the segment approaching maximum extents.
Segment Type The type of segment approaching maximum extents.
Extents Number of extents allocated to the segment.
Max Extents Maximum allowed extents that can be filled in a segment.
Next Extents Size of the next extent (in megabytes).
SessionParameter Description
Session Details:
ID Session Identifier for the connected session.
Status Current status of the session. (ONLINE, OFFLINE or INVALID)
Machine Name of the operating system.
User Name Name of the Oracle process user.
Amount of time elapsed after the user has logged into the Oracle server (in
Elapsed Time
seconds).
CPU Time Amount of time the CPU was in use by the session.
Memory Sorts Number of memory sorts used by the session.
Table Scans Number of table scans performed.
Physical Reads Number of physical reads occurred for the session.
Logical Reads Number of physical reads occurred for the session.
Commits Number of commits made by the user in a second.
Cursor Number of cursors that are currently in use.
Denotes the amount of session logical reads taking place from the buffer (in
Buffer Cache Hit Ratio
percentage).
Sessions Summary:
Machine Name Name of the machine hosting the session.
Program Name of the program which is causing the session.
Session Status Current status of the session. (ACTIVE or INACTIVE)
Session Count Denotes the number of sessions that are running.
Session Waits:
Session ID Session Identifier for the connected session.
User Name of the Oracle process user.
Event Resource or event for which the session is waiting.
State The state of the session.
The wait time for the session. If the value is 0, it means the session is currently
Wait Time
waiting.
Seconds in Wait Denotes the amount of time spent for the current wait condition (in seconds).
Number of Event
The number of events occurred during that session.
Occurrence
Users:
Username The username assigned to the user.
Expiry Date The date at which the user account expires.
Days to Expiry The number of days remaining for the user account to expire.
Account Status The current status of the user account.
User Profile The profile name of the user.
Process
Parameter Description
PGA Stats Per Process: Provides a graphical representation of the PGA used by processes.
Oracle Process:
Process ID Identifier for the Oracle process.
PGA Allocated Amount of PGA memory allocated for the process (in megabytes).
PGA Used Amount of PGA memory consumed by the process (in megabytes).
Amount of allocated PGA memory that can be freed back to the operating system (in
Freeable PGA
megabytes).
Max PGA Used Maximum amount of PGA memory consumed by the process.Parameter Description
Program
Name of the program in progress.
Name
Scheduled Jobs
Parameter Description
Schedule Jobs Details:
Job Name Name of the job.
Current State The current state of the job.
Last Run Status Status of the job that was running during the last run.
Last Run Date The date on which the job started running during the last run.
Last Run Duration Amount of time the job took to complete during the last run (in seconds).
Next Run Date The date on which the job is scheduled to run.
Run Count Number of times the job has run.
Failure Count Number of times the job has failed to run.
Retry Count Number of times the job has retried to run.
Elapsed Time Denotes the time elapsed since the job was started (in seconds).
Is Enabled Denotes whether the job is enabled or not.
Configuration
Parameter Description
CONFIGURATION DETAILS:
Autonomous Database Name Name of the autonomous database.
Compartment Name Name of the compartment.
Region Region where the autonomous database instance is running.
Compartment OCID Oracle Cloud ID for the compartment.
CPU Core Count The number of CPU cores to be made available for the autonomous database.
Auto Scaling Enabled Indicates if auto scaling is enabled for the Autonomous Database.
Created Time The date and time on which the database was created.
Dedicated Deployment Indicates if the database uses the dedicated deployment option.
License Model The license model that applies to the Oracle Autonomous Database.
DATABASE INFORMATION:
Database Name Name of the Oracle database.
Database Version Version of the valid Oracle Database for Autonomous Database.
Data Storage Size The amount of storage available in the database (in terrabytes).
Used Storage Size The amount of storage that has been used (in terabytes).
The workload type of the autonomous database. Possible values are:
Workload Type OLTP - Autonomous Transaction Processing
DW - Autonomous Data Warehouse
Always Free Resource Indicates if this the resource is ''Always Free''. The default value is false.
Preview Version Indicates if the Autonomous Database is a preview version or not.
Life Cycle State The current life cycle state of the autonomous database.
Life Cycle Details Information about the current life cycle state of the autonomous database.
The client IP access control list (ACL) for the database. (Available for server less
White listed IPs
deployments only)
CONNECTION INFORMATION:Parameter Description
Oracle Application Express
URL of the Oracle Application Express (APEX).
(APEX) URL
Oracle SQL Developer Web
URL of the Oracle SQL Developer.
URL
Service Console URL The URL of the Service Console for the Autonomous Database.
Denotes the database service tpurgent used for autonomous transaction
TPurgent
processing operations.
Denotes the database service tp used for autonomous transaction processing
TP
operations.
Denotes the database service high used for autonomous transaction processing
High
operations.
Denotes the database service medium used for autonomous transaction
Medium
processing operations.
Denotes the database service low used for autonomous transaction processing
Low
operations.
Amazon Web Services Monitoring
Amazon Web Services (AWS) - Overview
Creating a new Amazon Monitor, Settings and Demo
Monitored Parameters
Supported Regions
Troubleshooting
Amazon Web Services (AWS) - Overview
Amazon Web Services (AWS) is a comprehensive cloud computing platform from Amazon. AWS offers an array of
cloud computing services to build on from data centers spread across availability zones in regions across the
world. However, you would still need a proper AWS monitoring software to be able to monitor and understand what
is going on when you deploy and consume such a wide-ranging set of services.
From your infrastructure and applications to your end-user experience, Applications Manager''s AWS monitoring
provides robust monitoring of several core Amazon Web Services under your Amazon account. With all-in-one AWS
cloud monitoring tools like Applications Manager in place, users can obtain a single pane view over various AWS
services like:
Amazon Elastic Compute Cloud (Amazon EC2)
Amazon Elastic Load Balancing (Amazon ELB)
Amazon Relational Database Service (Amazon RDS)
Amazon Simple Storage Service (Amazon S3)
Amazon Simple Notification Service (Amazon SNS)
Amazon DynamoDB
Amazon Simple Queue Service (Amazon SQS)
Amazon Lambda Service (AWS Lambda)
Amazon Elastic Beanstalk Service (AWS Elastic Beanstalk)
Amazon Elastic Container Service (AWS ECS)
Amazon Elastic Kubernetes Service (AWS EKS)
In this help document, you will learn how to get started with AWS performance monitoring, along with the list of
parameters that are monitored using Applications Manager.
Supported Regions
You can collect metrics, visualize resource usage and alert on operational behavior for all supported services
across your AWS cloud environment for the following regions:Global Regions
China Regions
GovCloud (US) Regions
Creating a new Amazon monitor
Prerequisites for setting up Amazon performance monitoring: Click here.
Using the REST API to add a new Amazon monitor: Click here
To create a new Amazon monitor, follow the steps given below:
Click on New Monitor link.
Select Amazon under Cloud Apps category.
Specify the Display Name of the Amazon server
Select the Amazon Services you wish to discover and monitor from the drop-down menu.
Enter the Access Key Id of the AWS for accessing the AWS through the API. The access key has 20 alpha-
numeric characters.
Enter the Secret Access Key of the AWS. The secret key should be 40 alpha-numeric characters long.
Choose the Account Type. The default account type when adding a new Amazon monitor is AWS Global.
Choose AWS China as the Account Type to monitor services in the AWS China regions, or choose AWS Gov
Cloud to monitor services in the AWS GovCloud regions.
Based on the ''Account Type'' chosen, select the regions to monitor from either Global Regions, China Regions,
or Gov Cloud Regions drop-down menu.*
Select a Child Discovery option.*
If you choose the Advanced Settings option: *
Select the action you want to perform on deleted resources using the Action on Deleted Resources field.
Specify input for Regex to filter EC2 instances name option to filter our EC2 Instances based on the
name.
Enable Stop discovery if you want to stop discovering resources under a particular service.
Specify the Polling interval in minutes.
If you are adding a new monitor from Admin server, select a Managed server.
Choose the Monitor Group with which you want to associate the Amazon monitor to, from the combo box
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the Amazon server from the network and starts monitoring it.
Note: Parameters marked with a * have been added from Applications Manager version 15180 onwards.
How to add Amazon Web Services (AWS) Monitor?
Amazon Data Collection Settings
You can configure data collection settings for your Amazon monitor by going to the Admin tab, selecting
Performance Polling under Discovery and then the Amazon tab. Here are the settings that you can customize for
AWS performance monitoring in Applications Manager:
You can set the Unique Identifier for EC2 instances to be either the instance ID or a tag name.
Caution: Once set, changing the Unique Identifier will result in the existing monitors being deleted. If a
new instance with Tag name of an already terminated instance is launched, it will be merged with the
former instance.
Enabling the Collect S3 Storage Statistics via CloudWatch API option allows you to fetch S3 Storage metrics
using CloudWatch APIs.For Applications Manager versions till 15170:
Option Description
Alert for Terminated EC2
Option to receive notification when an EC2 instance is stopped.
Instance
Remove terminated EC2
Option to completely remove terminated EC2 Instances and Lambda functions
Instances & Lambda
from the Applications Manager console in the consecutiv next poll.
Functions
Remove deleted DynamoDB Option to completely remove deleted DynamoDB tables from the Applications
tables Manager console in the next poll.
Remove deleted Elastic Option to completely remove terminated Elastic Beanstalk Environments from the
Load Balancers Applications Manager console in the next poll if the environment is terminated.
Remove inactive ECS Option to completely remove terminated/deleted ECS clusters from the
clusters Applications Manager console in the next poll if the cluster is terminated/deleted.
Note: Make sure you have a working internet connecion to add or fetch data from the cloud services. If your
environment requires the use of a proxy server to access external Websites, you can configure the proxy
settings under the ''Admin'' tab.
For Applications Manager versions 15180 onwards:
Enable Auto Scaling alerts for EC2 instances: Option to receive alerts whenever an EC2 Instance is
created/deleted.
Set health severity as: Option to set Amazon monitor''s health severity as Critical or Warning whenever a
new EC2 Instance is created or deleted.
Raise autoscaling alerts when EC2 instances are: Option to configure when an alert has to be recieved
(When an EC2 Instance is created/deleted/both)
Monitored Parameters
Amazon accounts are monitored based on the parameters or the attributes listed below. These attributes provide
detailed information about the functioning of the Amazon account. You can also configure thresholds to the
numerical attributes based on these details and get notified when the thresholds are violated.
Go to the Monitors Category View by clicking the Monitors tab. Click on the Amazon monitor under the Cloud
Apps Table. Displayed is the Amazon bulk configuration view distributed into three tabs:
Availability tab displays the Availability history for the past 24 hours or 30 days.
Performance tab displays the Health Status and events for the past 24 hours or 30 days along with key
performance indicators of the Amazon account such as Total EC2 Instances running and Total RDS Instances
along with heat charts for these attributes.
List view tab enables you to perform bulk admin configurations and displays all the Amazon instances along
with an overall idea of their availability and health status.
AWS monitoring software like Applications Manager provide complete visibility into your Amazon cloud
environments altogether in a single window based on the following tabs:
Overview
Compute (EC2, Lambda, Elastic Beanstalk)
Containers (ECS, EKS)
Database (RDS, DynamoDB)
Amazon ELB
S3 Buckets
SNS Service
Amazon SQS
Billing
Note:
Each Amazon monitor instance is considered a basic monitor.Each service instances (except S3, SNS and Billing information) running in your Amazon monitor is
considered a basic monitor.
For more information, refer here.
Overview
Parameter Description
COMPUTE RESOURCES
Total EC2 Instances Running The number of EC2 instances running in the account.
The total number of Application Load Balancers present in the
Number of Application Load Balancers
account.
Number of Network Load Balancers The total number of Network Load Balancers present in the account.
Number of Lambda Functions The total number of Lambda functions present in the account.
Number of Elastic Beanstalk The total number of Elastic Beanstalk environments present in the
Environments account.
STORAGE RESOURCES
Total EBS Volumes in use The number of EBS storage volumes currently in use.
Total S3 Buckets The total number of S3 buckets present in the account.
DATABASE RESOURCES
Total RDS Instances The total number of RDS instances present in the account.
Total DynamoDB tables The total number of DynamoDB tables present in the account.
APPLICATION INTEGRATION
Number of SQS Queues The total number of SQS Queues present in the account.
Number of SNS Topics The total number of SNS topics present in the account.
CONTAINERS
Number of ECS Clusters The total number of ECS clusters present in the account.
Number of EKS Clusters The total number of EKS clusters present in the account.
Compute
Following are the list of services that are shown in the ''Compute'' tab:
EC2 Instances
Lambda
Elastic Beanstalk Environments
EC2 Instances
This table provides details about the EC2 instances present in the Amazon account. Know more about EC2
Monitoring
Parameter Description
EC2 Instances
Instance ID The unique identifier of the EC2 instance
The region where this EC2 instance is running. To know the list of regions supported, refer
Region Name
here.
The current state of the instance. The values include running, stopped, shutdown and
State
terminated
Platform The OS on which the instance is running
Monitoring Indicates whether monitoring is enabled for the instance.
Public DNS
The DNS name associated with the instance.
Name
System Log Displays the system log of the instance.You can perform the following admin actions on the EC2 instances:
Delete: Delete the EC2 instance from Applications Manager.
Assign Platform: Assign platforms such as Windows, Mac OS, etc. to instances.
Start Instances: Option to start the EC2 instance from Applications Manager.
Stop Instances: Option to stop EC2 instances from Applications Manager.
Reboot Instances: Option to reboot the EC2 instances from within Applications Manager.
Lambda
This table provides details about the Lambda functions present in the Amazon account. Know more about Lambda
functions
Parameter Description
LAMBDA
Function Name of the Lambda function.
The region where this Lambda function is running. To know the list of regions supported,
Region Name
refer here.
Version Version of the Lambda function.
Runtime The runtime environment for the Lambda function.
Deployed Code Size
Size of deployment package of the function (in MB).
(MB)
Timeout The amount of time that Lambda allows a function to run before stopping it (in seconds).
Last Modified Time Date and time at which the function was last modified.
Elastic Beanstalk Environments
This table provides details about the Elastic Beanstalk environments present in the Amazon account. Know more
about Elastic Beanstalk Environments
Parameter Description
Elastic Beanstalk Environments
Environment Name Name of the Elastic Beanstalk environment.
The region where the Elastic Beanstalk environment is running. To know the list of regions
Region Code
supported, refer here.
Tier Name Name of the tier. Indicates whether it is a WebServer or a Worker environment.
Environment Status Status of the environment. (Ready, Launching, Updating, Terminating, or Terminated)
Environment Health Shows the health status of the environment. (OK, Info, Unknown, No data, Warning,
Status Degraded, or Severe)
Containers
ECS Clusters
This tab provides details about the ECS clusters present in the Amazon account. Know more about ECS clusters
Parameter Description
ECS Clusters
ClusterName Name of the ECS cluster.
The status of the Cluster. (ACTIVE, PROVISIONING, DEPROVISIONING, FAILED,
Status
INACTIVE)
Registered Container
The number of containers instances registered to the cluster.
Instances
Active Services The number of active services running in the cluster.
Running Tasks The number of tasks that are in RUNNING state.
EKS Clusters
This tab provides details about the EKS clusters present in the Amazon account. Know more about EKS clustersParameter Description
EKS Clusters
ClusterName Name of the EKS cluster.
Status The status of the cluster. (CREATING, ACTIVE, DELETING, FAILED, UPDATING)
Database
Following are the list of services that are shown in the ''Database'' tab:
RDS Instances
DynamoDB
RDS Instances
This tab provides details about the RDS Instances present in the Amazon account. Know more about RDS Instances
Parameter Description
Instance ID The unique identifier of the instance.
The region in which the RDS instance is running. To know the list of regions supported, refer
Region Name
here.
The current state of this instance. The possible values for this field are available, creating,
State
failed, rebooting, etc.
DB Engine Name The name of the database engine associated with this instance
Allocated
The storage space allocated to this instance in Giga Bytes
Storage
Aurora Cluster
The name of the Aurora DB cluster.
Name
Cluster Instance
The role that is associated with the Aurora DB instance.
Role
Cluster Group
The current state of this DB cluster group.
status
DynamoDB
In this table, you can gather data for performance metrics of you Amazon DynamoDB like latency, request
throughput and throttling errors. Optimize resource usage and improve application performance of your Amazon
Dynamodb database. Know more about DynamoDB monitoring
Parameter Description
Tables
Name Name of the DynamoDB table.
Name of the AWS region where the current DynamoDB table resides. To know the list of
Region
regions supported, refer here.
Total Provisioned
Total number of provisioned read capacity units for a table.
Read CU
Total Provisioned
Total number of provisioned write capacity units for a table.
Write CU
Storage Size (GB) Total size of the specified table (in GB).
Table Status Current status of the table.
Creation Date The date and time at which the table was created.
DynamoDB Account Limits
Region The ID of AWS region where the current DynamoDB account resides.
Region Name Name of the region at which the DynamoDB account is located.
Read Limit Region wise maximum read capacity unit limit.
Provisioned Read Number of provisioned read capacity units.
Write Limit Region wise maximum write capacity unit limit.
Provisioned Write Number of provisioned write capacity units.Parameter Description
Table Read Limit Table-wise maximum read capacity units that can be provisioned.
Table Write Limit Table-wise maximum write capacity units that can be provisioned.
Amazon Elastic Load Balancing
Applications Manager''s AWS ELB monitoring gives you the ability to monitor your Load Balancers, analyze traffic
patterns and troubleshoot issues with your load balancers and targets for optimized performance. Know more
about AWS ELB monitoring
Application Load Balancers
Parameter Description
Name The name of the Application Load Balancer
The AWS region in which the load balancer is configured. To know the list of regions supported,
Region
refer here.
State The state of the load balancer - active | provisioning | active_impaired | failed.
Availability
The Availability Zones for the load balancer.
zones
VPC ID The ID of the VPC for the load balancer.
Creation time The date and time the load balancer was created.
Network Load Balancers
Parameter Description
Name The name of the Network Load Balancer
The AWS region in which the load balancer is configured. To know the list of regions supported,
Region
refer here.
State The state of the load balancer - active | provisioning | active_impaired | failed.
Availability
The Availability Zones for the load balancer.
zones
VPC ID The ID of the VPC for the load balancer.
Creation time The date and time the load balancer was created.
S3 Buckets
This tab provides details about the S3 buckets present in the Amazon account.
Parameter Description
S3 Buckets Storage Statistics
Bucket Name The unique name of the S3 bucket.
Bucket Size The size of the S3 bucket in megabytes.
Bucket The geographical region where Amazon has stored this bucket. To know the list of regions
Location supported, refer here.
Creation Time The time when the bucket was created.
Virtual
The number of folders present in this S3 bucket.
Folders
Number of
The number of objects stored in this S3 bucket.
Objects
S3 Buckets Request Statistics
Bucket Name The unique name of the S3 bucket.
Total
The total number of HTTP requests made to the bucket.
Requests
Requests/min Number of requests made per minute to the bucket.
Get Requests The number of HTTP GET requests made for objects in the bucket.
Put Requests The number of HTTP PUT requests made for objects in the bucket.Parameter Description
First Byte The per-request time (in milliseconds) from the complete request being received by the bucket
Latency to when the response starts to be returned.
The elapsed per-request time (in milliseconds) from the first byte received to the last byte sent to
Total Request
the bucket. This includes the time taken to receive the request body and send the response body,
Latency
which is not included in First Byte Latency.
Bytes The number of bytes downloaded (in MB) for requests made to the bucket, where the response
Downloaded includes a body.
Bytes
The number of bytes uploaded (in MB) that contain a request body, made to the bucket.
Uploaded
Client Errors The number of HTTP 4xx client error status code requests made to the bucket.
Server Errors The number of HTTP 5xx server error status code requests made to the bucket.
You can perform the following admin actions on the S3 buckets from within Applications Manager.
Disable: Disables the monitoring of S3 bucket.
Enable: Enables the monitoring of S3 bucket.
Delete: Deletes the S3 bucket from Applications Manager console. Please note that the required S3 bucket
instance should first be deleted from your AWS account before performing this action. Otherwise,
Applications Manager will rediscover that S3 bucket and start monitoring again.
You can also view comparison reports based on attributes such as bucket size, virtual folders and number of object
Note:
''Virtual Folder'' metric is not supported upon using CloudWatch API to fetch Storage metrics.
To monitor S3 Bucket Request metrics, the same should be enabled in AWS console. We recommend using
the name EntireBucket for a filter that applies to all objects. For more information, refer here.
SNS Services
In this tab you can monitor region and topic-wise metrics like notification status (delivery and failure), SMS
deliveries, messages throughput - sent and failed counts, subscription count and more. Know more about SNS
Service monitoring
Parameter Description
Total Messages
The total number of messages published throughout all the AWS supported regions.
Published
Total Notifications
The total number of messages delivered throughout all the AWS supported regions.
Delivered
Total Notifications
The total number of messages failed throughout all the AWS supported regions.
Failed
Total Published
The total size of messages published throughout all the AWS supported regions.
Size (KB)
Notifications
The percentage of total delivered notifications.
Delivered (%)
Notifications
The percentage of total failed notifications.
Failed (%)
SMS Month-To- The total charges accrued since the start of the current calendar month for sending SMS
Date charges messages in AWS supported regions. Unit - USD
SQS Services
In this tab, you can monitor all the available queues that are running within the SQS service. Know more about SQS
service monitoring
Parameter Description
Queue Name Name of the queue.
Queue Type Type of the queue. (Standard/FIF0)
Region Shows the region where the queue was created. To know the list of regions supported, referhere.
Arrival Rate The rate at which the messages are arrived in the queue per minute.
Completion
The rate at which the messages are processed and deleted in the queue per minute.
Rate
Created Time Displays the time when the queue was first created.
Billing
Parameters Description
Total Expenditure And Forecast
Month-to-
Date The total expenditure in the current month for an AWS account.
Expenditure
Current
Month The cost forecast for the current month.
Forecast
Services And Tax
Month-to-
Date Services The total cost in USD incurred by all the services [Excluding tax].
Cost
Month-to-
The total cost in USD by tax.
Date Tax
Month-to-Date Top Services by Spend
Month-to-
The Month-to-Date Spend by Service graph shows the top services that you use most and the
Date Costs
proportion of your costs(USD) that that service contributed to [excluding forecasting and *tax*].
(USD)
Month-to-Date Spend by Service
AWS Service The AWS services that you use.
Costs (USD) The cost in USD incurred for the month to date by the services.
Note: The Billing data will be available only for AWS Global accounts. The polling interval for the AWS Billing
Statistics can be changed by going to the Admin tab, clicking Performance Polling under Discovery and
Data Collection, and navigateing to the Optimize Data Collection tab. Choose Amazon for the Monitor Type
& AWS Billing Dashboards for the Metric Name and change the Default Polling Status.(Default and preferred
time interval is 24 hours).
Supported Regions
AWS Global Regions
From version 13600 onwards, we support the following global AWS regions:
US East (N. Virginia)
US East (Ohio)
US West (N. California)
US West (Oregon)
Canada (Central)
South America (Sao Paulo)
EU (Frankfurt)
EU (Ireland)
EU (London)
EU (Paris)
EU (Stockholm)
Asia Pacific (Tokyo)
Asia Pacific (Seoul)
Asia Pacific (Mumbai)
Asia Pacific (Singapore)
Asia Pacific (Sydney)
Asia Pacific (Hong Kong)
Asia Pacific (Osaka-Local)
Middle East (Bahrain)Africa (Cape Town)
Europe (Milan)
In case you want to monitor AWS in all the above-mentioned regions, choose the All Regions option under Global
Regions in the Add/Edit monitor page. By default, this option will be selected.
Note: Do not specify other regions when All Regions option is selected. If other regions are chosen along with
All regions, only the chosen regions will be considered while adding/updating the monitor.
AWS China Regions
The China regions are isolated from all other AWS (Global) regions and operated by AWS''s Chinese partners
separately from all other AWS regions. However, the cloud services offered in both AWS China regions are the
same as those available in other AWS (Global) regions. From Version 13620, we support monitoring of Amazon
Web Services in AWS China regions. Here is a list of regions available in the AWS China account:
China (Beijing)
China (Ningxia)
The default Account Type when adding a new Amazon monitor is AWS Global. Choose AWS China as the
Account Type to monitor services in the AWS China regions.
AWS Gov Cloud Regions
AWS Gov Cloud (US) gives government customers and their partners the flexibility to architect secure cloud
solutions. This is designed to host sensitive data, regulated workloads, and address the most stringent US
government security and compliance requirements. AWS Gov Cloud regions are operated by employees who are
US citizens on US soil, and are accessible only to US entities and root account holders who pass a screening
process.
From version 15390 onwards, we support monitoring of Amazon Web Services in AWS Gov Cloud regions.
Following are the list of regions available in the AWS Gov Cloud account:
US East (US-Gov-East)
US West (US-Gov-West)
The default Account Type when adding a new Amazon monitor is AWS Global. Choose AWS Gov Cloud as the
Account Type to monitor services in the AWS Gov Cloud (US) regions.
Troubleshooting
1. Some instances of EC2, RDS, S3, SNS are not being discovered for data collection
There are two ways of authenticating information in the requests made to AWS to collect data:
Signature version 2 (S2) and
Signature version 4 (S4)
In the following regions, AWS supports only signature version 4 signing process: [US East (Ohio), Canada
(Central), Asia Pacific (Mumbai), Asia Pacific (Seoul), EU (Frankfurt), EU (London)]. If you are using AWS
services from the regions which supports only S4, Applications Manager will not discover them as they require
S4 signing process.
Solution: Upgrade to Applications Manager Version 13600 (or newer). We have upgraded to the latest aws jar
and support both signing processes in AWS. From Version 13600, we also support all 15 regions available
currently. (Know more)
Note: Make sure you have a working internet connecion to add or fetch data from the cloud services. If your
environment requires the use of a proxy server to access external Websites, you can configure the proxy
settings under the ''Admin'' tab.
2. When child monitors are not discovered or when no data in AWS and its child monitors.
Check the list of APIs mentioned in this page and make sure the IAM user has all the required API permissions.
Check the region in which the user has created the resources in AWS and make sure the same region is
supported/discovered in Applications Manager. Know more3. No data in EC2 Instance in OS level metrics.
Most of the times, the issues occurs due to the wrong configuration in agent configuration file, using which the
Cloudwatch agent fetches the data from the EC2 instances.
Applications Manager can fetch the data from CloudWatch based on the following:
Namespace - AWS allows the user to have any namespace, but only ''CWAgent'' as namespace is supported in
Applications Manager
Dimensions - Only ''InstanceId'' as dimension is supported in Applications Manager. If any additional
dimensions are configured in agent configuration file, then it is not supported. It looks for only the ''instanceid''
dimension.
In every data collection of EC2 instance monitor, first we look for ''Memory'' metrics in Windows/Linux instances,
and then we check for ''Disk'' metrics. Make sure users are configured similar to the metrics mentioned in this page
sample configuration files.
Amazon Elastic Load Balancing
Amazon Elastic Load Balancing - An Overview
Monitoring Amazon Elastic Load Balancing- What We do
Adding a new Amazon ELB monitor
Monitored Parameters
Application Load Balancer Metrics
Network Load Balancer Metrics
Amazon Elastic Load Balancing - An Overview
Elastic Load Balancing (ELB) is a load-balancing service from Amazon Web Services (AWS). AWS ELB
automatically distributes incoming application traffic across multiple targets, such as EC2 instances, and scales
resources to meet traffic demands. Elastic Load Balancing helps IT teams adjust capacity according to incoming
application and network traffic.
AWS ELB supports three types of load balancers: Application Load Balancers, Network Load Balancers and
Classic Load Balancers.
The Application Load Balancer handles advanced traffic routing from other services or containers at the
application level.
The Network Load Balancer is ideal for load balancing of TCP traffic and capable of handling millions of
requests per second while maintaining low latencies.
Monitoring Amazon Elastic Load Balancing - What We do
This page discusses how Applications Manager''s AWS ELB monitoring gives you the ability to monitor your Load
Balancers, analyze traffic patterns and troubleshoot issues with your load balancers and targets for optimized
performance.
Gather real-time performance data - Get basic data about the number of healthy hosts, latency, requests,
error rates and more.
Analyze connection count statistics - Monitor the number of rejected connections to follow your Load
Balancer’s ability to properly connect to a target and route a request. Measure the number of rules and bytes
processed by the Application ELB.
Track healthy and unhealthy host count - Monitor the number of healthy targets registered with the
Application Elastic Load Balancer. Maintain a Healthy Host Count by tracking healthy instances
Troubleshoot and monitor target HTTP error response codes - Gather statistics on the number of Client and
Server errors generated by the load balancer. Measure the number of TLS connections that could not
successfully establish a session between your load balancer and its registered instances. Get an aggregate of
HTTP 4XX and 5XX error codes generated by the targets in your group.
Detect real-time performance issues and fix them faster - Understand the scalability of your ELB system
and get a jumpstart on monitoring the Load Balancers in your environment. Applications Manager provides
the ability to monitor your ELB configuration with detailed metrics about the requests made to your load
balancers.Get instant notifications of performance issues and bottlenecks. Take quick remedial action before your end-
users experience issues.
Creating a new Amazon ALB/NLB monitor
Mode of Monitoring: CloudWatch & AWS API using SDK.
Prerequisites for setting up Amazon ELB monitoring: Click here
To create a new Amazon monitor, follow the steps given below:
Click on New Monitor link.
Select Amazon under Cloud Apps category.
Specify the Display Name of the Amazon server
Choose ALB or NLB as the Amazon Service you wish to monitor.
Enter the Amazon Access Key Id of the AWS for accessing the AWS through the API. The access key has 20
alpha-numeric characters.
Enter the Secret Access Key of the AWS. The secret key should be 40 alpha-numeric characters long.
Choose the Account Type. The default Account Type when adding a new Amazon monitor is AWS Global.
Choose AWS China as the Account Type to monitor services in the AWS China regions.
Specify the Polling Interval in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group with which you want to associate the Amazon monitor to, from the combo box
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the Amazon server from the network and starts monitoring it.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on ALB or NLB in the Amazon Instances
under the Cloud Apps Table. Displayed is the bulk configuration view distributed into three tabs:
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the Amazon ALB metrics listed under the following tabs:
Overview
Errors
Target Groups
Targets
Configuration
Click on the monitor name to see all the Amazon NLB metrics listed under the following tabs:
Overview
Errors
Target Groups
Targets
Configuration
Applications Load Balancer (ALB) Metrics
Applications Load Balancer - Overview
Parameter Description
AVERAGE LATENCY
Average The time elapsed, in seconds, after the request leaves the load balancer until a response from
Target Latency the target is received. This is equivalent to the target_processing_time field in the access logs.
REQUESTSParameter Description
The number of requests processed over IPv4 and IPv6. This count includes only the requests
Total Requests
with a response generated by a target of the load balancer.
Requests / Min The requests processed per minute over IPv4 and IPv6.
CONNECTIONS
Active The total number of concurrent TCP connections active from clients to the load balancer and
Connections from the load balancer to targets.
New The total number of new TCP connections established from clients to the load balancer and
Connections from the load balancer to targets.
Rejected The number of connections that were rejected because the load balancer had reached its
Connections maximum number of connections.
PROCESSED BYTES
Total Data
The total number of bytes processed by the load balancer over IPv4 and IPv6.
Processed
Data
The bytes processed per minute by the load balancer over IPv4 and IPv6.
Processed/Min
RULE EVALUATIONS
Rule
The number of rules processed by the load balancer given a request rate averaged over an hour.
Evaluations
CONSUMED LB CAPACITY UNITS
Consumed
The number of load balancer capacity units (LCU) used by your load balancer.
Capacity Units
Applications Load Balancer - Errors
Parameter Description
CONNECTION ERRORS
Client TLS Negotiation The number of TLS connections initiated by the client that did not establish a session
Errors with the load balancer.
Target TLS Negotiation The number of TLS connections initiated by the load balancer that did not establish a
Errors session with the target.
Target Connection
The number of connections that were not successfully established with the target.
Errors
LOAD BALANCER ERRORS
ELB Client Errors The number of client errors that originate from the load balancer.
ELB Server Errors The number of server errors that originate from the load balancer.
Applications Load Balancer - Target Groups
Parameter Description
CONFIGURATION INFO
Target Group The name of the target group.
Port The port to use to connect with the target.
Protocol The protocol to use to connect with the target.
Target type The type of target that you must specify when registering targets with this target group.
Timeout(Seconds) The amount of time, in seconds, during which there was no response from the target.
Interval(Seconds) The approximate amount of time, in seconds, between health checks of an individual target.
HEALTHY AND UNHEALTHY HOST
Healthy Host
The number of targets that are considered healthy after health checks.
Count
Unhealthy Host
The number of targets that are considered unhealthy after health checks.
Count
TARGET GROUP REQUESTSParameter Description
Request Count The number of requests processed over IPv4 and IPv6.
PERFORMANCE METRICS
Target Group The name of the target group.
Healthy Hosts The number of targets that are considered healthy after health checks.
Unhealthy Hosts The number of targets that are considered unhealthy after health checks.
The time elapsed, in seconds, after the request leaves the load balancer until a response
Average Target
from the target is received. This is equivalent to the target_processing_time field in the
Latency(Seconds)
access logs.
The number of requests processed over IPv4 and IPv6. This count includes only the requests
Total Requests
with a response generated by the targets in a specific target group.
The average number of requests received by each target in a target group. You must specify
Requests Per
the target group using the TargetGroup dimension. This metric does not apply if the target is
Target
a Lambda function.
ERRORS
Target Group The name of the target group.
Target
The number of connections that were not successfully established with the target.
Connection Errors
Target TLS The number of TLS connections initiated by the load balancer that did not establish a
Negotiation Errors session with the target.
Target HTTP 5XX
The number of HTTP 5XX server error codes that originate from the load balancer.
Errors
Target HTTP 4XX
The number of HTTP 4XX client error codes that originate from the load balancer.
Errors
Target HTTP 3XX
The number of HTTP 3XX redirection codes that originate from the load balancer.
Errors
Target HTTP 2XX
The number of HTTP response codes generated by the targets.
Errors
Applications Load Balancer - Targets
Parameter Description
TARGET DETAILS
Target ID The ID of the target. If the target type of the target group is instance, specify an instance ID.
Target
The name of the Target Group.
Group
Port The port on which the target is listening.
Status The state of the target - initial | healthy | unhealthy | unused | draining | unavailableParameter Description
Heatlty: If the target state is healthy, a reason code is not provided.
Initial: If the target state is initial, the reason code can be one of the following values:
Elb.RegistrationInProgress - The target is in the process of being registered with the load
balancer.
Elb.InitialHealthChecking - The load balancer is still sending the target the minimum
number of health checks required to determine its health status.
Unhealthy: If the target state is unhealthy, the reason code can be one of the following values:
Target.ResponseCodeMismatch - The health checks did not return an expected HTTP code.
Target.Timeout - The health check requests timed out.
Target.FailedHealthChecks - The health checks failed because the connection to the target
timed out, the target response was malformed, or the target failed the health check for an
unknown reason.
Elb.InternalError - The health checks failed due to an internal error.
Reason
Unused: If the target state is unused, the reason code can be one of the following values:
Target.NotRegistered - The target is not registered with the target group.
Target.NotInUse - The target group is not used by any load balancer or the target is in an
Availability Zone that is not enabled for its load balancer.
Target.IpUnusable - The target IP address is reserved for use by a load balancer.
Target.InvalidState - The target is in the stopped or terminated state.
Draining: If the target state is draining, the reason code can be the following value:
Target.DeregistrationInProgress - The target is in the process of being deregistered and
the deregistration delay period has not expired.
Unavailable: If the target state is unavailable, the reason code can be the following value:
Target.HealthCheckDisabled - Health checks are disabled for the target group.
Applications Load Balancer - Configuration
Parameter Description
CONFIGURATION DETAILS
Load
Balancer The ID of the load balancer.
ID
Region The AWS region in which the load balancer is configured.
State The state of the load balancer - active | provisioning | active_impaired | failed.
Type The type of load balancer - application or network.
DNS name The public DNS name of the load balancer.
Internet-facing OR internal. Internet-facing load balancers can route requests from clients over the
Scheme internet. Internal load balancers can only route requests from clients with access to the VPC for the
load balancer.
IP address
The type of IP addresses used by the subnets for your load balancer.
type
VPC ID The ID of the VPC for the load balancer.
Availability
The Availability Zones for the load balancer.
zones
Security
The IDs of the security groups for the load balancer.
groups
Creation
The date and time the load balancer was created.
timeNetwork Load Balancer Metrics
Network Load Balancer - OVERVIEW
Parameter Description
TCP CONNECTIONS
Active The total number of concurrent TCP connections active from clients to the load balancer and
Connections from the load balancer to targets.
The total number of new TCP connections established from clients to the load balancer and
New Connections
from the load balancer to targets.
TLS CONNECTIONS
Active TLS
The total number of concurrent TLS connections from clients to targets.
Connections
New TLS The total number of new TLS connections established from clients to targets in the time
Connections period.
DATA PROCESSED (TCP)
Data processed
The total number of bytes processed by the load balancer.
(TCP)
Data processing
The rate of bytes processed per minute by the load balancer.
rate (TCP)
CONSUMED LB CAPACITY UNITS
Consumed The number of load balancer capacity units (LCU) used by your load balancer. You pay for
Capacity Units the number of LCUs that you use per hour.
Network Load Balancer - ERRORS
Parameter Description
CONNECTION ERRORS
Client TLS Negotiation The total number of TLS handshakes that failed during negotiation between a client
Errors and a TLS listener.
Target TLS Negotiation The total number of TLS handshakes that failed during negotiation between a TLS
Errors listener and a target.
RESET PACKETS COUNTERS
Client Reset Packets The total number of reset (RST) packets sent from a client to a target.
Load Balancer Reset
The total number of reset (RST) packets generated by the load balancer.
Packets
Target Reset Packets The total number of reset (RST) packets sent from a target to a client.
Network Load Balancer - TARGET GROUPS
Parameter Description
TARGET GROUPS DATA
Target Group The name of the target group.
Port The port to use to connect with the target.
Protocol The protocol to use to connect with the target.
Target type The type of target that you must specify when registering targets with this target group.
Timeout (seconds) The amount of time, in seconds, during which there was no response from the target.
Interval (seconds) The approximate amount of time, in seconds, between health checks of an individual target.
Healthy Hosts The number of targets that are considered healthy.
Unhealthy Hosts The number of targets that are considered Unhealthy.
Network Load Balancer - TARGETS
Parameter DescriptionParameter Description
TARGET DETAILS
Target ID The ID of the target. If the target type of the target group is instance, specify an instance ID.
Target
The name of the Target Group to which the target is mapped.
Group
Port The port on which the target is listening.
Status The state of the target - initial | healthy | unhealthy | unused | draining | unavailable
Healthy: If the target state is healthy, a reason code is not provided.
Initial: If the target state is initial, the reason code can be one of the following values:
Elb.RegistrationInProgress - The target is in the process of being registered with the load
balancer.
Elb.InitialHealthChecking - The load balancer is still sending the target the minimum
number of health checks required to determine its health status.
Unhealthy: If the target state is unhealthy, the reason code can be one of the following values:
Target.ResponseCodeMismatch - The health checks did not return an expected HTTP code.
Target.Timeout - The health check requests timed out.
Target.FailedHealthChecks - The health checks failed because the connection to the target
timed out, the target response was malformed, or the target failed the health check for an
unknown reason.
Elb.InternalError - The health checks failed due to an internal error.
Reason
Unused: If the target state is unused, the reason code can be one of the following values:
Target.NotRegistered - The target is not registered with the target group.
Target.NotInUse - The target group is not used by any load balancer or the target is in an
Availability Zone that is not enabled for its load balancer.
Target.IpUnusable - The target IP address is reserved for use by a load balancer.
Target.InvalidState - The target is in the stopped or terminated state.
Draining: If the target state is draining, the reason code can be the following value:
Target.DeregistrationInProgress - The target is in the process of being deregistered and
the deregistration delay period has not expired.
Unavailable: If the target state is unavailable, the reason code can be the following value:
Target.HealthCheckDisabled - Health checks are disabled for the target group.
Network Load Balancer - CONFIGURATION
Parameter Description
CONFIGURATION DETAILS
Load
Balancer The ID of the load balancer.
ID
Region The AWS region in which the load balancer is configured.
State The state of the load balancer - active | provisioning | active_impaired | failed.
Type The type of load balancer - application or network.
DNS name The public DNS name of the load balancer.
Internet-facing OR internal. Internet-facing load balancers can route requests from clients over the
Scheme internet. Internal load balancers can only route requests from clients with access to the VPC for the
load balancer.
IP address
The type of IP addresses used by the subnets for your load balancer.
type
VPC ID The ID of the VPC for the load balancer.Parameter Description
Availability
The Availability Zones for the load balancer.
zones
Creation
The date and time the load balancer was created.
time
Amazon SQS Monitoring
Amazon SQS - Overview
Amazon Simple Queue Service (SQS) is distributed message queuing service introduced by Amazon in 2004. SQS
lets us to integrate and decouple distributed software systems and components. It offers to send, receive and
delete messages programmatically via web service applications. Unlike other message queuing services, it is
serverless.
Monitored Parameters
Prerequisites for monitoring Amazon SQS metrics: Click here
Go to the Monitors Category View by clicking the Monitors tab. Click on the SQS instance available under
Amazon in the Cloud Apps section. Displayed is the Amazon SQS bulk configuration view distributed into three
tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
By clicking a monitor from the list, you''ll be taken to the AWS SQS dashboard. It has 2 tabs:
Overview
Configuration
Overview
Parameter Description
PERFORMANCE RATE
Arrival Rate The rate at which the messages are arrived in the queue per minute.
Completion Rate The rate at which the messages are processed and deleted in the queue per minute.
BREAKDOWN OF STANDARD/FIFO MESSAGES
Visible Messages Number of messages that are available for retrieval.
Not Visible Messages Number of messages that are not available for retrieval.
Delayed Messages Number of messages that are in delayed state. (Applicable only for Standard queue)
PROCESSED MESSAGES
Messages Received Number of messages returned by requests to the ReceiveMessage API action.
Empty Receives Number of ReceiveMessage API calls that did not yield a message.
AGE OF OLDEST MESSAGE
Age of Oldest Message Measures the approximate age of the oldest non-deleted message.
SIZE OF SENT MESSAGES
Sent Message Size Measures the size of the messages added to the queue (in KB).
Rate of Sent Message Size Measures the rate of size of the messages added to the queue (in KB/sec).
Configuration
Parameter Description
FIFO/STANDARD QUEUE DETAILS
Queue URL Shows the URL of the Amazon SQS queue.Parameter Description
Created Time Displays the time when the queue was first created.
Last Modified Time Displays the time when the queue was last modified.
Region Name Shows the region where the queue was created.
Queue Type Shows the type of queue. (Standard/FIFO)
Content-based Shows whether the content based deduplication is enabled for the queue. (Applicable
Deduplication only for FIFO queue)
STANDARD/FIFO QUEUE CONFIGURATIONS
Amount of time for which the message will be in delayed state (in seconds). (Applicable
Delayed Time
only for Standard queue)
Received Message
The time a ReceiveMessage API action waits for the message to arrive (in seconds).
Wait Time
Maximum Message
The maximum limit of size a message can contain before Amazon SQS rejects it.
Size
Message Retention
Time for which Amazon SQS retains a message (in seconds).
Period
Time during which Amazon SQS prevents other consumers from receiving and
Visibility Timeout
processing the message (in seconds).
Dead Letter Target ARN of the Dead letter queue where Amazon SQS moves the message after maximum
ARN receives value is exceeded.
Maximum number of times a message is delivered to the queue before being moved to a
Maximum Receives
dead letter queue.
Customer Master Key ID of the AWS managed Customer master key (CMK) for the Amazon queue.
Key Reuse Period Time for which a data key can be reused to encrypt or decrypt messages (in seconds).
Amazon EC2 Instance Monitoring
Monitored Parameters
The Amazon EC2 instances are monitored based on the parameters or the attributes listed below. These attributes
provide information about the functioning of the EC2 instances. You can also configure thresholds to the numerical
attributes based on these details and get notified when the thresholds are violated.
Go to the Monitors Category View by clicking the Monitors tab. Click on the EC2 Instance of Amazon monitors
under the Cloud Apps Table. Displayed is the Amazon EC2 bulk configuration view distributed into three tabs:
Availability tab displays the Availability history for the past 24 hours or 30 days.
Performance tab displays the Health Status and key performance indicators of an EC2 instance such as CPU
Utilization, Volume Idle Time, Network In and Network Out along with the heat charts for these attributes for
the past 24 hours or 30 days.
List view displays all the EC2 instances present in the Amazon account along with an overall idea of their
availability and health status. In this tab, you can also perform bulk admin configurations.
Below is an explanation of the metrics shown in the following tabs:
Overview
OS Level Metrics
Linux
Windows
Attached Volumes
Configuration
Note: The metrics marked with an * are collected using Amazon''s Cloudwatch
OverviewThis tab provides a high-level overview of the EC2 instance as well as its performance indicators.
Parameter Description
Monitor Information
Name The name of the EC2 instance
Type Denotes the type you are monitoring.
Health Denotes the health (Clear, Warning, Critical) status of the EC2 instance.
Region Name Name of the region where the instance is running
Instance Type Indicates the type of the EC2 instance
The current state of the instance. Valid values include running, stopped,
State
shutdown and terminated
Public IP Address The IP address of the instance.
Platform Indicates the platform of the instance (eg: Windows)
Last Polled at Specifies the time at which the last poll was performed.
Next Poll at Specifies the time at which the next poll is scheduled.
Shows the overall availability status of the instance for the day. You can also
Today''s Availability
view 7/30 reports and the current availability status of the instance.
CPU Utilization * The CPU utilization of the instance
Network Traffic
Network IN * Incoming traffic in bytes per minute
Network Out * Outgoing traffic in bytes per minute
Disk I/O
Disk Read Ops * The average number of disk read operations per second.
Disk Write Ops * The average number of disk write operations per second.
OS-level Metrics
To collect operating system-level metrics like Memory and Disk, you must deploy the Cloud-Watch Agent inside
EC2 instance. The agent will send your data to Cloud-Watch from where Applications Manager fetches and
displays it in the console. Click here to know more about how you can collect metrics from Amazon ec2 instances
and on-premises servers with the Cloud-Watch Agent.
Note: Fetching OS-level metrics via the Cloudwatch agent is supported from build 13740 of Applications
Manager.
Linux
Parameter Description
MEMORY STATISTICS
Available Memory The memory available for use of the EC2 instance (in GB).
Used Memory The memory currently in use (in GB).
MEMORY UTILIZATION
Memory Utilization The memory used on an instance in percentage.
Swap Utilization The disk swap utilization in percentages
DISK UTILIZATION
Disk Utilization The disk space used on an instance.
DISK SPACE DETAILS
DiskName Name of the disk.
Total Disk Space The total amount of disk space available on an instance.
Total Size (GB) Total size of the disk (in GB).
Disk Utilization (%) The percentage of disk space used on an instance.
Disk Available (GB) The total amount of disk space available on an instance (in GB).
Disk Used (GB) The total amount of disk space used by an instance (in GB).Windows
Parameter Description
AVAILABLE MEMORY
Available Memory The memory available for use of the EC2 instance (in GB).
The percentage of memory in use for which space has been reserved in the
% Committed Bytes In Use
paging file, should it need to be written to disk.
DISK UTILIZATION
DiskName Name of the disk.
Total Size (GB) Total size of the disk (in GB).
Disk Utilization (%) The percentage of disk space used on an instance.
Disk Available (GB) The total amount of disk space available on an instance in GB.
Disk Used (GB) The total amount of disk space used by an instance in GB
Attached Volumes
This tab provides metrics about the EBS volumes attached to the EC2 instance.
Parameter Description
Configuration
The ID of the Amazon EBS volume. The volume and instance must be within the
Volume ID
same Availability Zone and the instance must be running.
Size The size of the volume in Giga Bytes.
Snapshot ID Snapshot from which the volume was created.
Created Time Time stamp when volume creation was initiated.
Attached Time Time stamp when the attachment was initiated.
Delete on Termination Specifies whether the Amazon EBS volume is deleted on instance termination.
Health Denotes the health of the volume (clear, warning, critical)
Latency
The time period when no read or write operations were waiting to be
Idle Time *
completed in percentage(%)
The average of the total number of seconds spent by all Write operations that
Write Latency *
completed in the period
The average of the total number of seconds spent by all Read operations that
Read Latency *
completed in the period
Volume Traffic
Read Bandwidth * The sum of total number of Read operations in the period in bytes per second
Write Bandwidth * The sum of total number of write operations in the period in bytes per second
Volume IO
Read Throughput * The sum of read operations in the period in seconds
Write Throughput * The sum of write operations in the period in seconds
The average number of read and write operation requests waiting to be
Queue Length *
completed over the period.
Configuration
This tab provides the configuration details of the EC2 instance.
Parameter Description
Instance ID The unique key that identifies the EC2 instance.
Instance Type Indicates the type of the instance.
Instance Launch Time The time at which the instance was launched
The current state of the instance. The values include running, stopped,
State
shutdown and terminatedParameter Description
Image ID Image ID of the AMI used to launch the instance.
The AMI launch index, which can be used to find this instance within the
AMILaunch Index
launch group.
The public DNS name assigned to the instance. This DNS name is contactable
Public DNS Name
from outside the Amazon EC2 network.
The private DNS name assigned to the instance. This DNS name can only be
Private DNS Name
used inside the Amazon EC2 network.
Public IP Address The IP address of the instance.
Private IP Address The private IP address assigned to the instance.
The name of the key pair, if this instance was launched with an associated key
KeyPair Name
pair.
Platform Indicates the platform of the instance (eg: Windows)
Availability Zone The instance''s availability zone.
Architecture The architecture of the image.
RamDisk Id RAM disk associated with this instance.
Kernel Id Kernel associated with this instance.
The root device type used by the AMI. The AMI can use an Amazon EBS or
RootDevice Type
instance store root device.
RootDevice Name The name of the root device used by the AMI.
Monitoring Indicates whether monitoring is enabled for the instance.
Indicates whether the instance can be terminated through the Amazon EC2
Termination Protection
console, CLI, or API. If enabled, the instance cannot be terminated.
Configuring Cloud-Watch Agent in an EC2
instance
To collect operating system-level metrics like Memory and Disk, you must deploy the Cloud-Watch Agent inside
EC2 instance. The agent will send your data to Cloud-Watch from where Applications Manager fetches and
displays it in the console. Click here to know more about how you can collect metrics from amazon ec2 instances
and on-premises servers with the Cloud-Watch Agent.
Prerequisites to configuring the Cloud-Watch Agent in an EC2
instance:
Supported Operating Systems:
The Cloud-Watch agent is supported on the following operating systems:
Amazon Linux version 2014.03.02 or later
Ubuntu Server version 16.04 and 14.04
CentOS version 7.0 and 6.5
Red Hat Enterprise Linux (RHEL) version 7.4, 7.0, and 6.5
Debian 8.0
64-bit versions of Windows Server 2016, Windows Server 2012, and Windows Server 2008.
Steps to configure the Cloud-Watch agent:
Create the IAM role that you need to attach to each Amazon EC2 instance that runs the CloudWatch
agent. This role provides permissions for reading information from the instance and writing it to
CloudWatch. Click here to know how you can create IAM roles to use with the CloudWatch Agent on
Amazon EC2 Instances.
Attach the created IAM role to an EC2 instance. Click here to know how.
Install the Cloud-Watch Agent. There are two ways to install the Cloud-Watch Agent:
Using SYSTEMS MANAGER in ec2 console (You do not need to log in to the EC2 instance) or
Via direct download link. (You must log in to the EC2 instance)Note: The metrics_collection_interval parameter indicates how often all metrics specified in
this configuration file are to be collected. Make sure the value of this metric should be less
than the EC2 instance polling interval. A good practice would be to set it to 5 minutes (300
seconds).
Create a Cloud-Watch agent configuration file (click here to know how) using Parameter Store feature in
EC2 console. (More help here)
Start the Cloud-Watch Agent using the Run Command feature available in EC2 console. Refer here.
Creating a Cloud-Watch agent configuration file in the EC2
console.
Open the AWS EC2 console - https://console.aws.amazon.com/ec2
In the navigation pane, choose Parameter Store under SYSTEMS MANAGER SHARED RESOURCES
Click Create Parameter
Enter a name (Enter a name based on the OS type - ex: CwAgent Windows Config file Or CwAgent
Linux Config file) and description for your parameter and choose ''Type'' as ''String''
Copy the following configuration file content for Cloud-Watch Agent to fetch OS level metrics from EC2
instances.
Note : To modify/include/exclude the disk partitions to be monitored, see the "resources": tag in below
configuration files content. Change the "resources" tag if you want to monitor different partitions other
than the mentioned ones below ("resources": [ "*" ] - means it will fetch all partitions available). Refer
here for further info. Make sure the dimensions in ''append_dimensions'' tag has only ''InstanceId'' as
mentioned below in the sample agent configuration file.
Windows OS: { "metrics": { "append_dimensions": { "InstanceId": "${aws:InstanceId}" },
"metrics_collected": { "LogicalDisk": { "measurement": [ "% Free Space", "Free Megabytes" ],
"metrics_collection_interval": 300, "resources": [ "*" ] }, "Memory": { "measurement": [ "% Committed
Bytes In Use", "Available MBytes", "Committed Bytes" ], "metrics_collection_interval": 300 } } } }
Linux OS: { "metrics": { "append_dimensions": { "InstanceId": "${aws:InstanceId}" }, "metrics_collected":
{ "mem": { "measurement": [ "mem_total", "mem_used" ], "metrics_collection_interval": 300 }, "disk": {
"resources": [ "/", "/run" ], "measurement": [ "disk_total", "disk_used" ], "metrics_collection_interval": 300
}, "swap": { "measurement": [ "swap_used_percent" ], "metrics_collection_interval": 300 } } } }
Paste it in the Value* text box in the Create Parameter page and Click ''Create Parameter'' to create one.
Note : Create two different configuration files. One for windows instances and another for Linux
instances.
Amazon RDS Monitoring
Amazon RDS - An Overview
Creating a new Amazon Aurora DB monitor
Monitored Parameters
Amazon RDS - An Overview
Amazon Relational Database Service (or Amazon RDS) is a distributed relational database service by Amazon Web
Services (AWS). It is a web service running "in the cloud" designed to simplify the setup, operation, and scaling of a
relational database for use in applications. Amazon RDS supports an array of database engines to store and
organize data and helps with database management tasks, such as migration, backup, recovery and patching.
Amazon RDS is available on several database instance types - optimized for memory, performance or I/O - and
provides you with six familiar database engines to choose from, including Amazon Aurora, PostgreSQL, MySQL,
MariaDB, Oracle Database, and SQL Server.In this help document, you will learn how to get started with Amazon RDS Monitoring, along with the list of
parameters that are monitored using Applications Manager.
Creating a new Amazon RDS monitor
Prerequisites for setting up Amazon monitoring: Click here
Using the REST API to add a new Amazon RDS monitor: Click here
To create a new Amazon RDS monitor, follow the steps given below:
Click on New Monitor link.
Select Amazon under Cloud Apps category.
Specify the Display Name of the Amazon server
Select RDS from the Amazon Services drop-down menu.
Enter the Access Key Id of the AWS for accessing the AWS through the API. The access key has 20 alpha-
numeric characters.
Enter the Secret Access Key of the AWS. The secret key should be 40 alpha-numeric characters long.
Choose the Account Type. The default Account Type when adding a new Amazon monitor is AWS Global.
Choose AWS China as the Account Type to monitor services in the AWS China regions.
Specify the Polling Interval in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group with which you want to associate the Amazon monitor to, from the combo box
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the Amazon server from the network and starts monitoring it.
Applications Manager automatically discovers all the EC2 and RDS instances, and S3 buckets under your Amazon
account. You can then enable monitoring for those instances and buckets as per your requirement.
Monitored Parameters
Amazon RDS Instances are monitored based on the parameters or the attributes listed below. These attributes
provide information about the functioning of the RDS instance. You can also configure thresholds to the numerical
attributes based on these details and get notified when the thresholds are violated.
Go to the Monitors Category View by clicking the Monitors tab. Click on the RDS Instance of Amazon monitors
under the Cloud Apps table. Displayed is the Amazon RDS bulk configuration view distributed into three tabs:
Availability tab displays the Availability history of the RDS instances for the past 24 hours or 30 days.
Performance tab displays the Health Status and key performance indicators of an RDS instance such as CPU
Utilization, Free Storage Space, Database Connections and Write Throughput along with the heat charts for
these attributes for the past 24 hours or 30 days.
List view displays all the RDS instances present in the Amazon account along with an overall idea of their
availability and health status. The list view also enables you to perform bulk admin configurations.
The metrics monitored are categorized into 2 tabs for easy understanding. Below is an explanation of the metrics
displayed in the differnet tabs:
Monitor Information
Overview
Disk I/O
Network
Aurora DB
DB Operations
Replication
Configuration
Note: The metrics marked with an * are collected using Amazon''s Cloudwatch
Monitor Information
Parameter Description
Monitor Information
Name The name of the RDS instance.Parameter Description
Region The ID of AWS region where the current RDS instance is running.
Region Name The name of the region where the RDS instance is running.
Instance Type Indicates the type of instance
Created Time The time when the instance was created.
The current state of the instance. The values include:
running
State stopped
shutdown
terminated
DB Engine Name The name of the database engine associated with this instance
Last Polled at Specifies the time at which the last poll was performed.
Next Poll at Specifies the time at which the next poll is scheduled.
Associated Groups The groups to which the monitor is associated.
Overview
This tab provides a high-level overview of the RDS Instance as well as its resource utilization.
Metric Description Supported Engines
Aurora PgSQL Aurora Other engine
MySQL types
CPU Utilization(%)
The percentage of CPU utilization.
*
Database The number of database connections in
Connections * use.
Free Memory(GB)
Free Storage
The amount of available storage space.
Space(%) *
Free Local The amount of local storage that is free
Storage(GB) on an Aurora instance.
The amount of swap space used on the
Swap Usage(MB)
DB Instance.
Disk I/O
Metric Description Supported Engines
Aurora Aurora Other
PgSQL MySQL engine types
The average amount of time taken
Read Latency(Seconds) * per disk read I/O operation in
seconds.
The average number of disk read
Read Ops(Ops/Sec) *
I/O operations per second.
Read Throughput(Bytes/Sec) The average number of bytes read
* from disk per second.
The average amount of time taken
Write Latency(Seconds) *
per disk write I/O operation.
The average number of disk write
Write Ops(Ops/Sec) *
I/O operations per second.
Write Throughput(Bytes/Sec) The average number of bytes
* written to disk per second.
The amount of storage in bytes
Used Volume(GB)
used by the Aurora database.Metric Description Supported Engines
Aurora Aurora Other
PgSQL MySQL engine types
The number of billed read I/O
Volume Read IOPs(Ops/Sec) operations from a cluster volume,
reported at 5-minute intervals.
The average number of write disk
I/O operations to the cluster
Volume Write IOPs(Ops/Sec)
volume reported at 5-minute
intervals.
Network
Metric Description Supported Engines
Aurora PgSQL Aurora Other engine
MySQL types
The incoming (Receive) network
Incoming traffic(kB/s)
traffic on the DB instance.
The outgoing (Transmit) network
Outgoing traffic(kB/s)
traffic on the DB instance.
Aurora DB
Amazon Aurora is a relational database engine from Amazon Web Services, available as part of the Amazon
Relational Database Service (RDS). Being MySQL and PostgreSQL - compatible and built for the cloud, Amazon
Aurora provides security, availability, and reliability with the simplicity of open source databases.
Metric Description Supported Engines
Aurora Aurora Other engine
PgSQL MySQL types
The average rate of current transactions
Active Transactions
executing on a DB instance.
The average rate of transactions in the
Blocked Transactions
database that are blocked.
Bin Logs Disk The amount of disk space occupied by
Usage(MB) binary logs on the master.
Transaction Logs Disk The amount of disk space occupied by
Usage(MB) transaction logs.
Buffer Cache Hit The percentage of requests that are
Ratio(%) served by the Buffer cache.
ResultSet Cache Hit The percentage of requests that are
Ratio(%) served by the Resultset cache.
The average number of deadlocks in the
Deadlocks
database per second.
The average lag when replicating
updates from the primary instance. This
metric will be populated only for Aurora
Aurora ReplicaLag(ms) cluster ''Reader'' and similarly
''ReplicaLag Minimum and Maximum''
will be populated only for Aurora Cluster
''Writer'' role instances.
The maximum amount of lag between
ReplicaLag
the primary instance and each Aurora
Maximum(ms)
instance in the DB cluster.
The minimum amount of lag between
ReplicaLag
the primary instance and each Aurora
Minimum(ms)
instance in the DB cluster.
Note: The Aurora Replica Lag metric will be populated only for Aurora cluster ''Reader''. The ReplicaLag
Minimum/Maximum will be populated only for Aurora Cluster ''Writer'' role instances.DB Operations
Metric Description Supported Engines
Aurora Aurora Other
PgSQL MySQL engine
types
The amount of latency for committed
Commit Latency(ms)
transactions.
Commit The average rate of committed
Throughput(Ops/Sec) transactions.
The amount of latency for DDL
DDL Latency(ms)
requests (create/alter/drop).
The average rate of DDL requests per
DDL Throughput(Ops/Sec)
second.
The average latency for delete
Delete Latency(ms)
queries.
Delete
The average rate of delete queries.
Throughput(Ops/Sec)
The amount of latency for insert
Insert Latency(ms)
queries.
Insert
The average rate of insert queries.
Throughput(Ops/Sec)
Number of The average rate of queries executed
Queries(Queries/sec) per second.
Select Latency(ms) The average latency for select queries.
Select
The average rate of select queries.
Throughput(Ops/Sec)
The average latency for update
Update Latency(ms)
queries.
Update
The average rate of update queries.
Throughput(Ops/Sec)
Replication
This tab will be shown only if a RDS Instance has a source DB Instance identifier in the configuration details.
Metric Description Supported Engines
Aurora PgSQL Aurora Other engine
MySQL types
The amount of time a Read Replica
DB instance lags behind the source
Replication lag DB instance. Applies to MySQL,
MariaDB, and PostgreSQL Read
Replicas.
Replication Source The source DB instance.
The AWS Region that the encrypted
Source Region
Read Replica is created in.
The Amazon Resource Name of the
Source ARN
source.
Replication Status Type
Replication Status
Configuration
This tab provides the configuration details of the RDS instance.
Metric Description Supported EnginesMetric Description AuSrourpapoArtuerdo rEangiOnethser
PgSQL MySQL engine
types
Aurora Aurora Other
PgSQL MySQL engine
types
CONFIGURATION DETAILS
Instance ID The unique key that identifies the instance.
DBInstance ARN The Amazon Resource Name for the source DB instance.
DB Engine Name The name of the database engine used for this instance.
Engine Version The database engine version.
Created Time The time when the instance was created.
The name of the initial database created when the instance
DB Name
was created.
Master User Name The master username for the instance.
License Model The license model information for the DB instance.
INSTANCE DETAILS
Instance Type The type of instance.
Storage Type The storage type to be associated with the DB instance.
Allocated Storage
The storage space initially allocated to this instance in GB.
(GB)
Storage Encrypted Specifies the encryption status of the DB instance.
The current status of the instance. Valid values include
State available, backing-up, creating, deleted, deleting, failed,
modifying, rebooting and resetting-master-credentials.
Multi(A-Z)
Indicates if this is a Multi-AZ DB Instance.
Deployment
The name of AWS region where the current DynamoDB table
Region Name
resides.
SECURITY AND NETWORK
Availability Zone The instance''s availability zone.
Publicly Accessible Specifies if the DB instance is marked as publicly accessible.
Endpoint Address The DNS Address of the DB instance.
Endpoint Port The port used to connect to the DB instance.
MAINTENANCE DETAILS
Preferred
The period during which patching and instance modifications
Maintenance
will be performed.
Window
Latest Restorable The latest time to which a database can be restored using
Time point-in-time restore.
Backup Retention The number of days that automated backups are retained
Period before deletion.
Preferred Backup The daily period during which automated backups are
Window created.
CLUSTER CONFIGURATION
The name of the Aurora cluster to which the RDS instance
Aurora Cluster Name
belongs to.
Cluster ARN The Amazon Resource Name (ARN) for the DB cluster.
The endpoint for an Aurora DB cluster that connects to the
Cluster Endpoint
current primary DB instance for that DB cluster.
Cluster Reader The endpoint for an Aurora DB cluster that connects to one of
Endpoint the available Aurora Replicas for that DB cluster.
Cluster Created
The time when the DB cluster was created
TimeMetric Description Supported Engines
Aurora Aurora Other
PgSQL MySQL engine
types
Cluster Instance The role that is associated with the DB instance. [Reader/
Role Writer]
Cluster Group status The current state of this DB cluster group.
Amazon Aurora DB Monitoring
Amazon Aurora DB - An Overview
Adding a new Amazon Aurora DB monitor
Monitored Parameters
Amazon Aurora DB - An Overview
Amazon Aurora is a relational database engine from Amazon Web Services, available as part of the Amazon
Relational Database Service (RDS). Being MySQL and PostgreSQL - compatible and built for the cloud, Amazon
Aurora provides security, availability, and reliability with the simplicity of open source databases.
Adding a new Amazon Aurora DB monitor
Mode of Monitoring: CloudWatch & Amazon API using SDK.
Using the REST API to add a new Amazon monitor: Click here
To create a new Amazon Aurora DB monitor, follow the steps given below:
Click on New Monitor link.
Select Amazon under Cloud Apps category.
Specify the Display Name of the Amazon server.
Select RDS from the Amazon Services drop-down menu.
Enter the Amazon Access Key Id of the AWS for accessing the AWS through the API. The access key has 20
alpha-numeric characters.
Enter the Secret Access Key of the AWS. The secret key should be 40 alpha-numeric characters long.
Choose the Account Type. The default Account Type when adding a new Amazon monitor is AWS Global.
Choose AWS China as the Account Type to monitor services in the AWS China regions.
Specify the Polling Interval in minutes. (Default polling interval is set to 60 minutes.)
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group with which you want to associate the Amazon monitor to, from the combo box
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the Amazon server from the network and starts monitoring it.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on RDS in the Amazon Instances under the
Cloud Apps Table. Displayed is the bulk configuration view distributed into three tabs:
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the Amazon Aurora Database metrics listed under the following tabs:
Overview
Disk I/O
Network
Aurora DB
DB Operations
ConfigurationOverview
Supported Engines
Metric Description
Aurora PgSQL Aurora Other engine
MySQL types
CPU Utilization(%) The percentage of CPU utilization.
Database The number of database connections in
Connections use.
Free Memory(GB)
Free Storage
The amount of available storage space.
Space(%)
Free Local The amount of local storage that is free
Storage(GB) on an Aurora instance.
The amount of swap space used on the
Swap Usage(MB)
DB Instance.
Disk I/O
Supported Engines
Metric Description
Aurora Aurora Other
PgSQL MySQL engine types
The average amount of time taken
Read Latency(Seconds) per disk read I/O operation in
seconds.
The average number of disk read
Read Ops(Ops/Sec)
I/O operations per second.
The average number of bytes read
Read Throughput(Bytes/Sec)
from disk per second.
The average amount of time taken
Write Latency(Seconds)
per disk write I/O operation.
The average number of disk write
Write Ops(Ops/Sec)
I/O operations per second.
The average number of bytes
Write Throughput(Bytes/Sec)
written to disk per second.
The amount of storage in bytes
Used Volume(GB)
used by the Aurora database.
The number of billed read I/O
Volume Read IOPs(Ops/Sec) operations from a cluster volume,
reported at 5-minute intervals.
The average number of write disk
I/O operations to the cluster
Volume Write IOPs(Ops/Sec)
volume reported at 5-minute
intervals.
Network
Supported Engines
Metric Description
Aurora PgSQL Aurora Other engine
MySQL types
The incoming (Receive) network
Incoming traffic(kB/s)
traffic on the DB instance.
The outgoing (Transmit) network
Outgoing traffic(kB/s)
traffic on the DB instance.
Aurora DB
Supported Engines
Metric DescriptionAurora SuppAourtreodra EngineOsther engine
Metric Description PgSQL MySQL types
Aurora Aurora Other engine
PgSQL MySQL types
The average rate of current transactions
Active Transactions
executing on a DB instance.
The average rate of transactions in the
Blocked Transactions
database that are blocked.
Bin Logs Disk The amount of disk space occupied by
Usage(MB) binary logs on the master.
Transaction Logs Disk The amount of disk space occupied by
Usage(MB) transaction logs.
Buffer Cache Hit The percentage of requests that are
Ratio(%) served by the Buffer cache.
ResultSet Cache Hit The percentage of requests that are
Ratio(%) served by the Resultset cache.
The average number of deadlocks in the
Deadlocks
database per second.
The average lag when replicating
updates from the primary instance. This
metric will be populated only for Aurora
Aurora ReplicaLag(ms) cluster ''Reader'' and similarly
''ReplicaLag Minimum and Maximum''
will be populated only for Aurora Cluster
'' Writer'' role instances.
The maximum amount of lag between
ReplicaLag
the primary instance and each Aurora
Maximum(ms)
instance in the DB cluster.
The minimum amount of lag between
ReplicaLag
the primary instance and each Aurora
Minimum(ms)
instance in the DB cluster.
Note: The Aurora Replica Lag metric will be populated only for Aurora cluster ''Reader''. The ReplicaLag
Minimum/Maximum will be populated only for Aurora Cluster ''Writer'' role instances.
DB Operations
Supported Engines
Metric Description
Aurora Aurora Other
PgSQL MySQL engine
types
The amount of latency for committed
Commit Latency(ms)
transactions.
Commit The average rate of committed
Throughput(Ops/Sec) transactions.
The amount of latency for DDL
DDL Latency(ms)
requests (create/alter/drop).
The average rate of DDL requests per
DDL Throughput(Ops/Sec)
second.
The average latency for delete
Delete Latency(ms)
queries.
Delete
The average rate of delete queries.
Throughput(Ops/Sec)
The amount of latency for insert
Insert Latency(ms)
queries.
Insert
The average rate of insert queries.
Throughput(Ops/Sec)
Number of The average rate of queries executed
Queries(Queries/sec) per second.Supported Engines
Metric Description
Aurora Aurora Other
PgSQL MySQL engine
types
Select Latency(ms) The average latency for select queries.
Select
The average rate of select queries.
Throughput(Ops/Sec)
The average latency for update
Update Latency(ms)
queries.
Update
The average rate of update queries.
Throughput(Ops/Sec)
Configuration
Metric Description
CONFIGURATION DETAILS
Instance ID The unique key that identifies the instance.
DBInstance ARN The Amazon Resource Name for the source DB instance.
DB Engine Name The name of the database engine used for this instance.
Engine Version The database engine version.
Created Time The time when the instance was created.
DB Name The name of the initial database created when the instance was created.
Master User Name The master username for the instance.
License Model The license model information for the DB instance.
INSTANCE DETAILS
Instance Type The type of instance.
Storage Type The storage type to be associated with the DB instance.
Allocated Storage (GB) The storage space initially allocated to this instance in GB.
Storage Encrypted Specifies the encryption status of the DB instance.
The current status of the instance. Valid values include available, backing-up,
State creating, deleted, deleting, failed, modifying, rebooting and resetting-master-
credentials.
Multi(A-Z) Deployment Indicates if this is a Multi-AZ DB Instance.
Region Name The name of AWS region where the current DynamoDB table resides.
SECURITY AND NETWORK
Availability Zone The instance''s availability zone.
Publicly Accessible Specifies if the DB instance is marked as publicly accessible.
Endpoint Address The DNS Address of the DB instance.
Endpoint Port The port used to connect to the DB instance.
MAINTENANCE DETAILS
Preferred Maintenance
The period during which patching and instance modifications will be performed.
Window
Latest Restorable Time The latest time to which a database can be restored using point-in-time restore.
Backup Retention Period The number of days that automated backups are retained before deletion.
Preferred Backup
The daily period during which automated backups are created.
Window
CLUSTER CONFIGURATION
Aurora Cluster Name The name of the Aurora cluster to which the RDS instance belongs to.
Cluster ARN The Amazon Resource Name (ARN) for the DB cluster.
The endpoint for an Aurora DB cluster that connects to the current primary DB
Cluster Endpoint
instance for that DB cluster.Metric Description
The endpoint for an Aurora DB cluster that connects to one of the available Aurora
Cluster Reader Endpoint
Replicas for that DB cluster.
Cluster Created Time The time when the DB cluster was created
Cluster Instance Role The role that is associated with the DB instance. [Reader/ Writer]
Cluster Group status The current state of this DB cluster group.
Amazon Simple Notification Service Monitoring
(Amazon SNS)
Amazon Simple Notification Service (SNS) - An Overview
Monitoring Amazon Simple Notification Service (SNS) - What we do
Adding a new Amazon SNS monitor / Using AddMonitor API
Monitored Parameters
Amazon Simple Notification Service (SNS) - An Overview
Simple Notification Service (SNS) is a cloud messaging service from the host of Amazon web services. SNS is a
flexible, fully managed pub/sub messaging and mobile notifications service for coordinating the delivery of
messages to subscribing endpoints and clients. With SNS you can fan-out messages to a large number of
subscribers, including distributed systems and services, and mobile devices.
Monitoring Amazon SNS - What we do
Applications Manager provides you with insight into the performance of your Amazon SNS service. Monitor region
and topic-wise metrics like notification status (delivery and failure),SMS deliveries, messages throughput - sent
and failed counts, subscription count and more.
Create a new Amazon monitor
Mode of Monitoring: CloudWatch & Amazon API using SDK. Prerequisites for setting up Amazon SNS
monitoring: To create a new Amazon monitor, follow the steps given below:
Click on New Monitor link.
Select Amazon under Cloud Apps category.
Specify the Display Name of the Amazon server
Enter the Amazon Access Key Id of the AWS for accessing the AWS through the API. The access key has 20
alpha-numeric characters.
Enter the Secret Access Key of the AWS. The secret key should be 40 alpha-numeric characters long.
Choose the Account Type. The default Account Type when adding a new Amazon monitor is AWS Global.
Choose AWS China as the Account Type to monitor services in the AWS China regions.
Specify the Polling Interval in minutes. (Default polling interval is set to 60 minutes.)
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group with which you want to associate the Amazon monitor to, from the combo box (optional).
You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the Amazon server from the network and starts monitoring it.
Changing the Polling Interval for SNS Monitor:
The polling interval for the SNS monitor is set to 60 minutes by default. To change it:
Go to the Admin tab.
Click Performance Polling under Discovery and Data Collection.
Under Performance Data Collection, Click on the Optimize Data Collection tab.
Select Amazon from the Monitor Type drop-down menu.Select SNS Service from the Metric Name drop-down menu.
Select how you wish to configure the mertics:
By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of
this type, will have the default polling status, until any exclusive customization is done for the monitor.
You can choose between three different polling settings: Never collect data, Collect data in every
polling and Collect data at customized time interval. Changing the polling status of ''Monitor Type'', will
also change any configuration done for its ''Monitors''. You can use the options Collect data in every
polling or Collect data at customized time interval to change the polling interval.
By Monitors - Use this option to change the polling status of any particular monitor(s).
Click Save.
How to add Amazon Web Services (AWS) Monitor?
Note
1. Before creating a new Amazon monitor, you have to configure proxy settings under ''Admin'' tab.
2. Click here to know more about AWS credentials.
3. It is not advisable to change the polling interval to less than 60 minutes as it may increase the number of
request to amazon services.
Use the AddMonitor API to add an Amazon SNS Monitor
Syntax of Rest API for adding the monitor:
http://[Host]:[Port]/AppManager/xml/AddMonitor?apikey=[APIKEY]&type=[TYPE]&accessKey=[ACCESSKEY]&SecretAccessKey=
[SECRETACCESSKEY]&displayname=[DISPLAYNAME]&AccountType=[account type]
Request Parameters:
The parameters involved in the API request are described below. Also, refer the list of common Request Parameters.
Field Description
type The type of the monitor you want to add. Value should be Amazon.
accesskey The Amazon Access Key Id of the AWS for accessing the AWS.
secretaccesskey The Secret Access Key of the AWS. The secret key should be 40 alpha-numeric characters long.
displayname The display name of the Amazon server monitor.
The account type. Possible Values are:
AccountType AwsGlobal
AwsChina
Monitored Parameters
SNS Usage
Message Throughput
Notification Delivery Rate
Notification Failure RateRegion-Wise Metrics
Topic-Wise Metrics
SNS USAGE
Metric Description
Total Messages
The total number of messages published throughout all the AWS supported regions.
Published
Total Notifications
The total number of messages delivered throughout all the AWS supported regions.
Delivered
Total Notifications Failed The total number of messages failed throughout all the AWS supported regions.
Total Published Size (KB) The total size of messages published throughout all the AWS supported regions.
Notifications Delivered
The percentage of total delivered notifications.
(%)
Notifications Failed (%) The percentage of total failed notifications.
SMS Month-To-Date The total charges accrued since the start of the current calendar month for sending
charges SMS messages in AWS supported regions. Unit - USD
MESSAGE THROUGHPUT
Metric Description
Publish Size / Hour The published message size per hour in KB
NOTIFICATION DELIVERY RATE
Metric Description
Notifications Delivered /
The number of notifications delivered per hour.
Hour
NOTIFICATION FAILURE RATE
Metric Description
Notifications Failed /
The number of notifications failed per hour.
Hour
REGION-WISE METRICS
Metric Description
Region The name of the AWS SNS supported region.
Topic Count The number of topics available in a region.
Message Published The number of message published in a region.
Notifications Delivered The number of notifications delivered in a region.
Notifications Failed The number of notifications failed in a region.
Published Size (KB) The total Published size in a region. (KB)
SMS Month-To-Date
The total SMS spent charges in a region.
charge (USD)
TOPIC-WISE METRICS
Metric Description
Topic Name The user-specified name of a SNS topic.
Region The name of the AWS SNS supported region.
Messages Published The number of message published in a topic.
Notifications Delivered The number of notifications delivered in a topic.
Notifications Failed The number of notifications failed in a topic.
Published Size (KB) The total published size in a topic. (KB)
Subscription Count The total number of subscriptions in a topic.
ⓘ We have restricted topic count to 200 per regionAmazon DynamoDB Monitoring
Amazon DynamoDB - An Overview
Monitoring Amazon DynamoDB - What we do
Creating a new Amazon DynamoDB monitor
Monitored Parameters
Amazon DynamoDB - An Overview
Amazon DynamoDB, a part of the Amazon Web Services portfolio, is a non-relational database that delivers
reliable performance at any scale. It is a fully managed, proprietary NoSQL database service that supports key-
value and document data structures, offers built-in security, backup and restore, and in-memory caching.
Monitoring Amazon DynamoDB - What We do
With Applications Manager, you can auto-discover your DynamoDB tables, gather data for performance metrics
like latency, request throughput and throttling errors. Optimize resource usage and improve application
performance of your Amazon Dynamodb database.
Analyze database performance - Track Request Latency, get Successful request latency reports for various
read/write operations like GET, PUT, Scan, etc. Gather key usage stats like the count of returned records and
bytes from GetRecords operations (Amazon DynamoDB Streams) during specified periods.
Optimize Resource usage - Make informed decisions about setting up DynamoDB Provisioned Throughput
capacity. Monitor the consumed read/write capacity units to prevent throttling errors to and be up-to-date on
request rates, application throughput pattern and table activity.
Troubleshoot request throttling - Monitor Throttled requests and Throttled read/write events. Reserve
capacity so the provisioned throughput does not get exhausted and you can handle sudden increases in
traffic, without returning throttling errors.
Handle DB errors and exceptions - Identify performance anomalies by getting a dashboard view of the
break-down of System Errors and User Errors.
Gain insight into DB operations performed - Track the number of conditional write attempts to a table that
failed. Monitor the number of items returned by database scan and query operations.
Get instant notifications of performance issues and bottlenecks. Take quick remedial action before your end-
users experience issues.
Creating a new Amazon DynamoDB monitor
Mode of Monitoring: CloudWatch & Amazon API using SDK.
Prerequisites for setting up Amazon DynamoDB monitoring: Click here
Using the REST API to add a new Amazon DynamoDB monitor: Click here
To create a new Amazon DynamoDB monitor, follow the steps given below:
Click on New Monitor link.
Select Amazon under Cloud Apps category.
Specify the Display Name of the Amazon server
Choose DynamoDB as the Amazon Service you wish to monitor.
Enter the Amazon Access Key Id of the AWS for accessing the AWS through the API. The access key has 20
alpha-numeric characters.
Enter the Secret Access Key of the AWS. The secret key should be 40 alpha-numeric characters long.
Choose the Account Type. The default Account Type when adding a new Amazon monitor is AWS GlobaL.
Choose AWS China as the Account Type to monitor services in the AWS China regions.
Specify the Polling Interval in minutes. (Default polling interval is set to 60 minutes.)
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group with which you want to associate the Amazon monitor to, from the combo box
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the Amazon server from the network and starts monitoring it.
Enabling Data collection for DynamoDB Account metricsData collection for DynamoDB Account metrics is disabled by default. To enable them, follow the below given
steps:
Go to the Admin tab.
Click Performance Polling under Discovery and Data Collection.
Under Performance Data Collection, Click on the Optimize Data Collection tab.
Select DynamoDB from the Monitor Type drop-down menu.
Select the required metrics from the Metric Name drop-down menu.
Enable data collection at every poll or configure custom time intervals. (24 hours is the preferred time interval
for AWS DynamoDB Account metrics as to reduce the API count).
Select how you wish to configure the mertics:
By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of
this type, will have the default polling status, until any exclusive customization is done for the monitor.
You can choose between three different polling settings: Never collect data, Collect data in every
polling and Collect data at customized time interval. Changing the polling status of ''Monitor Type'', will
also change any configuration done for its ''Monitors''. You can use the options Collect data in every
polling or Collect data at customized time interval to change the polling interval.
By Monitors - Use this option to change the polling status of any particular monitor(s).
Click Save.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on DynamoDB from Amazon Instances
category under the Cloud Apps section. Displayed is the DynamoDB bulk configuration view distributed into three
tabs:
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the Amazon DynamoDB database metrics listed under the following tabs:
Overview
Read Operations
Write Operations
Table Errors
Global Secondary Index
Streams
Configuration
Overview
Parameter Description
READ CAPACITY UNITS
The number of provisioned read capacity units for a table or a global
Provisioned Read
secondary index between the poll interval time.
Provisioned Read - Average The average provisioned read capacity.
Provisioned Read - Minimum The lowest setting for provisioned read capacity.
Provisioned Read - Maximum The highest setting for provisioned read capacity.
The number of read capacity units consumed over the poll interval time. This
Consumed Read
will help you track how much of your provisioned throughput is used.
The maximum number of read capacity units consumed by any individual
Consumed Read - Average
request to the table or index.
The minimum number of read capacity units consumed by any individual
Consumed Read - Minimum
request to the table or index.
Consumed Read - Maximum The average per-request read capacity consumed.Parameter Description
WRITE CAPACITY UNITS
Provisioned Write The number of provisioned write capacity units for a table.
Provisioned Write - Average The average provisioned read capacity.
Provisioned Write - Minimum The lowest setting for provisioned read capacity.
Provisioned Write - Maximum The highest setting for provisioned read capacity.
The number of write capacity units consumed for the global secondary index
Consumed Write
between the poll interval time.
Consumed Write - Average The average per-request write capacity consumed.
The minimum number of write capacity units consumed by any individual
Consumed Write - Minimum
request to the table or index.
The maximum number of write capacity units consumed by any individual
Consumed Write - Maximum
request to the table or index.
READ THROTTLED REQUESTS
If your read or write requests exceed the throughput settings for a table and
tries to consume more than the provisioned capacity units or exceeds for an
Throttled Read Requests index, DynamoDB can throttle that request. Based on the type of operation
(Get, Scan, Query, BatchGet) performed on the table, throttled request data
can be populated.
The Get operation returns a set of attributes for the request with the given
Get Throttled Requests
primary key.
The Scan operation returns one or more requests and request attributes by
Scan Throttled Requests
accessing every request in a table or a secondary index.
The Query operation finds requests based on primary key values. You can
Query Throttled Requests query any table or secondary index that has a composite primary key (a
partition key and a sort key).
The BatchGet operation returns the attributes of one or more requests from
BatchGet Throttled Requests
one or more tables.
WRITE THROTTLED REQUESTS
The Put operation creates a new request, or replaces an old request with a new
Put Throttled Requests
one.
The Update operation edits an existing request''s attributes, or adds a new
Update Throttled Requests request to the table if it does not already exist. You can put, delete, or add
attribute values.
Delete Throttled Requests The Delete operation deletes a single request in a table by primary key.
The BatchWrite operation puts or deletes multiple requests in one or more
BatchWrite Throttled Requests
tables.
READ THROTTLED EVENTS
The number of throttled write events during the time period. Throttled events
Table Read Throttled Events occurs when any particular event or any single event in any batch operation
fails.
WRITE THROTTLED EVENTS
The number of throttled read events during the time period. Throttled events
Table Write Throttled Events occurs when any particular event or any single event in any batch operation
fails.
Read Operations
Parameter Description
READ LATENCY
Average "Successful request latency" reports for Get operations during the
Get Latency - Average
specified time period (in ms).
Average "Successful request latency" reports for BatchGet operations during
BatchGet Latency - Average
the specified time period (in ms).Parameter Description
Average "Successful request latency" reports for Scan operations during the
Scan Latency - Average
specified time period (in ms).
Average "Successful request latency" reports for Query operations during the
Query Latency - Average
specified time period (in ms).
GET LATENCY
Get Latency - (Average/ The elapsed time for successful requests to DynamoDB for Get operations
Minimum/ Maximum) during the specified time period (in ms). (Minimum, Maximum or Average).
BATCHGET LATENCY
The elapsed time for successful requests to DynamoDB for BatchGet
BatchGet Latency - (Average/
operations during the specified time period (in ms). (Minimum, Maximum or
Minimum/ Maximum)
Average).
SCAN LATENCY
Scan Latency - (Average/ The elapsed time for successful requests to DynamoDB for Scan operations
Minimum/ Maximum) during the specified time period (in ms). (Minimum, Maximum or Average).
QUERY LATENCY
Query Latency - (Average/ The elapsed time for successful requests to DynamoDB for Query operations
Minimum/ Maximum) during the specified time period (in ms). (Minimum, Maximum or Average).
RETURNED ITEM COUNT
The number of items returned by Scan operations during the specified time
Scan Returned Item Count
period.
The number of items returned by Query operations during the specified time
Query Returned Item Count
period.
Write Operations
Parameter Description
WRITE LATENCY
Average "Successful request latency" reports for Put operations during the
Put Latency - Average
specified time period (in ms).
Average "Successful request latency" reports for BatchWrite operations during
BatchWrite Latency - Average
the specified time period (in ms).
Average "Successful request latency" reports for Update operations during the
Update Latency - Average
specified time period (in ms).
Average "Successful request latency" reports for Delete operations during the
Delete Latency - Average
specified time period (in ms).
PUT LATENCY
Put Latency - (Average/ The elapsed time for successful requests to DynamoDB for Put operations
Minimum/ Maximum) during the specified time period (in ms). (Minimum, Maximum or Average).
BATCHWRITE LATENCY
The elapsed time for successful requests to DynamoDB for BatchWrite
BatchWrite Latency - (Average/
operations during the specified time period (in ms). (Minimum, Maximum or
Minimum/ Maximum)
Average).
UPDATE LATENCY
Update Latency - (Average/ The elapsed time for successful requests to DynamoDB for Update operations
Minimum/ Maximum) during the specified time period (in ms). (Minimum, Maximum or Average).
DETELE LATENCY
Delete Latency - (Average/ The elapsed time for successful requests to DynamoDB for Delete operations
Minimum/ Maximum) during the specified time period (in ms). (Minimum, Maximum or Average).
Table Errors
Parameter Description
USER ERRORSParameter Description
Requests to DynamoDB or Amazon DynamoDB Streams that generate an HTTP
User Errors
400 status code during the specified time period.
SYSTEM ERRORS
Requests to DynamoDB or Amazon DynamoDB Streams that generate an HTTP
System Errors
500 status code during the specified time period.
CONDITIONAL CHECK FAILED REQUESTS
Conditional Check Failed
The number of failed attempts to perform conditional writes.
Requests
TIME TO LIVE DELETED ITEM COUNT
The number of items deleted by Time To Live (TTL) during the specified time
Time To Live Deleted Item Count
period.
Global Secondary Index
Parameter Description
GSI READ CAPACITY UNITS
The provisioned read CU for the global secondary index between the poll
GSI Provisioned read CU
interval time.
GSI WRITE CAPACITY UNITS
The provisioned write CU for the global secondary index between the poll
GSI Provisioned Write CU
interval time.
GSI CAPACITY UNITS
GSI Name
Provisioned Read
Consumed read CU for the global secondary index between the poll interval
Consumed Read
time.
Provisioned Write
The consumed write CU for the global secondary index between the poll
Consumed Write
interval time.
GSI READ THROTTLED EVENTS
Read Throttled Events
GSI WRITE THROTTLED EVENTS
Write Throttled Events
GSI THROTTLED EVENTS
GSI Name
GSI Read Throttled Events The requests to DynamoDB that exceed the provisioned read CU for a GSI.
GSI Write Throttled Events The requests to DynamoDB that exceed the provisioned write CU for a GSI.
GSI INDEX CREATION
GSI Name
Online Index Consumed Write The number of write capacity units consumed when adding a new global
Capacity secondary index to a table.
Online Index Percentage The percentage of completion when a new global secondary index is being
Progress added to a table.
The number of write throttle events that occur when adding a new global
Online Index Throttle Events
secondary index to a table
CONFIGURATION
Index Name The name of the Global Secondary Index.
Status The status of the index.
Item Count The total count of items in the index.
Size (MB) The Storage Size in MB.
Partition key The hash attribute of an index.Parameter Description
Sort key The range attribute of an Index.
Projection Type The set of attributes that are projected into the index.
Streams
Parameter Description
REQUEST LATENCY
Successful request latency for GetRecords operations during the specified
GetRecords Request Latency
time period. Unit - Milliseconds.
RETURNED BYTES
The number of bytes returned by GetRecords operations during the specified
Average Returned Bytes
time period. Unit - Megabytes.
Total Returned Bytes The average of bytes returned per minute. Unit - [MB/Min]
RETURNED RECORDS COUNT
The number of stream records returned by GetRecords operations during the
Returned Records Count
specified time period.
STREAM CONFIGURATION
Stream Label A timestamp when the stream is enabled, in ISO 8601 format.
Specifies if DynamoDB Streams is enabled (true) or disabled (false) on the
Stream Status
table.
Stream View Type Specifies what information is written to the stream for this table.
The Amazon Resource Name (ARN) that uniquely identifies the latest stream
Stream ARN
for this table.
Configuration
Parameter Description
CONFIGURATION
Table Name The DynamoDB Table Name.
Region The ID of AWS region where the current DynamoDB table resides.
Region Name The name of AWS region where the current DynamoDB table resides.
The total provisioned read capacity units (Both table and all GSI''s
Total Provisioned Read CU
provisioned).
The total provisioned write capacity units (Both table and all GSI''s
Total Provisioned Write CU
provisioned).
Storage Size The total size of the specified table, in GB.
Item Count The number of items in the specified table.
Table Status The current state of the table.
Partition key The partition key of an item is also known as its hash attribute.
Sort key The sort key of an item is also known as its range attribute.
Creation date The date and time when the table was created.
Amazon Resource Name (ARN) The Amazon Resource Name (ARN) that uniquely identifies the table.
Last Decrease time The date and time of the last provisioned throughput increase for this table.
Last Increase time The date and time of the last provisioned throughput decrease for this table.
The number of provisioned throughput decreases for this table during this
Number Of Decreases Today
UTC calendar day.
Number of Global Secondary
The total number of Global Secondary Indexes
Index
Stream The Stream status [Enabled/Disabled].
AWS Lambda MonitoringAWS Lambda - Overview
AWS Lambda is a server-less compute service that runs your code in response to events and automatically
manages the underlying compute resources for you.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the Lambda instance available under
Amazon in the Cloud Apps section. Displayed is the Amazon Lambda bulk configuration view distributed into
three tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
By clicking a monitor from the list, you''ll be taken to the AWS Lambda dashboard. It has 2 tabs:
Overview
Configuration
Overview
Parameter Description
INVOCATIONS
Actual The number of times your function code is executed, including successful executions and
Invocations executions that result in a function error.
Failed
The number of invocations that result in a function error. Function errors include exceptions
Invocations
thrown by your code and exceptions thrown by the Lambda runtime.
(Errors)
The number of invocation requests that are throttled. When all function instances are
Throttled
processing requests and no concurrency is available to scale up, Lambda rejects additional
Invocations
requests.
INVOCATIONS RATE
Success Rate Number of successful invocations among the total invocations (in percentage).
Error Rate Number of failed invocations among the total invocations (in percentage).
Invocations/min Number of actual invocations obtained per minute.
CONCURRENT EXECUTIONS
Reserved
The number of concurrent executions that are reserved for this function. Available only when
Concurrent
function concurrency execution is configured.
Executions
The number of function instances that are processing events. If this number reaches your
Concurrent
concurrent executions limit for the Region, or the reserved concurrency limit that you
Executions
configured on the function, additional invocation requests are throttled.
Provisioned
Concurrent The number of function instances that are processing events on provisioned concurrency.
Executions
PROVISIONED CONCURRENCY
Provisioned
Concurrency The number of times your function code is executed on provisioned concurrency.
Invocations
Provisioned
Concurrency The number of times your function code is executed on standard concurrency when all
Spillover provisioned concurrency is in use.
Invocations
DURATION
The maximum time taken for a function to process an event between the poll interval (in
Max. Duration
milliseconds).
Avg. Duration The average time taken for a function to process all the events between the poll interval (inmilliseconds).
The minimum time taken for a function to process an event between the poll interval (in
Min. Duration
milliseconds).
ITERATOR AGE
The age of the last record in the event (in seconds). The age is the amount of time between
Avg. Iterator Age when the stream receives the record and when the event source mapping sends the event to
the function.
ASYNC DELIVERY FAILURES
For asynchronous invocation, the number of times Lambda attempts to send an event to a
Dead Letter
dead-letter queue but fails. Dead-letter errors can occur due to permissions errors,
Queue Errors
misconfigured resources, or size limits.
For asynchronous invocation, the number of times Lambda attempts to send an event to a
Destination
destination but fails. Delivery errors can occur due to permissions errors, misconfigured
Delivery Failures
resources, or size limits.
Configuration
Parameter Description
CONFIGURATION DETAILS
Function ARN Amazon Resource Name (ARN) of the function.
Region Name Name of the AWS Region.
Description Description of the function.
Role Execution role of the function.
Concurrent Execution Indicates whether function concurrency execution is configured or not.
Settings (Enabled/Disabled)
Dead Letter Queue ARN Dead Letter Queue of the function.
X-Ray Tracing Mode AWS X-Ray tracing configuration of the function.
Code Repository Type The service hosting the file which holds the deployment package of the function.
RESOURCE DETAILS
Memory Size Amount of memory allocated to the function (in MB).
Deployed Code Size Size of deployment package of the function (in MB).
The amount of time that Lambda allows a function to run before stopping it (in
Timeout
seconds).
FUNCTION DETAILS
Runtime The runtime environment for the Lambda function.
Handler The function that Lambda calls to begin executing your function.
Version The version of the Lambda function.
Last Modified Time The date and time at which the function was last modified.
SECURITY AND NETWORK DETAILS
VPC ID ID of the VPC configured..
Security Groups List of VPC security groups IDs.
Subnets List of VPC subnet IDs.
AWS Elastic Beanstalk Monitoring
AWS Elastic Beanstalk - Overview
AWS Elastic Beanstalk is an orchestration service from Amazon which is used for deploying and scaling
applications that orchestrates various AWS services like EC2, S3, Simple Notification Service (SNS), CloudWatch,
AutoScaling, and Elastic Load Balancers (ELB). With Elastic Beanstalk, you can deploy and manage applications in
the AWS cloud without having to learn about the infrastructure that is needed for those applications.
Monitored ParametersGo to the Monitors Category View by clicking the Monitors tab. Click on the Elastic Beanstalk instance available
under Amazon in the Cloud Apps section. Displayed is the Amazon Elastic Beanstalk bulk configuration view
distributed into three tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
By clicking a monitor from the list, you will be taken to the AWS Elastic Beanstalk dashboard. It has 7 tabs:
Overview
Performance
Requests
Latency
Instances
Configuration
Events
Overview
Parameter Description
ENVIRONMENT DETAILS
Status of the environment. (Aborting, Launching, Updating, LinkingFrom,LinkingTo,
Environment Status
Ready, Terminating, or Terminated)
Environment Health Shows the health status of the environment. (Ok, Info, Unknown, No data, Warning,
Status Degraded, Severe, Pending, or Suspended)
INSTANCE STATUS
Instances OK Number of instances with ''OK'' health status.
Instances Degraded Number of instances with ''Degraded'' health status.
Instances Severe Number of instances with ''Severe'' health status.
Instances Unknown Number of instances with ''Unknown'' health status.
Instances Info Number of instances with ''Info'' health status.
Instances Pending Number of instances with ''Pending'' health status.
Instances Warning Number of instances with ''Warning'' health status.
Instances No Data Number of instances with ''No Data'' health status.
INVENTORY
Number of EC2
Number of EC2 instances present in the environment.
Instances
Number of
Number of AutoScaling Groups present in the environment.
AutoScaling Groups
Number of SQS
Number of SQS Queues present in the environment.
Queues
Number of Launch
Number of Launch Configurations present in the environment.
Configurations
Number of Templates Number of Templates present in the environment.
Number of Load
Number of Load Balancers present in the environment.
Balancers
Performance
Parameter Description
CPU UTILIZATION
CPU Utilization Amount of CPU utilized by the AutoScaling Group (in percentage).
DISK I/OParameter Description
Disk Read Rate Rate at which data is read from the disk in the environment (in MB/s).
Disk Write Rate Rate at which data is written to the disk in the environment (in MB/s).
DISK I/O OPERATIONS
Disk Read Ops. Number of I/O read operations performed on the disk per second in the environment.
Disk Write Ops. Number of I/O written operations performed on the disk per second in the environment.
NETWORK TRAFFIC
Incoming Traffic Rate at which the network receives data in the environment (in MB/s).
Outgoing Traffic Rate at which the network sends data in the environment (in MB/s).
NETWORK PACKETS
Packets Received Number of packets received by the AutoScaling Group per second.
Packets Transmitted Number of packets transmitted from the AutoScaling Group per second.
Requests
Parameter Description
TOTAL REQUESTS
Requests per minute Number of requests processed per minute in the environment.
Total Requests Total number of requests completed in the environment.
RESPONSE SUMMARY
2xx Responses Number of requests completed with a 2xx code in the environment.
3xx Responses Number of requests completed with a 3xx code in the environment.
4xx Responses Number of requests completed with a 4xx code in the environment.
5xx Responses Number of requests completed with a 5xx code in the environment.
Top 5 Instances with Max Requests: Provides a graphical representation of the request details of top 5
instances with respect to maximum number of total requests in the environment.
Top 5 Instances with Error Requests: Provides a graphical representation of the request details of top 5
instances with respect to number of requests completed for various error response codes in the environment.
Instance Request Details
Instance ID Instance ID of the AWS Beanstalk instance.
Total Requests Total number of requests completed by the instance or environment.
2xx Responses Number of requests completed with a 2xx code.
3xx Responses Number of requests completed with a 3xx code.
4xx Responses Number of requests completed with a 4xx code.
5xx Responses Number of requests completed with a 5xx code.
Latency
Parameter Description
APPLICATION LATENCY
Application Latency Average time taken by the application to complete 99% of requests in the environment (in
P99 milliseconds).
Application Latency Average time taken by the application to complete 90% of requests in the environment (in
P90 milliseconds).
Application Latency Average time taken by the application to complete 75% of requests in the environment (in
P75 milliseconds).
Application Latency Average time taken by the application to complete 50% of requests in the environment (in
P50 milliseconds).
Application Latency Average time taken by the application to complete 10% of requests in the environment (in
P10 milliseconds).Parameter Description
Top 5 Instance Latency: Provides a graphical representation of the latency details of top 5 instances with
respect to various latency requests in the environment (in milliseconds).
Instance Latency Details
Instance ID Instance ID of the AWS Beanstalk instance.
Instance Latency
Average time taken by the instance to complete 99% of requests (in milliseconds).
P99
Instance Latency
Average time taken by the instance to complete 90% of requests (in milliseconds).
P90
Instance Latency
Average time taken by the instance to complete 75% of requests (in milliseconds).
P75
Instance Latency
Average time taken by the instance to complete 50% of requests (in milliseconds).
P50
Instance Latency
Average time taken by the instance to complete 10% of requests (in milliseconds).
P10
Instances
Parameter Description
CPU Usage of Instances: Provides a graphical representation of the CPU Usage of Instances with respect to
various time details such as User Time and Idle Time in the environment (in percentage).
High Disk Usage of Instances: Provides a graphical representation of the Disk Usage of Instances with
maximum Used Storage in the environment (in percentage).
High Avg. Load of Instances (1 min): Provides a graphical representation of the Avg. Load of Instances with
maximum CPU load over the last 1 minute in the environment.
High Avg. Load of Instances (5 min): Provides a graphical representation of the Avg. Load of Instances with
maximum CPU load over the last 5 minutes in the environment.
Linux Instance Performance Details
Instance ID Instance ID of the Linux EC2 instance in the environment.
Health status of the Linux EC2 instance in the environment. Possible values are:
0 - OK
1 - Info
Instance 5 - Unknown
Health 10 - No data
15 - Warning
20 - Degraded
25 - Severe
Average Load
Average CPU load over the last one minute in the instance.
(1 min)
Average Load
Average CPU load over the last five minutes in the instance.
(5 min)
Disk Usage Amount of disk space utilized by the instance in the instance (in percentage).
Amount of time spent by the CPU to execute user level processes in the instance (in
User Time
percentage).
Amount of time spent by the CPU to execute system (Kernel) level processes in the instance (in
System Time
percentage).
Amount of time for which the CPU is waiting for a process to complete in the instance (in
I/O Wait Time
percentage).
Idle Time Amount of time for which the CPU is in idle state in the instance (in percentage).
Windows Instance Performance Details
Instance ID Instance ID of the Windows EC2 instance in the environment.Parameter Description
Health status of the Windows EC2 instance in the environment. Possible values are:
0 - OK
1 - Info
Instance 5 - Unknown
Health 10 - No data
15 - Warning
20 - Degraded
25 - Severe
Amount of time spent by the CPU to execute user level processes in the instance (in
User Time
percentage).
Idle Time Amount of time for which the CPU is in idle state in the instance (in percentage).
Amount of time (Privileged Time) for which the CPU has spent in Kernel mode over the last
System Time
minute in the instance (in percentage).
Configuration
Parameter Description
ENVIRONMENT DETAILS
Environment
ID of the current environment.
ID
Region Code The AWS region where the environment is running.
Tier Name Name of the tier. Indicates whether it is a WebServer or a Worker environment.
LoadBalancer
Name of the Load Balancer.
Name
Abortable
Indicates whether there is an in-progress configuration update or application version
Option In
deployment.
Progress
Application
Name of the application where the environment is deployed.
Name
Version Name Version of the application that is deployed in the environment.
Solution Stack
Name of the web server, operating system and architecture.
Name
Description Description of the environment.
Indicates the Endpoint URL of the environment. For load-balanced environment, it is the URL of
Endpoint URL
the load-balancer. For Single instance environment, it is the IP address of the instance.
Environment
Amazon Resource Name (ARN) of the environment.
ARN
Platform ARN Amazon Resource Name (ARN) of the platform.
Template
Name of the configuration template used to launch the environment, if any.
Name
Environment
Date and Time at which the environment was created.
Created Time
Environment
Date and Time at which the environment was modified.
Updated Time
AUTOSCALING GROUP DETAILS
Autoscaling
Name of the AutoScaling Group.
Group Name
Autoscaling
Amazon Resource Name (ARN) of the AutoScaling Group.
Group ARN
Health Check
Service used for the health checks. Possible values are EC2 and ELB.
TypeParameter Description
Launch
Configuration Name of the associated Launch Configuration.
Name
VPC Zone
List of VPC subnet IDs separated by commas.
Identifier
Service
Amazon Resource Name (ARN) of the service-linked role that the Auto Scaling group uses to call
Linked Role
other AWS services.
ARN
Availability
List of availability zones for the group.
Zones
Autoscaling
Date and time at which AutoScaling Group was created.
Created Time
Default
Duration of the default cooldown period (in seconds).
Cooldown
Desired
The desired size of the group.
Capacity
HealthCheck The amount of time (in seconds) that Amazon EC2 Auto Scaling waits before checking the health
Grace Period status of an EC2 instance that has come into service.
Maximum
The maximum number of instances available in the group.
Instances
Minimum
The minimum number of instances available in the group.
Instances
Events
This tab displays the list of the most recent events that have occurred in the environment and its resources.
Parameter Description
Event Details
Generated Time Date and time at which the event was generated.
Status Severity status of the event. (TRACE, DEBUG, INFO, WARN, ERROR, or FATAL)
Message Indicates the message shown for the event.
Note:
Metrics under ''Events'' tab are mapped under Admin → Performance Polling.
By default, number of events fetched in the table after every poll interval is 20. However, it can be
modified by specifying the value in ''Number of events to fetch'' textbox found under Admin →
Performance Polling → Optimize Data Collection.
AWS ECS Monitoring
AWS ECS - Overview
Amazon Elastic Container Service (Amazon ECS) is a highly scalable, fast, container management service that
makes it easy to run, stop, and manage Docker containers on a cluster. Amazon ECS lets you launch and stop
container-based applications with simple API calls, allows you to get the state of your cluster from a centralized
service, and gives you access to many familiar Amazon EC2 features.
Creating a new monitor
To learn how to create a new ECS monitor, refer here.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the ECS available under Amazon in the
Cloud Apps section. Displayed is the Amazon ECS bulk configuration view distributed into three tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.Performance tab gives the health status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
By clicking a monitor from the list, you''ll be taken to the AWS ECS dashboard. It has 5 tabs:
Overview
Cluster Performance
Tasks
Services
Container Instances
Overview
Parameter Description
CLUSTER INFORMATION
Name Name of the cluster.
The status of the cluster. (ACTIVE, PROVISIONING, DEPROVISIONING, FAILED,
Status
INACTIVE)
Cluster ARN The Amazon Resource Name (ARN) that identifies the cluster.
Registered Container
The number of containers instances registered to the cluster.
Instances
CLUSTER TASKS
Running Tasks The number of tasks that are in RUNNING state.
Pending Tasks The number of tasks that are in PENDING state.
Running EC2 Tasks The number of EC2 tasks that are in RUNNING state.
Pending EC2 Tasks The number of EC2 tasks that are in PENDING state.
Running Fargate Tasks The number of Fargate tasks that are in RUNNING state.
Pending Fargate Tasks The number of Fargate tasks that are in PENDING state.
CLUSTER SERVICES
Active Services The number of active services running in the cluster.
Active EC2 Services The number of EC2 services that are running on the cluster in an ACTIVE state.
Draining EC2 Services The number of EC2 services that are in DRAINING state.
Active Fargate Services The number of Fargate services that are running on the cluster in an ACTIVE state.
Draining Fargate Services The number of Fargate services that are in DRAINING state.
Cluster Performance
Parameter Description
CPU
CPU
Amount of CPU units that are reserved by running tasks in the cluster (in percentage).
Reservation
CPU
Amount of CPU units that are used in the cluster (in percentage).
Utilization
MEMORY
Memory
Amount of memory that is reserved by running tasks in the cluster (in percentage).
Reservation
Memory
Amount of memory that is used in the cluster (in percentage).
Utilization
CPU USAGE
CPU The CPU units reserved by tasks in the cluster. This metric is collected only for tasks that have a
Reserved defined CPU reservation in their task definition.
The CPU units used by tasks in the cluster. This metric is collected only for tasks that have a
CPU Utilized
defined CPU reservation in their container definition.Parameter Description
MEMORY USAGE
Memory
Amount of memory that is reserved by tasks in the cluster (in GB).
Reserved
Memory
Amount of memory being used by tasks in the cluster (in GB).
Utilized
DISK I/O THROUGHPUT
Storage
Rate at which data is read from storage in the cluster (in kB/s).
Read Rate
Storage
Rate at which data is written from storage in the cluster (in kB/s).
Write Rate
CLUSTER NETWORK I/O
Data
Transmit Rate at which data is transmitted by the cluster (in kB/s).
Rate
Data Receive
Rate at which data is received by the cluster (in kB/s).
Rate
Tasks
Parameter Description
Task Details
Task ID The unique identifier for the task.
The health status for the task, which is determined by the health of the essential containers in the
Health Status
task. (HEALTHY, UNHEALTHY, UNKNOWN)
The last known status of the task. (PROVISIONING, PENDING, ACTIVATING, RUNNING,
Last Status
DEACTIVATING, DEPROVISIONING, STOPPED)
Desired Status Displays the desired status of the task.
Launch Type The launch type on which you task is running. (EC2 or Fargate)
Connectivity The connectivity status of a task. (CONNECTED or DISCONNECTED)
Connectivity
Shows the time stamp for when the task went to CONNECTED state.
At
Configured
Shows the number of CPU units used by the task.
CPU Units
Configured
Displays the amount of memory used by the task (in MB).
Memory
Number of
Number of containers in which the task is running.
Containers
Task Info
Task ID The unique identifier for the task.
Container
The unique identifier for the container instance.
Instance ID
Task Group The name of the task group associated with your task.
Task
The full description of the task definition.
Definition
Created At Shows the time stamp for when the task was created.
Started At Shows the time stamp for when the task was started.
Started By Shows the tag specified when a task is started.
Services
Parameter Description
Service StatusParameter Description
Service
The name of the service.
Name
Status The status of the service. (ACTIVE, DRAINING, INACTIVE)
CPU
The percentage of CPU units that are used in the service.
Utilization
Memory
The percentage of memory that are used in the service.
Utilization
Pending
The number of tasks in the service that are in the PENDING state.
Tasks
Running
The number of tasks in the service that are in the RUNNING state.
Tasks
Desired
The desired number of instantiations of the task definition to keep running on the service.
Tasks
Launch Type The launch type on which your service is running. (EC2 or FARGATE)
Scheduling
The scheduling strategy to use for the service. (REPLICA or DAEMON)
Strategy
Service Insights
Service
The name of the service.
Name
CPU The CPU units reserved by tasks in the service. This metric is collected only for tasks that have a
Reserved defined CPU reservation in their task definition.
The CPU units used by tasks in the service. This metric is collected only for tasks that have a
CPU Utilized
defined CPU reservation in their container definition.
Memory
The memory that is reserved by tasks in the service (in GB).
Reserved
Memory
The memory being used by tasks in the service (in GB).
Utilized
Storage
Rate at which data is read from storage in the service (in kB/s).
Read Rate
Storage
Rate at which data is written from storage in the service (in kB/s).
Write Rate
Data
Transmit Rate at which data is transmitted by the service (in kB/s).
Rate
Data Receive
Rate at which data is received by the service (in kB/s).
Rate
TaskSet
The number of task sets in the service.
Count
Service Details
Service
The name of the service.
Name
Task
The task definition to use for tasks in the service.
Definition
Platform
The platform version on which to run your service.
Version
Created At The timestamp for when the service was created.
Created By The principal that created the service.
Service Events
Event ID Indicates the ID for the event.
Service
Name of the service.
Name
Generated
Date and time at which the event was generated.
Time
Message The message shown for the event.Container Instances
Parameter Description
CPU
Instance CPU
The percentage of CPU currently being reserved on a single EC2 instance in the cluster.
Reserved Capacity
Instance CPU
The total percentage of CPU units being used on a single EC2 instance in the cluster.
Utilization
MEMORY
Instance Memory
The percentage of memory currently being reserved on a single EC2 instance in the cluster.
Reserved Capacity
Instance Memory
The total percentage of memory being used on a single EC2 instance in the cluster.
Utilization
CPU USAGE
Instance CPU Used Amount of CPU units being used on a single EC2 instance in the cluster.
Instance CPU
Amount of CPU units remaining after use on a single EC2 instance in the cluster.
Remaining
Instance CPU Limit Maximum amount of CPU units that can be assigned to a single EC2 instance in the cluster.
MEMORY
Instance Memory
Amount of memory being used on a single EC2 instance in the cluster (in GB).
Used
Instance Memory
Amount of memory remaining after use on a single EC2 instance in the cluster (in GB).
Remaining
Instance Memory Maximum amount of memory that can be assigned to a single EC2 instance in the cluster (in
Limit GB).
FILESYSTEM UTILIZATION
Instance
Total amount of file system capacity being used on a single EC2 instance in the cluster (in
FileSystem
percentage).
Utilization
NETWORK USAGE
Instance Network Rate at which data is sent and received over the network on a single EC2 instance in the
Traffic Rate cluster (in kB/s).
Container Instances
Container Instance
The ID of the container instance.
ID
The status of the container instance. (REGISTERING, REGISTRATION_FAILED, ACTIVE,
Status
INACTIVE, DEREGISTERING, DRAINING)
Running Tasks Number of tasks that are in RUNNING state per container instance.
Pending Tasks Number of tasks that are in PENDING state per container instance.
The version counter for the container instance. Every time a container instance experiences
Version
a change that triggers a CloudWatch event, the version counter is incremented.
Agent Version The version number of the Amazon ECS container agent.
Agent Connected Indicates whether the agent is connected to Amazon ECS. (True or False)
Instance ID The EC2 instance ID of the container instance.
Registered At The timestamp for when the container instance was registered.
Container Instances Insights
Container Instance
The ID of the container instance.
ID
Memory Reserved
Amount of memory currently being reserved on the instance (in percentage).
Capacity
Memory Utilization Amount of memory currently being used on the instance (in percentage).
CPU Reserved
Amount of CPU currently being reserved on the instance (in percentage).
CapacityParameter Description
CPU Utilization Amount of CPU currently being used on the instance (in percentage).
FileSystem
Amount of file system capacity being used on the instance (in percentage).
Utilization
Network Traffic
Rate at which data is sent and received over the network on the instance (in kB/s).
Rate
Instances Resource Details
Container Instance
The unique identifier for the container instance.
ID
Available CPU Amount of CPU units available to allocate tasks.
Available Memory Amount of memory available to allocate tasks (in MB).
Reserved Ports The ports that were reserved by the Amazon ECS container agent.
Amazon EKS Monitoring
Overview
Amazon Elastic Kubernetes Service (EKS) is a managed Kubernetes service that facilitates smooth running of
Kubernetes on both AWS and on-premises. EKS is integrated with many AWS services to provide scalability and
security and helps guarantee high availability of your clusters and its resources across numerous availability
zones. There is no need to install, operate and maintain our own Kubernetes control plane or node.
Creating a new monitor
Prerequisites for monitoring Amazon EKS metrics: Click here
To learn how to create a new EKS monitor, refer here.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the EKS instance available under
Amazon in the Cloud Apps section. Displayed is the Amazon EKS bulk configuration view distributed into three
tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
By clicking a monitor from the list, you''ll be taken to the Amazon EKS monitor dashboard. It has 6 tabs:
Overview
Node
Pods
Services
Persistent Volumes
Service Map
Note:
Metrics marked with * are collected from Container Insights.
If a node is not in the ''Ready'' state, the availability of the monitor will be automatically affected. Also, the
health of the node in the monitor is dependent on the following parameters by default and alerts can be
configured for the same under Admin → Performance Polling → Optimize Data Collection → Elastic
Kubernetes Service:
Memory Pressure
Disk Pressure
PID pressure
Out of Disk
Network UnavailableOverview
Parameter Description
CLUSTER INFORMATION
Status Current status of the cluster. (CREATING, ACTIVE, DELETING, FAILED, UPDATING)
Cluster ARN The Amazon Resource Name (ARN) of the cluster.
Cluster
The endpoint for your Kubernetes API server.
Endpoint
NAMESPACE DETAILS
Namespace
Name of the namespace
Name
Running pods
in namespace Number of running pods under the namespace.
*
Resource
The version number of the namespace.
Version
Namespace
Availability of the Namespace
Availability
Namespace
Timestamp at which the Namespace was created
Created Time
PODS
Used Pods % Percentage of the number of pods used.
Used Pods Number of pods used.
Maximum
Maximum number of pods available.
Pods
Top 5 Nodes by Used Pods - Displays a graphical representation of top 5 nodes with respect to the number of
pods used.
CLUSTER USAGE DETAILS
Average
Cluster CPU Average amount of CPU used by the cluster (in percentage).
Usage
Average
Cluster
Average amount of memory used by the cluster (in percentage).
Memory
Usage
NODE DETAILS
Master Nodes Number of master nodes available.
Worker
Number of worker nodes available.
Nodess
Failed Nodes
Number of nodes that have failed.
*
CLUSTER DETAILS
Git Version Git version of the cluster.
Build Date Build date of the cluster.
Compiler Name of the compiler used.
Platform OS Platform of the cluster.
COMPONENT DETAILS
Component
Name of the component.
Name
Availability Availability status of the component.
NODE GROUP DETAILS
Node group
The name associated with an Amazon EKS managed node group.
NameParameter Description
Node group The current status of the managed node group. (CREATING, ACTIVE, UPDATING, DELETING,
Status CREATE_FAILED, DELETE_FAILED, DEGRADED)
Kubernetes
The Kubernetes version of the managed node group.
Version
Release
AMI ID in launch template (OR) EKS version of the optimized AMI.
Version
Minimum
The minimum number of nodes that the managed node group can scale into.
Node Size
Maximum
The maximum number of nodes that the managed node group can scale out to.
Node Size
Desired Node
The desired number of nodes that the managed node group should maintain.
Size
If the node group wasn''t deployed with a launch template, then this is the instance type that is
Instance
associated with the node group. If the node group was deployed with a launch template, then
Types
this is null.
Created At The timestamp when the node group was created.
FARGATE PROFILE DETAILS
Fargate
The name of the Fargate profile.
Profile Name
Fargate The current status of the Fargate profile. (CREATING, ACTIVE, DELETING, CREATE_FAILED,
Profile Status DELETE_FAILED)
Created At The timestamp when fargate profile was created.
Subnets The IDs of subnets to launch pods into.
Node
Parameter Description
Top 5 Nodes by Memory Details - Displays a graphical representation of top 5 nodes with respect to their
corresponding memory details (in percentage).
Top 5 Nodes by CPU Details - Displays a graphical representation of top 5 nodes with respect to their
corresponding CPU details (in percentage).
Node Usage Details
Node Name Name of the node
Allocatable Memory The CPU resources of a node that are available for scheduling (in GiB).
Memory Limit The maximum limit of memory resource which can be used (in percentage).
Memory Request Number of memory requests (in percentage).
Allocatable CPU The number of CPU processes that are available.
CPU Limit The maximum limit of CPU resource which can be used (in percentage).
CPU Request Number of CPU requests (in percentage).
The total number of data transmitted and received over the network per node in a
Network Total Usage *
cluster (in kB/s).
The total amount of file system capacity being used on nodes in the cluster (in
File System Usage *
percentage).
Running containers in
The number of running containers per node in a cluster.
node *
Node Pod Details
Node Name Name of the pod
Displays a graphical representation of the total number of pods available with used
Pod Usage
and free pods split-up.
Kube-system Pod Count Number of Kube state pods.
Non-Kube-system Pod
Number of non-Kube state pods.
Count
Image Number of images present in the node.Parameter Description
Used Pods Total num of pods present in Kubernetes.
Allocatable Pods Number of pods that are available.
NODE DETAILS
Node Name Name of the node
Instance ID EC2 Instance ID of the node.
OS Image OS Image name of the node.
OS Name of the OS in which the container is deployed.
Architecture Architecture details of the node.
Type Type of node used.
Kubelet Version The version of Kubelet used.
Allocatable Ephemeral
Size of temporary memory available (in GiB).
Storage
Created Time Timestamp at which the node was created.
Pods
Parameter Description
POD DETAILS
Pod UUID Universal unique ID of the pod.
Pod Name Name of the pod
Pod Namespace Namespace in which the pod resides.
Pod Node Name Name of the pod-node.
Pod Application Name of the pod application.
Pod Type Type of pod used.
Pod created Medium by which the pod was created.
Pod Status Status of the pod. (Pending, Running, Succeeded, Failed, or Unknown)
Pod Start Time Timestamp at which the pod was started.
Pod Created Time Timestamp at which the pod was created.
Top 10 Pods by Memory Details - Displays a graphical representation of top 10 pods with respect to their
corresponding memory details (in percentage).
Top 10 Pods by CPU Details - Displays a graphical representation of top 10 pods with respect to their
corresponding CPU details (in percentage).
POD USAGE DETAILS
Pod UUID Universal unique ID of the pod.
Pod Name Name of the pod.
Number of Containers The number of containers run by the pod.
Pod CPU Limit The maximum limit of CPU resource which can be used (in percentage).
Pod CPU Request The number of CPU requests by pod (in percentage).
Pod Memory Limit The maximum limit of memory resource that can be used (in percentage).
Pod Memory Request The number of memory requested (in percentage).
Pod created Medium by which the pod was created.
Network Transmitted
Amount of data being transmitted over the network by the pod (in kB/s).
Bytes *
Network Received Bytes * Amount of data being received over the network by the pod (in kB/s).
Pod Persistent Volumes
Name of the Claim through which a pod can access the persistent volume.
Claim
CONTAINER DETAILS
Container ID ID of the container.
Container Name Name of the container.Parameter Description
Container Image Name of the container image.
Container Pod Name Name of the container pod.
Container Restarts The number of times the container has restarted.
Status of the container. Following are the list of possible values that are shown for
each status:
Status Value
Running Running
ContainerCreating
CrashLoopBackOff
ErrImagePull
Waiting ImagePullBackOff
Container Status CreateContainerConfigError
InvalidImageName
CreateContainerError
OOMKilled
Error
Terminated Completed
ContainerCannotRun
DeadlineExceeded
Container Start Time Timestamp at which the container was started.
Services
Parameter Description
SERVICE DETAILS
Service UUID Universal unique ID of the service.
Service Name Name of the service.
Service Namespace Name of the Namespace in which the service resides.
Application Name of the service application.
Service Type Type of the service.
Service Protocol Name of the service protocol.
Host IP Address IP address of the service host.
Service Target Port Name of the port that connects with the service.
Running pods in service * The number of pods running the service or services in the cluster.
Created Time Timestamp at which the service was created.
DEPLOYMENT DETAILS
Deployment UUID Universal unique ID of the deployment.
Deployment Name Name of the deployment.
Deployment Namespace Namespace where the deployment exists.
Deployment Replicas The number of replicas in a deployment.
Deployment Available Replicas Number of available replicas in a deployment.
Deployment Availability Availability of the deployment.
Persistent Volumes
Parameter Description
PERSISTENT VOLUMES (PV) DETAILSParameter Description
PV Name Name of the Persistent Volume.
PV Status Status of the Persistent Volume. (Available, Bound, Released, Failed, or Pending)
PV Claim Name of the Persistent Volume Claim.
PV Access Mode The mode through which you can access the Persistent Volume.
PV Storage Class Name of the Persistent Volume storage class.
PV Capacity The capacity of the Persistent Volume (in GiB).
PV Created Time Timestamp at which the Persistent Volume was created.
PERSISTENT VOLUMES CLAIM (PVC) DETAILS
PVC UUID Universal unique ID of the persistent volume.
PVC Name Name of the Persistent Volume Claim.
PVC Namespace Name of the Namespace in which the Claim exists.
PVC Status Status of the Persistent Volume Claim. (Available, Bound, Released, Failed, or Pending)
PV Name Name of the Persistent Volume.
PVC Access Mode The mode through which you can access the Persistent Volume Claim.
PVC Storage Class Name of the Persistent Volume storage class.
PVC Requests Number of Persistent Volume Claim requests (in GiB).
PVC Created Time Timestamp at which the Persistent Volume Claim was created.
Service Map
Displays a graphical map view containing namespace and service details.
All the namespace with its status and running pods count will be seen inside cluster circle.
Green color indicates that the namespace is UP and red color indicates it is DOWN.
Under the cluster services under a namespace can be seen as tree.
Each service contains, its host IP, port and number of running pods.
Microsoft Azure Monitoring
Microsoft Azure - An Overview
Monitoring Microsoft Azure - What we do
Creating a new Azure Monitor
Monitored Parameters
FAQs and Troubleshooting
Microsoft Azure - An OverviewMicrosoft Azure, formerly known as Windows Azure, is Microsoft''s public cloud computing platform. It provides a
range of cloud services, including those for compute, analytics, storage and networking. Users can pick and
choose from these services to develop and scale new applications, or run existing applications, in the public
cloud.
Monitoring Microsoft Azure - What we do
Applications Manager''s Microsoft Azure monitor enables users to discover Virtual machines under an Azure
subscription and monitors them. With Azure Storage Monitoring, you can monitor the health and performance of
your Storage accounts for better managing and utilizing our Azure hosted storage resources, Azure SQL DB
monitoring for keeping track of Azure SQL DB performance metrics and query statistics, Azure Service Bus
monitoring to monitor the performance of the service bus, and Azure Kubernetes Service Monitoring for tracking
the health and performance of the Kubernetes clusters and their underlying components, thereby ensuring smooth
operation of your Microsoft Azure business applications overall.
Applications Manager connects with Microsoft Azure through Azure APIs to determine the health status and other
performance counters. With Microsoft Azure monitoring, you can:
Discover and monitor Azure services such as virtual machines, SQL DBs, Storage Accounts, Service Buses,
and Kubernetes services that are associated under an Azure subscription.
Find the number of VMs that are provisioned and running.
View the status and configuration information of all the discovered resources.
Collect and monitor performance metrics (CPU, Memory, Disk, Network, Thread&Process count).
Collect and monitor Disk Utilization, Disk IO statistics, Network interface details by enabling Guest OS
configuration.
In this help document, you will learn how to get started with Azure Monitoring, along with the list of parameters that
are monitored using Applications Manager.
Creating a new Microsoft Azure Monitor
Prerequisites for monitoring Azure metrics: Click here
Using the REST API to add a new Azure monitor: Click here
To create a new Microsoft Azure monitor, follow the steps given below:
Click on the New Monitor link in the Applications Manager web client.
Select ''Microsoft Azure'' under Cloud Apps category
Specify the Display Name of Microsoft Azure monitor
Enter the Subscription ID for your Microsoft Azure subscription.
Select the Azure Services you wish to discover and monitor from the drop-down menu.
Choose the Discovery mode. Following are the 3 discovery modes available:
Discovery using AD Application & Service Principal: Provide the Client ID, Tenant ID & Application key
that were obtained in the above mentioned prerequisite step in the New monitor page. Refer
Prerequisites section.
Discovery using Azure Organizational Account (Powershell): Provide the User email & Password fields
in New monitor page with the Username & Password of the created Organizational account. Refer
Prerequisites section.
Discovery using OAuth: Use the OAuth Provider that was obtained in the prerequisite step in the New
monitor page. Refer Prerequisites section.
Specify the polling interval in minutes and timeout in seconds
Choose the Monitor Group from the combo box with which you want to associate Microsoft Azure monitor
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers Microsoft Azure from the network and starts monitoring them.
Note:
Azure resources deployed using ''Azure Resource Manager (ARM)'' model will be monitored by Applications
Manager. Azure Resources deployed using Classic model are not supported.
Make sure you have a working internet connection to add or fetch data from the cloud services.
If your environment requires the use of a proxy server to access external Websites, you can configure the
proxy settings under the ''Admin'' tab.
Monitored ParametersGo to the Monitors Category View by clicking the Monitors tab. Click on Microsoft Azure under the Cloud
Apps table. Displayed is the Microsoft Azure bulk configuration view distributed into three tabs:
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Microsoft Azure monitor provides a brief detail of the Azure virtual machines under the given subscription. Click on
the monitor name to see all the server details listed under the following tabs:
Monitor Information
Overview
Virtual Machines
Storage Accounts
Azure SQL Databases
Azure Service Buses
Kubernetes Service
Monitor Information
Parameter Description
Name Name of the Microsoft Azure monitor
Subscription ID Subscription ID of the Azure subscription
Azure Services The services that are monitored under this subscription
Discovery Mode The discovery mode chosen while creating the monitor
User Email The organizational account used to access Azure resources
Client ID Client ID of the Active Directory Application
Tenant ID Tenant ID of the Active Directory
OAuth Provider Name of the OAuth provider.
Timeout Timeout Duration (seconds)
Associated Groups The monitor groups to which this monitor is associated
Last Polled at Specifies the time at which the last poll was performed
Next Poll at Specifies the time at which the next poll is schedule
Overview
Parameter Description
Total Azure Virtual Machines Provisioned Total number of virtual machines under this subscription.
Total Azure Virtual Machines Running Total number of virtual machines in running state.
Azure Standard Storage Accounts Number of standard storage accounts available.
Azure Premium Storage Accounts Number of premium storage accounts available.
Azure SQL Databases Number of Azure SQL database available.
Azure Service Bus Namespace Count Number of Azure Service Bus Namespaces available.
Azure Kubernetes Service Cluster count Number of Azure Kubernetes Service clusters available.
Virtual Machines
Parameter Description
Virtual Machine Name Name of the Virtual machine
Status Virtual machine''s state
Resource group name The Resource Group which has this Virtual Machine
OS Type The Operating System of the Virtual MachineParameter Description
Location The Location where the Virtual Machine is located
Public IP Address IP address of the Virtual Machine
You can perform the following admin actions on the Azure virtual machines (VMs):
Delete: Deletes the Azure VMs from Applications Manager.
Start Virtual Machines: Option to start the Azure VMs from Applications Manager.
Stop Virtual Machines: Option to stop Azure VMs from Applications Manager.
Restart Virtual Machines: Option to restart Azure VMs from within Applications Manager.
By clicking over the Virtual Machine name, you will be redirected to the Azure Virtual Machine monitoring
dashboard.
Storage Accounts
Parameter Description
Azure Standard Storage Accounts
Storage Account
The Azure Storage Account Name.
Name
Provisioning state of Storage Account. Possible values :
Invalid
Creating
Provisioning State Deleting
Succeeded
Failed
Cancelled
Resource Group Resource Group where the Storage Account is allocated in.
Location Region where the storage account is provisioned
Status of Storage Account. Possible Values:
Primary Status Available
Unavailable
The replication type used by the Storage account. Possible values:
Standard_LRS
Standard_GRS
Replication Type
Standard_RAGRS
Standard_ZRS
Premium_LRS
Azure Premium Storage Accounts
Premium Storage
The Azure Premium Storage Account Name.
Account Name
Provisioning state of Premium Storage Account. Possible values : Invalid, Creating,
Provisioning State
Deleting, Succeeded, Failed, Cancelled.
Resource Group Resource Group where the Premium Storage Account is allocated in.
Location Region where the Premium Storage Account is provisioned.
Status Status of Premium Storage Account. Possible Values: Available, Unavailable.
By clicking over the Azure Standard Storage Account name, you will be redirected to the Azure Storage
monitoring dashboard.
Azure SQL Databases
Parameter DescriptionParameter Description
Azure SQL Databases
Database Name Name of the Azure SQL Database.
Database Status Status of the Azure SQL database.
Database Server Name of the SQL server.
Resource Group Name Name of the resource group to which the SQL database is associated.
Database Usage Amount of space currently used in the database (in GB).
Database Location Location of the SQL database
Total Database Size Total amount of space allocated to the SQL database (in GB).
By clicking over the database name, you will be redirected to the Azure SQL database monitoring dashboard.
Azure Service Buses
Parameter Description
Azure Service Buses
Namespace Name of the Service Bus Namespace.
Status Status of the Service Bus Namespace.
Tier Indicates the tier used by the Service Bus Namespace.
Location Indicates the location/region of the Service Bus Namespace.
Resource Group Specifies the Resource Group of the Service Bus Namespace.
By clicking over the database name, you will be redirected to the Azure Service Bus monitoring dashboard.
Kubernetes Service
Parameter Description
Kubernetes Clusters
Cluster Name Name of the Kubernetes cluster.
Cluster Status Status of the Kubernetes cluster. (Running or Stopped)
Cluster Location Indicates the location/region of the Kubernetes cluster.
Resource Group Name Specifies the Resource Group of the Kubernetes cluster.
By clicking over the cluster name, you will be redirected to the Azure Kubernetes Service monitoring dashboard.
FAQs and Troubleshooting
Error Messages and how to troubleshoot them:
1. Error: "Authentication Failed. Access is denied for the provided Azure Organizational Account Credentials"
This error message is displayed upon adding a New Azure monitor using Azure Organizational Account mode. For
troubleshooting steps, refer this link.
2. Error: "Azure Services discovery failed for subscription . Invalid Application key"
This error message is displayed upon editing a new Azure monitor using Azure Organizational Account/AD
Application & Service Principal mode. For troubleshooting steps, refer to the below link for respective modes:
Azure Organizational Account mode
AD Application & Service Principal mode
3. Error: "Connection to the database failed with error: Cannot open server requested by the
login. Client with IP address is not allowed to access the server. To enable access, use the Windows
Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this
IP address or address range"
This error message is displayed in the monitor details page/Edit monitor page of Azure SQL Database monitor. For
troubleshooting steps, refer this link.4. Error: "Connection to the database failed with error: The TCP/IP connection to the host ,
port 1433 has failed.
[OR]
Error: "Connection timed out: no further information. Verify the connection properties. Make sure that an
instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that
TCP connections to the port are not blocked by a firewall."
This error message is displayed in the monitor details page/Edit monitor page of Azure SQL Database monitor. For
troubleshooting steps, refer this link.
For more troubleshooting steps on Microsoft Azure monitoring, refer our FAQs.
Azure Virtual Machines
Azure virtual machines are monitored based on the parameters or the attributes listed below. These attributes
provide information about the functioning of Azure Virtual machines. You can also configure thresholds to the
numerical attributes based on these details and get notified when the thresholds are violated.
Monitored Parameters
Prerequisites for monitoring Azure VM metrics: Click here
Go to the Monitors Category View by clicking the Monitors tab. Click on Azure Virtual Machines under
the Cloud Apps section. Displayed is the Azure Virtual Machine bulk configuration view distributed into three tabs:
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the server details listed under the following tabs:
Note:
Data collection for the following metrics is done via the following methods:
Metrics to be Data collection method Required Privileges
monitored
Azure monitor Via Azure APIs ---
Diagnostic Extension should be enabled
Diagnostic
Via Storage Table APIs for the virtual machine. (Windows and
Extension
Linux)
Guest OS Via PowerShell scripts PowerShell remoting should be enabled.
Guest OS metrics will be available only for Windows installations of Applications Manager for Windows
VMs alone.
Windows Virtual Machines - Monitored Metrics
Monitor Information
Overview
CPU
Memory
Disk
Network
Threads & Processes
Services
Configuration
Linux Virtual Machines - Monitored Metrics
Overview
CPUMemory
Disk
Configuration
Windows Virtual Machines - Monitored Metrics
Monitor Information
Parameter Description
Name Display name of the Virtual machine
Subscription ID Subscription ID of the Azure subscription which contains this VM
Virtual Machine name Name of the Virtual machine
Virtual Machine Resource ID Resource ID of the Virtual machine
Enable Guest OS monitoring Indicates whether Guest OS monitoring is enabled for the monitor.
Username VM''s username
Timeout Timeout Duration (seconds)
Associated groups The monitor groups to which this monitor is associated
Last polled at Specifies the time at which the last poll was performed
Next poll at Specifies the time at which the next poll is scheduled
Overview
Parameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
CPU UTILIZATION
Amount of CPU
CPU utilized by the
Utilization virtual machine
(in %).
MEMORY UTILIZATION
Amount of
memory
Memory
utilized by the
Utilization
virtual machine
(in %).
CPU CREDITS (Applicable only for B-series virtual machines)
Number of
CPU credits
Credits consumed by
Consumed the virtual
machine
Remaining
number of
CPU
credits
Credits
available for
Remaining
the virtual
machine.
CPU
Parameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
PROCESSOR METRICSParameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
Amount of time for which the
Privileged
processor was running in
Time
privileged mode (in %).
Amount of time for which the
User Time processor was running in user
mode (in %).
Processor Number of times the processor
Frequency is in running state.
Memory
Parameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
MEMORY (COMMITTED vs AVAILABLE)
Committed Amount of commited Virtual
Bytes Memory (in MB).
Available Amount of available Physical
Bytes Memory (in MB).
Committed Ratio of Committed Bytes to
Bytes In the Commit Limit (in
Use percentage).
POOL (PAGED vs NONPAGED)
Pool Paged
Size of the paged pool (in MB).
Bytes
Pool Size of physical memory that
Nonpaged cannot be written to disk
Bytes though it is not in use (in MB).
MEMORY FAULTS
Page Number of page faults per
Faults/sec second.
Disk
Parameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
READ THROUGHPUT
Amount of data read from
OS Disk Read
OS disk during monitoring
Throughput
period (in kB/s).
Data Disk Amount of data read from
Read data disk during monitoring
Throughput period (in kB/s).
WRITE THROUGHPUT
Amount of data written to
OS Disk Write
OS disk during monitoring
Throughput
period (in kB/s).
Data Disk Amount of data written to
Write data disk during monitoring
Throughput period (in kB/s).
DISK I/O OPS
Disk Read Number of disk read IOPS
Ops (in Ops/sec).
Disk Write Number of disk write IOPS
Ops (in Ops/sec).Parameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
DISK UTILIZATION
Disk Disk Partition
Disk Free space & Used
Disk Usage
space
Total Size
Total disk size
(MB)
Used disk space as
Used (%)
percentage
Used (MB) Used disk space
Free disk space as
Free (%)
percentage
Free (MB) Free disk space
DISK IO STATISTICS
Disk Disk partition
The number of read/write
Transfers/Sec operations on the disk that
occur each second
The percentage of elapsed
time that the disk drive was
Writes/sec
busy servicing write
requests
The percentage of elapsed
time that the disk drive was
Reads/Sec
busy servicing read
requests
The percentage of time the
% Busy Time
disk was busy
The average number of both
Average read and write requests that
queue length were queued for the disk
during the sample interval
DISK SPACING
Disk Name Name of the hard disk
Disk Size Total size of the disk
Network
Parameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
NETWORK TRAFFIC
Amount of data
received on all
network
Incoming
interfaces by
Traffic
the virtual
machine (in
kB/min).
Amount of data
transmitted
from all
Outgoing network
Traffic interfaces by
the virtual
machine (in
kB/min).Parameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
NETWORK INTERFACE
The name of
Network
the network
Interface
interface
The estimate of
Speed the current
(MB/s) bandwidth in
MB/s
The rate at
which packets
Input
are received on
traffic
the interface, in
(kB/s)
kilo bytes per
second.
Input
Input traffic
Utilization
percentage
(%)
The rate at
which packets
Output
are sent on the
traffic
interface, in
(kB/s)
kilo bytes per
second.
Output
Output traffic
Utilization
percentage
(%)
Number of
Inbound packets that
Errors could not be
received
Number of
Outbound packets that
Errors could not be
sent
Threads & Processes
Parameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
THREAD STATS
Thread
The total number of threads.
Count
Context The total number of context
switches/sec switches per second.
PROCESS STATS
Process The total number of
count processes.
HANDLES
Handle count The total number of handles
Services
Parameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
Service DetailsParameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
Service
Name of the service.
Name
Display Display name of the service set
Name by the user.
Status of the service. (Running,
Paused, Stopped,
Status StartPending, PausePending,
ContinuePending, or
StopPending)
Indicates the mode with which
Start
the service was started. (Auto
Mode
or Manual)
You can also add a new service by clicking over the ''Add New Service'' link.
Configuration
Parameter Description
SYSTEM INFORMATION
Resource Name Complete resource name of the virtual machine.
Resource ID Virtual machine resource ID
Status State of the VM
Resource Group Name The resource group which has this VM
VM Size Size of the VM
Location Location at which the VM is set up
Computer Name Name of the virtual machine.
Public IP Address Public IP of the VM
Private IP Address Private IP of the VM
OS INFORMATION
OS Type VM''s Operating system
VM Image VM server configuration
NETWORK INTERFACE
Network Interface Name The name of the network interface
Network Interface ID The ID of the network interface
MAC Address MAC address of the network
Network security group ID Network security group of the network interface
Linux Virtual Machines - Monitored Metrics
The below mentioned metrics are monitored for Linux VM:
Overview
Parameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
CPU UTILIZATION
Amount of CPU
CPU utilized by the
Utilization virtual machine
(in %).
CPU CREDITS (Applicable only for B-series virtual machines)Parameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
Number of
CPU credits
Credits consumed by
Consumed the virtual
machine
Remaining
number of
CPU
credits
Credits
available for
Remaining
the virtual
machine.
CPU
Parameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
CPU METRICS
Percentage of time that the
processor is waiting (i.e. is in
IO Wait an idle state and does
Time (%) nothing), during which there in
fact was outstanding disk I/O
requests.
Idle Time Percentage of time that the
(%) processor was idle
Percentage of time that the
Processor processor was used for
Time(Linux) processing instructions of a
(%) computer program or
operating system
Memory
Parameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
MEMORY DETAILS
Available The amount of memory
Memory available (in GB).
Used The amount of memory used
Memory (in GB).
Available Percentage of memory
Memory % available to the total memory
Used Percentage of used swap
Swap memory to the total swap
Memory % memory
Disk
Parameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
READ THROUGHPUT
Amount of
data read from
OS Disk
OS disk during
Read
monitoring
Throughput
period (in
kB/s).Parameter Description Data Collection Method
Azure Monitor Diagnostic Agent Guest OS
Amount of
data read from
Data Disk data disk
Read during
Throughput monitoring
period (in
kB/s).
WRITE THROUGHPUT
Amount of
data written to
OS Disk
OS disk during
Write
monitoring
Throughput
period (in
kB/s).
Amount of
data written to
Data Disk data disk
Write during
Throughput monitoring
period (in
kB/s).
DISK I/O OPS
Number of
Disk Read
disk read IOPS
Ops
(in Ops/sec).
Number of
Disk Write disk write
Ops IOPS (in
Ops/sec).
DISK IO LATENCY
Average time
Average
taken for a
Read Time
read operation
Average time
Average taken for a
Write time write
operation
DISK SPACING
Disk Name Name of the hard disk
Disk Size Total size of the disk
Configuration
Configuration Table lists Virtual machine details like Status, Location, IP, Network interface, MAC address and
Network Security Group.
Parameter Description
SYSTEM INFORMATION
Resource Name Complete resource name of the virtual machine.
Resource ID Virtual machine resource ID
Status State of the VM
Resource Group Name The resource group which has this VM
VM Size Size of the VM
Location Location at which the VM is set up
Computer Name Name of the virtual machine.
Public IP Address Public IP of the VMParameter Description
Private IP Address Private IP of the VM
OS INFORMATION
OS Type VM''s Operating system
VM Image VM server configuration
NETWORK INTERFACE
Network Interface Name The name of the network interface
Network Interface ID The ID of the network interface
MAC Address MAC address of the network
Network security group ID Network security group of the network interface
Microsoft Azure Storage Monitoring
Microsoft Azure Storage - An Overview
Creating a new Azure Storage Monitor
Monitored Parameters
Microsoft Azure Storage - An Overview
Azure Storage is a group of highly scalable cloud-based storage services available for applications running in
Azure cloud. Azure Storage provides facilities for storing files (File storage), files and media (Blob storage),
messages (Queue storage) and non-relational schema-less data (Table storage).
This help document enables you to understand how to get started with Azure Storage monitoring and to keep a
close watch on the numerous Azure Storage performance metric using Applications Manager''s Azure monitoring.
Creating a new Microsoft Azure Monitor
To create a new Azure Storage monitor, follow the steps given below:
Click on the New Monitor link in the Applications Manager web client.
Select ''Microsoft Azure'' under Cloud Apps category.
Specify the Display Name of Microsoft Azure monitor.
Enter the Subscription ID for your Microsoft Azure subscription.
Click the Azure Services textbox and choose Storage Accounts from the drop-down menu.
Choose the Discovery mode:
Discovery using AD Application & Service Principal: Refer Prerequisites link and provide the Client ID,
Tenant ID & Application key that were obtained in the above mentioned prerequisite step in the New
monitor page.
Discovery using Azure Organizational Account (Powershell): Refer Prerequisites link and provide the
User email & Password fields in New monitor page with the Username & Password of the created
Organizational account.
Discovery using OAuth: Use the OAuth Provider that was obtained in the prerequisite step in the New
monitor page. Refer Prerequisites section.
Specify the polling interval in minutes and timeout in seconds
Note:
Azure Storage Account Monitoring supports ZRS Storage Accounts from v15310 onwards.
Azure Premium Accounts are not supported in this monitor. However, you can view basic information for
the same in the Azure parent monitor.
Capacity metrics data is collected once in an hour and is mapped under Admin → Performance Polling.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Microsoft Azure Storage under the
Cloud Apps table. Displayed is the Microsoft Azure Storage bulk configuration view distributed into three tabs:
Availability tab gives the Availability history for the past 24 hours or 30 days.Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Microsoft Azure monitor provides a brief detail of the Azure Storage Accounts under the given subscription.
Following are the list of metrics monitored in Azure Storage Monitoring in their corresponding tabs:
Overview
Blobs
Tables
Files
Queues
Overview
Parameter Description
Storage Services Availability
The percentage of availability for the Blob storage service. Availability is
calculated by taking the TotalBillableRequest value and dividing it by the number
Blob Availability of applicable requests, including those that produced unexpected errors. All
unexpected errors result in reduced availability for the storage service or the
specified API operation.
The percentage of availability for the Table storage service.Availability is
calculated by taking the TotalBillableRequests value and dividing it by the
Table Availability number of applicable requests, including those that produced unexpected errors.
All unexpected errors result in reduced availability for the storage service or the
specified API operation.
The percentage of availability for the Queue storage service . Availability is
calculated by taking the TotalBillableRequests value and dividing it by the
Queue Availability number of applicable requests, including those that produced unexpected errors.
All unexpected errors result in reduced availability for the storage service or the
specified API operation.
The percentage of availability for the File storage service .Availability is
calculated by taking the TotalBillableRequests value and dividing it by the
File Availability number of applicable requests, including those that produced unexpected errors.
All unexpected errors result in reduced availability for the storage service or the
specified API operation.
CONFIGURATION
Storage Account Name The Azure Storage Account Name
Status of Storage Account.Possible Values:
Primary Status Available
Unavailable
Status of the Replica of Storage Account.Possible Values:
Available
Secondary Status Unavailable
This attribute is available only if the Replication Type is Standard_RAGRS or
Standard_GRS.
Resource Group Resource Group where the Storage Account is allocated in.
Location Region where the storage account is provisioned
Provisioning state of Storage AccountPossible values :
Invalid
Creating
Provisioning State Deleting
Succeeded
Failed
CancelledParameter Description
The replication type used by the Storage account:Possible values:
Standard_LRS
Standard_GRS
Replication Type
Standard_RAGRS
Standard_ZRS
Premium_LRS
Blobs
Parameter Description
Capacity
Blobs User Data Size The amount of storage used by the storage account’s Blob service, in GB.
Container Count The number of blob containers in the storage account’s Blob service.
Blob Object Count The number of blob containers in the storage account’s Blob service.
Throughput
The amount of ingress data, in MB. This number includes ingress from an external
Blobs Total Ingress
client into Azure Storage as well as ingress within Azure.
The amount of egress data, in MB. This number includes egress to an external
Blobs Total Egress client from Azure Storage as well as egress within Azure. As a result, this number
does not reflect billable egress.
The number of requests made to Blobs storage service or the specified API
Blobs Total Requests operation. This number includes successful and failed requests, as well as
requests which produced errors.
Blobs Total Billable
The number of billable requests to Blobs
Requests
Latency
The average end-to-end latency of successful requests made to Blobs or the
Blobs Average End-To-End specified API operation, in milliseconds. This value includes the required
Latency processing time within Azure Storage to read the request, send the response, and
receive acknowledgment of the response.
The average latency used by Azure Storage to process a successful request, in
Blobs Average Server
milliseconds. This value does not include the network latency specified in
Latency
AverageE2ELatency.
Requests Failed- Throttling Errors
The number of authenticated requests to Blob storage service or the specified API
Blobs Throttling Errors
operation that returned a ThrottlingError.
Blobs Anonymous Throttling The number of anonymous requests to Blob storage service or the specified API
Errors operation that returned an AnonymousThrottlingError.
The number of SAS requests to Blob storage service or the specified API operation
Blobs SAS Throttling Errors
that returned a SASThrottlingError.
Blobs Throttling Error
The percentage of requests that failed with a throttling error.
Percentage
Requests Failed – Timeout Errors
The number of authenticated requests to Blob storage service or the specified API
Blobs Client Timeout Errors
operation that returned a ClientTimeoutError.
Blobs Anonymous Client The number of anonymous requests to Blob storage service or the specified API
Timeout Errors operation that returned an AnonymousClientTimeoutError.
Blobs SAS Client Timeout The number of SAS requests to Blob storage service or the specified API operation
Errors that returned an SASClientTimeoutError.
The number of authenticated requests to Blob storage service or the specified API
Blobs Server Timeout Errors
operation that returned a ServerTimeoutError.
Blobs Anonymous Server The number of anonymous requests to Blob storage service or the specified API
Timeout Errors operation that returned an AnonymousServerTimeoutError.Parameter Description
Blobs SAS Server Timeout The number of SAS requests to Blob storage service or the specified API operation
Errors that returned an SASServerTimeoutError.
Blobs Percent Timeout The percentage of requests that failed with a timeout error. This number includes
Errors both client and server timeouts.
Requests Failed – Other Client Errors
The number of authenticated requests to a storage service or the specified API
Blobs Client Other Errors
operation that returned a ClientOtherError.
Blobs SAS Client Other The number of SAS requests to a storage service or the specified API operation
Errors that returned an SASClientOtherError.
Blobs Anonymous Client The number of anonymous requests to a storage service or the specified API
Other Errors operation that returned an AnonymousClientOtherError.
Blobs Client Other Error
The percentage of requests that failed with a ClientOtherError.
Percentage
Requests Failed – Other Server Errors
The number of authenticated requests to Blob storage service or the specified API
Blobs Server Other Errors
operation that returned a ServerOtherError.
Blobs Anonymous Server The number of anonymous requests to Blob storage service or the specified API
Other Errors operation that returned an AnonymousServerOtherError.
Blobs SAS Server Other The number of SAS requests to Blob storage service or the specified API operation
Errors that returned an SASServerOtherError.
Blobs Server Other Error
The percentage of requests that failed with a ServerOtherError.
Percentage
Requests Failed – Authorization Errors
The number of authenticated requests to Blob storage service or the specified API
Blobs Authorization Errors
operation that returned an AuthorizationError.
Blobs Anonymous The number of anonymous requests to Blob storage service or the specified API
Authorization Errors operation that returned an AnonymousAuthorizationError.
Blobs SAS Authorization The number of SAS requests to Blob storage service or the specified API operation
Errors that returned an SASAuthorizationError.
Blobs Authorization Errors
The percentage of requests that failed with an AuthorizationError.
Percentage
Requests Failed – Network Errors
The number of authenticated requests to Blob storage service or the specified API
Blobs Network Errors
operation that returned a NetworkError.
Blobs Anonymous Network The number of anonymous requests to Blob storage service or the specified API
Errors operation that returned an AnonymousNetworkError .
The number of SAS requests to Blob storage service or the specified API operation
Blobs SAS Network Errors
that returned a SASNetworkError.
Blobs Network Errors
The percentage of requests that failed with a NetworkError.
Percentage
Successful Requests
Successful Requests to The number of successful requests made to a storage service or the specified API
Blobs operation.
Blobs Anonymous The number of successful anonymous requests made to a storage service or the
Successful Requests specified API operation.
Blobs SAS Successful The number of successful Shared Access Signature (SAS) requests made to a
Requests storage service or the specified API operation.
The percentage of successful requests.
Note: that if there are no requests made against storage, the value of the
Blobs Successful Requests
PercentSuccess metric will be zero. If you are monitoring PercentSuccess, you
Percentage
will also want to ensure that the value of the TotalRequests metric is greater than
zero.
TablesParameter Description
CAPACITY
Table User Data Size (GB) The amount of storage used by the storage account’s Table service, in GB.
Table Count Total number of tables present in the storage account''s Table service.
Table Entity Count The total number of table entities in the storage account''s Table service.
THROUGHPUT
The amount of ingress data, in MB. This number includes ingress from an external
Tables Total Ingress
client into Azure Storage as well as ingress within Azure.
The amount of egress data, in MB. This number includes egress to an external
Tables Total Egress client from Azure Storage as well as egress within Azure. As a result, this number
does not reflect billable egress.
The number of requests made to Table storage service or the specified API
Tables Total Requests operation. This number includes successful and failed requests, as well as
requests which produced errors.
Tables Total Billable
The number of billable requests to Tables
Requests
Latency
The average end-to-end latency of successful requests made to Tables or the
Tables Average End-To-End specified API operation, in milliseconds. This value includes the required
Latency processing time within Azure Storage to read the request, send the response, and
receive acknowledgment of the response.
The average latency used by Azure Storage to process a successful request, in
Tables Average Server
milliseconds. This value does not include the network latency specified in
Latency
AverageE2ELatency.
Requests Failed- Throttling Errors
The number of authenticated requests to Table storage service or the specified
Tables Throttling Errors
API operation that returned a ThrottlingError.
Tables Anonymous The number of anonymous requests to Table storage service or the specified API
Throttling Errors operation that returned an AnonymousThrottlingError.
The number of SAS requests to Table storage service or the specified API
Tables SAS Throttling Errors
operation that returned a SASThrottlingError.
Tables Throttling Error
The percentage of requests that failed with a throttling error.
Percentage
Requests Failed – Timeout
Errors
The number of authenticated requests to Table storage service or the specified
Tables Client Timeout Errors
API operation that returned a ClientTimeoutError.
Tables Anonymous Client The number of anonymous requests to Table storage service or the specified API
Timeout Errors operation that returned an AnonymousClientTimeoutError.
Tables SAS Client Timeout The number of SAS requests to Table storage service or the specified API
Errors operation that returned an SASClientTimeoutError.
Tables Server Timeout The number of authenticated requests to Table storage service or the specified
Errors API operation that returned a ServerTimeoutError.
Tables Anonymous Server The number of anonymous requests to Table storage service or the specified API
Timeout Errors operation that returned an AnonymousServerTimeoutError.
Tables SAS Server Timeout The number of SAS requests to Table storage service or the specified API
Errors operation that returned an SASServerTimeoutError.
Tables Percent Timeout The percentage of requests that failed with a timeout error. This number includes
Errors both client and server timeouts.
Requests Failed – Other Client Errors
The number of authenticated requests to Table storage service or the specified
Tables Client Other Errors
API operation that returned a ClientOtherError.
Tables SAS Client Other The number of SAS requests to Table storage service or the specified API
Errors operation that returned an SASClientOtherError.
Tables Anonymous Client The number of anonymous requests to Table storage service or the specified API
Other Errors operation that returned an AnonymousClientOtherError.Parameter Description
Tables Client Other Error
The percentage of requests that failed with a ClientOtherError.
Percentage
Requests Failed – Other Server Errors
The number of authenticated requests to Table storage service or the specified
Tables Server Other Errors
API operation that returned a ServerOtherError.
Tables Anonymous Server The number of anonymous requests to Table storage service or the specified API
Other Errors operation that returned an AnonymousServerOtherError.
Tables SAS Server Other The number of SAS requests to Table storage service or the specified API
Errors operation that returned an SASServerOtherError.
Tables Server Other Error
The percentage of requests that failed with a ServerOtherError.
Percentage
Requests Failed – Authorization Errors
The number of authenticated requests to Table storage service or the specified
Tables Authorization Errors
API operation that returned an AuthorizationError.
Tables Anonymous The number of anonymous requests to Table storage service or the specified API
Authorization Errors operation that returned an AnonymousAuthorizationError.
Tables SAS Authorization The number of SAS requests to Table storage service or the specified API
Errors operation that returned an SASAuthorizationError.
Tables Authorization Errors
The percentage of requests that failed with an AuthorizationError.
Percentage
Requests Failed – Network Errors
The number of authenticated requests to Table storage service or the specified
Tables Network Errors
API operation that returned a NetworkError.
Tables Anonymous Network The number of anonymous requests to Table storage service or the specified API
Errors operation that returned an AnonymousNetworkError .
The number of SAS requests to Table storage service or the specified API
Tables SAS Network Errors
operation that returned a SASNetworkError.
Tables Network Errors
The percentage of requests that failed with a NetworkError.
Percentage
Successful Requests
The number of successful requests made to Table storage service or the specified
Tables Requests to Blobs
API operation.
Tables Anonymous The number of successful anonymous requests made to Table storage service or
Successful Requests the specified API operation.
Tables SAS Successful The number of successful Shared Access Signature (SAS) requests made to Table
Requests storage service or the specified API operation.
The percentage of successful requests.
Note that if there are no requests made against storage, the value of the
Tables Successful Requests
PercentSuccess metric will be zero. If you are monitoring PercentSuccess, you
Percentage
will also want to ensure that the value of the TotalRequests metric is greater than
zero.
Files
Parameter Description
CAPACITY
File User Data Size (GB) The average amount of storage used by the storage account’s File service, in GB.
File Count The total number of files present in the storage account''s File service.
File Share Count The total number of file shares present in the storage account''s File service.
File Share Quota (GB) The total amount of storage that can be used by File service, in GB.
The total number of snapshots present on the share in storage account''s File
File Share Snapshot Count
service.
File Share Snapshot Size The total amount of storage used by the snapshots in storage account''s File
(GB) service, in GB.Parameter Description
THROUGHPUT
The amount of ingress data, in MB. This number includes ingress from an external
Files Total Ingress
client into Azure Storage as well as ingress within Azure.
The amount of egress data, in MB. This number includes egress to an external
Files Total Egress client from Azure Storage as well as egress within Azure. As a result, this number
does not reflect billable egress.
The number of requests made to File storage service or the specified API
Files Total Requests operation. This number includes successful and failed requests, as well as
requests which produced errors.
Files Total Billable Requests The number of billable requests to Files
Latency
The average end-to-end latency of successful requests made to File Storage
Files Average End-To-End Service or the specified API operation, in milliseconds. This value includes the
Latency required processing time within Azure Storage to read the request, send the
response, and receive acknowledgment of the response.
The average latency used by Azure Storage to process a successful request, in
Files Average Server
milliseconds. This value does not include the network latency specified in
Latency
AverageE2ELatency.
Requests Failed- Throttling Errors
The number of authenticated requests to File storage service or the specified API
Files Throttling Errors
operation that returned a ThrottlingError.
Files Anonymous Throttling The number of anonymous requests to File storage service or the specified API
Errors operation that returned an AnonymousThrottlingError.
The number of SAS requests to File storage service or the specified API operation
Files SAS Throttling Errors
that returned a SASThrottlingError.
Files Throttling Error
The percentage of requests that failed with a throttling error.
Percentage
Requests Failed – Timeout Errors
The number of authenticated requests to File storage service or the specified API
Files Client Timeout Errors
operation that returned a ClientTimeoutError.
Files Anonymous Client The number of anonymous requests to File storage service or the specified API
Timeout Errors operation that returned an AnonymousClientTimeoutError.
Files SAS Client Timeout The number of SAS requests to File storage service or the specified API operation
Errors that returned an SASClientTimeoutError.
The number of authenticated requests to File storage service or the specified API
Files Server Timeout Errors
operation that returned a ServerTimeoutError.
Files Anonymous Server The number of anonymous requests to File storage service or the specified API
Timeout Errors operation that returned an AnonymousServerTimeoutError.
Files SAS Server Timeout The number of SAS requests to File storage service or the specified API operation
Errors that returned an SASServerTimeoutError.
The percentage of requests that failed with a timeout error. This number includes
Files Percent Timeout Errors
both client and server timeouts.
Requests Failed – Other Client Errors
The number of authenticated requests to File storage service or the specified API
Files Client Other Errors
operation that returned a ClientOtherError.
The number of SAS requests to File storage service or the specified API operation
Files SAS Client Other Errors
that returned an SASClientOtherError.
Files Anonymous Client The number of anonymous requests to File storage service or the specified API
Other Errors operation that returned an AnonymousClientOtherError.
Files Client Other Error
The percentage of requests that failed with a ClientOtherError.
Percentage
Requests Failed – Other Server Errors
The number of authenticated requests to File storage service or the specified API
Files Server Other Errors
operation that returned a ServerOtherError.Parameter Description
Files Anonymous Server The number of anonymous requests to File storage service or the specified API
Other Errors operation that returned an AnonymousServerOtherError.
Files SAS Server Other The number of SAS requests to File storage service or the specified API operation
Errors that returned an SASServerOtherError.
Files Server Other Error
The percentage of requests that failed with a ServerOtherError.
Percentage
Requests Failed – Authorization Errors
The number of authenticated requests to File storage service or the specified API
Files Authorization Errors
operation that returned an AuthorizationError.
Files Anonymous The number of anonymous requests to File storage service or the specified API
Authorization Errors operation that returned an AnonymousAuthorizationError.
Files SAS Authorization The number of SAS requests to File storage service or the specified API operation
Errors that returned an SASAuthorizationError.
Files Authorization Errors
The percentage of requests that failed with an AuthorizationError.
Percentage
Requests Failed – Network Errors
The number of authenticated requests to File storage service or the specified API
Files Network Errors
operation that returned a NetworkError.
Files Anonymous Network The number of anonymous requests to File storage service or the specified API
Errors operation that returned an AnonymousNetworkError .
The number of SAS requests to File storage service or the specified API operation
Files SAS Network Errors
that returned a SASNetworkError.
Files Network Errors
The percentage of requests that failed with a NetworkError.
Percentage
Successful Requests
The number of successful requests made to File storage service or the specified
Files Requests to Blobs
API operation.
Files Anonymous Successful The number of successful anonymous requests made to File storage service or the
Requests specified API operation.
Files SAS Successful The number of successful Shared Access Signature (SAS) requests made to File
Requests storage service or the specified API operation.
The percentage of successful requests.
Note that if there are no requests made against storage, the value of the
Files Successful Requests
PercentSuccess metric will be zero. If you are monitoring PercentSuccess, you
Percentage
will also want to ensure that the value of the TotalRequests metric is greater than
zero.
Queues
Parameter Description
CAPACITY
The average amount of storage used by the storage account’s Queue service, in
Queue User Data Size (GB)
GB.
Queue Count The total number of queue in the storage account''s Queue service.
The approximate number of queue messages in the storage account''s Queue
Queue Message Count
service.
THROUGHPUT
The amount of ingress data, in MB. This number includes ingress from an external
Queues Total Ingress
client into Azure Storage as well as ingress within Azure.
The amount of egress data, in MB. This number includes egress to an external
Queues Total Egress client from Azure Storage as well as egress within Azure. As a result, this number
does not reflect billable egress.
The number of requests made to Queue storage service or the specified API
Queues Total Requests operation. This number includes successful and failed requests, as well as
requests which produced errors.Parameter Description
Queues Total Billable
The number of billable requests to Queues
Requests
Latency
The average end-to-end latency of successful requests made to Queue or the
Queues Average End-To-End specified API operation, in milliseconds. This value includes the required
Latency processing time within Azure Storage to read the request, send the response, and
receive acknowledgment of the response.
The average latency used by Azure Storage to process a successful request, in
Queues Average Server
milliseconds. This value does not include the network latency specified in
Latency
AverageE2ELatency.
Requests Failed- Throttling Errors
The number of authenticated requests to Queue storage service or the specified
Queues Throttling Errors
API operation that returned a ThrottlingError.
Queues Anonymous The number of anonymous requests to Queue storage service or the specified API
Throttling Errors operation that returned an AnonymousThrottlingError.
Queues SAS Throttling The number of SAS requests to Queue storage service or the specified API
Errors operation that returned a SASThrottlingError.
Queues Throttling Error
The percentage of requests that failed with a throttling error.
Percentage
Requests Failed – Timeout Errors
Queues Client Timeout The number of authenticated requests to Queue storage service or the specified
Errors API operation that returned a ClientTimeoutError.
Queues Anonymous Client The number of anonymous requests to Queue storage service or the specified API
Timeout Errors operation that returned an AnonymousClientTimeoutError.
Queues SAS Client Timeout The number of SAS requests to Queue storage service or the specified API
Errors operation that returned an SASClientTimeoutError.
Queues Server Timeout The number of authenticated requests to Queue storage service or the specified
Errors API operation that returned a ServerTimeoutError.
Queues Anonymous Server The number of anonymous requests to Queue storage service or the specified API
Timeout Errors operation that returned an AnonymousServerTimeoutError.
Queues SAS Server Timeout The number of SAS requests to Queue storage service or the specified API
Errors operation that returned an SASServerTimeoutError.
Queues Percent Timeout The percentage of requests that failed with a timeout error. This number includes
Errors both client and server timeouts.
Requests Failed – Other Client Errors
The number of authenticated requests to Queue storage service or the specified
Queues Client Other Errors
API operation that returned a ClientOtherError.
Queues SAS Client Other The number of SAS requests to Queue storage service or the specified API
Errors operation that returned an SASClientOtherError.
Queues Anonymous Client The number of anonymous requests to Queue storage service or the specified API
Other Errors operation that returned an AnonymousClientOtherError.
Queues Client Other Error
The percentage of requests that failed with a ClientOtherError.
Percentage
Requests Failed – Other Server Errors
The number of authenticated requests to Queue storage service or the specified
Queues Server Other Errors
API operation that returned a ServerOtherError.
Queues Anonymous Server The number of anonymous requests to Queue storage service or the specified API
Other Errors operation that returned an AnonymousServerOtherError.
Queues SAS Server Other The number of SAS requests to Queue storage service or the specified API
Errors operation that returned an SASServerOtherError.
Queues Server Other Error
The percentage of requests that failed with a ServerOtherError.
Percentage
Requests Failed – Authorization Errors
The number of authenticated requests to Queue storage service or the specified
Queues Authorization Errors
API operation that returned an AuthorizationError.Parameter Description
Queues Anonymous The number of anonymous requests to Queue storage service or the specified API
Authorization Errors operation that returned an AnonymousAuthorizationError.
Queues SAS Authorization The number of SAS requests to Queue storage service or the specified API
Errors operation that returned an SASAuthorizationError.
Queues Authorization Errors
The percentage of requests that failed with an AuthorizationError.
Percentage
Requests Failed – Network Errors
The number of authenticated requests to Queue storage service or the specified
Queues Network Errors
API operation that returned a NetworkError.
Queues Anonymous The number of anonymous requests to Queue storage service or the specified API
Network Errors operation that returned an AnonymousNetworkError .
The number of SAS requests to Queue storage service or the specified API
Queues SAS Network Errors
operation that returned a SASNetworkError.
Queues Network Errors
The percentage of requests that failed with a NetworkError.
Percentage
Successful Requests
The number of successful requests made to Queue storage service or the
Queues Requests to Blobs
specified API operation.
Queues Anonymous The number of successful anonymous requests made to Queue storage service or
Successful Requests the specified API operation.
Queues SAS Successful The number of successful Shared Access Signature (SAS) requests made to Queue
Requests storage service or the specified API operation.
The percentage of successful requests.
Note that if there are no requests made against storage, the value of the
Queues Successful
PercentSuccess metric will be zero. If you are monitoring PercentSuccess, you
Requests Percentage
will also want to ensure that the value of the TotalRequests metric is greater than
zero.
Windows Azure Cloud Service Monitoring
(Classic) (Deprecated)
Windows Azure - Overview
Creating a new Windows Azure Monitor
Monitored Parameters
Windows Azure - Overview
Applications Manager''s Windows Azure monitor enables users to collect diagnostic data for the applications
deployed in Windows Azure platform. Windows Azure is monitored using REST API to discover the list of deployed
applications and get the performance counters based on the Role instances of the service.
With Windows Azure monitoring capabilities in ManageEngine Applications Manager, you can:
Discover Windows Azure applications and all its roles instances.
Collect and monitor performance information based on role instances.
Collect and monitor Windows Azure Event Logs, Trace Logs and Diagnostic Infrastructure Logs
Adding a Windows Azure application will include all the Hosted Services, deployments and its roles instance
based on the Storage account. The hosted services and deployments will be created as a group.
Creating a new Windows Azure monitor in Applications
Manager
Prerequisites: To add Windows Azure in Applications Manager, you must first export your Windows Azure Managed
Certificates file (eg., testcertificate.pfx) and the password of the pfx file. To export your Windows Azure Managed
Certificates file , invoke the batch script exportCertificateToAppManager.bat in the bin directory.To create a new Windows Azure monitor, follow the steps given below:
Click on the New Monitor link in the Applications Manager web client.
Enter the Subscription ID for your Windows Azure account. (Note: Subscription ID can be obtained by signing
into windows.azure.com using your windows live id. Then click Hosted Service and navigate to Storage &
CDN, then to Storage Accounts)
Enter the Account Name and Account key of your Windows Azure Storage account.
Check the checkbox if your service is https-enabled.
Specify a Timeout interval in seconds
Specify the Polling Interval in minutes
If you are adding a new monitor from an Admin Server, select a Managed Server.
Note:
Before creating a new Windows Azure monitor, you have to configure proxy settings under ''Admin'' tab.
Creating and deploying Management Certificates in Azure
Login to the machine where you have installed Windows Azure SDK and IIS 7.
To load the IIS 7 Management console, go to the Control Panel, select Administrative Tools and then IIS
Manager.
In the IIS section of the center pane, double-click Server Certificates.
Click Create Self-Signed Certificate in the Actions panel.
Enter a name for the file.
Close the IIS Manager and open the Certificate Manager.
Under Trusted Root Certification Authorities, open Certificates.
Right-click your certificate, choose All Tasks and Export. The Certificate Export Wizard appears. Click Next.
You can export the certificate with or without a private key. First, export the certificate without a private key to be
uploaded to Windows Azure Portal. Then export the certificate again with a private key to be used in Service
Management API.
Exporting the certificate without a private key:
When the Certificate Export Wizard appears, Click Next.
On the Export Private Key page, click No.
Select the CER file format and click Next.
Enter a name and click Next.
Click Finish to start the export process.
Exporting the certificate with a private key:
When the Certificate Export Wizard appears, Click Next.
On the Export Private Key page, click Yes, export the private key.
Keep the default value, then click Next.
Specify a password for protecting your private key and click Next.
Specify a name for the PFX file and click Next.
Click Finish to start the export process.
The .cer file can be uploaded in the Windows Azure portal and the .pfx file which has the private key can be used in
Applications Manager.
Monitored Parameters
Windows Azure platforms are monitored based on the parameters or the attributes listed below. You can also
configure thresholds to the numerical attributes based on these details and get notified when the thresholds are
violated.
The Availability tab shows the availability history for Azure Role instances for the past 24 hours or 30 days. The
Performance tab shows some key performance indicators such as CPU, Memory Utilization, Exceptions thrown andHealth History along with heat charts for these attributes. This tab also shows the health status and events for the
past 24 hours or 30 days.
The List view displays all the Azure role instances along with an overall idea of their availability and health status.
The list view also enables you to perform bulk admin configurations. You can click on the individual role instances
to view detailed performance metrics.
Click on the monitor listed in the Availability tab to view detailed performance metrics of the Azure role instances.
These metrics are categorized into 4 different tabs for easy understanding:
Overview
Event Logs
Trace Logs
Diagnostic Infrastructure Logs
Overview
This tab provides a high-level overview of your Azure account as well as information about the Role instances
present in this account.
Parameter Description
Monitor Information
Name The name of the Windows Azure account.
Type Denotes the type you are monitoring.
Denotes the health (Clear, Warning, Critical) status of the Windows Azure
Health
account.
Denotes the monitor groups associated with the Windows Windows Azure
Associated Groups
monitor.
Last Polled at Specifies the time at which the last poll was performed
Next Poll at Specifies the time at which the next poll will be performed
CPU Utilization Usage of CPU resources or the amount of work handled by CPU
Memory Utilization Memory Available Memory Usage Time Spend in Garbage Collection
Exceptions Thrown Number of exceptions thrown per second
Number of times Application Restarted
Request Execution Time
Number of Requests Disconnected
Number of times Worker Process Restarted
ASP .NET System Performance Total Number of Requests
Counters Number of Requests executed per second
Current Requests
Recent Request Waited Time
Number of Queued Request waiting for service
Number of Requests Rejected
Number of TCP Connections failed
TCP Connections Number of TCP Connections Established
Number of TCP Connections Reset
TCP Segment Connections TCP segments sent per sec
Total number of Bytes received per second for all interfaces
Network Traffic
Total number of Bytes sent per second for all interfaces
Network Traffic VM Bus Adapter
Total number of bytes send and received per sec for VM Bus Network
Adapter
Total number of bytes received per second for VM Bus Network
AdapterTotal number of bytes sent per second for VM Bus Network Adapter
Monitoring Logs in Applications Manager
Event Logs, Trace logs and Diagnostic infrastructure logs of the Windows Azure Role Instances can be monitored
by defining rules. On clicking Windows Azure Log rule configuration, you can create rules for Diagnostic
Infrastructure and Trace logs.
When the Azure Role Instance starts it data collection, all the logs associated to the role instance will be matched
the rule. On matching the rule, an event will be generated and the log entry will be persisted in the database. The
log information will be available in the GUI of the Azure role instance
Event Logs
On clicking Event Log Rules configuration tab, you can create rules on various category such as Application,
System, Application, Security, DNS Server, File replication service and Directory service.
You can view Windows Azure Event Log Details like:
Parameter Description
Rule Name Specify the name of the rule.
Provider Guid Globally unique identifier of the provider
Provider Name Provider name of the event.
Event ID The identifier of the event.
Level This field provides the severity of the event.
Process ID The process ID of the event.
Thread ID The thread ID of the event.
Channel You can get notified by the events from channels like Applications, Security, System, etc.
Generated Time The time at which the event is generated.
Trace logs
In the trace logs tab, you can view Windows Azure Event Log Details like:
Parameter Description
Rule Name Specify the name of the rule.
Event ID The identifier of the events
Level This field provides the severity of the log event.
Process ID The process ID of the log.
Thread ID The thread ID of the log.
Generated Time The time at which the event is generated.
Diagnostic infrastructure logs
In the Diagnostic infrastructure logs tab, you can view Windows Azure Diagnostic Infrastructure Log Details like :
Parameter Description
Rule Name Specify the name of the rule.
Error Code Specify the error code of the log.
Level This field provides the severity of the log event.
Process ID The process ID of the log.
Thread ID The thread ID of the log.
Function Specify the function of the log event.
Line Specify the line containing the function.
MD Result Specify the MDetect result of the log.
Event Generated Time The time at which the event is generated.
Microsoft Azure SQL Database MonitoringMicrosoft Azure SQL Database- An Overview
Adding a new Microsoft Azure SQL Database monitor
Monitored Parameters
Microsoft Azure SQL Database Monitoring Tool - An Overview
Azure SQL DB is a relational database-as-a-service (DBaaS) hosted in the Azure cloud. Data is hosted, managed
and provisioned in Microsoft data centers. Since organizations constantly deal with large amounts of data at a
global scale, it goes without saying that a proper Microsoft Azure SQL database management tool is highly
recommended to monitor and understand what is going on while storing and retrieving huge amounts of data
constantly on cloud.
Applications Manager''s Azure SQL database performance monitoring provides monitoring of Azure SQL
performance metrics and query statistics so that users can be informed of any performance issues happening in
their Azure SQL database. It eases your Azure monitoring needs by keeping a close watch on Azure SQL database
monitoring metrics along with proactive Azure SQL database query monitoring, providing deep insights into the
performance of your Azure SQL environments.
In this help document, you will learn how to get started with Azure SQL database performance monitoring by
keeping a close watch on various Azure SQL performance metrics with the help of Applications Manager.
Creating a new Microsoft Azure SQL Database monitor
Prerequisites for setting up Microsoft SQL Azure database monitoring: Click here
Using the REST API to add a new Microsoft Azure SQL Database monitor: Click here
Follow the steps given below to create a new monitor:
Click on the New Monitor link in the Applications Manager web client.
Select ''Microsoft Azure'' under Cloud Apps category.
Specify the Display Name of Microsoft Azure monitor.
Enter the Subscription ID for your Microsoft Azure subscription.
Click the Azure Services textbox and choose ''Azure SQL Databases'' from the drop-down menu.
Choose the Discovery mode:
Discovery using AD Application & Service Principal: Refer Prerequisites link and provide the Client ID,
Tenant ID & Application key that were obtained in the above mentioned prerequisite step in the New
monitor page.
Discovery using Azure Organizational Account (Powershell): Refer Prerequisites link and provide the
User email & Password fields in New monitor page with the Username & Password of the created
Organizational account.
Discovery using OAuth: Use the OAuth Provider that was obtained in the prerequisite step in the New
monitor page. Refer Prerequisites section.
Specify the polling interval in minutes and timeout in seconds.
Choose the Monitor Group from the combo box with which you want to associate Microsoft Azure SQL server
Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers Microsoft Azure SQL database server from the network and starts
monitoring them.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Azure SQL Database under the Cloud
Apps table. Displayed is the Azure SQL database bulk configuration view distributed into three tabs:
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Azure SQL Database Monitoring Metrics
SQL Azure database monitoring tool like Applications Manager eases out your Microsoft Azure SQL database
management needs by providing visibility into your Azure SQL cloud environments along with Azure SQL database
query monitoring altogether in a single window, providing all the vital Azure SQL database monitoring metrics in
the following tabs:Monitor Information
Overview
Top Queries by CPU
Top Queries by IO
Top CLR Queries and Waits
Top Slow Running Queries
Frequently Executed Queries
Most Blocked Queries
Configuration
Note: To monitor Query Statistics, the username and password of the SQL database should be provided in the
''Edit Monitor'' page.
Monitor Information
Parameter Description
Database Name Name of the Azure SQL Database
Database Username Username of the SQL Server of this particular database
Database Server Name of the SQL server
Resource Group Name Resource group to which the SQL database is associated
Timeout Timeout Duration(seconds)
Associated Groups The monitor groups to which this monitor is associated
Last Polled At Specifies the time at which the last poll was performed
Next Poll At Specifies the time at which the next poll is scheduled
Overview
Parameter Description
RESOURCE UTILIZATION
CPU Utilization Average percentage of CPU utilized between the poll interval.
Average percentage of Data Transaction Unit (DTU) consumed between the
DTU Utilization *
poll interval.
IO Utilization Average percentage of Data IO utilized between the poll interval.
DTU UTILIZATION
DTU Limit * Average limit of Data Transaction Unit between the poll interval.
DTU Used * Average Data Transaction Unit used between the poll interval.
DATABASE SIZE
Storage Utilization Amount of storage space utilized in the database (in percentage).
Allocated Database Amount of storage space allocated for the database (in MB).
Used Database Amount of storage space used in the database (in MB).
Total Database Maximum amount of storage space available in the database (in GB).
CONNECTIONS
Successful connections Total number of successful connections between the poll interval.
Failed connections Total number of failed connections between the poll interval.
Total number of connections that are blocked by firewall between the poll
Connections Blocked by firewall
interval.
PERFORMANCE STATISTICS
Deadlocks Total number of deadlocks occurred between the poll interval.
Log IO Percentage Average percentage of log IO between the poll interval.
In-memory OLTP storage used Average percentage of In-Memory Online Transaction Processing storage
percentage used between the poll interval.Parameter Description
Workers(concurrent requests)
Average percentage of Workers used between the poll interval.
used percentage
Sessions used percentage Average percentage of sessions between the poll interval.
Note: Metrics marked with * can be monitored only in DTU-based Azure SQL Database servers.
Top Queries by CPU
Parameter Description
Average CPU time(ms) Average CPU time taken to execute this query
Total CPU time(ms) Total CPU time taken to execute this query
Average Execution time(ms) Average time taken to execute this query
Query Indicates the query executed.
Last Execution time The time when this query was last executed
Top Queries by IO
Parameter Description
Average IO Average IO operations for this query
Total IO Total IO operations for this query
Average Execution time(ms) Average time taken to execute this query
Query Indicates the query executed.
Last Execution time The time when this query was last executed
Top CLR Queries and Waits
Parameter Description
Top CLR queries
Average CLR time(ms) Average CLR time taken to execute this query
Total CLR time(ms) Total CLR time taken to execute this query
Average Execution time(ms) Average time taken to execute this query
Query Indicates the query executed.
Last Execution time The time when this query was last executed
Top Waits by waiting tasks
Waiting tasks Number of waiting tasks
Wait time(ms) Total wait time
Average Wait time(ms) Average wait time by the waiting tasks
Signal time(ms) Signal time by the waiting task
Wait type Type of the waiting tasks
Top Slow Running Queries
Parameter Description
Average Execution Time(ms) Average execution time for this query
Maximum Execution Time(ms) Maximum execution time for this query
Minimum Execution time(ms) Minimum execution time for this query
Number of Executions Number of times this query was executed
Query Indicates the query executed.
Last Execution time The time when this query was last executedFrequently Executed Queries
Parameter Description
Execution count Number of times this query was executed
Average Execution time(ms) Average execution for this query
Query Indicates the query executed.
Last Execution time The time when this query was last executed
Most Blocked Queries
Parameter Description
Average time blocked(ms) Average time this query was blocked
Total time blocked(ms) Total time this query was blocked
Average Execution time(ms) Average time taken to execute this query
Query Indicates the query executed.
Last Execution time The time when this query was last executed
Configuration
Parameter Description
Database name Name of the Azure SQL Database
Database status Status of the SQL database
Database Location Location of the SQL database
Database Server Name of the SQL Server
Resource Group Name Resource group to which the SQL database is associated
Database Edition Edition/Pricing tier of this database
Database Creation Date Date on when this database was created
Database Earliest Restore Date Oldest restore point
Elastic Pool The Elastic pool to this this database is associated if any
Azure Service Bus Monitoring (ARM)
Azure Service Bus - Overview
Microsoft Azure Service Bus is a fully managed enterprise integration message broker. Service Bus can decouple
applications and services. Service Bus offers a reliable and secure platform for asynchronous transfer of data and
state.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the Service Bus instance available under
Microsoft Azure in the Cloud Apps section. Displayed is the Azure Service Bus bulk configuration view distributed
into three tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
By clicking a monitor from the list, you''ll be taken to the Azure Service Bus dashboard. It has 4 tabs:
Overview
Queues
Topics
ConfigurationOverview
Parameter Description
NAMESPACE DETAILS
Number of Queues The number of queues present in a namespace.
Number of Topics The number of topics present in a namespace.
Namespace Used Size Amount of space utilized by the namespace (in MB).
Status Status of the namespace.
REQUEST STATISTICS
Incoming Requests The number of requests made to the Service Bus service over a specified poll interval.
Incoming
The number of requests made per minute to the Service Bus.
Requests/min
The number of successful requests made to the Service Bus service over a specified
Successful Requests
poll interval.
Throttled Requests The number of requests that were throttled because the usage was exceeded.
REQUEST ERRORS
User Errors The number of requests not processed due to user errors over a specified period.
The number of requests not processed due to an error in the Service Bus service over a
Server Errors
specified period.
MESSAGE STATISTICS
Incoming Messages The number of events or messages sent to Service Bus over a specified period.
Incoming
The number of events or messages sent per minute to Service Bus.
Messages/min
Outgoing Messages The number of events or messages received from Service Bus over a specified period.
Outgoing
The number of events or messages received per minute from Service Bus.
Messages/min
MESSAGE DETAILS
Total Messages Total number of messages available on an entity.
Active Messages Number of active messages on an entity.
Dead Letter Messages Number of dead-lettered messages on an entity.
Scheduled Messages Number of scheduled messages on an entity.
CONNECTIONS STATISTICS
Active Connections The number of active connections on a namespace as well as on an entity.
Connections Opened Number of connections that were opened.
Connections Closed Number of connections that were closed.
RESOURCE USAGE *
Namespace CPU
The percentage of the amount of CPU used by the namespace.
Usage
Namespace Memory
The percentage of the amount of memory used by the namespace.
Usage
Note: The server details marked with an * symbol is applicable only for ''Premium'' tier namespaces and not for
Basic and Standard tiers.
Queues
Parameter Description
Queue Details
Queue Name of the queue.
Status Status of the queue. Possible values are Active, Activating, or Removed.
Total Size Total amount of space allocated for the queue.
Used Size(%) Amount of space utilized by the queue (in percentage).Parameter Description
Free Size(%) Remaining amount of space available for use by the queue (in percentage).
Used Size(MB) Amount of space utilized by the queue (in MB).
Free Size(MB) Remaining amount of space available for use by the queue (in MB).
Messages Total number of messages available in a queue.
Active Messages Number of active messages in a queue.
Dead Letter Messages Number of dead-lettered messages in a queue.
Transfer Messages Number of transfer messages in a queue.
Transfer Dead Letter
Number of transfer dead-lettered messages in a queue.
Messages
Active Queues based on Incoming Requests: Provides a graphical representation of the request details of
Active Queues with respect to number of incoming requests in the namespace.
Active Queues based on Messages: Provides a graphical representation of the message details of Active
Queues with respect to number of incoming and outgoing messages in the namespace.
Queue Metrics
Queue Name of the queue.
Incoming Requests The number of requests made to the queue over a specified poll interval.
Successful Requests The number of successful requests made to the queue over a specified poll interval.
Throttled Requests The number of throttled requests made to the queue over a specified poll interval.
Incoming Messages The number of events or messages sent to the queue over a specified poll interval.
The number of events or messages received from the queue over a specified poll
Outgoing Messages
interval.
Scheduled Messages Number of scheduled messages in a queue.
The number of requests not processed due to user errors in the queue over a
User Errors
specified period.
The number of requests not processed due to server errors in the queue over a
Server Errors
specified period.
Topics
Parameter Description
Topic Details
Topic Name of the topic.
Status Status of the topic. Possible values are Active, Activating, or Removed.
Total Size Total amount of space allocated for the topic.
Used Size(%) Amount of space utilized by the topic (in percentage).
Free Size(%) Remaining amount of space available for use by the topic (in percentage).
Used Size(MB) Amount of space utilized by the topic (in MB).
Free Size(MB) Remaining amount of space available for use by the topic (in MB).
Subscription Count Total number of subscriptions available in a topic.
Active Messages Number of active messages in a topic.
Dead Letter Messages Number of dead-lettered messages in a topic.
Transfer Messages Number of transfer messages in a topic.
Transfer Dead Letter
Number of transfer dead-lettered messages in a topic.
Messages
Active Topics based on Incoming Requests: Provides a graphical representation of the request details of Active
Topics with respect to number of incoming requests in the namespace.
Active Topics based on Messages: Provides a graphical representation of the message details of Active Topics
with respect to number of incoming and outgoing messages in the namespace.
Topic Metrics
Topic Name of the topic.Parameter Description
Incoming Requests The number of requests made to the topic over a specified period.
Successful Requests The number of successful requests made to the topic over a specified period.
Throttled Requests The number of throttled requests made to the topic over a specified period.
Incoming Messages The number of events or messages sent to the topic over a specified period.
Outgoing Messages The number of events or messages received from the topic over a specified period.
Scheduled Messages Number of scheduled messages in a topic.
The number of requests not processed due to user errors in the topic over a
User Errors
specified period.
The number of requests not processed due to server errors in the topic over a
Server Errors
specified period.
Configuration
Parameter Description
NAMESPACE DETAILS
Resource Group Specifies the Resource Group of the Service Bus Namespace.
Location The location/region of the Service Bus Namespace.
Indicates the tier used in the Service Bus Namespace. Possible values are Basic, Standard
Tier
or Premium.
Service Bus End
Indicates the endpoint URL of the Service Bus Namespace.
point
Created Time Date and time at which the Service Bus Namespace was created.
Last Updated Time Date and time at which the Service Bus Namespace was last updated.
Resource ID Indicates the resource ID of the Service Bus Namespace.
Microsoft Azure Kubernetes Service (AKS)
Monitoring
Overview
Azure Kubernetes Service (AKS) offers server-less Kubernetes, an integrated continuous integration and
continuous delivery (CI/CD) experience and enterprise-grade security and governance. Azure Kubernetes Service
(AKS) simplifies deploying a managed Kubernetes cluster in Azure by offloading the operational overhead to
Azure. As a hosted Kubernetes service, Azure handles critical tasks, like health monitoring and maintenance. Since
Kubernetes masters are managed by Azure, you only manage and maintain the agent nodes. Thus, AKS is free; you
only pay for the agent nodes within your clusters, not for the masters. It allows you to rapidly build, deliver and
scale applications.
Creating a new monitor
Prerequisites for monitoring Microsoft AKS metrics: Click here
To learn how to create a new AKS monitor, refer here.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the Kubernetes Service instance
available under Microsoft Azure in the Cloud Apps section. Displayed is the Microsoft AKS bulk configuration
view distributed into three tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
By clicking a monitor from the list, you''ll be taken to the Microsoft AKS monitor dashboard. It has 6 tabs:
OverviewNode Pool
Node
Pods
Services
Persistent Volumes
Service Map
Overview
Parameter Description Data Collection Method
Kubectl Azure Monitor Container Insights
CLUSTER INFORMATION
Current status of the
Status cluster. (Running,
Stopped)
The Azure Resource Name
Cluster FQDN
(ARN) of the cluster.
Cluster Location where the cluster
Location resides.
Cluster
Kubernetes version of the
Kubernetes
cluster server.
Version
CLUSTER DETAILS
Git Version Git version of the cluster.
Build Date Build date of the cluster.
Name of the compiler
Compiler
used.
Platform OS Platform of the cluster.
CLUSTER AUTOSCALER DETAILS (Applicable only when cluster autoscaler is enabled)
Determines if the scale
Cluster down is in cooldown. No
Scaledown nodes will be removed
Cooldown during this timeframe at
the time of polling.
Cluster autoscaler marks
Cluster those nodes as candidates
UnNeeded for deletion and are
Nodes eventually deleted at the
time of polling
Number of pods that are
Cluster
currently unschedulable in
UnSchedulable
the cluster at the time of
Pods
polling.
Determines the health of
Cluster Health the autoscaler at the time
of polling.
NAMESPACE DETAILS
Namespace
UUID of the namespace.
UUID
Namespace
Name of the namespace
Name
Number of pods count in
Pods Count the namespace at the time
of polling.Parameter Description Data Collection Method
Kubectl Azure Monitor Container Insights
Number of running pods
Running pods
under the namespace at
in namespace
the time of polling.
Number of pending pods
Pending Pods under the namespace at
the time of polling.
Number of succeeded
Succeeded pods under the
Pods namespace at the time of
polling.
Number of failed pods
Failed Pods under the namespace at
the time of polling.
Number of succeeded
pods under the
Unknown Pods
namespace at the time of
polling.
Number of containers
Restarting
restarted count in the
Container
namespace at the time of
Count
polling.
Number of OOM killed
OOMKilled
containers count in the
Container
namespace at the time of
Count
polling.
Percentage of the number
of pods that are in ready
Pods Ready
stage at the time of
polling.
Namespace
Timestamp at which the
Resource
Namespace was created
Version
Namespace Timestamp at which the
Availability Namespace was created
Namespace Timestamp at which the
Created Time Namespace was created
CLUSTER CPU & MEMORY DETAILS
Available Total number of available
Cluster CPU CPU cores in the cluster at
Cores the time of poll interval.
Available Total number of available
Cluster Memory in the cluster at
Memory the time of poll interval.
NODE DETAILS
Number of master nodes
Master Nodes
available in the cluster.
Number of worker nodes
Worker Nodes
available in the cluster.
CLUSTER USAGE DETAILS
Average amount of CPU
Avg. CPU
used by the cluster (in
Usage
percentage).
Average amount of
Avg. Memory
memory used by the
Usage
cluster (in percentage).
NODE COUNT DETAILSParameter Description Data Collection Method
Kubectl Azure Monitor Container Insights
Number of nodes that are
Nodes Ready in ready stage at the time
of polling.
Number of nodes that are
Nodes Not
not in ready stage at the
Ready
time of polling.
Top 5 Nodes by Used Pods - Displays a graphical representation of top 5 nodes with respect to the number of
pods used.
PODS
Used pods in Percentage of the number
cluster % of pods used.
Used pods in Number of pods used in
cluster the cluster.
Maximum pods Maximum number of pods
in cluster available in the cluster.
PODS PHASE
Total number of pods
Total Failed
failed in the cluster at the
Pods
time of polling.
Total number of pods
Total Pending
pending in the cluster at
Pods
the time of polling.
Total number of pods
Total Running
running in the cluster at
Pods
the time of polling.
Total number of pods
Total Unknown
unknown in the cluster at
Pods
the time of polling.
Total Total number of pods
Succeeded succeeded in the cluster
Pods at the time of polling.
COMPONENT DETAILS
Component
Name of the component.
Name
Availability status of the
Availability
component.
Node Pool
Parameter Description Data Collection Method
Kubectl Azure Monitor Container Insights
Node Pool Details *
Name Name of the node pool.
The current status of the
Status managed node pool. (Running
or Stopped)
The size of the agent pool
VM Size VMs. VM size availability
varies by region.
Kubernetes The version of Kubernetes
Version running on the agent pool.
Image The version of node pool
Version image.Parameter Description Data Collection Method
Kubectl Azure Monitor Container Insights
Minimum
Node Size The minimum number of
(Auto- nodes for auto-scaling.
Scaling)
Maximum
Node Size The maximum number of
(Auto- nodes for auto-scaling.
Scaling)
Maximum The maximum number of pods
Pods Count that can run on a node.
Node Pool Utilization *
Name Name of the node pool.
The operating system type.
OS Type
Default value is Linux.
Specifies an OS SKU. This
OS SKU value must not be specified if
OS type is Windows.
The OS disk type to be used
OS Disk
for machines in the agent
Type
pool.
Size of the OS Disk to be used
OS Disk to specify the disk size for
Size every machine in the
master/agent pool (in GB).
Average CPU utilization
measured across the node
CPU Usage
pool between the poll interval
(in percentage).
Disk space used for node pool
Disk Usage between the poll interval (in
percentage).
Container RSS memory used
Memory
for node pool between the poll
RSS Usage
interval (in percentage).
Container working set memory
Memory used for node pool between
WS Usage the poll interval (in
percentage).
* Note: Azure Monitor metrics are not available for Windows node pool.
Node
Parameter Description Data Collection Method
Kubectl Azure Monitor Container Insights
Top 5 Nodes by Memory Details - Displays a graphical representation of top 5 nodes with respect to their
corresponding memory details (in percentage).
Top 5 Nodes by CPU Details - Displays a graphical representation of top 5 nodes with respect to their
corresponding CPU details (in percentage).
Node Usage Details *
Node Name Name of the node.
Average CPU utilization in
CPU Usage
millicores across the node
Millicores
between the poll interval.Parameter Description Data Collection Method
Kubectl Azure Monitor Container Insights
Average CPU utilization
CPU Usage measured across the node
(%) between the poll interval (in
percentage).
Disk space used for node
Disk Usage
between the poll interval (in
(GB)
GB).
Disk space used for node
Disk Usage
between the poll interval (in
(%)
percentage).
Memory Container RSS memory used
RSS Usage for node between the poll
(GB) interval (in GB).
Memory Container RSS memory used
RSS Usage for node between the poll
(%) interval (in percentage).
Container working set
Memory WS memory used for node
Usage (GB) between the poll interval (in
GB).
Container working set
Memory WS memory used for node
Usage (%) between the poll interval (in
percentage).
Amount of data received by
Network In the network for the node
Usage between the poll interval (in
MB).
Amount of data transmitted
Network Out by the network for the node
Usage between the poll interval (in
MB).
Node Pod Details
Node Name Name of the node.
Number of pods available for
Pod Usage usage with used and free
pods split-up.
Number of pods that are used
Used Pods
in the node.
Number of pods that are free
Free Pods
in the node.
Allocatable Number of pods that are
Pods allocatable in the node.
Kube-
Number of Kube state pods in
system Pod
the node.
Count
Non-Kube-
Number of non-Kube state
system Pod
pods in the node.
Count
Number of images present in
Images
the node.
NODE DETAILS
Node Name Name of the node.
OS Image OS Image name of the node.
Name of the OS in which the
OS
container is deployed.Parameter Description Data Collection Method
Kubectl Azure Monitor Container Insights
Architecture details of the
Architecture
node.
Type Type of node used.
Kubelet
The version of Kubelet used.
Version
Allocatable
Size of temporary memory
Ephemeral
available (in GiB).
Storage
Created Timestamp at which the node
Time was created.
* Note: Azure Monitor metrics are not available for Windows node.
Pods
Parameter Description Data Collection Method
Kubectl Azure Container
Monitor Insights
Pod Details
Pod UUID Universal unique ID of the pod.
Pod Name Name of the pod.
Pod
Namespace in which the pod resides.
Namespace
Pod Node
Name of the pod-node.
Name
Pod
Name of the pod application.
Application
Pod Type Type of pod used.
Pod created Medium by which the pod was created.
Status of the pod. (Pending, Running,
Pod Status
Succeeded, Failed, or Unknown)
Amount of time elapsed since the pod was
Pod Age
created (in days).
Pod Start
Timestamp at which the pod was started.
Time
Pod
Created Timestamp at which the pod was created.
Time
Top 10 Pods by Memory Details - Displays a graphical representation of top 10 pods with respect to their
corresponding memory details (in percentage).
Top 10 Pods by CPU Details - Displays a graphical representation of top 10 pods with respect to their
corresponding CPU details (in percentage).
Pod Usage Details
Pod UUID Universal unique ID of the pod.
Pod Name Name of the pod.
Pod
Name of the pod.
Namespace
Pod
Containers The number of containers run by the pod.
Count
Pod CPU The maximum limit of CPU resource which can
Limit be used (in percentage).Parameter Description Data Collection Method
Kubectl Azure Container
Monitor Insights
Pod CPU The number of CPU requests by pod (in
Request percentage).
Pod
The maximum limit of memory resource that
Memory
can be used (in percentage).
Limit
Pod
The number of memory requested (in
Memory
percentage).
Request
Pod created Medium by which the pod was created.
Pod
Persistent Name of the Claim through which a pod can
Volumes access the persistent volume.
Claim
Container Details
Container
ID of the container.
ID
Container
Name of the container.
Name
Container
Name of the container image.
Image
Container
Name of the container pod.
Pod Name
Container The number of times the container has
Restarts restarted.
Status of the container. Following are the list of
possible values that are shown for each status:
Status Value
Running Running
ContainerCreating
CrashLoopBackOff
ErrImagePull
Waiting ImagePullBackOff
Container
CreateContainerConfigError
Status
InvalidImageName
CreateContainerError
OOMKilled
Error
Terminated Completed
ContainerCannotRun
DeadlineExceeded
Container Amount of time elapsed since the container was
Age started (in days).
Container
Timestamp at which the container was started.
Start Time
Services
Parameter Description Data Collection Method
Kubectl Azure Monitor Container Insights
Service DetailsParameter Description Data Collection Method
Kubectl Azure Monitor Container Insights
Universal unique ID of the
Service UUID
service.
Service Name Name of the service.
Name of the Namespace
Service
in which the service
Namespace
resides.
Name of the service
Application
application.
Service Type Type of the service.
Service Name of the service
Protocol protocol.
Host IP IP address of the service
Address host.
Service Target Name of the port that
Port connects with the service.
Timestamp at which the
Created Time
service was created.
Deployment Details
Deployment Universal unique ID of the
UUID deployment.
Deployment
Name of the deployment.
Name
Deployment Namespace where the
Namespace deployment exists.
Deployment The number of replicas in
Replicas a deployment.
Deployment
Number of available
Available
replicas in a deployment.
Replicas
Deployment Availability of the
Availability deployment.
Persistent Volumes
Parameter Description Data Collection Method
Kubectl Azure Monitor Container Insights
PERSISTENT VOLUMES (PV) DETAILS
Universal unique ID of the
PV UUID
Persistent Volume.
Name of the Persistent
PV Name
Volume.
Status of the Persistent
PV Status Volume. (Available, Bound,
Released, Failed, or Pending)
Name of the Persistent
PV Claim
Volume Claim.
The mode through which you
PV Access
can access the Persistent
Mode
Volume.
PV Storage Name of the Persistent
Class Volume storage class.
The capacity of the Persistent
PV Capacity
Volume (in GiB).Parameter Description Data Collection Method
Kubectl Azure Monitor Container Insights
Timestamp at which the
PV Created
Persistent Volume was
Time
created.
PERSISTENT VOLUMES CLAIM (PVC) DETAILS
Universal unique ID of the
PVC UUID
persistent volume.
Name of the Persistent
PVC Name
Volume Claim.
PVC Name of the Namespace in
Namespace which the Claim exists.
Status of the Persistent
Volume Claim. (Available,
PVC Status
Bound, Released, Failed, or
Pending)
Name of the Persistent
PV Name
Volume.
The mode through which you
PVC Access
can access the Persistent
Mode
Volume Claim.
PVC
Name of the Persistent
Storage
Volume storage class.
Class
PVC Number of Persistent Volume
Requests Claim requests (in GiB).
PVC Timestamp at which the
Created Persistent Volume Claim was
Time created.
Service Map
Displays a graphical map view containing namespace and service details.
All the namespace with its status and pods count for each phase will be seen inside cluster circle.
Green color indicates that the namespace is UP and red color indicates it is DOWN.
The cluster services under a namespace can be seen branching as a tree.
Each service contains its host IP address and port details.
Note: For metrics available in both Container insights and Azure Monitor, Applications Manager give
preference to Container Insight metrics if Container Insights is enabled.
OpenStack MonitoringOpenStack – An Overview
Creating a new OpenStack monitor
Monitored Parameters
OpenStack – An Overview
OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources,
providing a framework to create and manage both public cloud and private cloud infrastructures.
Creating a new OpenStack monitor
Prerequisites for adding a new OpenStack monitor: Click here
Using the REST API to add a new OpenStack monitor: Click here
To create a new OpenStack monitor, follow the steps given below:
Click on New Monitor link.
Select OpenStack under Cloud Apps category.
Specify the Display Name of the OpenStack server
Enter the Base Authentication URL of the OpenStack for accessing the OpenStack. The sample URL is:
http://openstack:5000/
Enter the Tenant Name. Tenant Name is the project name of the OpenStack
Choose the Credential Details either use below credentials or select from credential list
Enter the Username and Password of the OpenStack.
Select Need Proxy, if you require to give proxy server details
Select ProjectScopeToken, if the authorization scope is set to Project/Tenant.
Specify the Polling Interval in minutes.
Choose the Monitor Group with which you want to associate the OpenStack monitor to, from the combo box
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the OpenStack server from the network and starts monitoring it.
Note: If you require proxy server, you have to configure proxy settings under ''Admin'' tab.
Applications Manager automatically discovers all the OpenStack instances under your OpenStack account. You
can then enable monitoring for those instances and images as per your requirement.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the OpenStack monitor under the Cloud
Apps Table. Displayed is the OpenStack bulk configuration view distributed into three tabs:
Availability tab displays the Availability history for the past 24 hours or 30 days.
Performance tab displays the Health Status and events for the past 24 hours or 30 days along with key
performance indicators like Response Time.
List view enables you to perform bulk admin configurations and displays all the OpenStack instances along
with an overall idea of their availability and health status.
Openstack monitoring software like Applications Manager provides complete visibility into your OpenStack
environments altogether in a single window based on the following tabs:
Overview
Compute
Storage
Network
Overview
This tab provides a high-level overview of your OpenStack account as well as information about the OpenStack
instances present in this account.
Parameter Description
InstancesParameter Description
ID The unique ID of the server.
Name The name of the monitored instance.
The current status of the instance. The possible values are: ACTIVE, BUILDING, DELETED, ERROR,
Status PAUSED, RESCUED, RESIZED, SHELVED, SHELVED_OFFLOADED, SOFT_DELETED, STOPPED,
SUSPENDED.
A virtual machine image is a single file which contains a virtual disk that has a bootable operating
Image
system installed on it
Images
ID The unique ID of the image.
Name The name of the image uploaded to the image service.
The current status of the image. Images in Glance can be in one the following statuses:
queued - The image identifier has been reserved for an image in the Glance registry. No image
data has been uploaded to Glance and the image size was not explicitly set to zero on creation.
saving - Denotes that an image’s raw data is currently being uploaded to Glance. When an
image is registered with a call to POST /images and there is an x-image-meta-location header
present, that image will never be in the saving status (as the image data is already available in
some other location).
active - Denotes an image that is fully available in Glance. This occurs when the image data is
uploaded, or the image size is explicitly set to zero on creation.
Status
deactivated - Denotes that access to image data is not allowed to any non-admin user.
Prohibiting downloads of an image also prohibits operations like image export and image
cloning that may require image data.
killed - Denotes that an error occurred during the uploading of an image’s data, and that the
image is not readable.
deleted - Glance has retained the information about the image, but it is no longer available to
use. An image in this state will be removed automatically at a later date.
pending_delete - This is similar to deleted, however, Glance has not yet removed the image
data. An image in this state is not recoverable.
Visibility The scope of image accessibility. Possible values are ''public'', ''private'', ''shared'', ''community''.
The disk format of a virtual machine image is the format of the underlying disk image. Possible
values are:
aki - An Amazon kernel image.
ami - An Amazon machine image.
ari - An Amazon ramdisk image.
iso - An archive format for the data contents of an optical disc, such as CD-ROM.
qcow2 - Supported by the QEMU emulator that can expand dynamically and supports Copy on
Disk Write.
Format raw - An unstructured disk image format; if you have a file without an extension it is possibly a
raw format.
vdi - Supported by VirtualBox virtual machine monitor and the QEMU emulator.
vhd - The VHD disk format, a common disk format used by virtual machine monitors from
VMware, Xen, Microsoft, VirtualBox, and others.
vhdx - The VHDX disk format, an enhanced version of the VHD format, which supports larger
disk sizes among other features.
vmdk - Common disk format supported by many common virtual machine monitors.
Size The Size of the image to be uploaded.
Services
ID The unique ID of the service.
Name The name of the OpenStack service.
An endpoint is just a URL that can be used to access a service within OpenStack. An endpoint is just
Endpoint
like a point of contact for YOU (the user) to use an OpenStack service.
Response
The Service endpoint HTTP response status code.
CodeCompute
This tab provides information about the OpenStack Hypervisors and Compute Services present in this account.
Parameter Description
Hypervisors
The unique ID of the hypervisor. The format of the Hypervisor ID is a combination of ID and
ID
Hostname.
Hostname The hypervisor host name.
State The state of the hypervisor. Possible values are up,down.
Status The status of the hypervisor. Possible values are enabled, disabled.
Compute Services
The unique ID of the Compute Service. The format of the Compute Service ID is a
ID
combination of ID and Hostname.
Name The binary name of the service.
Hostname The name of the host.
Zone The availability zone name.
Compute Service
The state of the Compute service. Possible values are up, down.
State
Compute Service
The status of the Compute service. Possible values are enabled, disabled.
Status
Storage
This tab provides information about the OpenStack Cinder Services present in this account.
Parameter Description
Cinder Services
The unique ID of the Cinder Service. The format of the Cinder Service ID is a combination of
ID
name and hostname.
Name The binary name of the service.
Hostname The name of the host.
Zone The availability zone name.
Cinder Service
The state of the Cinder service. Possible values are up, down.
State
Cinder Service
The status of the Cinder service. Possible values are enabled, disabled.
Status
Network
This tab provides information about the OpenStack Neutron Agents present in this account.
Parameter Description
Neutron Agents
ID The unique ID of the resource.
Type The type of agent such as Open vSwitch agent or DHCP agent.
Hostname The hostname of the system the agent is running on.
Neutron Agent State The administrative state of the resource, which is up (true) or down (false).
Neutron Agent The status of the network agent (true/false). True indicates that the agent is alive and
Status running.
Microsoft 365 Monitoring
Microsoft 365 - An Overview
Monitoring Microsoft 365 - What we doCreating a new Microsoft 365 monitor (Video)
Monitored Parameters
Microsoft 365 - An Overview
Microsoft 365 (formerly Office 365) refers to a group of subscription plans that provide productivity software like
access to Office applications plus and related services. This includes server that are enabled over the internet
(cloud services), such as Lync web conferencing and Exchange Online hosted email for business and additional
online storage with OneDrive and Skype world minutes for home.
There are different tiers to Microsoft 365, such as personal, home and business. In its most basic form, you get
access to full Office desktop apps, mobile apps for Android and iOS, OneDrive storage, Skype minutes and more.
For business users, Microsoft 365 also offers service subscriptions for e-mail and social networking
services through hosted versions of Exchange Server, Skype for Business Server, SharePoint Office Online,
Microsoft Teams, and integration with Yammer.
Monitoring Microsoft 365 - What we do
Applications Manager''s Microsoft 365 monitoring provides operational intelligence into Microsoft 365
applications, including Exchange Online, SharePoint Online, Skype for Business, and Microsoft Teams. You can
view a holistic picture of the health and performance of Microsoft 365 deployments and associated services using
custom, interactive dashboards.
Exchange Online - Gather long-term data and present detailed reports for Exchange Online, such as mailbox
statistics, Exchange Online service health, endpoint connectivity and dozens of other details.
SharePoint Online - Get detailed metrics into the health and affected tenant count of SharePoint Online
services, including Access Services, Office Web Apps, Yammer components, etc. Applications Manager also
keeps track of the TCP connectivity of various SharePoint Online endpoints as well as the performance of
SharePoint applications and sites.
Skype For Business Online - Monitor key metrics of Skype for Business Online, including the health status of
services such as audio and video, federation, sign-in, etc. Checks for the connectivity status and response
time of various endpoints as well as the top sessions by duration.
Microsoft Teams - Track the key performance metrics such as the health status of services, connectivity
status and response time of various endpoints. Obtain useful insights about the number of members and
channels of all the teams in your organization, and get complete information on the usage statistics based on
various devices and activity types.
Note: Microsoft 365 Services are supported only on Windows installations of Applications Manager.
Applications Manager offers comprehensive performance monitoring for Microsoft 365, enabling admins to
minimize downtime and performance degradation as well as take corrective actions before any problems arise.
The latest monitoring capabilities in Applications Manager also include:
Microsoft 365 License Reporting and Management - Stay on top of the provisioning of licenses; manage
user licenses in bulk and know the actual Assigned License Count under each service type. Get organization
license information like Consumed Licenses, Locked out units, Suspended Units, Unassigned Licenses, Total
User Count, License and Tenant Name.
Microsoft 365 Service Health - You can view the health of Microsoft 365, and associated services on the
Service health page. If you are experiencing problems with a cloud service, you can check the service health
to see its Affected Tenant Count and Last Updated Time to determine if a resolution in progress before you
call support or spend time troubleshooting.
Endpoints Connectivity - Keep track of the TCP connectivity of various SharePoint Online endpoints as well as
the performance of SharePoint applications and sites.
Fix Performance Problems Faster - Get instant notifications of common performance issues with a cloud
service; check the service health to diagnose service incidents, drill down to their root cause and resolve them
quickly to ensure smooth and uninterrupted service delivery. Ensure Microsoft 365 applications are
consistently delivering a high-quality experience for end users
In this help document, you will learn how to get started with Microsoft 365 monitoring using Applications Manager.
Creating a new Microsoft 365 monitor
Mode of Monitoring: PowerShell
Prerequisites for monitoring Microsoft 365 metrics: Click hereUsing the REST API to add a new Microsoft 365 monitor: Click here
Follow the steps given below to create a new Microsoft 365 monitor:
Click on New Monitor link. Choose Microsoft 365.
Specify the Display Name of the Microsoft 365 monitor.
Enter the Domain Name/Tenant Name used to sign up for Microsoft 365. Example: The tenant name for
apm@apmtest.onmicrosoft.com is apmtest
Enter the Microsoft 365 admin account User Email.
Enter the Password for the Microsoft 365 admin email.
Choose Microsoft 365 Services: Exchange Online, Skype For Business Online, Sharepoint Online or Microsoft
Teams
Enable the Service Health Monitoring option to monitor the Service Health information. After enabling,
specify the following details:
Tenant ID: Enter the Tenant ID of the tenant in which the applicaton is created to monitor the service
health.
Client ID: Enter the Client ID/Application ID of the applicaton created to monitor the service health.
Client Secret: Enter the Client Secret created in the applicaton created to monitor the service health.
Note: Service Health monitoring is mandatory to monitor Microsoft Teams in Applications Manager.
Specify the polling interval in minutes and timeout in seconds.
Choose the Monitor Group from the combo box with which you want to associate Microsoft 365 monitor
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers Microsoft 365 from the network and starts monitoring them.
Create a new Microsoft 365 Monitor video
How to add O ce 365 Monitor?
Note: The Microsoft 365 admin account used for monitoring must be assigned the below roles: Exchange
administrator, SharePoint administrator or Skype For Business administrator
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the Microsoft 365 monitors under the
Cloud Apps table. Displayed is the Microsoft 365 bulk configuration view distributed into three tabs:
Availability tab displays the availability history for the past 24 hours or 30 days.
Performance tab displays the health status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configuration.
Click on the monitor name to see all the server details listed under the following tabs:
Overview
Exchange Online
Sharepoint Online
Skype For Business Online
Microsoft Teams
OverviewParameter Description
USER DETAILS
Total User
The total number of users for the Microsoft 365 subscription
Count
Licensed
The number of user accounts with license.
User Count
Unlicensed
The number of user accounts without license.
User Count
License Details
License
The name of the license plan.
Name
Total
License The number of licenses that have been purchased for a specific licensing plan.
Count
Consumed
The number of licenses that have been assigned to users from a specific licensing plan.
Licenses
Unassigned
The number of licenses available for assignment
Licenses
Warning The number of licenses in a licensing plan that you haven''t renewed, and that will expire after the
Units 30-day grace period.
Locked Out
The number of accounts that have been locked out
Units
Suspended
The number of accounts that have been suspended
Units
Microsoft 365 Service Health Details
Service ID ID of the Microsoft 365 service.
Service
Name of the service.
Name
Overall status of the service. Possible values are serviceOperational, investigating,
restoringService, verifyingService, serviceRestored, postIncidentReviewPublished,
Service
serviceDegradation, serviceInterruption, extendedRecovery, falsePositive,
Status
investigationSuspended, resolved, mitigatedExternal, mitigated, resolvedExternal, confirmed,
reported, or unknownFutureValue.
Microsoft 365 Service Issue Details
Service ID -
Feature
Group - Indicates the Service ID, Feature Group, Feature, and Issue ID of the Microsoft 365 service issue.
Feature -
Issue ID
Status of the service issue. Possible values are serviceOperational, investigating, restoringService,
Issue verifyingService, serviceRestored, postIncidentReviewPublished, serviceDegradation,
Status serviceInterruption, extendedRecovery, falsePositive, investigationSuspended, resolved,
mitigatedExternal, mitigated, resolvedExternal, confirmed, reported, and unknownFutureValue.
Issue Type Type of the service issue. Possible values are advisory, incident, or unknownFutureValue.
Origin of the service issue. Possible values are microsoft, thirdParty, customer, or
Issue Origin
unknownFutureValue.
Issue
Indicates the description for the service issue.
Description
Hour(s)
since issue Amount of time (in hours) elapsed since the issue has occurred.
occurred
Issue Start
Timestamp at which the service issue was started.
Time
Last
Modified Timestamp at which service issue was last modified.
Time
Endpoints ConnectivityParameter Description
Endpoint The Microsoft 365 endpoint / URL.
Port The port on which endpoint / URL is accessible.
Status The status of endpoint/ URL.
Response
The time taken for connecting to endpoint/URL.
Time
Exchange Online Monitoring
Exchange Online - An Overview
Monitoring Exchange Online - What we do
Monitored Parameters
Exchange Online - An Overview
Exchange Online is a business-class email and calendaring service developed by Microsoft and hosted in the
public cloud. It is available as a stand-alone service or as part of an Microsoft 365 plan. Exchange Online provides
the benefits of a cloud-based email service with the robust capabilities of an on-premises Exchange server
deployment.
Monitoring Exchange Online - What we do
Applications Manager gathers long-term data and present detailed reports for Exchange Online, such as mailbox
statistics, Exchange Online service health, endpoint connectivity and dozens of other details.
Note: Microsoft 365 Services are supported only on Windows installations of Applications Manager
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the Exchange Online monitors under the
Cloud Apps table. Displayed is the Exchange Online bulk configuration view distributed into three tabs:
Availability tab displays the Availability history for the past 24 hours or 30 days.
Performance tab displays the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
You can also navigate to the Exchange Online bulk configuration view through the Exchange Online tab in the
Microsoft 365 Monitor page.
Click on the monitor name to see all the server details listed under the following tabs:
Overview
Mailbox Statistics
Overview
Parameter Description
Exchange Online Service Health Details
Service ID ID of the Exchange Online service.
Service
Name of the service.
Name
Overall status of the service. Possible values are serviceOperational, investigating,
restoringService, verifyingService, serviceRestored, postIncidentReviewPublished,
Service
serviceDegradation, serviceInterruption, extendedRecovery, falsePositive,
Status
investigationSuspended, resolved, mitigatedExternal, mitigated, resolvedExternal, confirmed,
reported, or unknownFutureValue.
Exchange Online Issue DetailsParameter Description
Feature
Group -
Indicates the Feature Group, Feature, and Issue ID of the Exchange Online service issue.
Feature -
Issue ID
Status of the service issue. Possible values are serviceOperational, investigating, restoringService,
Issue verifyingService, serviceRestored, postIncidentReviewPublished, serviceDegradation,
Status serviceInterruption, extendedRecovery, falsePositive, investigationSuspended, resolved,
mitigatedExternal, mitigated, resolvedExternal, confirmed, reported, and unknownFutureValue.
Issue Type Type of the service issue. Possible values are advisory, incident, or unknownFutureValue.
Issue Origin of the service issue. Possible values are microsoft, thirdParty, customer, or
Origin unknownFutureValue.
Issue
Indicates the description for the service issue.
Description
Hour(s)
since issue Amount of time (in hours) elapsed since the issue has occurred.
occurred
Issue Start
Timestamp at which the service issue was started.
Time
Last
Modified Timestamp at which service issue was last modified.
Time
Endpoints Connectivity
Endpoint The Exchange Online endpoint / URL
Port The port on which endpoint / URL is accessible
Status The status of endpoint/ URL
Response
The time taken for connecting to endpoint/URL
Time
Mailbox Statistics
Parameter Description
Top Mailboxes by Size
Mailbox UserName The mailbox account username
Total Mailbox Size(MB) The total size of Mailbox in MB
Number of Items The number of items in mailbox
Inactive Mailbox Users
Mailbox UserName The Mailbox account username
Last Logon Time The last Login Time of Mailbox User
SharePoint Online Monitoring
Sharepoint Online - An Overview
Monitoring Sharepoint Online - What we do
Monitored Parameters
SharePoint Online - An Overview
SharePoint online is a cloud-based service that allows organizations store, retrieve, search, archeive, track,
manage, and report on digitized documents. It is available as a standalone product. SharePoint Online comes in
handy when the security requirements are complex and when content management requires custom workflows.
Monitoring SharePoint Online - What we do
Get detailed metrics into the health and affected tenant count of SharePoint Online services, including Access
Services, Office Web Apps, Yammer components, etc. Applications Manager also keeps track of the TCPconnectivity of various SharePoint Online endpoints as well as the performance of SharePoint applications and
sites.
Note: Microsoft 365 Services are supported only on Windows installations of Applications Manager
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the Sharepoint Online monitors under
the Cloud Apps table. Displayed is the SharePoint Online bulk configuration view distributed into three tabs:
Availability tab displays the Availability history for the past 24 hours or 30 days.
Performance tab displays the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
You can also navigate to the Sharepoint Online bulk configuration view through the Sharepoint Online tab in the
Microsoft 365 Monitor page.
Click on the monitor name to see all the server details listed under the following tabs:
Overview
Sites and Applications
Overview
Parameter Description
Sharepoint Online Service Health Details
Service ID ID of the Sharepoint Online service.
Service
Name of the service.
Name
Overall status of the service. Possible values are serviceOperational, investigating,
restoringService, verifyingService, serviceRestored, postIncidentReviewPublished,
Service
serviceDegradation, serviceInterruption, extendedRecovery, falsePositive,
Status
investigationSuspended, resolved, mitigatedExternal, mitigated, resolvedExternal, confirmed,
reported, or unknownFutureValue.
Sharepoint Online Issue Details
Feature
Group -
Indicates the Feature Group, Feature, and Issue ID of the Sharepoint Online service issue.
Feature -
Issue ID
Status of the service issue. Possible values are serviceOperational, investigating, restoringService,
Issue verifyingService, serviceRestored, postIncidentReviewPublished, serviceDegradation,
Status serviceInterruption, extendedRecovery, falsePositive, investigationSuspended, resolved,
mitigatedExternal, mitigated, resolvedExternal, confirmed, reported, and unknownFutureValue.
Issue Type Type of the service issue. Possible values are advisory, incident, or unknownFutureValue.
Issue Origin of the service issue. Possible values are microsoft, thirdParty, customer, or
Origin unknownFutureValue.
Issue
Indicates the description for the service issue.
Description
Hour(s)
since issue Amount of time (in hours) elapsed since the issue has occurred.
occurred
Issue Start
Timestamp at which the service issue was started.
Time
Last
Modified Timestamp at which service issue was last modified.
Time
Endpoints Connectivity
Endpoint The Sharepoint Online endpoint / URL
Port The port on which endpoint / URL is accessibleParameter Description
Status The status of endpoint/ URL
Response
The time taken for connecting to endpoint/URL
Time
Sites and Applications
Parameter Description
Sites Statistics
Site URL The sharepoint Site URL
Storage Used (GB) The storage used by sites in GB
Storage Free (GB) The storage free for use for site in GB
Resources Used The resources used out of allocated limit
Resources Free The resources free for use from allocated limit.
Lock State The lock status of site.
Last Content Modified
The last content modified time of sharepoint site.
Time
Status The status of site.
Websites Count The number of websites in sharepoint site collection.
Application Statistics
Product ID Unique ID of the SharePoint application.
Application Name Name of the SharePoint application.
Source Source of the SharePoint application.
Install Errors Number of errors occurred during installation of SharePoint application.
Runtime Errors Number of errors occurred during runtime of SharePoint application.
Upgrade Errors Number of errors occurred during upgrade of SharePoint application.
Skype for Business Online Monitoring
Note: Skype for Business Online monitoring is not supported from Applications Manager version 15340
onwards as it has reached end of support. Please unmanage or delete this monitor if already present. By
default, these monitors will be unmanaged from version 15340 onwards.
Skype for Business - An Overview
Monitoring Skype for Business - What we do
Monitored Parameters
Skype for Business - An Overview
Skype for Business (formerly known as Microsoft Lync Server) is a unified communications (UC) platform that
integrates common channels of business communication and online meetings, including instant messaging (IM),
presence, voice over IP (VoIP), voicemail, file transfers, video conferencing, web conferencing and email.
Skype for Business can be deployed on premises, in the cloud or as a hybrid service.
Monitoring Skype for Business - What we do
Monitor key metrics of Skype for Business Online, including the health status of services such as audio and video,
federation, sign-in, etc. Checks for the connectivity status and response time of various endpoints as well as the
top sessions by duration.
Note: Microsoft 365 Services are supported only on Windows installations of Applications Manager.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the Skype for Business monitors under
the Cloud Apps table. Displayed is the Skype for Business bulk configuration view distributed into three tabs:Availability tab displays the Availability history for the past 24 hours or 30 days.
Performance tab displays the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
You can also navigate to the Skype for Business bulk configuration view through the Skype for Business tab in the
Microsoft 365 monitor page.
Overview
Sessions *
Note: Tabs/attributes marked with * have been removed from the UI as the APIs used to fetch these details
have been deprecated.
Overview
Parameter Description
Skype For Business Online Service Health
Service – Feature The Skype For Business Online Service – Feature Name.
Status The status of the Service – Feature.
Affected Tenant Count The number of tenants potentially affected by service incident.
Affected User Count The number of users potentially affected by service incident.
Last Updated Time The last updated time for service incident.
Description The description of the service incident.
Endpoints Connectivity
Endpoint The Skype For Business Online endpoint / URL.
Port The port on which endpoint / URL is accessible.
Status The status of endpoint / URL.
Response Time The time taken for connecting to endpoint/URL.
Sessions *
Parameter Description
Top Sessions Statistics *
From URI The user’s SIP URI from which the call was made.
To URI The user’s SIP URI to which the call was made.
Call Duration (Minutes) The length of calls (actively connected) in a time slot.
Media Type The media type - Conference, IM, Audio, Video
Microsoft Teams Monitoring
Microsoft Teams - An Overview
Microsoft Teams is a proprietary business communication platform developed by Microsoft, as part of the
Microsoft 365 family of products. Teams primarily competes with the similar service Slack, offering workspace
chat and video conferencing, file storage, and application integration. Also, it helps you to replace other Microsoft-
operated business messaging and collaboration platforms, including Skype for Business and Microsoft
Classroom.
Monitoring Microsoft Teams - What we do
Applications Manager''s Microsoft Teams monitoring helps you to keep track of the key performance metrics such
as the health status of services, connectivity status and response time of various endpoints. Obtain useful insights
about the number of members and channels of all the teams in your organization, and get complete information on
the usage statistics based on various devices and activity types.
Note: Microsoft 365 Services are supported only on Windows installations of Applications ManagerMonitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the MS Teams monitors under the Cloud
Apps table. Displayed is the Microsoft Teams bulk configuration view distributed into three tabs:
Availability tab displays the Availability history for the past 24 hours or 30 days.
Performance tab displays the Health Status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
You can also navigate to the Microsoft Teams bulk configuration view through the Microsoft Teams tab in the
Microsoft 365 monitor page.
Click on the monitor name to see all the server details listed under the following tabs:
Overview
Teams and Channels
Usage
Overview
Parameter Description
Microsoft Teams Service Health Details
Service ID ID of the Microsoft Teams service.
Service
Name of the service.
Name
Overall status of the service. Possible values are serviceOperational, investigating,
restoringService, verifyingService, serviceRestored, postIncidentReviewPublished,
Service
serviceDegradation, serviceInterruption, extendedRecovery, falsePositive,
Status
investigationSuspended, resolved, mitigatedExternal, mitigated, resolvedExternal, confirmed,
reported, or unknownFutureValue.
Microsoft Teams Issue Details
Feature
Group -
Indicates the Feature Group, Feature, and Issue ID of the Microsoft Teams service issue.
Feature -
Issue ID
Status of the service issue. Possible values are serviceOperational, investigating, restoringService,
Issue verifyingService, serviceRestored, postIncidentReviewPublished, serviceDegradation,
Status serviceInterruption, extendedRecovery, falsePositive, investigationSuspended, resolved,
mitigatedExternal, mitigated, resolvedExternal, confirmed, reported, and unknownFutureValue.
Issue Type Type of the service issue. Possible values are advisory, incident, or unknownFutureValue.
Issue Origin of the service issue. Possible values are microsoft, thirdParty, customer, or
Origin unknownFutureValue.
Issue
Indicates the description for the service issue.
Description
Hour(s)
since issue Amount of time (in hours) elapsed since the issue has occurred.
occurred
Issue Start
Timestamp at which the service issue was started.
Time
Last
Modified Timestamp at which service issue was last modified.
Time
Endpoints Connectivity
Endpoint The Microsoft Teams endpoint / URL.
Port The port on which endpoint / URL is accessible.
Status The status of endpoint / URL.
Response
The time taken for connecting to endpoint / URL (in milliseconds).
TimeTeams and Channels
Parameter Description
Team Details
Team Name Name of the team.
Team ID Unique identifier assigned for the team.
Description Gives the description about the team.
Channel Count Number of channels created in the team.
Member Count Number of members added to the team.
Channel Details
Channel Name Name of the channel.
Team Name The team in which the channel is present.
Channel ID Unique identifier assigned for the channel.
Description Gives the description about the channel.
Member Count Number of members added to the channel.
Note: While monitoring Channel Details, there are instances where data might not be shown for Member
Count attribute. To resolve this, refer here.
Usage
Parameter Description
Collected Date
Collected date for usage data Date from which the usage data is collected.
NUMBER OF USERS BASED ON DEVICE TYPE PER DAY
Web (Users Per Day) Number of users using Microsoft Teams from the Web per day.
Number of users using Microsoft Teams from the Windows Phone per
Windows Phone (Users Per Day)
day.
Number of users using Microsoft Teams from the Android Phone per
Android Phone (Users Per Day)
day.
iOS (Users Per Day) Number of users using Microsoft Teams from the iOS per day.
Mac (Users Per Day) Number of users using Microsoft Teams from the Mac per day.
Windows (Users Per Day) Number of users using Microsoft Teams from the Windows per day.
NUMBER OF USERS BASED ON DEVICE TYPE IN LAST 30 DAYS
Number of users using Microsoft Teams from the Web in the last 30
Web (Users Per Month)
days.
Number of users using Microsoft Teams from the Windows Phone in the
Windows Phone (Users Per Month)
last 30 days.
Number of users using Microsoft Teams from the Android Phone in the
Android Phone (Users Per Month)
last 30 days.
Number of users using Microsoft Teams from the iOS in the last 30
iOS (Users Per Month)
days.
Number of users using Microsoft Teams from the Mac in the last 30
Mac (Users Per Month)
days.
Number of users using Microsoft Teams from the Windows in the last 30
Windows (Users Per Month)
days.
USER COUNT BASED ON ACTIVITY TYPE
Team Chat Messages (Users Per Day) Number of users doing team chat messages per day.
Private Chat Messages (Users Per Day) Number of users doing private chat messages per day.
Calls (Users Per Day) Number of users doing calls per day.
Meetings (Users Per Day) Number of users doing meetings per day.
ACTIVITY COUNT BASED ON ACTIVITY TYPEParameter Description
Team Chat Messages (Activity Count
Total number of team chat messages done by all users per day.
Per Day)
Private Chat Messages (Activity Count
Total number of private chat messages done by all users per day.
Per Day)
Calls (Activity Count Per Day) Total number of calls done by all users per day.
Meetings (Activity Count Per Day) Total number of meetings done by all users per day.
Custom Monitors
The following custom monitors are available in Applications Manager.
JMX / SNMP Dashboard
File / Directory Monitor
Windows Performance Counters
Script Monitors
Database Query Monitor
JMX / SNMP Dashboard
These custom monitors provide a real-time, correlated view of the entire application stack improving J2EE/J2SE
application performance by monitoring its data sources such as JMX MBean source and SNMP Agents.
JMX / SNMP Dashboard is a logical grouping that consist of data sources such as JMX MBean and SNMP OID. It can
have both the JMX and SNMP attributes.
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Building JMX / SNMP Dashboard involves
Creating JMX / SNMP Dashboard and adding it to a specific Monitor Group
Adding Attributes
The advantage of creating the dashboard is to monitor various data source at a common place.
Creating a JMX / SNMP Dashboard
For example, you have a Java application with built-in manageability using JMX and any application that has an
SNMP interface, then they are managed by building JMX / SNMP Dash Board.
To create a JMX / SNMP Dash Board, follow the given steps:
Select New Monitor. Choose JMX / SNMP Dashboard.
Provide any name for the custom monitor and a description.
Click Add JMX / SNMP Dashboard to create the custom monitor. This opens a screen that allows you to add
attributes for custom monitors.
Note:
In case you are unable to add the monitor even after enabling JMX, try providing the below argument:
-Djava.rmi.server.hostname=[YOUR_IP]
The next step is to build the custom monitor to enable monitoring your data sources.
You need to discover JMX MBeans and SNMP Agent data source to add attributes. The following are the JMX MBean
resources whose MBean attributes are monitored by Applications Manager using Custom Monitor.
Troubleshoot: Having trouble in monitoring custom applications? Refer the Online Troubleshooting section.
Adding AttributesOnce you add a JMX / SNMP Dashboard, the Add Attributes option is available. Click that to add custom attributes
to your Custom Monitor. The following are the data source for which custom monitors are built by Applications
Manager. Click on the topics to view the steps required to add the respective data sources or attributes to the
Custom Monitor.
Adding JMX MBean Attributes.
Adding SNMP OID Attributes.
Adding JMX MBeans Attributes
The following are the JMX MBean resources whose MBean attributes are monitored by Applications Manager using
Custom Monitor:
JMX [MX4J / JDK 1.5]
WebLogic Server
JBoss Server
To add the attributes, follow these steps:
In the Add Attributes screen, select the JMX MBean resource from the combo box and click Add. You can also
discover a resource using Add Monitorprovided alongside the combo box and add them to the list of
resources.
Select the domains and click Show MBeans to list all the MBeans of those domains. You can also specify some
filter criteria to match the MBean names. Alternatively, you can add the MBean atrributes directly, by choosing
the Add the MBean attributes directly option. You can enter the MBean ObjectName, Attribute Name and
Attribute Type (String / Numeric) and then add that attribute to be monitored. For Numeric attributes, you can
edit and set whether you want to view the values as Counters or Non Counters. From the next poll onwards, the
latest type would be displayed.
On clicking Show MBeans button, you get the list of all the MBeans. Select the MBean (all attributes) or only the
required attribute(s) by enabling the check box provided alongside. In case of tabular MBeans, select the
attribute (all columns) or only the required columns.
Click Add Attributes. All the selected attributes will be listed with their details. Note: You have an option to
enable / disable reports for scalar numerical attributes, which is indicated through the above images in the
Reports column. Refer to Viewing Reports for more details on report generation.
Click the Back to Details Page button to view the newly created Custom Monitor. This screen lists all the
attributes added.
If you want to add or delete attributes, click Add or Delete Custom Attributes.
Note:
If the JMX data source is WebLogic Server 6.1 or WebLogic 6.1 sp1, you have to specify the full object name in
the filter criteria to get the MBean attributes. This is because of the implementation bug in WebLogic 6.1.
However, versions WebLogic 6.1 SP2 and above do not have this problem.
Note: Steps to Create JMX Notification Listener (JMX [MX4J / JDK 1.5])
In the JMX [MX4J / JDK 1.5] Monitor page, click on the ''Create new JMX Notification Listener'' link.
The first step is to choose the Domain of the JMX Agent. After selecting the Domain, Click on ''Show
MBeans'' to view the MBeans that belong to the selected Domain.
The second step is to choose the Mbeans from the list that is shown.
The third step will be to create the new JMX Notification Listener. Enter the Name and select the status of
the Listener as enabled or disabled. Set the severity of the Alarm that will be generated once a JMX
notification is received, as Critical/Warning/Clear. Associated actions that need to be executed when the
notification is received can be chosen from the list of actions configured.
Clicking on ''Save'' will have a JMX Notification Listener configured, which would generate alarms of the
configured severity and execute actions.
Adding SNMP OID Attributes
Once the Custom Monitor is created, you have to add the required SNMP attributes added to it. Follow these steps:
Click on Add attributes link.It opens up Customize screen - Select a SNMP monitor from the combo box for adding the attributes. Click
add.
Mib Browser opens up - select the MIB that contains the attribute to be added to the Custom Monitor.
Select the attributes that you want to monitor. Click Add to add the selected attributes.
Note:
The MIB, whose attributes are required to be added to the Custom Monitor, must be present in the
/working/mibs directory of Applications Manager. To add the MIBs to the
directory, use Add Mib Form.
The MIB must be implemented in the SNMP Agent being monitored.
File / Directory Monitor
Creating a new monitor
Monitored Parameters
Configuring RCA Message for File Monitor
Creating a new File/Directory monitor
Using the REST API to add a new File/Directory monitor: Click here
To create a file / directory monitor, follow the steps given below:
From the New Monitor link, select File / Directory Monitor.
Provide a Display Name for the monitor.
Select whether it is a File or Directory monitor.
Specify whether the File / Directory to be monitored is in the Local or Remote Server.
If it is in the Local Server, provide the absolute path to the file / directory.
If it is in the Remote Server, either select the Host Name from the dropdown or create a new host, and
then provide the file / directory''s absolute path.
You can create a new host by entering a new hostname / IP address and login credentials of the host.
You can either enter the credential details like user name, password, the command prompt or
select the required credential from the Credential Manager list. Select the Mode Of Monitoring
(WMI for Windows, Telnet / SSH for Linux), the port and the Command Prompt, if required. Also,
there is an option to Resolve Hostname / IP, enabling which will resolve the entered IP address to its
corresponding hostname.
The new hosts that are created can also be deleted by selecting the required host and clicking on the
Delete Host link. However, hostnames that are already present and configured for server monitoring
cannot be deleted in this manner.
For a File monitor, select the Do Content Check checkbox if you wish to run a content check. If this checkbox is
enabled, perform the following steps:
Choose between the File Parsing Options to perform a content check to Only appended content or the
Whole File.
Select the required option under Monitor Severity to perform this content check to change the Health or
Availability severity status.
You can add criteria based on which the content check can be performed to change the Health or
Availability severity by clicking on the Create New Rule link. This opens a new window where you can add
new rules.
Under this window, select the severity criteria for Health (CRITICAL / WARNING / CLEAR) or Availability
(UP / DOWN) from the Severity drop-down menu.
Enter the string for which you want to check content matching in the Content to be searched text box. You
can add/remove multiple strings using the (+ / -) button.
There are two conditions to configure the monitor status:
Any: When this option is chosen, the monitor status will be affected based on the chosen Severity
criteria if any of the contents from the above Content textbox match. Also, you can enter the number
of contents to be checked in the corresponding textbox if you wish to check for more than one string.
All: If all of the content matches, the monitor status will become UP / DOWN. The monitor status will
be affected based on the chosen Severity criteria.You can perform a content check for regular expressions by enabling the Do Regular Expression Search
checkbox (Refer Regex Guide for more info).
You can perform a content check for case sensitive character strings by enabling the Do Case Sensitive
Search checkbox.
Enable the Clear monitor status when the file is not modified checkbox to control content check when
the file is not updated during the polling interval. If this option is enabled and the file was not updated,
then the current monitor status will be set for Availability as UP and Health as CLEAR. However, this option
is displayed only after selecting the Only appended content option under File Parsing Options.
For both File and Directory monitor, you can enable the Do file / directory age check checkbox to change the
monitor status to UP / DOWN if the file/directory is MODIFIED / NOT MODIFIED within a certain time period.
For Directory monitor, enable the Filter files in directory option to filter files in the given directory (does not
include Sub-directories) and generate alerts. After enabling, enter the following details:
File Name: File name pattern with which the files need to be filtered in the directory.
Filter Category: Parameters based on which the files need to be filtered. Files can be filtered based on
their Size, Last Modified Time, and Created Time (supported only for Windows directory).
Alert for Severity: The severity with which alert needs to be raised when the above specified conditions
are met.
Enable the Alert when file / directory doesn''t exist checkbox for alerting when the required file / directory to
be monitored is not found.
Enter the Polling interval time period in minutes and the Timeout in seconds.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the dropdown to which you want to associate the Monitor (optional). You can
choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the file/directory from the network and starts monitoring them.
Note:
Applications Manager cannot perform multiple regex checks.
The file present in a remote Windows server cannot be monitored by using the Applications Manager
which is installed in the Linux OS.
The severity of the monitor will be affected based on the order of the criteria configured.
The content match will be not proceeded to next criteria when the match is found.
When the content match is configured with Availability as DOWN or Health as CRITICAL / WARNING for
Primary Severity, and if the content match is not found, then the alert will be triggered for Monitor Severity
Availability as UP and Health as CLEAR respectively.
Similarly when the content match is configured for Availability as UP or Health as CLEAR for Primary
Severity, and if the content match is not found, then the alert will be triggered for Monitor Severity
Availability as DOWN and Health as CRITICAL respectively. If the user wishes to retain previous severity
with Availability as UP or Health as CLEAR, then ''Clear monitor status when the file is not modified''
option can be chosen.
Limitations for ''Check Content'' String:
For Windows file, double quotes (") will be not be supported .
For Non-Windows file, double quotes(") needs to be prepended with backslash as (\").
Monitored Parameters
Applications Manager uses this File / Directory Monitor to monitor the changes in the selected files and directories.
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configuration. Click on the individual monitors listed, to view the
following information.
File Monitor
Parameter Description
File size The size of the file. (KB)
Change in File Size The amount of change in file size. (KB)
% Change in File Size The amount of change in file size. (%)File Modified Duration The modified time duration of the file. (Minutes)
Last Modified Time The time at which the file was last modified.
Contents Matched Displays the matched contents.
Directory Monitor
Parameter Description
Directory Size The size of the directory. (MB)
Change in Directory Size The amount of change in directory size. (MB)
% Change in Directory Size The amount of change in directory size. (%)
Directory Modified Duration The modified time duration of the directory. (Minutes)
Total No. of Subdirectories The subdirectory count of a directory.
Total No. of Files The total number of files available in the directory.
Total No. of Files (in Main Folder) The total number of files available under the main folder in the directory.
Directory Modified Duration Amount of time elapsed since the directory was last modified (in minutes).
View Filtered Files Displays the list of files that are filtered in the directory.
Last Modified Time The time at which the directory was last modified.
Configuring RCA Message for File Monitor
The Root Cause Analysis message of the File monitor can be configured by navigating to Admin -> Performance
Polling -> Optimize Data Collection -> File / Directory Monitor. There are 3 different options available:
Content match File link: This is the default option in which the contents that have been matched will be shown
in the RCA message along with the link to the HTML file that contains line number and lines in which content
was matched.
Last Matched Lines: The last matched lines for the configured content will be added to the RCA message
along with the default content file match link.
All matched content: All the matched content is appended on to the RCA file along with the default content
file match link.
Note: All matched content option is only available for files hosted on linux servers and the last matched line
is appended for files hosted on windows servers.
Database Query Monitoring
Overview
Database Query Monitor is used to monitor a single query or a set of queries for any given database. This SQL-
based query monitor allows user to monitor the status of that particular query.
Creating a new Database Query monitor
Using the REST API to add a new DB Query Monitor: Click here
To create a new Database Query Monitor, follow the below given steps:
Click New Monitor and select Add New Monitor. Choose Database Query Monitor.
Enter the Display Name of the Monitor.
Select the Database for which the query is being executed. The Database Query monitor currently supports
queries of the following databases - DB2, Informix, Ingres, MS SQL, MySQL, Oracle, Oracle RAC, Postgres,
Sybase, DB2 for i, SAP HANA (on-premise) and SAP Max DB. The DB2 for i database will be shown only for
trail users and the Users with AS400 Add-on.
Enter the Host Type of the Monitor on which the database is running - New or Existing (You can select the an
existing host from a drop-down list).
Enter the Hostname or IP Address of the host.
Enter the Port number in which the database is running.Select the Enable Kerberos Authentication checkbox if you want to monitor MS SQL database through
Kerberos authentication.
Enter the Username and Password of the database server.
Enter the Database name.
If you want to connect using a Named Instance, enable the Connect using Named Instance checkbox and
specify the instance name for MS SQL database.
Check the SSL is enabled checkbox if SSL authentication is enabled for MySQL, MS SQL, Oracle and
PostgreSQL databases.
Choose jTDS JDBC Driver or Microsoft JDBC Driver option in Driver for SQL Server Connection field to
choose the required driver for connecting to the MS SQL database for data collection.
Enter the Query. Please note that the number of queries is limited to five queries. Also, note that the delimiter
for a query is new line.
Select whether you would prefer Query Output by choosing the Yes or No radio button.
If a table row is unavailable in the next poll, you can configure appropriate table row actions (Retain, Delete or
Unmanage) by enabling the Manage Table Row option.
Enter the Polling Interval. By default, it is 5 minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which you want to associate Database Query monitor.
Limitation:
From the Enterprise Edition Admin Server, only the following database types are supported for Database
Query Monitoring - MySQL, Oracle, DB2, MsSQL, Sybase, PostgreSQL, SAP HANA and SAP MaxDB.
Enable Configure Alarms Template for Database Query Monitor
You can enable a link to Configure Alarms (link will appear on the right top corner of each table in your Database
Query Monitor page). Using the link, the user can set Predefined Thresholds for any attributes in the table.
Here is how you can enable Configure Alarms Template for Database Query Monitor:
Go to the Admin tab.
Click Performance Polling under Discovery and Data Collection.
Under Performance Data Collection, click on the Optimize Data Collection tab.
Choose Script / Database Query Monitor from the drop-down menu.
Check the Enable Configure Alarm Template for Script Monitor and Database Query Monitor option.
The Configure Alarm link will appear on the right top corner of each table in your Database Query Monitor
page.
Monitored Parameters
Database Query Monitor is used to monitor a single or a specific set of queries for any given database.
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Using a single query or a given set of queries, you can monitor the status of any given database using Applications
Manager Database Query monitor. Queries are the best way to find out whether your database is up and running
24x7. In business enterprises such as an online store, there are a number of applications and databases used for e-
commerce. Any interruption in such an environment could mean only one thing: loss of revenue.
The execution of such a query or a set of queries can be automated by setting the polling interval. By fixing the
polling interval, user can automate this process and the results are obtained at the end of the polling. The result
includes execution time (time taken by the query to provide results) and also displays any error that may occur
during regular polling intervals. These errors help identify any issue that may occur with the database.
Let us consider an example. Many enterprise environment run critical applications which need to be up and
running 24x7. Let us assume, the status of such applications are maintained in a "APPLICATION_STATUS" table.
Using Database Query monitor, the user shall be able to send a select set of queries to that database to find out if
they are operational or not.
|-----------------------------------------------------------|
| APPLICATIONS_STATUS |
|-----------------------------------------------------------|
| APPLICATIONS_NAME | Status ||-----------------------------------------------------------|
| PURCHASE | OK |
| CRM | CRITICAL |
| PAYROLL | OK |
| LEADS | OK |
|-----------------------------------------------------------|
SELECT * APPLICATIONS_STATUS
By executing the above command using Database Query monitor, the user will then obtain the list of applications
that are running along with its status. The user can then identify the applications whose status is ''Critical'' and then
carry out necessary action by configuring Alarms in Applications Manager. This action could be in the form of
creating a ticket, or executing a script to rectify the problem.
Database Query monitor can also be used to identify any bottle necks in the networks which are linked to several
databases and help remove them by identifying the correct database which has the issue. This bottle neck issue
can arise because there is a problem with the one of applications or with the databases. Using Database Query
monitor, user can then execute a given set of queries and analyze the result which provides a clear indication of the
error that has caused such an occurance. The result includes the execution time (time taken by the query to
generate the result). If the execution time is above a certain pre-assigned threshold, then the issue is with the
database or if the result is below the pre-assigned threshold, then the issue is elswhere.
Supported Databases
The Database Query monitor currently supports queries of the following databases:
DB2
Informix
Ingres
MS SQL
MySQL
Oracle
Oracle RAC
Postgres
Sybase
SAP HANA
SAP MaxDB
DB2 for I
SAP MaxDB
SAP HANA
Applications Manager also provides the ability to compare various column value in the output by attributes types.
Option to Enable or Disable Reports is provided.
Note: Please note that the number of queries is limited to five queries. Total number of rows shown in the
output is limited to 50 rows.
Here is a list of the compatible JDBC URLs for Oracle database type under Database query monitor:
jdbc:oracle:thin:@HOSTNAME:PORTNUMBER:INSTANCE
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=HOSTNAME)
(PORT=PORTNUMBER)))(CONNECT_DATA=(SID=INSTANCE)(SERVER=DEDICATED)))
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=HOSTNAME)(PORT=PORTNUMBER))
(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=INSTANCE)))
jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=yes)(ADDRESS=(PROTOCOL=TCP)(HOST=NODE1-VIP)
(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=NODE2-VIP)(PORT=1521))(CONNECT_DATA=
(SERVER=DEDICATED)(SERVICE_NAME=MYRAC)))Support for Stored Procedures in Database Query Monitor
We have added support for Stored Procedures for all databases that we support in Database Query Monitor. We
support Stored Procedures which returns only one Result Set.
To Enable Stored Procedures, go to Admin → Performance Polling → Optimize Data Collection → Script /
Database Query Monitor and select Enable Stored Procedure Monitoring for Database Query Monitor.
FAQs and Troubleshooting
1. How can I form an SQL Query?
The query should be in a single line and maximum of 2000 characters. Please note that the number of queries is
limited to five queries in one monitor. Also, note that the delimiter for query is new line. Total number of rows
shown in the output is limited to 50 rows.
If there is more than one column in the results, we recommend that you set a column which has string values as
primary key in the monitor.
The query should have an identifier. For queries involving counts we recommend you have a dummy column and
use that as primary key.
Let''s take the example below:
Select ''count'' as value, count(*) as alert_count from alert;
In the above query, we the identifier is alert_count and a dummy primary column is set called value. Whenever this
query is executed during the polling we store the actual count values based on the primary key selection. In this
case, the primary key is alert_count.
You can configure an alarm for the count attribute and then define a threshold value.
For reference: https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/ef/language-
reference/identifiers-entity-sql
2. How can I form SQL Queries when using Aggregate functions like count, min,
max etc?
The query should be in a single line and maximum of 2000 characters. Please note that the number of queries is
limited to five queries in one monitor. Also, note that the delimiter for query is new line. Total number of rows
shown in the output is limited to 50 rows.
If there are more than one columns in the results, we recommend to have set a column which has string values as
primary key in the monitor.
For queries involving counts we recommend to have a dummy column and use that as primary key.
Lets take for example some pending tasks for your application is stored in app_pending_tasks table and you want
to monitor the number of pending tasks for the application.
Typically we will form the query as given below:
select count(*) from app_pending_tasks
The problem with the above query is it doesn''t have an identifier. Instead you can form the query as given below.
For MySQL, Oracle, Sybase:
---------------------------------
select ''Number of Pending Tasks'', count(*) as totalcount from app_pending_tasks
Make the ''Number of Pending Tasks'' the primary column.
For MS SQL, PostgreSQL, Db2:
---------------------------------
select ''Number of Pending Tasks'' as NumberOfPendingTasks, count(*) as totalcount from app_pending_tasks
Make the ''Number of Pending Tasks'' the primary column.
Now you can generate alarms by assigning thresholds and generate reports for ''totalcount''.
Note: After adding Database Query Monitor, the user should select the primary key for every table and update
it.Script Monitors
Script Monitor - An Overview
Creating a new Script Monitor
Sample Input
Sample Output
Monitored Parameters
Examples:
Sample Scalar Usecase
Sample Table Usecase
Other:
Overriding Availability and Response Time of the Script
Monitoring SNMP OIDs
Rest API for getting the remote hostname for Script monitor
Custom Monitor Types
Script Monitor - An Overview
Custom script monitoring can be a tedious task if the output of the scripts that are run, are to be monitored
manually. Applications Manager provides with script monitoring functionality to ease the process by automatically
monitoring the output of in-house custom scripts (Windows/Linux) and by creating alarms as per the configuration.
Script monitor allows you to monitor the script that is present in the local system or in the remote system, transfers
the output to an Output File, parses the output and executes the actions configured.
Applications Manager provides Script Monitoring functionality to automatically monitor the output of ad-hoc
Windows/Linux/Solaris scripts that are used in-house.
During creation of a new script monitor, you must give the location of the custom script (local /
remote), attributes (numeric/string) to be monitored, the Output File in which the output is going to be
redirected and the polling interval.
Based on the polling interval, Applications Manager executes the script.
The script will transfer its output to the Output File configured. The output of the script should be in a
Key=Value format where ''='' can be any delimiter.
Applications Manager parses the Output File and executes the actions configured. It enables you to alert an
Administrator or automatically take corrective actions by way executing other OS scripts.
Reports for the attributes configured would be shown as graphs. Option to enable or disable reports is given.
Creating a new Script Monitor
Using the REST API to add a new Script monitor: Click here
To add a Script Monitor, follow the given steps:
Click New Monitor. Choose Script Monitorstrong>
Enter the Display Name of the Monitor.
Specify if the script to be monitored is present in the Local Server or in a Remote Server.
If it is Local Server, Give the absolute path of the Script to be Monitored and also the absolute path of the
directory from which the script should be executed. The execution directory should in the same hierarchy of the
''script to be monitored'' directory structure.
Select the script location as command or script / batch file.
Specify the absolute path of the script / command to be monitored.
Specify the absolute path of the execution directory from which the script should be executed.. The execution
directory should in the same hierarchy of the script to be monitored directory structure.
Check the Output Settings checkbox, to configure output settings
Check the Get output from file checkbox and specify the path of the file. If the checkbox is not checked,
Applications Manager takes the output from the output stream.
Enter the String and Numeric attributes (one attribute per line).Enter the value of Delimiter used in the output file. By default, it is "=". If you don''t specify a delimiter, then
''space'' would be considered as a delimiter.
If you want to monitor a tabular Output file, enter the details of the tables - Name, String and Numeric
column attributes, delimiter and also specify which attribute is the Unique Column.
Inorder to identify a tabular output file, execute the following commands before and after the actual
script.
echo <--table starts-->
[Script Commands]
echo <--table ends-->
This would enable Applications Manager to identify the Output File''s table.
Even if you''re using a command instead of a script as input, then the output of the command should be in
the above format. It is also mandatory to have the headers and footer in the command output as the first
line in the file.
If a table row is unavailable in the next poll, you can configure appropriate table row actions (Retain,
Delete or Unmanage) by enabling the Manage Table Row option.
If no table rows are available in the output file, you can configure appropriate health severity (Critical,
Warning, or Clear) by enabling the Manage Table Data option.
Enable the ''Affect health when exception occurs'' option if you want to configure health severity based on
exceptions occurred in the scripts.
Note: This option can be configured by enabling under Admin → Performance Polling → Optimize Data
Collection → Script/Database Query Monitors.
Specify the Arguments. For e.g., hostname 80 http
Set the Polling Interval. By default, it is 5 minutes
Specify the Timeout value in seconds. The value can be the maximum time taken by the script to execute.
In Linux, Specify the mode in which script should be executed. By default, it is "sh".
If the script is in a remote server, select the Host Name from the list
If the remote server is a new host, then enter the server''s Host Name / IP Address. Choose the Mode of
Monitoring - Telnet, SSH or Powershell.
Enter the User Name and Password of the server.
Enter the Port number - Default Telnet port no: 23, SSH: 22
Specify the command prompt value, which is the last character in your command prompt. Default value is $
and possible values are >, #, etc.
Upon adding the script monitor, you can view the details of the newly added Script Monitor
Note:
Remote Windows script monitoring is supported only in Powershell mode of monitoring.
Script/Command to monitor should not contain whitespace(s) for Powershell mode of monitoring.
Output file is mandatory when ''Output Settings'' option is enabled for Powershell mode of monitoring.
Enable Configure Alarms Template for Script Monitor
You can enable a link to Configure Alarms (link will appear on the right top corner of each table in your Script
Monitor page). Using the link, the user can set Predefined Thresholds for any attributes in the table.
Here is how you can enable Configure Alarms Template for Script Monitor:
Go to the Admin tab.
Click Performance Polling under Discovery and Data Collection.
Under Performance Data Collection, click on the Optimize Data Collection tab.
Choose Script / Database Query Monitor from the drop-down menu.
Check the Enable Configure Alarm Template for Script Monitor and Database Query Monitor option.
The Configure Alarm link will appear on the right top corner of each table in your Script Monitor page.
Tips
If you choose the Script Location as command:
Command Length must not exceed 255 characters.
Linux commands must not contain backslash (\)
Here is an example.
If you choose the Command type of script:Here is an example.
If you choose the Script Location as script:
Any Script in a Local Windows server will be executed as,
cmd /C [ScriptName] [Arguments]
Example: cmd /C D:\testScript.bat hostname username password.
To execute a VBS, Powershell or any script that is not a batch file:
The script should write the output to command prompt or file.
You can also execute files by embedding them inside a Batch script and using the Batch script for
monitoring. Here are some examples.
You can use them directly by selecting "Command", without using another batch file:
C:\windows\system32\cscript.exe D:\testFile.vbs hostname username > outputfile.txt
Arguments can be used in the script.
Local & Remote Non-Windows Script Monitoring:
Provide proper "Shell Type" for executing the scripts. By default "sh" is used.
You can execute script directly as "Command": sh ./test.sh
Note: The user must have permission to execute the script and read/write permission for Output file.
Example Command
Command: netstat -an | grep "CLOSE_WAIT" | wc -l | awk ''{print "CLOSE_WAIT=" $1}''
Example Scripts
To Execute VBS files:
To execute testFile.vbs, embed it inside a batch script testScript.bat
Contents of testScript.bat file:
c:\windows\system32\cscript.exe D:\testFile.vbs > outputFile.txt
Add testScript.bat for monitoring and use outputFile.txt to get Output.
To Execute a Powershell file:
To execute test.ps1, embed it inside a batch script testScript.bat
Content of test.bat:PowerShell.exe -NoProfile -ExecutionPolicy Bypass -Command
Add test.bat file for monitoring and use outputFile.txt to get Output.
Note:
PowerShell script must be executed with -NoProfile -ExecutionPolicy Bypass
Need to add "-encoding ascii" for output files created via powershell.
Sample Input
To monitor a script interfacestatus.bat that creates a user defined table called InterfaceStats and user defined
parameters like DiskStatus, DiskErrors and No. ofProcess, in the output file interfacestatusoutput.txt
In the Script Monitor creation form, give the absolute path of the script : c:\interfacestatus.bat
Under Output settings, give the absolute path of Output file: c:\interfacestatusoutput.txt
Give DiskStatus as the string attribute, No.ofProcess and DiskErrors are the numeric attributes
with Delimiter "="
If you want to monitor statistics in a table format , select Tables in output file.
Here, we have the table InterfaceStats with the stats Name, IP, Status, In, Out where Name, IP, Status are
string attributes; In & Out are numeric attributes. TheDelimiter is the separater between the two column
names -> space. If tab is the delimiter, then give \t . Usually tab will be the delimiter for sql queries
results.
Note: The starting tag of the table, InterfaceStats is "<--table InterfaceStats starts-->" and the end tag is "<--
table InterfaceStats ends-->". Also, the first line of the table should contain the attribute names. The attribute
names or the column names should also be separated by the same delimiter used to separate the data rows
and that is specified as the column delimiter. In this case, they are Name, IP, Status, In and out. The remaining
lines between the start and end tag should comprise of the actual data. Make sure that the delimiter for the
table is unique and you should specify that as the column delimiter.Unique Column is the attribute that doesn''t repeat itself in the rows and identify the row by that value. Here it
is IP.
Sample Output
DiskStatus=Up
No.ofProcess=1
DiskErrors=0
<--table InterfaceStats starts-->
Name IP In Out
eth0 192.168.1.1 123451 234567
eth1 192.168.1.2 345633 453267
<--table InterfaceStats ends-->
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Script Monitor under the Custom
Monitors Table. Displayed is the Script Monitor bulk configuration view distributed into three tabs:
Availability tab, gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Overriding Availability and Response Time of the Script
This option would be useful, if you want to override the response time measured for custom scripts using a defined
value in the output file. Applications Manager looks for few reserved keywords in the output file, if it matches then
it will replace the corresponding attribute.
For eg., if the script output looks like this,
script_availability=1 (Allowed values are 0 or 1. "0" refers to success. "1" refers to failure.)
script_message=Server is not running.
script_responsetime=10
Then, while parsing the output file, script_availability value will be taken and based on that the availability is
calculated.The same is the case for response time.
Examples:
Sample Scalar Usecase
Let''s assume you want to monitor a script < filesystem.sh> present under /home/test-solaris/ in test-solaris
machine. The output from this script is dumped to output.txtfile present under the same directory. The format
of output.txt is as shown below :
SystemTemperature=37
TimeSinceLastReboot=30
TopPaginApp=sendmail
IOReads=1050
Setting up Script Monitor:
Login to the Applications Manager Web Client.
Click New Monitor. From the combo box, choose Script Monitor.
For the Display Name give some name. For e.g FileSystem
Choose whether the script to be monitored is present in the Local Server or in a Remote Server. If the script is
in a Remote Server, then make sure you put the script in the Remote Server.
If it is Local Server/ Remote Server, give the absolute path of the Script to Monitor (/home/test-
solaris/filesystem.sh) and also the absolute path of the directory from which the script should be
executed(/home/test-solaris/).
Under Output Settings, give the Output file name (/home/test-solaris/output.txt) with absolute path. This is
the file where the output from the script is dumped.
Enter the Name of the Non Numeric and Numeric attributes.In the Numeric area, add
SystemTemperature
TimeSinceLastReboot
IOReads
In the String Attributes Text area, add :
TopPaginApp
Enter the value of Delimiter (=) used in the output file. By default, it is "=". If you don''t specify a delimiter, then
''space'' would be considered as a delimiter.
Specify the additional Arguments (if required to pass to the script). For e.g., hostname 80 http
Set the Polling Interval. By default, it is 5 minutes
Specify the Timeout value in seconds. The value can be the maximum time taken by the script to execute.
In Linux, Specify the mode in which script should be executed. By default, it is "sh".
If the script is in a Remote Server, select the Host Name from the list
If the remote server is a new host choose New Host, then enter the server''s Host Name / IP Address (test-
solaris). Choose the mode of monitoring - Telnet, SSH, or Powershell. (Telnet)
Enter the User Name(test) and Password(test) of the server.
Enter the Port number - Default Telnet port no: 23, SSH: 22
Specify the command prompt value, which is the last character in your command prompt. Default value is $
and possible values are >, #, etc.
Once all the values are entered, click Add Monitor(s).
The success message should be displayed. Click Monitor Details > Script Monitor and go to the create script, to
view the details.
Note: Applications Manager uses either ANSI or UTF-8 encoding. Hence it is advised that you use the same
format while writing output to the file.
Sample Table Usecase
Let''s assume you want to monitor a script present under /home/test-solaris/ in test-solaris machine.
The output from this script is dumped to output.txt file present under the same directory. The format
of output.txt is as shown below
<--table prustat starts-->
PID CPU Mem Disk Net COMM
7176 0.88 0.70 0.00 0.00 dtrace
7141 0.00 0.43 0.00 0.00 sshd
7144 0.11 0.24 0.00 0.00 sshd
3 0.34 0.00 0.00 0.00 fsflush
7153 0.03 0.19 0.00 0.00 bash
99 0.00 0.22 0.00 0.00 nscd
7146 0.00 0.19 0.00 0.00 bash
52 0.00 0.17 0.00 0.00 vxconfigd
7175 0.07 0.09 0.00 0.00 sh
98 0.00 0.16 0.00 0.00 kcfd
<--table prustat ends-->
Note: the table headers <--table prustat starts-->. This is mandatory and should follow the same format as
mentioned. Here "prustat" should be replaced by the Table Name explained below
Setting up Script Monitor
Follow the same instructions as mentioned for Scalar till point 6
Select Tables in output file check box
For the Table Name provide some name(prustat). Note that this same should be present in the table header(<--
table prustat starts-->) in the output file.
For the Numeric Attributes area provide the column names in the script output that are numeric: CPU, Mem,
Disk, Net
For the String Attributes provide the column names in the script output that are non numeric: PID, COMM
For the Unique Column provide the column names that can identify a row data. This can be a single value or
multiple value: PID, COMMFor the Column Delimiter provide the column separator. The default value is a space.
In case you have scripts that output multiple tables then you can select More and configure the values.
Once all the values are entered, click Add Monitor(s).
You can use script monitor to monitor the SNMP OIDs
Please look at the steps below for creating a script monitor,
Create a script file ( say script.sh ) under the /opt/ManageEngine/AppManager_Home/ directory
Edit that file and type in the following content into that file,
snmpwalk -v 1 -c public app-w2k1 CPQHLTH-MIB::cpqHeFltTolPowerSupplyRedundant.0.1| awk ''{ y = $1; x = $4
; gsub(/[a-zA-Z()]/, "", x)} {print y " = " x}''>> output.txt
snmpwalk -v 1 -c public app-w2k1 CPQHLTH-MIB::cpqHeFltTolPowerSupplyRedundant.0.2 | awk ''{ y = $1; x =
$4 ; gsub(/[a-zA-Z()]/, "", x)} {print y " = " x}'' >> output.txt
Click on "New Monitor" in applications manager and choose script monitor. Then create a new monitor using
the following parameters,
Script to Monitor
Directory from which the script should be executed
Under Output Settings, Output File
Numeric Attributes
Use the default parameters for configuring the remaining attributes.
Note: If an attribute does not have any data, the script returns ''N.D'', where ''N.D'' means No Data.
REST API to get the HostName
This API gives host name for the given Script Monitor.
Syntax
http://[Host]:[Port]/AppManager/json/GetRemoteHost?apikey=[APIKEY]&resourceid=[RESOURCEID]
Request Parameters
The parameters involved in executing this API request are:
Field Description
apikey The key generated using the Generate API Key option in the ''Admin'' tab.
resourceid The resource id of the monitor that needs to be polled.
Sample Request
http://app-windows:9090/AppManager/json/GetRemoteHost?
apikey=095cb3835ff015b01a3b3a6c4ab2c38a&resourceid=10000293
Sample Response
{"response":{"result":[{"hostname":"app-w7-64-8"}],"uri":"/AppManager/json/GetRemoteHost"},"response-
code":"4000"}
Custom Monitor Types
Custom Monitor Types in Applications Manager allow you to associate a monitor type to the inhouse scripts, for
monitoring your own applications. You can define your own monitor types apart from the monitor types that are
available by default. Know more.
Windows Performance Counters
To create windows performance counters in Applications Manager, follow the steps given below:Select New Monitor. Choose Windows Performance Counters.
Provide Name for Windows Performance Counter.
Enter the Description for the counter.
Enter the Polling Interval for the counter.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Select the Host Name from the combo box or you can create a new host (by giving the new host name / IP
address, username and password of the host)
Note: Windows Performance Counters is currently supported for Windows Vista, Windows 7, Windows 8,
Windows Server 2000, 2003, 2008 and 2012.
Applications Manager uses WMI (Windows Management Instrumentation) for monitoring Windows Performance
Counters. WMI gives preinstalled performance counter classes; each class describes an object in performance
libraries.
For eg., the object that appears in the Perfmon System Monitor named NetworkInterface is represented in WMI
by the Win32_PerfRawData_Tcpip_NetworkInterface class for raw data
Win32_PerfFormattedData_Tcpip_NetworkInterface class for pre-calculated, or "cooked" data.
Currently Applications Manager supports monitoring the counters of classes derived
from Win32_PerfFormattedData
Some of the WMI Performance classes for Performance Objects that are present in Perfmon are
Processor -Win32_PerfFormattedData_PerfOS_Processor
Browser -Win32_PerfFormattedData_PerfNet_Browser
PagingFile -Win32_PerfFormattedData_PerfOS_PagingFile
Memory -Win32_PerfFormattedData_PerfOS_Memory
Server -Win32_PerfFormattedData_PerfNet_Server
Some classes can only have one instance of it, they are called "Singleton Classes".
After creating Windows Performance Counters, You will see the WMI Monitor details page showing availability and
other details.Availability tab, gives the Availability history for the past 24 hours or 30 days. Performance tab gives
the Health Status and events for the past 24 hours or 30 days. List view enables you to perform bulk admin
configurations. Click on the individual monitors listed, to view the following information. The windows
performance counter values can be added and monitored as attribues. The overall ability to configure thresholds
on attributes and taking corrective actions are supported out-of-the-box.
Adding Attributes
Click on Add Attributes link.
This will take you to the list of WMI Performance Classes. You can choose the classes whose attributes you
want to monitor.
Click on Show Attributes; the list of WMI classes selected along with their attributes and instances are
displayed. Select the attributes and instances. The attributes would then be added for monitoring.
You can configure thresholds and alarms for the attributes. At a class level, you can configure alarms for
Health, which inturn depends on the attributes it comprises of.
Note: Windows Performance Counters is currently supported for Windows Vista, Windows 7, Windows 8,
Windows Server 2000, 2003, 2008 and 2012..
Database Servers
Applications Manager provides Database Server monitoring that monitors system resources. It also provides
proactive measures by notifying database and system administrators about potential problems that could
compromise database performance. This database server monitoring has the ability to connect to the database
source, process any query received in the database, monitor various system table column values, collect data, etc.
and also notify through alarms, if the database system properties are beyond a given threshold.
The different database servers supported are:
MySQL Database ServersOracle Database Servers
MS SQL Database Servers
IBM DB2 Database Servers
IBM Informix Database
SAP HANA Database Servers
Sybase Database Servers
PostgreSQL Database Servers
Database Query Monitor
Apache HBase Database Servers
NoSQL Database Servers
Cassandra Database Servers
CouchBase Database Servers
MongoDB Database Servers
Redis Database Servers
Memcached Database Servers
Oracle NoSQL Database Servers
Please browse through the different database servers that provide server information and their parameters being
monitored. For all databases, data collection happens by establishing a JDBC connection and executing queries to
collect the data.
SQL Anywhere Monitoring User Guide
To ensure peak health and performance, SQL Anywhere monitoring tools that are perceptive and sensitive to errors
are employed by businesses. Applications Manager''s SQL Anywhere monitor is one such tool which can help you
monitor and maintain your databases and IT environments with minimal manual intervention.
Adding a SQL Anywhere monitor
Follow the steps given below to create a new SQL Anywhere monitor:
Click on New Monitor link. Select SQL Anywhere under Database Servers category.
Specify the Display Name of the SQL Anywhere Server.
Enter the Hostname of the server on which SQL Anywhere is running.
Specify the Port at which SQL Anywhere is running. The Default Port is 2638.
If you choose the Use Below Credentials option, then enter the credentials - UserName and Password of the
SQL Anywhere Instance.
UserName - Name of the User who has read permission.
Password - Password of the above user.If you choose the Select from credential list option, then select the respective credential from preconfigured
credential list.
Specify the Polling Interval in minutes.
Choose the Monitor Group with which you want to associate the SQL Anywhere to, from the combo box
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the SQL Anywhere from the network and starts monitoring it.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on SQL Anywhere under the Database
Servers table. Displayed is the SQL Anywhere bulk configuration view distributed into three tabs:
Availability tab, gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
On clicking a monitor from the list, you''ll be taken to the SQL Anywhere monitor dashboard. It has 4 tabs-
Overview
Databases
Connections
Configurations
Overview
Parameter Description
CONNECTION STATISTICS
Total Connection Count Total number of connections made to the SQL Anywhere server.
HTTP Connections Number of HTTP connections made to the SQL Anywhere server.
HTTPS Connections Number of HTTPS connections made to the SQL Anywhere server.
SESSION ACTIVITY
Active HTTP Requests Number of active HTTP requests.
Active HTTPS Requests Number of active HTTPS requests.
Unscheduled Requests Number of unscheduled requests.
Active Sessions Total number of active sessions.
CACHE USAGE
Current Cache Size Size of the cache memory currently used in KB.
Max Cache Size The maximum allowed cache size in KB.
Peak Cache Size The largest value the cache has reached in the current session in KB.
CACHE STATISTICS
Cache Dirty Number of cache pages that are dirty i.e. that needs to be written.
Cache Pinned Number of pinned cache pages.
Cache Replacements Number of pages in the cache that have been replaced.
Main Heap Pages Number of pages used for global server data structures.
Databases
Parameter Description
Databases
Name Name of the database.
Total Size(MB) Total size of the database in MB.
Used(MB) Size of the used database memory in MB.
Free(MB) Size of the free database memory in MB.
Used(%) Size of the used database memory in %.Disk Reads/Min Number of disk reads in a minute.
Disk Writes/Min Number of disk writes in a minute.
Connection Count Number of connections made to the database.
Locks Count Number of locks held on the database.
Database Details Click one of the database names in the Databases table to view database details.
Dbspace and File Details
Dbspace Name Name of the dbspace.
File Name Name of the file inside the dbspace.
Total Disk Size(MB) Total size of the disk for dbspace in MB.
Disk Free(MB) Free disk space for dbspace in MB.
Disk Free(%) Free disk space for dbspace in %.
Total File Size(MB) Total size of the file in MB.
File Used(MB) Total size of the file used in MB.
File Free(MB) Total size of the file which is free in MB.
File Used(%) Size of the used file in %.
DB Mirroring Details
Name Name of the database.
Mirror Mode Mode of mirroring.
Mirror State Status of the mirrored database—whether it is synchronized or not.
Partner State Status of the partner server—whether it is connected or not.
Arbiter State Status of the arbiter server—whether it is connected or not.
Connections
Parameter Description
DB Connections
DB Name Name of the database.
Connection ID Unique ID number of the connection.
Connection Name Name of the connection.
Connection Host Name of the host.
User Name of the user.
Communication Link Type of communication link.
Last Request Type Type of request that was previously processed.
Blocked On Connection ID of the user who blocked the database.
Configurations
Parameter Description
CONFIGURATION PROPERTIES
Sybase Version Version of the SQL Anywhere server used.
Server Name Name of the SQL Anywhere server used.
Server Language Language used in the SQL Anywhere server.
Start up time Time at which the server started running.
License Seats Number of license seats or processors.
License Type Type of license.
Licensed Company Name of the licensed company.
Licensed User Name of the licensed user.
Network Server Whether the added SQL Anywhere server is a network server or not.Neo4j Monitoring User Guide
Neo4j, one of the most popular databases, is a graph database management system which is ACID-compliant. As
with any database, Neo4j is also a core component in any system and requires constant monitoring. Tracking
memory management, garbage collection, and also aspects of Neo4j such as growth of your store, active
transactions, and many other operational facets is important to understand the relationship between Neo4j and
other elements in your IT environment. Applications Manager''s Neo4j monitoring tool provides valuable insights
into key Neo4j metrics, and notifies of areas that need attention, enabling you to optimize performance of Neo4j
servers.
Adding a Neo4j monitor:
Follow the steps given below to create a new Neo4j monitor:
Click on New Monitor link.Select Neo4j under Database Servers category.
Specify the Display Name of the Neo4j Server.
Enter the Hostname of the server on which Neo4j is running.
Specify the bolt Port at which Neo4j is running. The Default Port is 7687.
If you choose the Use Below Credentials option, then enter the credentials - UserName and Password of the
Neo4j Instance.
UserName - Name of the User who has read permission.
Password - Password of the above user.
If you choose the Select from credential list option, then select the respective credential from preconfigured
credential list.
Choose whether you want to Discover all nodes in the cluster.
Specify the Polling Interval in minutes.
Choose the Monitor Group with which you want to associate the Neo4j to, from the combo box (optional). You
can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the Neo4j from the network and starts monitoring it.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Neo4j under the Database Servers
table. Displayed is the Neo4j bulk configuration view distributed into three tabs:
Infrastructure View tab, gives the details about all Neo4j instances present in the Infrastructure.
Availability tab, gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
On clicking a monitor from the list, you''ll be taken to the Neo4j monitor dashboard. It has 9 tabs-
Overview
Thread
Heap Details
ID Allocation
Store
Transactions
Page Cache
Clustering
Configurations
Overview
Parameter Description
PHYSICAL AND VIRTUAL MEMORY
Total Physical Size of the total physical memory of the machine in GB.
Used Physical Size of the total physical memory used in GB.Free Physical Size of the total physical memory free in GB.
Committed Virtual Size of the total virtual memory committed.
SWAP MEMORY
Total Swap Space Size of the total swap space of the machine in GB.
Free Swap Space Size of the total swap space free in GB.
Used Swap Space Size of the total swap space used in GB.
NODE DETAILS
Name Name of the node.
Role in cluster Role of the node in cluster.
Read Only Instance Shows whether it''s read only instance- TRUE/FALSE.
MEMORY UTILIZATION
Physical Memory Utilization Total physical memory usage calculated and represented in %.
Swap Space Utilization Total swap space usage calculated and represented in %.
Thread
Parameter Description
THREAD DETAILS
Daemon Number of Daemon Threads.
Peak Number of Peak Threads.
Live Number of Live Threads.
Total Started Number of total threads started.
Heap Details
Parameter Description
HEAP MEMORY DETAIL
Committed Heap Size of Heap memory committed in GB.
Initial Heap Size of initial Heap memory in GB.
Maximum Heap Size of maximum Heap memory in GB.
Used Heap Size of Heap memory used in GB.
NON HEAP MEMORY DETAIL
Committed Non Heap Size of Non Heap memory committed in GB.
Initial Non Heap Size of initial Non Heap memory in GB.
Maximum Non Heap Size of maximum Non Heap memory in GB.
Used Non Heap Size of Non Heap memory used in GB.
ID Allocation
Parameter Description
ID ALLOCATION
Node Ids An estimation of the number of nodes used in this Neo4j instance.
Property An estimation of the number of properties used in this Neo4j instance
Relationship An estimation of the number of relationships used in this Neo4j instanceRelationship Type The number of relationship types used in this Neo4j instance
Store
Parameter Description
STORE SIZES
Total Disk space used by whole store, in KB.
Labels Disk space used to store labels, in KB.
Nodes Disk space used to store nodes, in KB.
Transaction Log Disk space used by the transaction logs, in KB.
Relationships Disk space used to store relationships, in KB.
Indices Disk space used to store all indices, in KB.
Counters Disk space used to store counters, in KB.
PROPERTY SIZES
Schemas Disk space used to store schemas (index and constrain declarations), in KB.
Properties Disk space used to store properties (excluding string values and array values), in KB.
String Properties Disk space used to store string properties, in KB.
Array Properties Disk space used to store array properties, in KB.
Page Cache
Parameter Description
PAGE CACHE COUNT DETAILS
Hit Ratio Ratio of hits to the total number of lookups in the page cache
Hits Number of page hits. How often requested data was found in memory.
Exception while Page
Number of exceptions caught during page eviction.
Eviction
Number of page evictions. How many pages have been removed from memory to
Evictions
make room for other pages.
Number of page faults. How often requested data was not found in memory and had
Faults
to be loaded.
Flushes Number of page flushes. How many dirty pages have been written to durable storage.
Usage Ratio The percentage of used pages.
PAGE CACHE SIZE DETAILS
Read Number of bytes read from durable storage.
Write Number of bytes written to durable storage.
Files Mapped Number of files that have been mapped into the page cache.
Files UnMapped Number of files that have been unmapped from the page cache.
Pins Number of page pins. How many pages have been accessed.
Number of page unpins. How many pages have been accessed and are not accessed
UnPins
anymore.
Transactions
Parameter Description
TRANSACTION DETAILSCommitted The total number of committed transactions.
Started The total number started transactions.
Open The number of currently open transactions.
Rollbacked The total number of rolled back transactions.
Peak
The highest number of transactions ever opened concurrently.
Concurrent
DEADLOCK
Averted The number of lock sequences that would have lead to a deadlock situation that Neo4j has
Deadlocks detected and averted (by throwing DeadlockDetectedException).
Clustering
Parameter Description
CLUSTERING DETAILS
Raft Log Total amount of disk space used by the raft log, in KB.
Replicated State Total amount of disk space used by the replicated states, in KB.
Configurations
Parameter Description
CONFIGURATIONS DETAILS
Mounted Database
The name of the mounted database.
Name
Start Time The time from which this Neo4j instance was in operational mode.
Version The version of Neo4j.
Store Creation Time The time when this Neo4j graph store was created.
An identifier that, together with store creation time, uniquely identifies this Neo4j
Store Id
graph store.
MySQL Database / MariaDB Monitoring
Note: In the MySQL database (that you are trying to monitor), ensure that the user name assigned to
Applications Manager has the permission to access the MySQL database from the host where Applications
Manager is running. Else, give a relevant user who has the privileges to do the same.
Creating a new MySQL monitor
Minimum User Privileges : The user should have privileges to execute SELECT, SHOW DATABASES, REPLICATION
commands in the MySQL server. Also, Applications Manager machine should be allowed to access the MySQL
database server.
For enabling the privileges, execute the below commands in the remote MySQL Server
INSERT INTO user (Host,User) VALUES('''','''');
GRANT SELECT,SHOW DATABASES,REPLICATION CLIENT ON *.* TO ''''@'''';
FLUSH PRIVILEGES;
(Host -> Applications Manager machine)
Prerequisites for monitoring MySQL DB metrics: Click here
Using the REST API to add a new MySQL DB monitor: Click hereTo create a MySQL database server Monitor, follow the steps given below:
Click on New Monitor link.
Select MySQL DB Server.
Enter the IP Address or hostname of the host.
Enter the Subnet Mask of the network.
Check the ''Force SSL'' box to force an SSL connection.
Enter the port number in which MySQL is running.
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Provide the user name and password of user who has permission to access the MySQL database.
Specify the database name. Please note that the Database name must be valid. Also, the database name is
associated with the user name. Hence, provide the database name corresponding to the user name given in
the above field.
Choose the Monitor Group from the combo box with which you want to associate MySQL database server
Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers MySQL database server from the network and starts monitoring them.
Troubleshoot: Having trouble in monitoring MySQL database server? Refer to the online troubleshooting
section.
Supported Versions
MySQL 3.23.x
MySQL 4.x, 4.1.x
MySQL 5.x, 5.1.x, 5.5.x, 5.6.x, 5.7.x
MySQL 8.x
All Versions of MariaDB
Monitored Parameters
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
To view detailed performance metrics of a MySQL server, click the corresponding monitor listed in
the Availability tab. These metrics are categorized into six different tabs for better understanding.
Overview
Database
Replication
Performance
Session
Configuration
Overview
This tab provides information into the overall performance of the MySQL server.
Parameter Description
Monitor Information
Name Denotes the name of MySQL server monitor.
Health Denotes the health (Clear, Warning, Critical) of the MySQL server.
Type Denotes the type you are monitoring.
MySQL Version Specifies the version of the database server.
Port Specifies the port number at which the database server is running.
Base Directory Specifies the directory in which the database server is installed.
Data Directory Specifies the directory in the hard disk of the system where the data for the databaseserver is stored.
Host Name Specifies the host at which the database server is running.
Host OS Specifies the OS of the host where the database server is running.
Last Alarm Specifies the last alarm that was generated for the database server.
Last Polled at Specifies the time at which the last poll was performed.
Next Poll at Specifies the time at which the next poll is scheduled.
Availability Shows the current status of the server - available or not available.
Connection Time
The time taken to connect to the MySQL database server from Applications Manager
Connection Time
server.
Connection Time Out Specifies the maximum time taken by the application to connect to MySQL Server
Request Statistics
Request Rate Number of request received in one second.
Bytes Received Rate Number of bytes received in one second.
Bytes Sent Rate Number of bytes sent in one second.
Connection Statistics
Open Connections The number of connections opened at present in the MySql Server.
Aborted Connections Number of tries to connect to the MySQL server that failed.
Aborted Clients Number of clients aborted by MySQL server.
Open Connections in
The ratio of connections opened with max connections.
(%)
Thread Details
Threads Used Number of threads processing the request.
Threads in Cache Number of threads currently placed in the thread cache.
Thread Cache Size Specifies the cache size in the MySQL server.
Table Lock Statistics
Immediate Locks Number of times a table lock for the table is acquired immediately.
Locks Wait Number of times a table lock could not be acquired after waiting.
Key Efficiency
Key Hitrate Percentage of key read requests that resulted in actual key reads from the key buffer.
Key Buffer Used Amount of allocated key buffer in use.
Key Buffer Size Size of the buffer used for index blocks. Also known as the key cache.
Query Statistics
Queries Inserted/Min No. of Insert Queries executed per minute
Queries Deleted/Min No. of Delete Queries executed per minute
Queries
No. of Update Queries executed per minute
Updated/Min
Queries
No. of Select Queries executed per minute
Selected/Min
Query Cache Hitrate (This performance data is not available for MySQL versions 3.23.x)
Query Cache Hitrate Ratio of queries that were cached and queries that were not cached.
Query Cache Size Amount of memory allocated for caching query results.
Query Cache Limit Maximum amount of memory for storing cache results.
Database
Parameter Description
Database Details
Database Name Name of the database instance.
Database Size Size of the various databases in the MySQL server (in MB).Replication
Parameter Description
Replication Details
1. Master-Slave Replication
Replication
The status of Slave process in MySQL Server
Status
Slave IO
Status of the Slave IO Process in MySQL Server. Possible values are Yes or No.
Running
Slave SQL
Status of the Slate SQL Process in MySQL Server. Possible values are Yes or No.
Running
Last Error The last error occured when Slave is synching the data from master.
Master Host The hostname or IP number of the master replication server.
Master Port The TCP/IP port number that the master is listening on.
The username of the account that the slave thread uses for authentication when it connects to the
Master User
master.
Time Behind
This indicates of how “late” the slave is behind the Master.
Master
2. Group Replication
Defines the state of the Member. Possible values are ONLINE, OFFLINE, ERROR, RECOVERY,
State
UNREACHABLE.
Connection The status of connection whether it is active/Idle or no Longer exists or trying to connect. Possible
State values are ON, OFF, CONNECTING.
Count
Conflicts The number of transactions that did not pass the conflict detection check.
Detected
Count The number of transactions in the queue pending conflict detection checks. Once the
Transactions transactions have been checked for conflicts, if they pass the check, they are queued to be
In Queue applied as well.
Count
The number of transactions that this member originated that were rolled back after being sent to
Transactions
the replication group.
Rollback
Last Error The error message which has triggered lastly.
Last Error
The Timestamp of last Error.
TimeStamp
Replication Gives the status of Replication Applier Thread is Active/Idle and Dead. Possible values are ON,
Applier OFF.
The member server UUID. This has a different value for each member in the group. This also
Member ID
serves as a key because it is unique to each member.
Host Name The Name of the Host of this Member.
Role This metric defines the member''s role in the group. Possible values are PRIMARY, SECONDARY.
Port The port Number on which the Member is Running.
Replication The mode of Replication, which the group is using. Possible values are single-primary, multi-
Mode primary.
Group Name The name group that the Member (MySQL server) belongs to.
Channel
The name of the Group Replication Channel.
Name
Primary Host Host Name of the Primary Member in the Group.
Primary Port Port Number of the Primary Member in the Group.
Performance
Parameter Description
TOP QUERIES BY CPU
Avg. CPU Time The average CPU time taken to execute the query (in millisecond).The cumulative total amount of CPU time that has been spent running this query (in
Total CPU Time
millisecond).
Max CPU The maximum amount of time that was taken by the CPU to run this query (in millisecond).
Query The SQL query which consumed the maximum CPU time.
DB Name The database under which this query has been executed.
Last Execution
The last time at which the query executed.
Time
Note : The TOP QUERIES BY CPU data will be displayed only for MySQL versions 5.7 & above.
Session
Parameter Description
Session Details
PID Displays the process ID of the session running in the MySQL server.
Status Displays the status of the process in the MySQL server.
User The login name of the user executing the process.
DB Name Displays the name of the database currently being used by the process.
Program Name The name of the program that has established the session.
Memory Usage The amount of memory that has been utilized by the process (in kilobytes).
CPU Time The cumulative CPU time taken for the process running in the MySQL Server (in millisecond).
Lock Latency Amount of time taken to establish a lock for the established session (in millisecond).
For foreground threads, the type of command the thread is executing on behalf of the client, or
Command
Sleep if the session is idle.
Query The query the thread is executing, or NULL if it is not executing any statement.
Last Query The last query executed by the thread, if there is no currently executing statement or wait.
Last Query CPU
The CPU time taken for the last query to be executed (in millisecond).
Time
Note : The Session Details data will be displayed only for MySQL versions 5.7 & above.
Configuration
This tab provides information about the system variables maintained by the MySQL server. These system variables
indicate how the server is configured.
You can also view realtime and historical data of any of the attributes present in the ''Configuration Information''
section in the Configuration tab. Click on any attribute under the Configuration tab. This will open up a new window
named ''History Data'' that provides more information about these attributes.
There are two tabs in the History Data window - History Report and Global View.
History Report: This tab provides historical reports of the attribute selected based on the time period chosen. You
can also use the Select Attribute drop-down box and view reports for other attributes.
Global View: This tab displays the current values of the attribute selected, across multiple monitors. To view
information about other attributes present in the monitor, use the Select Attribute drop-down box and change the
attribute.
If you want to view data of multiple attributes, click the Customize Columns link present at the top left corner of the
window. This will take you to the Edit Global Viewscreen. In this screen, you can change the monitor type using
the Filter by Monitor Type drop-down box, select the metrics to be displayed, and show monitors on a monitor
basis or a monitor group basis. After you select your options, click the Show Report button to view those
information in the Global View tab.
The View Process List option present on the right side under the Show Status section gives you information on the
current threads that are running in the MySQL server.
Oracle Database ServersOverview
Applications Manager provides out-of-the-box performance metrics and helps you visualize the health and
availability of an Oracle Database server farm. Database administrators can login to the web client and visualize
the status and Oracle performance metrics.
Creating a new Oracle DB monitor
Supported Versions: Applications Manager supports monitoring of Oracle database servers of versions 9i, 10g,
10.1.3, 11g, 12c, 18c & 19c.
Prerequisites for monitoring Oracle DB metrics: Click here
Using the REST API to add a new Oracle DB monitor: Click here
Follow the given steps to create a Oracle database server monitor:
Click on New Monitor link.
Select Oracle DB Server.
Enter the IP Address or hostname of the host.
Enter the Subnet Mask of the network.
Enter the port number in which the Oracle is running.
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Provide the user name of the admin user (''system'' is the default username) and its corresponding password.
Provide a valid System Identifier / Host Connection String.
Choose Discover Pluggable Database (PDB) as ''Yes'' to discover and monitor pluggable databases associated
with the Oracle DB server (Applicable only for CDB instance of an Oracle Multitenancy-enabled server). To add
only the required PDB(s), choose ''No'' and add the PDB(s) via Add PDB link available under ''PDB'' tab in Oracle
DB monitor.
Provide the Socket Read Timeout and Query Execution Timeout values in seconds.
Choose the Monitor Group from the combo box with which you want to associate Oracle database server
Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers Oracle database server from the network and starts monitoring them.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Oracle Server under the Database
Servers Table. Displayed is the Oracle servers bulk configuration view in three tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Note: To create a new Oracle database monitor, you should have admin privileges. Minimum User Privileges →
user with CONNECT and SELECT_CATALOG_ROLE roles.
Click on the monitor name to see all the server details listed under the following tabs:
Overview
PDB
Tablespace
Session
Rollback & Corrupted Blocks *
SGA
Query
Lock Statistics
Jobs & Backup *
PGA
Process
ASM *
RPO
Alert Logs
Redo LogsNote: The server details marked with * symbol is supported in Oracle database servers version 10g and above.
Overview
Parameters Type Description
Monitor Information
Name String Name of the Oracle server monitor
Oracle Version String The version of the Oracle Database.
Oracle Start
String The time when Oracle server was started.
Time
Availability String The status of the database server - available or not available.
Today''s Availability
Current Status String Availability history graph with uptime
Connection Statistics
Response Time String The time taken to connect to the database.
Session Activity
Number of
Numeric Graph for the number of users executing an SQL Statement. vs time
Session Users
Table spaces with least free bytes
Name String The name of the table space.
Free Bytes (MB) Numeric The free space available in bytes.
% of Free Bytes Numeric The percentage of free space available in bytes.
Database Details
Version Numeric Version of the database.
Indicates whether the added Oracle DB Sever is a CDB instance or Non-CDB
DB Type String
instance.
Database
String Creation time of the database.
Created Time
Open Mode String Indicates the Open mode of the Instance which can be either Read Write or Read.
FRA Status String Indicates whether Flashback is enabled for the database instance.
The two Log Modes are:
NOARCHIVELOG - When you run your database in NOARCHIVELOG mode, you
Log Mode String disable the archiving of the redo log.
ARCHIVELOG - When you run a database in ARCHIVELOG mode, you enable the
archiving of the redo log.
Current role of the database:
LOGICAL STANDBY
DB Role String
PHYSICAL STANDBY
PRIMARY
Type of control file:
STANDBY - Indicates that the database is in standby mode
CLONE - Indicates a clone database
Control File type String
BACKUP | CREATED - Indicates the database is being recovered using a backup
or created control file
CURRENT - database is available for general useParameters Type Description
Indicates whether switchover is allowed:
NOT ALLOWED - Either this is a standby database and the primary database
has not been switched first or this is a primary database and there are no
standby databases.
SESSIONS ACTIVE - Indicates that there are active SQL sessions attached to
the primary or standby database that need to be disconnected before the
switchover operation is permitted. Query the V$SESSION view to identify the
specific processes that need to be terminated.
SWITCHOVER PENDING - This is a standby database and the primary database
switchover request has been received but not processed.
SWITCHOVER LATENT - The switchover was in pending mode, but did not
complete and went back to the primary database.
TO PRIMARY - This is a standby database and is allowed to switch over to a
primary database.
Switch over
String TO STANDBY - This is a primary database and is allowed to switch over to a
status standby database.
RECOVERY NEEDED - This is a standby database that has not received the
switchover request.
PREPARING SWITCHOVER - Either this is a primary database that is accepting
redo data from a logical standby database in preparation for switch over to the
logical standby database role, or it is a logical standby database sending redo
data to a primary database and other standby databases in preparation for
switch over to the primary database role. In the latter case, a completed
dictionary has already been sent to the primary database and other standby
databases.
PREPARING DICTIONARY - This is a logical standby database that is sending
redo data to a primary database and other standby databases in the
configuration in preparation for switch over to the primary database role.
TO LOGICAL STANDBY - This is a primary database that has received a
complete dictionary from a logical standby database.
Protection mode currently in effect for the database:
MAXIMUM PROTECTION - Database is running in maximized protection mode
MAXIMUM AVAILABILITY - Database is running in maximized availability mode
RESYNCHRONIZATION - Database is running in resynchronization mode
Protection Mode String
MAXIMUM PERFORMANCE - Database is running in maximized protection
mode
UNPROTECTED - Database is unprotected (this normally occurs when the
primary database is mounted and not open)
Indicates whether the next database open allows or requires the resetlogs option
NOT ALLOWED
Open reset logs String
ALLOWED
REQUIRED
Protects data from being changed:
ALL - Indicates all users other than SYS are prevented from making changes to
any data in the database.
Guard Status String
STANDBY - Indicates all users other than SYS are prevented from making
changes to any database object being maintained by logical standby.
NONE - Indicates normal security for all data in the database.
Force logging String Indicates whether the database is under force logging mode (YES) or not (NO).
Database Status
Database Size ** Numeric Size of the database in Megabytes.
Average This is the average number of executions that happen during the execution of every
Numeric
Executions SQL Statement.Parameters Type Description
Reads Numeric Refers to the number of reads from the database.
Writes Numeric Refers to the number of writes to the database.
Database Block
Numeric This refers to the lowest possible storage area for an Instance in bytes.
Size
Free Space ** Numeric Size of free extents in all tablespaces in the database (Size in MB).
Invalid/Unusable
Numeric Number of Invalid/Unusable indexes in the databse.
Index Count
Current SCN Numeric Current System Change Number (SCN) of the database.
Data transferred
Numeric Total data sent and received via SQL*Net services in MB.
via SQL*Net
Database CPU
Numeric Ratio of DB CPU time to DB time. Ideal value is greater than 90%.
Time Ratio
Hit Ratio
The buffer cache hit ratio calculates how often a requested block has been found in
Buffer Cache Hit
Numeric the buffer cache without requiring disk access. It is the percentage of cache hits
Ratio
taking place from the buffer cache.
The Data Buffer Hit Ratio Oracle metric is a measure of the effectiveness of the
Data Buffer Hit
Numeric Oracle data block buffer. It is the percentage of logical reads taking place from the
Ratio
data block.
The ratio of the data gets to the data misses in the row cache is Data Dictionary Hit
Data Dictionary Numeric
Ratio.
The Library cache stores all shared SQL and PL/SQL blocks, along with their parse
trees. In OLTP environments where a large numbers of users are entering and
Library Numeric exchanging data, there is a great chance for overlapping the parse and execute
needs of those different queries. Such an overlap in the library is called a cache hit
and the ratio determined to the misses and hits is called Library Cache Hit Ratio.
SGA Details
Buffer Cache
Numeric The total size of the Buffer Cache given in bytes.
Size
Shared Pool Size Numeric The size of the shared pool given in bytes.
Shared Pool
Numeric Amount of space utilized in the shared pool in percentage.
Used Size
Redolog Buffer
Numeric The size of the buffers for the Redo Logs in mb.
Size
Library Cache
Numeric The size of the Library Cache given in bytes.
Size
Data Dictionary
Numeric The cache size of the data dictionary or row cache in bytes.
Cache Size
SQL Area Size Numeric The size of the SQL Area for usage of SQL/PL statements in bytes.
Fixed Area Size Numeric The size of the SGA, which is fixed throughout the instance.
Oracle DB Links
DB link name String Name of the database link
Owner String Owner of the database link
User String Name of the user when logging in
Oracle Net
String Host Name
connect string
Creation time String Creation time of the database link
Invalid Objects
Owner String Owner of the invalid dba object.
Object Name String Name of the invalid object.
Status String Status of the invalid object.
Invalid/Unusable Indexes
Index Name String Name of the indexParameters Type Description
Tablespace
String Name of the tablespace containing the index
Name
Owner String Owner of the index
Table Name String Name of the indexed object
Indicates whether a nonpartitioned index is VALID or UNUSABLE. We list all
Index Status String
UNUSABLE indexes.
Note: Metrics marked with ** are mapped under Admin → Performance Polling.
PDB
Parameter Type Description
Pluggable Database (PDB) Details
Name String Name of the pluggable database.
Open Mode String Displays the open mode information like MOUNTED, READ WRITE, READ ONLY.
Database Size Numeric Size of the pluggable database in MB.
Database Block Size Numeric Size of the pluggable database block in MB.
By clicking over the PDB name, you will be redirected to the Oracle PDB monitoring dashboard.
Tablespace
Parameter Type Description
Table Space Details
Name String Refers to the name of the Table space.
Allocated
Numeric Refers to the size of the Table space in bytes.
Bytes
Allocated
Numeric Refers to the number of allocated blocks in Table space.
Blocks
Data Files Numeric Refers to the number of data files in Table space.
Table Space Status
Name String Refers to the name of the Table space.
Status String Tablespace status: ONLINE, OFFLINE, or INVALID (tablespace has been dropped)
Free Bytes Numeric Refers to the available free space in bytes.
Free Blocks Numeric Refers to the number of free blocks in Table space.
Reads Numeric Refers to the number of reads from the Table space.
Writes Numeric Refers to the number of writes on the Table space.
Read Time Numeric Time taken for a single read from the Table space.
Write Time Numeric Time taken for a single write on the Table space.
Performance of Data Files
Data File
String Name and location of the data file.
Name
Table
Space String Name of the Table space.
Name
If a data file is a part of the system table space, its status is SYSTEM (unless it requires
recovery). If a data file in a non-SYSTEM table space is online, its status is ONLINE. If a
Status String
data file in non-SYSTEM table space is offline, its status can be either OFFLINE OR
RECOVER.
AutoExtend String Indicates whether AutoExtend is enabled for this data file or not.
Created
Numeric Size of the Data file in bytes.
Bytes
Reads Numeric Refers to the number of reads from the Data file.Parameter Type Description
Writes Numeric Refers to the number of writes to the Data file.
Average
Numeric Refers to the average read time.
Read Time
Average
Numeric Refers to the average write time.
Write Time
Objects Approaching MAX Extents
Owner String Owner name of the table space.
TableSpace
String Name of the TableSpace.
Name
Segment
String Name of the segment approaching maximum extents
Name
Segment
String The type of segment approaching maximum extents
Type
Extents Numeric Number of extents allocated to the segment
Max Extents Numeric Maximum allowed extents that can be filled in a segment
Next Extent
Numeric Next extent size in MB
(MB)
Note: Data collection is scheduled to take place once a day; the user can use the ''Optimize Data Collection''
option to change the schedule.
Session
Parameter Type Description
Session Details
ID String Session Identifier for the connected session.
Status String Current status: ONLINE, OFFLINE, or INVALID (tablespace has been dropped).
Machine String Name of the operating system user.
User
String Name of the Oracle process user.
Name
Elapsed
Numeric Time elapsed in seconds after which the user has logged into the oracle server.
Time
CPU Used Numeric CPU centiseconds (divide by 100 to get real CPU seconds) used by this session.
Memory
Numeric Number of memory sorts performed.
Sorts
Table
Numeric Number of table scans performed.
Scans
Physical
Numeric Physical reads for the session.
Reads
Logical
Numeric Sum of consistent gets and db block gets.
Reads
Commits Numeric Number of commits made by user in a second.
Cursor Numeric Number of cursor currently in use.
Buffer
Percentage of session logical reads taking place from the buffer (1 - physical
Cache Hit Numeric
reads/session logical reads * 100).
Ratio
Session Waits
ID String Session Identifier for the connected session.
User
String Name of the Oracle process user.
Name
Event Numeric Resource or event for which the session is waiting
State Numeric Wait state:
0 - WAITING (the session is currently waiting)
-2 - WAITED UNKNOWN TIME (duration of last wait is unknown)-1 - WAITED SHORT TIME (last wait <1/100th of a second)
>0 - WAITED KNOWN TIME (WAIT_TIME = duration of last wait)
A non-zero value is the session''s last wait time (in milliseconds). A zero value means the
Wait Time Numeric
session is currently waiting.
If WAIT_TIME = 0, then SECONDS_IN_WAIT is the seconds spent in the current wait
Seconds condition. If WAIT_TIME > 0, then SECONDS_IN_WAIT is the seconds since the start of the
Numeric
in Wait last wait, and SECONDS_IN_WAIT - WAIT_TIME / 100 is the active seconds since the last
wait ended.
Users
Username String The username assigned to the user.
Expiry
String The date when the user account expires.
Date
Days to
Numeric The number of days to account expiration.
Expiry
Account
String The current status of the user account.
Status
User
String The profile name of user.
Profile
Rollback & Corrupted blocks
Parameter Type Description
Rollback Segment
Segment
String Name of the rollback segment.
Name
Table Space
String Name of the tablespace containing the rollback segment.
Name
ONLINE if the segment is online, or PENDING OFFLINE if the segment is going offline but
Status String some active (distributed) transactions are using the rollback segment. When the
transaction(s) complete, the segment goes OFFLINE.
Current Size Numeric Current size in bytes of the rollback segment.
Initial Extent Numeric Initial extent size in bytes.
Next Extent Numeric Secondary extent size in bytes.
Min. Extent Numeric Minimum number of extents.
Max. Extent Numeric Maximum number of extents.
Hit Ratio Numeric Ratio of gets to waits. This should be >= 99%.
HWMSize Numeric High Water Mark of rollback segment size.
Number of times rollback segment shrank, eliminating one or more additional extents
Shrinks Numeric
each time.
Wraps Numeric Number of times rollback segment wraps from one extent to another.
Extend Numeric Number of times rollback segment was extended to have a new extent.
Blocks Corrupted
File Number Numeric Datafile number
Data File
String Name of the database file.
Name
Block
Numeric First block of the corrupted range
Number
Number of
corrupted Numeric Number of contiguous blocks in the corrupted range
blocks
Type of String Type of block corruption in the datafile:
block
ALL ZERO - Block header on disk contained only zeros. The block
corruption
may be valid if it was never filled and if it is in an Oracle7 file. The
buffer will be reformatted to the Oracle8 standard for an empty
block.FRACTURED - Block header looks reasonable, but the front and back
of the block are different versions.
CHECKSUM - optional check value shows that the block is not
self-consistent. It is impossible to determine exactly why the check
value fails, but it probably fails because sectors in the middle of the
block are from different versions.
CORRUPT - Block is wrongly identified or is not a data block (for
example, the data block address is missing)
LOGICAL - Specifies the range is for logically corrupt blocks.
CORRUPTION_CHANGE# will have a nonzero value.
Fast Recovery Area
FRA Name String Current location of the FRA.
FRA Space The maximum amount of disk space that the database can use for the flash recovery
Numeric
Limit area (in MB).
FRA Space The amount of disk space used by flash recovery area files created in current and all
Numeric
Used previous flash recovery areas (in MB).
Used The percentage of disk space used by flash recovery area files created in current and all
Numeric
Percentage previous flash recovery areas.
FRA Space
Reclaimable Numeric The amount of flash recovery area that is reclaimable (in MB).
Limit
FRA
Reclaimable Numeric The percentage of the amount of flash recovery area that is reclaimable.
Percentage
FRA Actual
Used Numeric The percentage of the amount of flash recovery area used, including reclaimable space.
Percentage
Note: Data collection is scheduled to take place once every 12 hours; the user can use the ''Optimize Data
Collection'' option to change the schedule.
SGA
Parameter Type Description
SGA Performance: Graph displaying value (in %) of Buffer Cache Hit Ratio, Data Buffer Hit Ratio, Data Dictionary
Hit Ratio and Library Hit Ratio vs time
Buffer
Cache Hit Numeric Percentage of cache hits taking place from the buffer cache.
Ratio
When a scan of the buffer cache shows that there are no free buffers, Database Block
Data Writer determines which blocks to be eliminated based on a least recently used algorithm
Buffer Hit Numeric or LRU. Having a block required by a user process in the buffer cache already is called a
Ratio buffer cache hit or is determined as a ratio. Hits are good because they reduce the
amount of disk I/O required for the user process.
The purpose of the row or dictionary cache is to store rows of information from the data
dictionary in memory for faster access. The row cache is designed to hold the actual rows
Data
of data from objects in data dictionary. While this data is held in the row cache, the users
Dictionary Numeric
of the database may access that information more quickly than if Oracle had to read the
Hit Ratio
data into memory from disk. The ratio of the data gets to the data misses in the row cache
is Data Dictionary Hit Ratio.
The Library cache stores all shared SQL and PL/SQL blocks, along with their parse trees.
In OLTP environments where a large numbers of users are entering and exchanging data,
Library Hit
Numeric there is a great chance for overlapping the parse and execute needs of those different
Ratio
queries. Such an overlap in the library is called a cache hit and the ratio determined to the
misses and hits is called Library Cache Hit Ratio.
SGA Details
Buffer
Cache Numeric The total size of the Buffer Cache given in bytes.
Size
Shared Numeric The size of the shared pool given in bytes.Pool Size
Shared
Pool Used Numeric Amount of space utilized in the shared pool in percentage.
Size
Redolog
Numeric The size of the buffers for the Redo Logs in bytes.
Buffer Size
Library
Cache Numeric The size of the Library Cache given in bytes.
Size
Data
Dictionary
Numeric The cache size of the data dictionary or row cache in bytes.
Cache
Size
SQL Area
Numeric The size of the SQL Area for usage of SQL/PL statements in bytes.
Size
Fixed Area
Numeric The size of the SGA, which is fixed throughout the instance.
Size
SGA Status
When a scan of the buffer cache shows that there are no free buffers, Database Block
Writer determines which blocks to be eliminated based on a least recently used algorithm
Buffer Hit
Numeric or LRU. Having a block required by a user process in the buffer cache already is called a
Ratio
buffer cache hit or is determined as a ratio. Hits are good because they reduce the
amount of disk I/O required for the user process.
The purpose of the row or dictionary cache is to store rows of information from the data
dictionary in memory for faster access. The row cache is designed to hold the actual rows
Data
of data from objects in data dictionary. While this data is held in the row cache, the users
Dictionary Numeric
of the database may access that information more quickly than if Oracle had to read the
Hit Ratio
data into memory from disk. The ratio of the data gets to the data misses in the row cache
is Data Dictionary Hit Ratio.
The Library cache stores all shared SQL and PL/SQL blocks, along with their parse trees.
In OLTP environments where a large numbers of users are entering and exchanging data,
Library Hit
Numeric there is a great chance for overlapping the parse and execute needs of those different
Ratio
queries. Such an overlap in the library is called a cache hit and the ratio determined to the
misses and hits is called Library Cache Hit Ratio.
Free
Numeric Refers to the size of the free memory in bytes.
Memory
Query
Query attributes are not monitored by default. Applications Manager allows you to enable/disable data collection
of query metrics. Once enabled, you can also customize the polling interval of these metrics. To monitor query
metrics:
Go to Admin tab.
Click Performance Polling under Discovery and Data Collection.
Under Performance Data Collection, Click on the Optimize Data Collection tab.
Select Oracle from the Monitor Type drop-down menu.
Select Top 10 Queries by Buffer Gets from the Metric Name drop-down menu.
Select how you wish to configure the queries:
By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of
this type, will have the default polling status, until any exclusive customization is done for the monitor.
You can choose between three different polling settings: Never collect data, Collect data in every
polling and Collect data at customized time interval. Changing the polling status of ''Monitor Type'', will
also change any configuration done for its ''Monitors''.
By Monitors - Use this option to change the polling status of any particular monitor(s).
Parameter Type Description
Buffer Gets
Buffer Gets Numeric Number of buffer gets for the child cursorParameter Type Description
Number of executions that took place on the object since it was brought into
Executions Numeric
the library cache
Buffer Gets per
Numeric The ratio of buffer gets to execution in the current polling interval
Executions
Query String First thousand characters of the SQL text for the current cursor
Disk Reads
Disk Reads Numeric Number of disk reads for this child cursor
Number of executions that took place on this object since it was brought into
Executions Numeric
the library cache
Disk Reads per
Numeric The ratio of disk reads to execution in the current polling interval
Executions
Query String First thousand characters of the SQL text for the current cursor
Lock Statistics
Lock statistics are not monitored by default. Applications Manager allows you to enable/disable data collection of
Lock statistics. Once enabled ,you can also customize the polling interval of these metrics. To monitor Lock
statistics:
Go to Admin tab.
Click Performance Polling under Discovery and Data Collection.
Under Performance Data Collection, Click on the Optimize Data Collection tab.
Select Oracle from the Monitor Type drop-down menu.
Select Lock and Wait Statistics from the Metric Name drop-down menu.
Select how you wish to configure the Lock and Wait Statistics:
By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of
this type, will have the default polling status, until any exclusive customization is done for the monitor.
You can choose between three different polling settings: Never collect data, Collect data in every
polling and Collect data at customized time interval. Changing the polling status of ''Monitor Type'', will
also change any configuration done for its ''Monitors''.
By Monitors - Use this option to change the polling status of any particular monitor(s).
Parameter Type Description
Sessions holding a lock
Id Numeric Session identifier of Session holding a lock
Session serial number. Used to uniquely identify a session''s objects. Guarantees that
Serial Numeric session-level commands are applied to the correct session objects if the session ends
and another session begins with the same session ID.
Machine String Operating system machine name.
PROGRAM String Operating system program name.
Lock Wait String Address of lock waiting for; null if none.
Sessions waiting for a lock
Waiting
Numeric ID of Session waiting for lock.
Session ID
Holding
Numeric ID of Session holding lock.
Session ID
Lock Type String The lock type.
Mode
String The mode held.
Held
Mode
String The mode requested.
Requested
Lock ID1,
String The Lock IDs.
ID2
Lock StatisticsObject String Name of the locked object
Name
Session Id Numeric The session ID of a locked object.
Serial Numeric The session serial number. Used to uniquely identify a session''s objects.
Lock Mode Numeric The lock mode in which the session holds the lock.
OS
Numeric The operating system process identifier.
Process ID
If the session STATUS is currently ACTIVE, then the value represents the elapsed time in
Blocked
minutes since the session has become active. If the session STATUS is currently
Session Numeric
INACTIVE, then the value represents the elapsed time in minutes since the session has
Time
become inactive.
Time of
String Login time.
logon
Blocked Sessions
Waiting
Session Numeric Serial number of the session waiting for lock.
Serial
Waiting
Numeric Session ID of the session waiting for lock.
Session ID
Blocking
Numeric Session ID of the blocking session.
Session ID
Waiting
String The SQL query that waiting for lock.
Query
If the session STATUS is currently ACTIVE, then the value represents the elapsed time (in
Blocked minutes) since the session has become active. If the session STATUS is currently
Numeric
Time INACTIVE, then the value represents the elapsed time (in minutes) since the session has
become inactive.
Instance
Numeric ID of the database instance.
ID
OS
Numeric The operating system process ID.
Process ID
Machine String Name of the machine where the blocking session is running.
Program String Name of the program where the blocking session is running.
LogOn
String Date and time of logon.
Time
Jobs & Backup
Parameter Type Description
Schedule jobs details
Job Name String Name of the job.
Current state of the job (DISABLED, RETRY SCHEDULED, SCHEDULED, RUNNING,
Current State String
COMPLETED, BROKEN, FAILED, REMOTE, SUCCEEDED, CHAIN_STALLED)
Last Run
String Status of the job run.
Status
Last Run Date String Last date on which the job started running.
Last Run
Numeric Amount of time the job took to complete during the last run (in seconds)
Duration (sec)
Next Run Date String Next date on which the job is scheduled to run.
Schedule Jobs Stats
Job Name String Name of the job.
Run Count Numeric Number of times the job has run.
Failure Count Numeric Number of times the job has failed to run.
Retry Count Numeric Number of times the job has retried, if it is retrying.Parameter Type Description
Elapsed Time
Numeric Elapsed time since the job was started (in seconds).
(sec)
Running Backup Jobs Count
DB FULL Numeric Number of jobs running of type DB FULL.
RECVR AREA Numeric Number of jobs running of type RECVR AREA.
DB INCR Numeric Number of jobs running of type DB INCR.
DATAFILE
Numeric Number of jobs running of type DATAFILE FULL.
FULL
DATAFILE
Numeric Number of jobs running of type DATAFILE INCR.
INCR
ARCHIVELOG Numeric Number of jobs running of type ARCHIVELOG.
CONTROLFILE Numeric Number of jobs running of type CONTROLFILE.
SPFILE Numeric Number of jobs running of type SPFILE.
Backup Jobs Details
Session Key Numeric The Session identifier.
Type of input files backed up in this session. Can have one of the following values:
DB FULL
RECVR AREA
DB INCR
Backup Type String DATAFILE FULL
DATAFILE INCR
ARCHIVELOG
CONTROLFILE
SPFILE
Last Backup
String Last backup start time.
Time
Backup Status String Back up status with the value FAILED.
Time Taken Numeric Time Taken to complete last back-up (in seconds).
Backup Size
Numeric Backup size in megabytes.
(MB)
Backup Jobs History Recent Backups
Backup Type String Type of input files backed up in this session.
Session Key Numeric The Session identifier.
Last Backup
String Last backup start time.
Time
Backup Status String Back up status with the value FAILED.
Time Taken Numeric Time Taken to complete last back-up (in seconds).
Backup Size
Numeric Backup size in megabytes.
(MB)
Click the Recent backups link on the top right-hand corner of the Backup Job Details table to view recent backup
job detailsfor each backup type.
Note:
Data collection is scheduled to take place once every 12 hours; the user can use the ''Optimize
datacollection'' option to change the schedule.
Limitation: Thresholds configured on older backup jobs status will not be retained for PPM users.
PGA
Parameter Type DescriptionParameter Type Description
TOP 10 Process using PGA - Graphical representation of the PGA used by processes.
PGA Stats Per Process (TOP 10)
Process Id Numeric Oracle process identifier.
Program Name String Program in progress.
PGA used (MB) Numeric Amount of PGA memory consumed in megabytes.
PGA Allocated (MB) Numeric Maximum PGA memory allocated at one time since instance startup.
Max PGA Used (MB) Numeric PGA memory currently used by the process.
Freeable PGA (MB) Numeric Allocated PGA memory which can be freed.
PGA Stats
Total PGA used (MB) Numeric Indicates how much PGA memory is currently consumed.
Total PGA allocated (MB) Numeric Current amount of PGA memory allocated by the instance.
Maximum PGA allocated
Numeric Maximum amount of PGA memory consumed .
(MB)
Number of bytes of PGA memory in all processes that could be freed
Total freeable PGA (MB) Numeric
back to the operating system.
PGA freed back to OS (MB) Numeric Number of bytes of PGA memory freed back to the operating system.
Percentage of PGA memory component, cumulative since instance
Cache hit percentage Numeric
startup
Resource being used by
Numeric Percentage resources currently being used by processes.
processes (%)
Resouce limit for processes
Resource being used by
Numeric Resources (locks or processes) currently being used.
processes
Free Resource Numeric Percentage of unused resources.
Process
Parameters Type Description
Session Details
Process Id Numeric Oracle process identifier.
PGA used (MB) Numeric Indicates how much PGA memory is currently consumed.
PGA Stats Per Process (TOP 10)
Process Id Numeric Oracle process identifier.
Program Name String The program in progress.
PGA used(MB) Numeric Indicates how much PGA memory is currently consumed.
PGA
Numeric Current amount of PGA memory allocated by the instance.
Allocated(MB)
Max PGA
Numeric Maximum amount of PGA memory consumed .
Used(MB)
Freeable Number of bytes of PGA memory in all processes that could be freed back to the
Numeric
PGA(MB) operating system.
ASM
Applications Manager allows you to enable/disable data collection of several metrics. Once enabled ,you can also
customize the polling interval of these metrics. Data collection for ASM is not enabled by default and here is how
you can enable it:
Enabling ASM Metrics
Go to the Admin tab.
Click Performance Polling under Discovery and Data Collection.
Under Performance Data Collection, Click on the Optimize Data Collection tab.Select Oracle from the Monitor Type drop-down menu.
Select ASM Details from the Metric Name drop-down menu.
Select how you wish to configure the mertics:
By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of
this type, will have the default polling status, until any exclusive customization is done for the monitor.
You can choose between three different polling settings: Never collect data, Collect data in every
polling and Collect data at customized time interval. Changing the polling status of ''Monitor Type'', will
also change any configuration done for its ''Monitors''.
By Monitors - Use this option to change the polling status of any particular monitor(s).
Click Save.
Parameter Type Description
Disk Group Details
Disk Group
Numeric Cluster-wide number assigned to the disk group.
Number
Name String Name of the disk group.
State of the disk group relative to the instance (Connected, Broken, Unknown,
State String
Dismounted, Mounted).
Type String Redundancy type for the disk group (EXTERN, NORMAL, HIGH).
Total Memory
Numeric Total capacity of the disk group (in megabytes).
(GB)
Free Memory
Numeric Unused capacity of the disk group (in megabytes).
(GB)
RPO
RPO statistics are not monitored by default. Applications Manager allows you to enable/disable data collection of
RPO statistics. Once enabled, you can also customize the polling interval of these metrics. To monitor RPO
statistics:
Go to Admin tab.
Click Performance Polling under Discovery and Data Collection.
Under Performance Data Collection, Click on the Optimize Data Collection tab.
Select Oracle from the Monitor Type drop-down menu.
Select Log Apply Gap details in Primary Server/Log Apply Lag details in Standby Server from the Metric
Name drop-down menu.
Select how you wish to configure the Log Apply Gap details:
By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of
this type, will have the default polling status, until any exclusive customization is done for the monitor.
You can choose between three different polling settings: Never collect data, Collect data in every
polling and Collect data at customized time interval. Changing the polling status of ''Monitor Type'', will
also change any configuration done for its ''Monitors''.
By Monitors - Use this option to change the polling status of any particular monitor(s).
Log Apply Gap Details
For Primary and Physical Standby Databases:
Parameter Type Description
Thread Numeric Indicates the thread number.
Last Sequence
Numeric Shows the last log sequence that was received by the database.
Received
Last Sequence
Numeric Shows the last log sequence that was applied to the database.
Applied
Shows the difference between log sequence received and the log sequence
Log apply gap Numeric
applied.
For Logical Standby databases:Parameter Type Description
Type String Type of the log applied.
SCN Numeric The System Change Number (SCN) of the database.
Time String Timestamp of the log that was applied.
Sequence Numeric Sequence number of the log that was applied.
Log Apply Lag Details
Parameter Type Description
Log Apply Lag Details (only from standby)
Transport Transport lag is a measure of the degree to which the transport of redo to the standby
Numeric
Lag database lags behind the generation of redo on the primary database. (no units)
Log Apply Log Apply lag is a measure of the degree to which the redo data on the standby database
Numeric
Lag lags behind the primary database. (no units)
Apply
Estimated time before log apply services will finish applying the redo data available on
Finish Numeric
the standby database. (in minutes)
Time
Archive Log Destination Details are not monitored by default. Applications Manager allows you to enable/disable
data collection of archive log destination metrics. Once enabled ,you can also customize the polling interval of
these metrics. To monitor metrics:
Go to Admin tab.
Click Performance Polling under Discovery and Data Collection.
Under Performance Data Collection, Click on the Optimize Data Collection tab.
Select Oracle from the Monitor Type drop-down menu.
Select Archive Log Destination Monitoring from the Metric Name drop-down menu.
Select how you wish to configure the queries:
By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of
this type, will have the default polling status, until any exclusive customization is done for the monitor.
You can choose between three different polling settings: Never collect data, Collect data in every
polling and Collect data at customized time interval. Changing the polling status of ''Monitor Type'', will
also change any configuration done for its ''Monitors''.
By Monitors - Use this option to change the polling status of any particular monitor(s).
Parameter Type Description
Archive Log Destination Details (only from primary)
Dest Id Numeric Identifies the log archive destination parameter
Name String Archived log file name.
Status String Status of the archived log.
Type of archival destination database:
LOCAL - Local to primary database
Type String PHYSICAL - Physical standby
CROSS-INSTANCE - An instance of the primary
LOGICAL - Logical standby
Destination String Original destination from which the archive log was generated.
Indicates whether the database is protected:
MAXIMUM PROTECTION
Protection MAXIMUM AVAILABILITY
String
Mode RESYNCHRONIZATION
MAXIMUM PERFORMANCE
UNPROTECTEDParameter Type Description
Specifies network transmission mode:
SYNCHRONOUS
Transmit
String
mode
PARALLELSYNC
ASYNCHRONOUS
Current mode of media recovery at the archival destination database:
IDLE - Managed recovery is not active
MANUAL - Manual media recovery active
Recovery
String
mode MANAGED - Managed recovery is active
MANAGED REAL TIME APPLY - Log apply services recover redo data from standby
redo logs at the same time the logs are being written to, as opposed to recovering
redo from archived redo logs when a log switch occurs
Archive Log Destination Stats (only from primary)
Dest Id Numeric Log archive destination parameter identifier
Log
Numeric Identifies the sequence number of the last archived redo log to be archived
sequence
Net Number of seconds the log writer process will wait for status from the network server of a
Numeric
timeout network operation issued by the log writer process
Fail
Numeric Sequence number of the archived redo log being archived when the last error occurred
Sequence
Archived Identifies the log sequence number of the most recent archived redo log received at the
Numeric
Sequence destination
Applied Identifies the log sequence number of the most recent applied redo log received at the
Numeric
Sequence destination
Delay Identifies the delay interval (in minutes) before the archived redo log is automatically
Numeric
(Mins) applied to a standby database
Error String Displays the error text
Alert Logs
Alert Logs are not monitored by default. Applications Manager allows you to enable/disable data collection for
Lock statistics. Once enabled, you can also customize the polling interval of these metrics. To monitor Alert Log
Statistics:
Go to the Admin tab.
Click Performance Polling under Discovery and Data Collection.
Under Performance Data Collection, click on the Optimize Data Collection tab.
Select Oracle from the Monitor Type drop-down menu.
Select Oracle Alert Log from the metric drop-down menu.
Select how you wish to configure the Alert Log Statistics:
By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of
this type will have the default polling status, until any exclusive customization is performed. You can
choose between three different polling settings: Never collect data, Collect data at every poll and
Collect data at customized time interval. Changing the polling status of ''Monitor Type'', will also change
any configuration done for its ''Monitors''.
By Monitors - Use this option to change the polling status of a particular monitor(s).
Oracle Error List table lists only recent errors. To view history of ORA errors, click View Alert Log history.
Monitored Parameters
Parameter Type Description
Oracle ORA Error CountParameter Type Description
Critical / Severe / The number of critical errors, severe errors, important message and
Numeric
Important / Normal normal messages.
Oracle ORA Error List
The record number for the message (this value is same as the row
Record ID Numeric
number).
Level the message belongs to. Lower level values imply higher severity for
errors. Possible values include:
1: CRITICAL: critical errors
Message Level String
2: SEVERE: severe errors
8: IMPORTANT: important message
16: NORMAL: normal message
Originating Time String The date and time at which the message was generated.
Host Address String The IP of other network address of the originating host for the mesaage.
Message Text String The fully formed and localized text of the message.
Redo Logs
Redo Logs are not monitored by default. To enable Redo Log monitoring:
Go to the Admin Tab
Click Performance polling.
Go to the Optimize data collection tab.
Select Oracle from the Monitor Type drop-down menu.
Select Redo Logs.
Parameter Type Description
REDO PERFORMANCE
Buffer
The ratio of redo buffer allocation retries/redo writes in Percentage. Ideal value is upto
Allocation Numeric
1%.
Retries Ratio
Space
Numeric The ratio of redo log space requests/redo entries in Percentage.Ideal value is upto 1%.
Request Ratio
Space Wait
Numeric The ratio of redo log space requests/redo writes in Percentage.Ideal value is upto 1%
Ratio
REDO LOG DETAILS
RedoLog
Numeric The size of the buffers for the Redo Logs in Mb.
Buffer Size
Log switches
Numeric The average number of log switches in the last hour.
in past 1 hour
Current Redo
Numeric The percentage of redo logs used/filled up.
Log Usage
REDO LOG GROUPS INFORMATION
Group Numeric The redo log group identifier.
The number of redo log threads. (The redo log file groups of an instance are
Thread Numeric
collectively called a redo log thread.)
Log Size
Numeric The size of each log in the redo log groups.
(MB)
Member
Numeric The number of members in the log group.
Count
Archive Archive status: YES or NO. (Oracle lets you save filled groups of redo log files to one or
String
Status more offline destinations, known as the archived redo log.)Parameter Type Description
Log status:
UNUSED - Online redo log has never been written to. This is the state of a redo log
that was just added, or just after a RESETLOGS, when it is not the current redo log.
CURRENT - Current redo log. This implies that the redo log is active. The redo log
could be open or closed.
ACTIVE - Log is active but is not the current log. It is needed for crash recovery. It
may be in use for block recovery. It may or may not be archived.
Log Status String
CLEARING - Log is being re-created as an empty log after an ALTER DATABASE
CLEAR LOGFILE statement. After the log is cleared, the status changes to
UNUSED.
CLEARING_CURRENT - Current log is being cleared of a closed thread. The log can
stay in this status if there is some failure in the switch such as an I/O error writing
the new log header.
INACTIVE - Log is no longer needed for instance recovery. It may be in use for
media recovery. It may or may not be archived.
REDO LOG MEMBERS INFORMATION
Member
String The redo log member name.
Name
Group Numeric The redo log group identifier.
The status of the log member:
INVALID - File is inaccessible
Member
String STALE - File''s contents are incomplete
Status
DELETED - File is no longer used
IN USE - File is in use
The member status type:
Member
String ONLINE
Type
STANDBY
Oracle Pluggable Database (PDB) Servers
Overview
Multitenancy is the new feature introduced in Oracle 12c and it is the concept of consolidating Pluggable
Databases (PDB) into a single database server. Starting in Oracle Database 12c Release 1 (12.1), you must create a
database as either a Multitenant Container Database (CDB) or as an Oracle database that is non-CDB. A Pluggable
Database (PDB) is a portable collection of Schemas, Schema Objects, and Non-Schema Objects that appears as a
separate database with its own instance name.
Monitored Parameters
Prerequisites for monitoring Oracle PDB metrics: Click here
Go to the Monitors Category View by clicking the Monitors tab. Click on Oracle PDB Server under the Database
Servers table. Displayed is the Oracle PDB servers bulk configuration view in three tabs:
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the server details listed under the following tabs:
Overview
Tablespace
SessionQuery
Lock Statistics
Jobs
Overview
Parameters Type Description
Database Details
Database
String Creation time of the database.
Created Time
Open Mode String Indicates the Open mode of the Instance which can be either Read Write or Read.
The two Log Modes are:
NOARCHIVELOG - When you run your database in NOARCHIVELOG mode, you
Log Mode String disable the archiving of the redo log.
ARCHIVELOG - When you run a database in ARCHIVELOG mode, you enable the
archiving of the redo log.
Indicates whether the next database open allows or requires the resetlogs option
NOT ALLOWED
Open Reset Logs String
ALLOWED
REQUIRED
Protects data from being changed:
ALL - Indicates all users other than SYS are prevented from making changes to
any data in the database.
Guard Status String
STANDBY - Indicates all users other than SYS are prevented from making
changes to any database object being maintained by logical standby.
NONE - Indicates normal security for all data in the database.
Database Status
Database Size ** Numeric Size of the database in Megabytes.
Average This is the average number of executions that happen during the execution of every
Numeric
Executions SQL Statement.
Total Reads Numeric Number of reads from the database.
Total Writes Numeric Number of writes to the database.
Database Block
Numeric Refers to the lowest possible storage area for an Instance (in MB).
Size
Free Space ** Numeric Size of free extents in all tablespaces in the database (in MB).
Invalid/Unusable
Numeric Number of Invalid/Unusable indexes in the database.
Index Count
Current SCN Numeric Current System Change Number (SCN) of the database.
Data transferred
Numeric Total data sent and received via SQL*Net services (in MB).
via SQL*Net
Database CPU
Numeric Ratio of DB CPU time to DB time. Ideal value is greater than 90%.
Time Ratio
Connection Statistics
Response Time Numeric The time taken to connect to the database (in milliseconds).
Session Activity
Number of User
Numeric The number of user sessions running in the database.
Sessions
Table spaces with least free bytes
Name String The name of the TableSpace.
Free Bytes Numeric The free space available in MB.Parameters Type Description
% of Free Bytes Numeric The percentage of free space available in MB.
Oracle DB Links
DB Link Name String Name of the database link.
Owner String Owner of the database link.
User String Name of the user using the database link.
Oracle Net
String The Oracle Net Connection String of the database link.
Connect String
Creation time String Creation time of the database link.
Invalid Objects
Owner String Owner of the invalid dba object.
Object Name String Name of the invalid object.
Status String Status of the invalid object.
Invalid/Unusable Indexes
Index Name String Name of the index
Tablespace
String Name of the tablespace containing the index
Name
Owner String Owner of the index
Table Name String Name of the indexed object
Indicates whether a nonpartitioned index is VALID or UNUSABLE. We list all
Index Status String
UNUSABLE indexes.
Note: Metrics marked with ** are mapped under Admin → Performance Polling.
Tablespace
Parameter Type Description
TableSpace Details
Name String Name of the Table space.
Allocated
Numeric Allocated size of the TableSpace in MB.
Bytes
Total
Allocated Numeric Allocated size of the TableSpace in MB.
Bytes
Used Bytes Numeric Used size of the TableSpace in MB.
Free Bytes Numeric Available free space of the TableSpace in MB.
Percentage
of Used Numeric Used size of the TableSpace in percentage.
Bytes
Percentage
of Free Numeric Available free space of the TableSpace in percentage.
Bytes
Allocated
Numeric Number of allocated blocks in TableSpace.
Blocks
Free Blocks Numeric Number of free blocks in TableSpace.
TableSpace Status
Name String Name of the Table space.
Status String Tablespace status: ONLINE, OFFLINE, or INVALID (tablespace has been dropped)
Data Files Numeric Number of data files in TableSpace.
Reads Numeric Number of reads from the TableSpace per minute.
Writes Numeric Number of writes on the TableSpace per minute.
Read Time Numeric Time taken for a single read from the TableSpace in centiseconds.Parameter Type Description
Write Time Numeric Time taken for a single write on the TableSpace in centiseconds.
Performance of Data Files
Data File
String Name and location of the data file.
Name
TableSpace
String Name of the Table space.
Name
If a data file is a part of the system table space, its status is SYSTEM (unless it requires
recovery). If a data file in a non-SYSTEM table space is online, its status is ONLINE. If a
Status String
data file in non-SYSTEM table space is offline, its status can be either OFFLINE OR
RECOVER.
AutoExtend String Indicates whether AutoExtend is enabled for this data file or not.
Created
Numeric Size of the Data file in MB.
Bytes
Reads Numeric Number of reads from the Data file.
Writes Numeric Number of writes to the Data file.
Average
Numeric The average time taken for read operations to occur in milliseconds.
Read Time
Average
Numeric The average time taken for write operations to occur in milliseconds.
Write Time
Objects Approaching MAX Extents
Owner String Owner name of the table space.
TableSpace
String Name of the TableSpace.
Name
Segment
String Name of the segment approaching maximum extents
Name
Segment
String The type of segment approaching maximum extents
Type
Extents Numeric Number of extents allocated to the segment
Max Extents Numeric Maximum allowed extents that can be filled in a segment
Next Extent Numeric Size of the Next Extent in MB
Note: Data collection is scheduled to take place once a day; the user can use the ''Optimize Data Collection''
option to change the schedule.
Session
Parameter Type Description
Session Details
ID Numeric Session Identifier for the connected session.
Serial String Serial number of the connected session.
Status String Current status: ONLINE, OFFLINE, or INVALID (tablespace has been dropped).
Machine String Name of the machine.
User
String Name of the Oracle process user.
Name
Elapsed
Numeric Time elapsed in seconds after which the user has logged into the oracle server.
Time
CPU Used Numeric Amount of time the CPU was in use by the session in centiseconds.
Memory
Numeric Number of memory sorts performed.
Sorts
Table
Numeric Number of table scans performed.
Scans
Physical
Numeric Physical reads for the session.
ReadsLogical Numeric Sum of consistent gets and db block gets.
Reads
Commits Numeric Number of commits made by user in a second.
Cursor Numeric Number of cursor currently in use.
Buffer
Cache Hit Numeric Amount of session logical reads taking place from the buffer in percentage.
Ratio
Sessions Summary
Machine String Name of the machine.
Program String Name of the program.
Session
String Status of the sessions.
Status
Session
Numeric Number of sessions available.
Count
Session Waits
ID String Session Identifier for the connected session.
User
String Name of the Oracle process user.
Name
Event Numeric Resource or event for which the session is waiting
Wait state:
0 - WAITING (the session is currently waiting)
State Numeric -2 - WAITED UNKNOWN TIME (duration of last wait is unknown)
-1 - WAITED SHORT TIME (last wait <1/100th of a second)
>0 - WAITED KNOWN TIME (WAIT_TIME = duration of last wait)
A nonzero value is the session''s last wait time (in milliseconds). A zero value means the
Wait Time Numeric
session is currently waiting.
If WAIT_TIME = 0, then SECONDS_IN_WAIT is the seconds spent in the current wait
Seconds condition. If WAIT_TIME 0, then SECONDS_IN_WAIT is the seconds since the start of the
Numeric
in Wait last wait, and SECONDS_IN_WAIT - WAIT_TIME / 100 is the active seconds since the last
wait ended.
Users
Username String The username assigned to the user.
Expiry
String The date when the user account expires.
Date
Days to
Numeric The number of days to account expiration.
Expiry
Account
String The current status of the user account.
Status
User
String The profile name of user.
Profile
Query
Query attributes are not monitored by default. Applications Manager allows you to enable/disable data collection
of query metrics. Once enabled, you can also customize the polling interval of these metrics. To monitor query
metrics:
Go to Admin tab.
Click Performance Polling under Discovery and Data Collection.
Under Performance Data Collection, Click on the Optimize Data Collection tab.
Select Oracle PDB from the Monitor Type drop-down menu.
Select Top 10 Queries by Buffer Gets from the Metric Name drop-down menu.
Select how you wish to configure the queries:
By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of
this type, will have the default polling status, until any exclusive customization is done for the monitor.
You can choose between three different polling settings: Never collect data, Collect data in everypolling and Collect data at customized time interval. Changing the polling status of ''Monitor Type'', will
also change any configuration done for its ''Monitors''.
By Monitors - Use this option to change the polling status of any particular monitor(s).
Parameter Type Description
Buffer Gets
Buffer Gets Numeric Number of buffer gets for the child cursor
Number of executions that took place on the object since it was brought into
Executions Numeric
the library cache
Buffer Gets per
Numeric The ratio of buffer gets to execution in the current polling interval
Executions
Query String First thousand characters of the SQL text for the current cursor
Disk Reads
Disk Reads Numeric Number of disk reads for this child cursor
Number of executions that took place on this object since it was brought into
Executions Numeric
the library cache
Disk Reads per
Numeric The ratio of disk reads to execution in the current polling interval
Executions
Query String First thousand characters of the SQL text for the current cursor
Lock Statistics
Lock statistics are not monitored by default. Applications Manager allows you to enable/disable data collection of
Lock statistics. Once enabled ,you can also customize the polling interval of these metrics. To monitor Lock
statistics:
Go to Admin tab.
Click Performance Polling under Discovery and Data Collection.
Under Performance Data Collection, Click on the Optimize Data Collection tab.
Select Oracle PDB from the Monitor Type drop-down menu.
Select Lock and Wait Statistics from the Metric Name drop-down menu.
Select how you wish to configure the Lock and Wait Statistics:
By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of
this type, will have the default polling status, until any exclusive customization is done for the monitor.
You can choose between three different polling settings: Never collect data, Collect data in every
polling and Collect data at customized time interval. Changing the polling status of ''Monitor Type'', will
also change any configuration done for its ''Monitors''.
By Monitors - Use this option to change the polling status of any particular monitor(s).
Parameter Type Description
Sessions holding a lock
Id Numeric Session identifier of Session holding a lock
Session serial number. Used to uniquely identify a session''s objects. Guarantees that
Serial Numeric session-level commands are applied to the correct session objects if the session ends
and another session begins with the same session ID.
Machine String Operating system machine name.
PROGRAM String Operating system program name.
Lock Wait String Address of lock waiting for; null if none.
Sessions waiting for a lock
Waiting
Numeric ID of Session waiting for lock.
Session ID
Holding
Numeric ID of Session holding lock.
Session ID
Lock Type String The lock type.
Mode String The mode held.
Held Mode
String The mode requested.
Requested
Lock ID1,
String The Lock IDs.
ID2
Lock Statistics
Object
String Name of the locked object
Name
Session Id Numeric The session ID of a locked object.
Serial Numeric The session serial number. Used to uniquely identify a session''s objects.
Lock Mode Numeric The lock mode in which the session holds the lock.
OS
Numeric The operating system process identifier.
Process ID
If the session STATUS is currently ACTIVE, then the value represents the elapsed time in
Blocked
minutes since the session has become active. If the session STATUS is currently
Session Numeric
INACTIVE, then the value represents the elapsed time in minutes since the session has
Time
become inactive.
Time of
String Login time.
logon
Blocked Sessions
Waiting
Session Numeric Serial number of the session waiting for lock.
Serial
Waiting
Numeric Session ID of the session waiting for lock.
Session ID
Blocking
Numeric Session ID of the blocking session.
Session ID
Waiting
String The SQL query that waiting for lock.
Query
If the session STATUS is currently ACTIVE, then the value represents the elapsed time (in
Blocked minutes) since the session has become active. If the session STATUS is currently
Numeric
Time INACTIVE, then the value represents the elapsed time (in minutes) since the session has
become inactive.
Instance
Numeric ID of the database instance.
ID
OS
Numeric The operating system process ID.
Process ID
Machine String Name of the machine where the blocking session is running.
Program String Name of the program where the blocking session is running.
LogOn
String Date and time of logon.
Time
Jobs
Parameter Type Description
Schedule Job Details
Job Name String Name of the job.
Current Current state of the job (DISABLED, RETRY SCHEDULED, SCHEDULED, RUNNING,
String
State COMPLETED, BROKEN, FAILED, REMOTE, SUCCEEDED, CHAIN_STALLED)
Last Run
String Status of the job run.
Status
Last Run
String Last date on which the job started running.
Date
Last Run
Numeric Amount of time the job took to complete during the last run (in seconds)
Duration
Next Run
String Next date on which the job is scheduled to run.
DateParameter Type Description
Schedule Job Stats
Job Name String Name of the job.
Run Count Numeric Number of times the job has run.
Failure
Numeric Number of times the job has failed to run.
Count
Retry
Numeric Number of times the job has retried, if it is retrying.
Count
Elapsed
Numeric Elapsed time since the job was started (in seconds).
Time
Is Enabled String Indicates whether the job is enabled or not.
MS SQL DB Servers Monitoring
MS SQL Server - An Overview
Creating a new MS SQL database monitor
Monitored Parameters
MS SQL Server - An Overview
Applications Manager''s SQL Server monitoring feature helps database administrators monitor the performance
and availability of production databases. It is an agentless monitoring solution that provides out-of-the-box
performance metrics making sure that the SQL server runs efficiently.
Creating a new MS SQL database monitor
Supported Versions - Applications Manager supports monitoring of MS SQL 2000, 2005, 2008, 2008 R2, 2012,
2014, 2016, 2017 and 2019 versions.
Prerequisites to create a new monitor: Click here
To create a MS SQL database server Monitor, follow the given steps:
Click on New Monitor link.
Select MS SQL DB Server.
Enter the IP Address or Hostname of the host.
Enter the subnetmask of the network.
Enter the Port number in which the MS SQL is running.
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Provide the User Name and Password of user who has permission to access the MS SQL database. The user
name specified for collecting the data from MS SQL Server should have either System Administrator role or the
user should be the DB owner for master database. Alternatively, you can provide the Windows Authentication
details (give the User Name like domainname\username) also.
Select the Enable Kerberos Authentication checkbox, if you want to monitor MS SQL server through Kerberos
authentication.
If you want to connect using a Named Instance, check the Connect using Named Instance checkbox and
specify the instance name.
Choose Force Encryption option if the server is configured for encrypted connections.
Choose jTDS JDBC Driver or Microsoft JDBC Driver option in Driver for SQL Server Connection field to
choose the required driver for connecting to the database for data collection.
Choose the Monitor Group from the combo box with which you want to associate MS SQL database server
Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers MS SQL database server from the network and starts monitoring them.
Note: Applications Manager allows you to enable/disable data collection of the SQL Server Performance several
metrics like Jobs, Backup and Replications . Once enabled, you can also customize the polling interval of these
metrics.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on MS SQL under the Databases Table.
Displayed is the MS SQL bulk configuration view distributed into three tabs:Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the MS SQL Database metrics listed under the following tabs:
Overview
Performance
Database
Sessions
Jobs
Backup/Restore
Replication
Users
Configuration
AlwaysOn Availability Groups
SQL Server - Cluster Details
Overview
Parameters Description
Name The name of MS SQL server monitor.
Health The health (Clear, Warning, Critical) of the MS SQL server.
Type The type you are monitoring.
Version The version of the database server.
ODBC Driver
The ODBC driver version used.
Version
Instance Name Name of the SQL instance
Port The port number at which the database server is running.
Host Name The host at which the database server is running.
Host OS The OS of the host where the database server is running.
Last Alarm The last alarm that was generated for the database server.
Last Polled at The time at which the last poll was performed.
Next Poll at The time at which the next poll is scheduled.
Availability Shows the current status of the server - available or not available.
Percentage of pages found in the buffer cache without having to read from disk. If Buffer
Buffer Cache Hit Cache Hit Ratio value is “high”, then SQL Server is efficiently caching the data pages in
Ratio memory, reads from disk are relatively low, and so there is no memory bottleneck. It should be
> 90% for a well performing server.
This metric measures how much the plan cache is being used. A high percentage here means
Plan Cache Hit that your SQL Server is not building a new plan for every query it is executing so is working
Ratio effectively and efficiently. A low percentage here means that for some reason, the SQL Server
is doing more work than it needs to.
MEMORY USAGE
Total Memory The total amount of dynamic memory the server is currently consuming.
SQL Cache
The total amount of dynamic memory the server is using for the dynamic SQL cache.
Memory
Lock Memory The total amount of dynamic memory the server is using for locks.
Optimizer
The total amount of dynamic memory the server is using for query optimization.
Memory
Connection
The total amount of dynamic memory the server is using for maintaining connections.
MemoryParameters Description
Granted
The total amount of memory granted to executing processes. This memory is used for hash,
WorkSpace
sort and create index operations.
Memory
Memory Grants
The current number of processes waiting for a workspace memory grant.
Pending
Memory Grants
The current number of processes that have successfully acquired a workspace memory grant.
Success
BUFFER MANAGER STATISTICS
The percentage of pages that were found in the buffer pool without having to incur a read
Buffer Hit Ratio
from disk.
Page
The number of requests to find a page in the buffer pool.
LookUps/Min
Page Reads/Min The number of physical database page reads issued.
Page Writes/Min The number of physical database page writes issued.
Total Pages The number of pages in the buffer pool (includes database, free, and stolen).
Database Pages The number of pages in the buffer pool with database content.
Free Pages The total number of pages on all free lists.
Page Life
The number of seconds a page will stay in the buffer pool without references.
Expectancy
ACCESS
METHOD
DETAILS
Full Scans/Min The number of unrestricted full scans. These can either be base table or full index scans.
Range
The number of qualified range scans through indexes.
Scans/Min
The number of probe scans. A probe scan is used to directly look up rows in an index or base
Probe Scans/Min
table.
Work Files Displays the number of work files created per minute. These work files could be used to store
Created/Min temporary results for hash joins and hash aggregates.
Work Tables Displays the number of work tables created per minute. These work tables could be used to
Created/Min store temporary results for query spool, LOB variables, XML variables, and cursors.
Free Space Displays the number of scans per minute that were initiated to search for free space within
Scans/Min pages already allocated to an allocation unit to insert or modify record fragments.
Lazy Writes/Min Displays the number of buffers written by buffer manager''s lazy writer per minute.
Scan point
Displays the number of times the scan point had to be revalidated to continue the scan.
Revalidation/Min
Index Displays the number of index searches per minute. These index searches are used to start
Searches/Min range scans, single index record fetches, and to reposition within an index.
CACHE DETAILS
This metric measures how much the plan cache is being used. A high percentage here means
Plan Cache Hit that your SQL Server is not building a new plan for every query it is executing so is working
Ratio effectively and efficiently. A low percentage here means that for some reason, the SQL Server
is doing more work than it needs to.
Total Log Cache Displays the overall total percentage of log cache reads that were satisfied from the log
Hit Ratio cache.
Cache Used/Min Displays the number of times each type of cache object has been used.
Cache Count Displays the number of cache objects in the cache.
Cache Pages Displays the number of 8k pages used by cache objects.
LOCK DETAILS
Lock
The number of new locks and lock conversions requested from the lock manager.
Requests/Min
Lock Waits/Min The total wait time for locks in the last minute.Parameters Description
Lock
The number of lock requests that timed out. This includes internal requests for NOWAIT locks.
Timeouts/Min
Deadlocks/Min The number of lock requests that resulted in a deadlock.
Average Lock
The average amount of wait time for each lock request that resulted in a wait.
Wait Time
LATCH DETAILS
The number of latch requests that could not be granted immediately and had to wait before
Latch Waits/Min
being granted.
Average Latch
The average latch wait time for latch requests that had to wait.
Wait Time
Performance
Parameters Description
TOP QUERIES BY CPU
Avg. CPU Time Average CPU Time taken to execute the query.
The cumulative total amount of CPU time that has been spent running this query since the plan
Total CPU Time
was compiled.
Query The SQL Query Text.
DB Name The database against which this query has been executed.
Last Execution
The last time at which the query started executing.
Time
Average
Average time taken to execute an individual query.
Execution Time
TOP QUERIES BY I/0
Avg. Logical
Average number of logical reads and logical writes performed by executions of this query.
I/O
The cumulative total number of logical reads and logical writes performed by executions of this
Total I/O
query since the plan was compiled.
Query The SQL query text.
The Database against which this query has been executed (will be empty for ad hoc and
DB Name
prepared batches).
Last Execution
The last time at which the query started executing.
Time
Average
Average time taken to execute an individual query.
Execution Time
TOP QUERIES BY CLR (Top 10 queries having high CLR time (Common Language Runtime inside Microsoft .NET
Framework).
Average Time consumed inside Microsoft .NET Framework Common Language Runtime (CLR)
Average CLR
for executions of this query.
The cumulative Total Time consumed inside Microsoft .NET Framework Common Language
Total CLR
Runtime (CLR) objects by executions of this query since the plan was compiled.
DB Name The Database against which this query has been executed.
Last Execution
The last time at which the query started executing.
Time
Average
Average time taken to execute an individual query.
Execution Time
Top Waits by Waiting Tasks
Wait Type Indicates name of the wait type.
Waiting Tasks Displays the number of waits on that particular wait type.
Wait Time Total time in milliseconds for that particular type of wait.
Average Wait
Average time in milliseconds for that particular type of wait.
TimeParameters Description
Displays the difference between the time the waiting thread was signaled and when it started
Signal Time
running.
Top Slow Running Queries
Avg. Execution
Average time taken for complete execution of this query.
Time
Maximum
Maximum elapsed time for any complete execution of this query.
Execution Time
Minimum
Minimum elapsed time for any complete execution of this query.
Execution Time
No of
The number of times that the query has been executed since the plan was last compiled.
Executions
Query The SQL query text.
The Database against which this query has been executed (will be empty for ad hoc and
DB Name
prepared batches).
Object Name Returns the database object name for schema-scoped objects.
Last Execution
The last time at which the query started executing.
Time
Most Frequently Executed Queries
Execution
The number of times that the query has been executed since the plan was last compiled.
Count
Query The SQL query text.
The Database against which this query has been executed (will be empty for ad hoc and
DB Name
prepared batches).
Last Execution
The last time at which the query started executing.
Time
Average
Average time taken to execute an individual query.
Execution Time
Most Blocked Queries
Average Time
The average amount of time the query was blocked.
Blocked
Total Time
The cumulative total amount of time for which the query was blocked.
Blocked
Query The SQL query text.
DB Name The Database against which this query has been executed.
Last Execution
The last time at which the query started executing.
Time
Average
Average time taken to execute an individual query.
Execution Time
Top Queries by Lowest Plan Reuse (Top 10 queries whose query plan are not cached by the SQL Server. Query
plan will be cached by SQL Server for faster query execution.)
Plan Usage Number of times this cache object has been used since its inception.
Cache Object Type of object in the cache. (Possible Values : Compiled Plan / Compiled Plan Stub / Parse Tree
Type / Extended Proc / CLR Compiled Func / CLR Compiled Proc).
Query The SQL Query Text.
The Database against which this query has been executed (will be empty for ad hoc and
DB Name
prepared batches).
Last Execution
The last time at which the query started executing.
Time
Average
Average time taken to execute an individual query.
Execution Time
Cost of Missing Indexes (Displays information of the Top 10 missing indexes in the SQL Server. These indexes
will have varying levels of impact on query performance. From this table, you can find out the most costly
missing indexes across all the databases on the server and thus help finding out which missing indexes are likely
to have the most significant impact on performance.)Parameters Description
Overall cost of the queries executing without having the recommended indexes. It simply is a
unit, the SQL Server Query Optimizer does its calculations with and is not associated with any
type of known measurement unit like seconds or CPU time. Bigger the total cost number, more
Total Cost the resources could be saved after creating the recommended index. You need to check the
query execution plan before creating the index for these particular columns and you need not
check any other details. Also note that every index has a negative impact on the
inserts/updates/deletes on that table and this impact can not be measured.
Displays the average percentage of benefit that the user queries could experience if this
Avg. User
missing index group was implemented. This value means that the query cost would on average
Impact
drop by this percentage if this missing index group was implemented.
Displays the name of table (along with Database Name and Schema Name) in which the index
Table Name
is missing.
Displays the column names for which Index is missing. These column names are used in
Equality Usage
equality predicates of the form: table.column = constant_value
Displays the column names for which Index is missing. These column names are used in
Inequality
inequality predicates ( any comparison operator other than "=" ) of the form: table.column >
Usage
constant_value.
Include Displays the column names for which Index is missing. These column names are Comma-
Columns separated list of columns needed as covering columns for the query.
Top Components by Memory Usage (Displays information about the various Memory clerks. Memory clerks
allocates resource / memory to SQL memory object during times of need.)
Component
The type of memory clerk.
Type
Single The total amount of single page memory allocated in kilobytes (KB) directly from the buffer
Pages(KB) pool. Its is the memory consumed by this component from the Buffer pool.
Multi
The total amount of multipage memory allocated in (KB) from outside the buffer pool.
Pages(KB)
Virtual Memory
The total amount of virtual memory reserved directly by the component that uses this clerk.
Reserved(KB)
Virtual Memory The total amount of virtual memory that is committed by the memory clerk. This should be
Committed(KB) always less than the amount of reserved memory.
AWE Memory The total amount of memory that is allocated by the memory clerk by using Address Windowing
Allocated(KB) Extensions (AWE).
Shared
The total amount of shared memory that is reserved by a memory clerk memory reserved for use
Memory
by shared memory and file mapping.
Allocated(KB)
Shared
Memory The total amount of shared memory that is committed by the memory clerk.
Committed(KB)
Database
Database Management Actions
Applications Manager provides the ability to perform the following actions on your database(s).
Parameters Description
Online Changes the offline database(s) to online state.
Changes the online database(s) to offline state. If there is any open connection in the database,
Offline
this action waits for the connection to be closed and then brings the database offline.
Checks for open connections and changes the online database(s) to offline state only if all
Offline with no
connections are closed. This action returns error without waiting for existing connections to be
wait
closed.
Offline with
Changes the database(s) to offline state immediately and all incomplete transactions are rolled
immediate
back.
rollback
Offline with Waits for the specified period of time for the open connections to close and then brings the
rollback after database offline. If there is any incomplete transactions even after specified period of time, the
given time transactions will be rolled back.Parameters Description
Delete Deletes the selected database(s) permanently from the server.
Database Connection Detail
Parameters Description
Database Name Displays the name of the database.
Login Name Displays the SQL user name connected to the database.
No. of Connections Displays the number of connections currently open in the database.
Parameters Description
Database Details
Name The Name of the database of the SQL server.
Data File (MB) The data file size of the database of the SQL server.
Used The total used space of the data file/log file of the SQL server.
Free The total free space available in the data file/log file of the SQL server.
Total The total alloted size of the data file/log file of the SQL server.
Max size The maximum file size of the data file/log file of the SQL server upto which it can grow.
Log File (MB) The log file size of the database of the SQL server
Used The total used space of the data file/log file of the SQL server.
Free The total free space available in the data file/log file of the SQL server.
Total The total alloted size of the data file/log file of the SQL server.
Max size The maximum file size of the data file/log file of the SQL server upto which it can grow.
Total size (MB) The total file size of the entire database of the SQL server.
Percentage Log
The percentage of Log used of the database of the SQL Server.
Used
Availability The current availability of the database in the SQL Server.
Health The current health of the database in the SQL Server.
The current status of the database of the SQL Server.:
ONLINE: Database is available for query.
INACTIVE: Database is inactive as it is no longer accessed by any application for some
time now.
OFFLINE: Database was explicitly taken offline.
Status
RESTORING: Database is being restored.
RECOVERING: Database is recovering and not yet ready for queries.
SUSPECT: Database did not recover.
EMERGENCY: Database is in an emergency, read-only state. Access is restricted to
sysadmin member.
Click on the database name to see further details:
Parameters Description
System Table Name - Name of the System Table.
System Tables Total Rows - Total number of rows present in that table.
Total Space Used in MB - Size of the table (MB).
Parent Table – Table which contains the primary / parent column for the foreign key.
Table Parent Column – The primary column for which a foreign exists.
Relationship Foreign Table – Table name of foreign key column.
Foreign Column – The foreign key column name.Parameters Description
System Table Name - Name of the User Table.
User Tables Total Rows - Total number of rows present in that table.
Total Space Used in MB - Size of the table (MB).
View Name - Name of the View.
Schema Name - Schema Name to which this view is associated.
IsIndexed - Shows if there is an index for the view ( 1 = Index Present, 0 = No Index ).
View Details IsIndexable - Shows whether an index can be created ( 1 = Index can be created, 0 = No
Index can be created ).
Create Date - Date on which the view was created.
Modify Date - Date on which the view was last modified.
Table Name - Name of the Table.
Index Name - Name of Index present in the table.
Maximum Size Row - Maximum size for a row in that table (in bytes).
Max Noleafindex Row - Maximum size of a nonleaf index row (in bytes).
Index Details File Group Name - Name of the filegroup (Primary or User-defined).
Column Name - Name of the column for which index is present.
Type - Data type of the Column.
Clustered Index - Shows if the index is a Clustered Index or not (Yes or No). A clustered
index determines the physical order of data in a table.
Indexes that Object Name – Name of the table in which the index is present.
have not been Index Name – Name of the index which is not used.
used
Type – Type of the Index.
Table Name - Name of the table in which the index is present
Index Name - Name of Index present in the table
Fragmentation
Fragmentation Percent - Percentage of Logical fragmentation present in the Index. This is
Details
the percentage of out-of-order pages in the leaf pages of an index. The Percentage of
Fragmentation should be as close to zero as possible for maximum performance. However,
values from 0% through 10% may be acceptable
Object Name – Name of the table in which the index is present.
Schema Name – Schema Name to which this table is associated.
Index Name – Name of the index which is not used.
Indexes that
Type – Type of the Index.
have been
used User Seeks - The number of seeks in this index by user queries.
User Scans - The number of scans in this index by user queries.
User Lookups - The number of bookmark lookups in this index by user queries.
User Updates - The number of updates in this index by user queries.
Note: The data file details of the database are updated once in an hour. You can also manually update each data
file of the database by clicking on the ''Update Data/ Log File''.
Parameters Description
Database Disk Utilization
Total Size The total disk space of all available data files(in MB).
Used % The percentage of used disk space.
Used MB The total disk space used by all data files (in MB).
Free % The percentage of free/unused disk space.
Free MB The free/unused disk space (in MB).Parameters Description
Growth % The percentage at which all data files grow.
Data File Details
File Name Name of the data file.
Total Size The total disk space of all available data files(in MB).
Used % The percentage of used disk space.
Used MB The total disk space used by all data files (in MB).
Free % The percentage of free/unused disk space.
Free MB The free/unused disk space (in MB).
Growth % The percentage at which all data files grow.
Growth Rate The rate at which the data files grow.
Maximum size The maximum size (in MB) up to which the data file can grow.
Log File Details
File Name Name of the log file
Total Size The total disk space of all available log files(in MB).
Used % The percentage of used disk space.
Used MB The total disk space used by all log files (in MB).
Free % The percentage of free/unused disk space.
Free MB The free/unused disk space (in MB).
Growth % The percentage at which all log files grow.
Growth Rate The rate at which the log files grow.
Maximum size The maximum size (in MB) up to which the log file can grow.
Transaction Details
Transactions/Min Number of transactions started for the database per minute.
Active
Number of transactions that''s currently executing.
Transactions
Replication
Number of replication transactions per minute.
Transactions/Min
Bulk Copy
Number of rows bulk copied.
Rows/Min
Bulk Copy
Amount of KiloBytes bulk copied.
Throughput/Min
Backup/Restore
Read/write throughput for backup/restore of a database.
Throughput/Min
Log Cache
Reads performed through the log manager cache.
Reads/Min
Log Flush Details
Log Flush/Min Number of log flushes
Log Flush
Number of commits waiting on log flush
Waits/Min
Log Flush Wait
Total wait time (milliseconds)
Time
Log Cache Hit
The log cache hit ratio file size.
Ratio
VLF Details
The number of VLFs (Virtual Log Files) created. A transaction log is split internally into smaller
Number of VLFs chunks called virtual log files. A large number of VLFs can cause degradation in performance
when transaction log backups occur or in any transaction log related activities.
FileID Physical log file identifier from sysfiles
FileSize Virtual log file size ( in bytes )
StartOffset Beginning point of the virtual log fileParameters Description
FSeqNo Virtual log file''s sequence number
Whether the virtual file contains the active part of the transaction log. 0 means that virtual file
Status does not contain the active portion of the log and it is available for log use ; 2 means that VLF
is active
Parity Parity information for virtual log file
CreateLSN Log sequence number that began the virtual log file.
Database Properties
Creation Date Date in which the Database was created.
Database Mode The recovery model for the database which shows how transactions are logged.
Page Verify The option used to discover and report incomplete I/O transactions caused by disk I/O errors.
Compatibility The latest version of SQL Server that the database supports. The values are SQL Server 2014
Level (120), SQL Server 2012 (110), and SQL Server 2008 (100).
Auto Shrink Indicates whether the database files are available for periodic shrinking.
Auto Create
Indicates whether the database automatically creates missing optimization statistics.
Statistics
Auto Update
Indicates whether the database automatically updates out of date optimization statistics.
Statistics
DBCC Information
DBCC CHECKDB Shows when the DBCC CHECKDB command was issued last.
DBCC
Shows when the DBCC INDEXDEFRAG command was issued last.
INDEXDEFRAG
Database Mirroring Details
Applications Manager provides the option to monitor mirroring details of SQL databases. You can monitor
attributes like Mirroring role, Status, Mirroring partner details,Witness details, Unsent log available in Send Queue,
Current send rate, Time to restore log and more.
Parameters Description
Mirroring Role- Displays the role of the mirroring database. The possible values are:
Principal
Mirror
Mirroring Status - Displays the status of mirroring process. The possible values are
Synchronized, Synchronizing, Suspended, Pending failover, Disconnected.
Transaction Safety - Displays whether the mirroring operates in synchronous or
Mirroring asynchronous mode.
Details
Mirroring Partner - Displays the server name of the mirroring partner.
Mirroring Partner Connection - Displays the connection string of the mirroring partner
server.
Witness Status - Displays the status of witness connection. The possible values are
Connected, Unknown, Disconnected.
Witness Connection - Displays the connection string of the witness server.
Witness Address - Displays the name of the witness server
Unsent Log (in KB) - Displays the unsent logs that are in the Send Queue.
Oldest Unsent Transaction (DD:HH:mm:ss) - Displays the estimated time of transaction
pending in the Send Queue.
Time to send log (DD:HH:mm:ss) - Displays the estimated time that takes to send the log to
Principal Log
the mirror server.
Current Send Rate - Displays the current send rate in KB/Sec.
Current Rate of new transactions - Displays the rate of new transactions entered in the
principal server in KB/Sec.Parameters Description
Unrestored log - Displays the amount of log waiting in the redo queue in KB/Sec.
Time to restore log (DD:HH:mm:ss) - Displays the estimated amount of time that takes to
Mirror Log
restore the log to the mirroring database.
Current restore rate - Displays the current restore rate in KB/Sec
Mirror Commit Overhead - Displays the amount of overhead incurred in milliseconds while
the principal server instance waits for the mirror server instance to write the transaction''s
Mirroring
log record into the redo queue.
session
Time to send and restore log (DD:HH:mm:ss) - Displays the time needed to send and
restore the transactions committed in the principal database.
For Principal database :
Logs Sent KB/Min - The number of logs sent per minute.
Log Send Queue KB - Total kilobytes of log that have not yet been sent to the mirror server.
Average Delay/Transaction (ms) - The delay (in milliseconds) in waiting for commit
acknowledgement from the mirror. This reports the approximate delay for a single
Mirroring transaction in process at that time.
Performance
Counters For Mirror database :
Logs Redo KB/Min - The amount of transaction log applied on the mirror database per
minute.
Redo Queue KB - Total kilobytes of hardened log that remain to be applied to the mirror
database to roll it forward.
Sessions
Parameters Description
Connection Statistics
The time taken to connect to the Microsoft SQL database server from Applications
Connection Time
Manager server.
Active Connections Number of users connected to the system.
Logins/Min Total number of logins started per minute.
Logouts/Min Total number of logouts started per minute.
Blocked Sessions Number of sessions that are blocked.
SQL Statistics
Batch Requests/Min Number of SQL batch requests received by server.
SQL Compilations/Min Number of SQL compilations.
SQL
Number of SQL re-compiles.
Recompilations/Min
AutoParams/Min Number of auto-parameterization attempts.
Failed AutoParams/Min Number of failed auto-parameterizations.
Host Details
Host Connected to the
Displays the hosts name connected to the SQL server.
SQL
No. of Connections Displays the number of connections each host has to the SQL server.
Memory Usage Displays the total memory usage by each host connected to the SQL server.
CPU Time (ms) Displays the total CPU time (in milliseconds) of each host connected to the SQL server.
I/O The cumulative Disk reads and writes for the process running in the SQL Server.
Database Connection Detail
Database Name Displays the name of the database.
Login Name Displays the SQL user name connected to the database.Parameters Description
No. of Connections Displays the number of connections currently open in the database.
You can find the list of sessions, lock and block running for the selected database.
Parameters Description
Database Name The name of the database.
Agent Type The type of agent - Backup, Copy or Restore.
Status The status of the database log shipping - Starting, Running, Success, Error, Warning.
Time Elapsed (in min) The total time taken to run the log shipping operation.
Log Time The time and date last log shipping operation.
Error Log Time The time of the last error log shipping operation ran.
Error Message The error messages received while running the log shipping operation if any.
Session Details
Parameters Description
PID Displays the SQL server session ID running in SQL Server.
Displays the status of the process in SQL Server. The possible values are:
Dormant : SQL Server session that hasn''t done any work in more than an hour.
Running : SQL Server session running one or more batches. A session can run multiple
batches when Multiple Active Result Sets (MARS) is enabled.
Background : SQL Server session running a background task, such as deadlock detection.
Rollback : SQL Server session which has a transaction rollback in process.
Status
Pending : SQL Server session waiting for a worker thread to become available.
Runnable : The task in SQL Server session which is in the runnable queue of a scheduler while
waiting to get a time quantum.
Spinloop : The task in SQL Server session waiting for a spinlock (Spinlock is a lock where the
thread waits in a loop, repeatedly checking until the lock becomes available) to become free.
Suspended : SQL Server session is waiting for an event, such as I/O, to complete.
User Name The login name used for executing the process.
Host The host machine name from where the session has been established from.
DB Name Displays the name of the database currently being used by the process.
Program The application in SQL Server which has established the session.
Memory
The number of pages in the procedure cache that are currently allocated to this process (in KB).
Usage
CPU Time The cumulative CPU time for the process running in the SQL Server (in ms).
I/O The cumulative Disk reads and writes for the process running in the SQL Server.
Session
Blocked Amount of time elapsed after the session was blocked (in seconds).
Time
Displays the ID of the session that is blocking the request.
If this column is 0, then the request is not blocked, or the session information of the blocking
session is not available (or cannot be identified).
Blocking
If value is -2, then the blocking resource is owned by an orphaned distributed transaction.
Session
If value is-3, then the blocking resource is owned by a deferred recovery transaction.
If value is -4, then the Session ID of the blocking latch owner could not be determined due to
internal latch state transitions.
Kill Allows you to kill the session of the selected database.
SQL Session Blocked Lock Details
On clicking ''View More'', following details will be displayed:
Parameters DescriptionParameters Description
Holding ID The Blocked sessions ID.
The status of the process in SQL Server. The possible values are:
Dormant : SQL Server session that hasn''t done any work in more than an hour.
Running : SQL Server session running one or more batches. A session can run multiple
batches when Multiple Active Result Sets (MARS) is enabled.
Background : SQL Server session running a background task, such as deadlock detection.
Rollback : SQL Server session which has a transaction rollback in process.
Status
Pending : SQL Server session waiting for a worker thread to become available.
Runnable : The task in SQL Server session which is in the runnable queue of a scheduler while
waiting to get a time quantum.
Spinloop : The task in SQL Server session waiting for a spinlock (Spinlock is a lock where the
thread waits in a loop, repeatedly checking until the lock becomes available) to become free.
Suspended : SQL Server session is waiting for an event, such as I/O, to complete.
Lock Type The type of Lock.
Command
Displays the command that is being currently executed.
Name
Query Displays the query for the selected database session.
Hold User The user the Lock.
Wait User The blocked user waiting for the Lock.
DB Name The Name of the database being used by the process.
Object ID The Object ID associated with the resource.
Hold Host The host machine holding the Lock.
Wait Host The Blocked Host waiting the Lock.
Host
The Command being executed by the process holding the Lock.
Command
Wait
The Command to be executed by the process waiting for the Lock.
Command
Memory
The number of pages in the procedure cache that are currently allocated to this process.
Usage
Wait Time The time, in milliseconds, in which this task is waiting for a resource. When the task is not waiting,
(ms) the wait time is 0.
Last Wait
The name of the last wait type.
Type
Wait
The name of the resource that is needed.
Resource
Jobs
Applications Manager also allows you to easily manage these Jobs and Backup processes in bulk. Just select the
Job(s) you wish to manage and then select any one of the option ( ''Start Job, Stop Job, Delete Job, Enable Job,
Disable Job, Manage, Unmanage, Unmanage and Reset'') from the pull-down menu.
Create a new Job
You can also create a job right from Applications Manager console. To do so, follow the steps given below:
Click on ''Create job'' link.
Provide Job Name, select the Owner from the pull-down menu, select the Category and the Description.
You can also set the status as either ''Enable'' or ''Disable'' if you choose to run the Job later.
Provide the Step Name, Type, Run As, Database on which it should run, enter the SQL Command you wish to
execute. You can repeat this process to add ''n'' number of steps. You can also edit them at a later stage or even
delete a step if found not required.
Set the action On Success Action either as ''Go to the next step'' or ''Quit the job reporting success'' or ''Quit the
job reporting failure''.
Set the Retry attempts and Retry interval (minutes).
Set the action On Failure Action either as ''Quit the job reporting failure'' or ''Go to the next step'' or ''Quit the
job reporting success''.If you like to schedule the job, click on Schedule and provide the following information.
Provide a Name for the schedule job.
Select the Frequency at which you want the job to be executed : Daily / Weekly / Monthly.
If its Daily, then choose the occurrence at which you want this job to run daily: Occurs once / Multiple
Times. If it Occurs once, provide the time (hh:mm). Also select the date from which the job needs to run.
If the frequency is Weekly, choose the days on which you want this job to run and provide whether it
recurring every ''nth'' weeks.
If the frequency is Monthly, choose the nth day of every nth month or select whether it should run on ''nth''
day of every ''nth'' week of every nth month.
If you like to receive/send notifications of these jobs, click on Notifications, and select Email notification
when the job either succeeds, fails or finishes to the appropriate operator. If the operator name is not
specified, then select ''New Operator'' and provide the Name and Email ID of the same.
You can also set notification and allow jobs to be written into Windows Event Log files when it succeeds, fails
or finishes.
The Jobs tab displays the performance metrics of various Jobs history running in SQL Server. You will be able to
view SQL Job''s history when you click on the corresponding SQL Job from Job History table. This will show the step
by step job execution history for that corresponding job in a pop-up window.
Note: Applications Manager allows you to enable/disable data collection of the SQL Server Performance several
metrics like Jobs, Backup and Replications . Once enabled, you can also customize the polling interval of these
metrics.
Parameters Description
Job Name Name of the SQL Job
Current Execution Status The status of the job execution in each step.
Last Run Status Gives the last run status of the job
Run Date & Time Gives the date & time for which the jobs are scheduled to run.
Job Time (in seconds) Elapsed time in seconds for the execution of the job or step.
Retries Attempted Gives the number of times the scheduled jobs attempted to run.
Backup/Restore Details
Backup Details
Parameters Description
DB Name Displays the name of the database involved in the backup operation.
Start Displays the date and time of the back up operation started.
End Displays the date and time of the back up operation ended.
Expiration Displays the date and time the back up operation is supposed to expire.
If the value is 1, then it means that the damage to database was detected while this back up was
Damaged
being created. However the back up operation continued despite the errors.
Size Displays the size of the back up set (in bytes).
Physical
Displays the physical name of the back up device.
Name
Backup Age
Displays the number of hours passed since the back up operation was completed.
(Hours)
Note: Applications Manager allows you to enable/disable data collection of the SQL Server Performance several
metrics like Jobs, Backup and Replications . Once enabled, you can also customize the polling interval of these
metrics.
Restore Details
Parameters Description
DB Name Displays the name of the destination database for which the restore operation operate upon.
Restore by Displays the name of the user who performed the restore operation on the database.Parameters Description
Restore Displays the type of restore operation performed which could be either Database / File / Filegroup
Type / Log / Verifyonly / Differential / Revert.
Started Displays the date and time of the restore operation.
Restore
Displays the physical name of the backup file created.
From
Restore To Displays the name of the file where the backup was restored to.
Replication
Log Shipping Status
Parameters Description
Database
Primary Name of the primary database.
Secondary Name of the secondary database.
Status
Backup Status of the backup session. (Starting, Running, Success, Error, or Warning)
Copy Status of the copy session. (Starting, Running, Success, Error, or Warning)
Restore Status of the restore session. (Starting, Running, Success, Error, or Warning)
Time since
Amount of time elapsed since the last log backup (in minutes).
Backup
Time since
Amount of time elapsed since the last log backup was copied (in minutes).
Copy
Time since
Amount of time elapsed since the last log backup was restored (in minutes).
Restore
Restore Amount of time that elapsed between when the log backup was created on the primary database
Latency and when it was restored on the secondary databases (in minutes).
Log Shipping Role
Parameters Description
Primary Server
Agent Type Type of the log shipping job. (Backup)
Secondary Server(s) Name of the secondary instance(s) of MS SQL in the log shipping configuration.
Backup File The filename of the last backup file.
Backup Time The time and date of the last backup operation ran.
Backup Error Log Time Date and time at which the error occurred during backup operation.
Backup Error Message Displays the error messages received while running the backup operation if any.
Secondary Server
Agent Type Type of the log shipping job. (Copy or Restore)
Copied File The filename of the last backup file that was copied to the secondary server.
Copied Time The time and date of the last copy operation to the secondary server.
Copy Error Log Time Date and time at which the error occurred during copy operation.
Copy Error Message Displays the error messages received while running the copy operation if any.
Restored File The filename of the last backup file that was restored to the secondary server.
Restored Time The time and date of the last restore operation on the secondary database.
Restore Error Log Time Date and time at which the error occurred during restore operation.
Restore Error Message Displays the error messages received while running the restore operation if any.
Replication Status
Note:The Distributor is the same SQL Server as the Publisher, or can be a separate SQL Server from the
Publisher.
As Applications Manager monitors publication and subscription metrics from the distributor server, add
the distributor SQL server as a monitor.
The SQL user used for monitoring must be given read access to the distribution database present in the
distributor.
Publications
This table displays status information for all publications available in the corresponding SQL monitor.
Parameters Description
Status The status of each publication.
Publication Name of the publication
Type Type of the publication
No. of Subscriptions Number of subscriptions associated with the corresponding publication.
Synchronizing The number of distribution agents running for the publication.
Current Average Performance Current average performance of the replication based on the latency.
Current Worst Performance Current worst performance of the replication based on the latency.
Subscriptions
Applications Manager provides information about subscriptions available in the corresponding monitor.
Parameters Description
Running status Status of each subscription.
Subscription Name of the subscription
Publication Name of the publication running the corresponding subscription.
Performance Performance of the subscription.
Latency Latency value
Shows expiring status of the subscription which can be one of the following
Expired
Expiration Status
Expiring soon
Critical
Replication Agents
Replication Agents tab displays information about each replication agent running in the corresponding monitor.
Parameters Description
Agent Name Name of the agent involved in the replication
Agent Type Type of the agent
Current Status Current status of the agent
[Database].
Name of the publisher
[Publication]
Last Start Time Last start time of the agent
Duration
Duration of the agent session.
(HH:mm:ss)
Delivary Rate
Ratio of delivered commands to the duration of the agent.
(cmds/sec)
The current amount of time, in milliseconds, elapsed from when transactions are applied at the
Latency
Publisher to when they are delivered to the distributor.
#Trans The number of transactions delivered to the distributor.
#Cmds The number of commands delivered to the distributor.
Avg #Cmds The average number of commands per transaction delivered to the distributor for the session.
Replication Agent History TableDisplays the performance metrics of various agents history running in SQL server. You will be able to view
replication agent''s history when you click on the corresponding agent from Agent Details table. This will show the
step by step agent execution history for that corresponding agent in a pop-up window.
Parameters Description
Current status Current status of the agent
Last start time Last start time of the agent
Duration (HH:mm:ss) Duration of the agent session.
Last Action Displays the last action message of the agent.
Users
ManageEngine Applications Manager User Details section displays the entire list of active users of SQL servers. It
displays the Username, Status, Login Type, Default DB and Creation Date. The DBA can also, quite easily, perform
actions to the selected list of users such as Enable User, Disable User and Delete User.
Parameters Description
User Details
User Name Name of the user.
Status Status of the user.
Login Type Type of login made by the user.
Default DB Default database name accessed by the user.
Creation Date Timestamp at which the user was created.
Configuration
You can manage and optimize SQL Server resources using configuration options in Applications Manager.
Optimizing these resources can have a significant effect on SQL Server''s behavior and performance.
Applications Manager lists all available configuration options, the range (minimum and maximum value) of
possible settings, and configuration values.
Parameters Description
Configuration Details
Name Name of the configuration option
Minimum Minimum range of configuration value
Maximum Maximum range of configuration value
Configured The value currently configured to the server. For few options, this value takes effect for use only
value after restarting the SQL instance
Value in use The value currently in use for the server
Advanced options will be available or changed only when the ''show advanced option'' is set to 1. You can enable
these options in the following two ways:
Click on the link ''Enable Advanced options'' (or)
Change the value of show advanced options to 1.
For some of the configuration options, the changes take effect only after restarting the SQL instance.The values
used for the parameters Configured value and Value in use columns should match for a dynamically updated
option. Options that require SQL Server to restart will initially show the changed value only in the Configured
value column. After restart, the new value will appear in both the Configured value column and the Value in use
column.
For example, the minimum and maximum server memory options are updated dynamically in the Database
Engine; therefore, you can change them without restarting the server.
Note: Only users with Administrator / Operator with permission can edit the SQL Server Configuration Settings.
Parameters DescriptionParameters Description
access check The Access check cache bucket count option controls the number of hash buckets used for
cache bucket access check result cache. The default value - 0 indicates that SQL Server is managing these
count* options.
access check The access check cache quota option controls the number of entries used for access check
cache quota* result cache. The default value - 0 indicates that SQL Server is managing these options.
Ad Hoc By default, SQL Server does not allow ad hoc distributed queries. When this option is set to 1, SQL
Distributed Server allows ad hoc access. When this option is not set or is set to 0, SQL Server does not allow
Queries* ad hoc access.
The value for affinity I/O mask specifies which CPUs in a computer are eligible to process SQL
Server disk I/O operations. The values for affinity I/O mask are as follows:
A 1-byte affinity I/O mask covers up to 8 CPUs in a multiprocessor computer.
affinity I/O A 2-byte affinity I/O mask covers up to 16 CPUs in a multiprocessor computer.
mask* A 3-byte affinity I/O mask covers up to 24 CPUs in a multiprocessor computer.
A 4-byte affinity I/O mask covers up to 32 CPUs in a multiprocessor computer.
To cover more than 32 CPUs, configure a four-byte affinity I/O mask for the first 32 CPUs and
up to a four-byte affinity64 I/O mask for the remaining CPUs.
The affinity mask option dynamically controls CPU affinity. The values for affinity mask are as
follows:
A one-byte affinity mask covers up to 8 CPUs in a multiprocessor computer.
affinity A two-byte affinity mask covers up to 16 CPUs in a multiprocessor computer.
mask* A three-byte affinity mask covers up to 24 CPUs in a multiprocessor computer.
A four-byte affinity mask covers up to 32 CPUs in a multiprocessor computer.
To cover more than 32 CPUs, configure a four-byte affinity mask for the first 32 CPUs and up
to a four-byte affinity64 mask for the remaining CPUs.
affinity64 I/O The affinity64 I/O mask binds SQL Server disk I/O to a specified subset of CPUs. This option is
mask* only visible on the 64-bit version of SQL Server.
affinity64 The affinity64 mask binds processors to specific threads. This option is only visible on the 64-bit
mask* version of SQL Server.
Use the Agent XPs option to enable the SQL Server Agent extended stored procedures on this
server. The possible values are:
0 - indicating that SQL Server Agent extended stored procedures are not available (the
Agent XPs*
default).
1 - indicating that SQL Server Agent extended stored procedures are available.
The setting takes effect immediately without a server stop and restart.
allow This option is still present in the sp_configure stored procedure, although its functionality is
updates unavailable in SQL Server.
awe You can use the Address Windowing Extensions (AWE) API to provide access to physical
enabled* memory in excess of the limits set on configured virtual memory.
backup Used by the BACKUP Transact-SQL statement to select the backup compression setting if a user
compression does not specify WITH COMPRESSION or WITH NO_COMPRESSION. Used in SQL Server 2008
default Enterprise and later only. Default backup compression is set to 0
blocked
Use the blocked process threshold option to specify the threshold, in seconds, at which blocked
process
process reports are generated. The threshold can be set from values 0 to 86,400.
threshold (s)*
c2 audit This option will configure the server to record both failed and successful attempts to access
mode* statements and objects.
Use the clr enabled option to specify whether user assemblies can be run by SQL Server. Possible
values are as follows:
clr enabled
0 - Assembly execution not allowed on SQL Server
1 - Assembly execution allowed on SQL ServerParameters Description
cost The cost threshold for parallelism option specifies the threshold at which Microsoft SQL Server
threshold for creates and runs parallel plans for queries. The cost threshold for parallelism option can be set to
parallelism* any value from 0 through 32767.
Use the cross db ownership chainingoption to configure cross-database ownership chaining for
an instance of Microsoft SQL Server. Possible Values are :
cross db
0 - cross db ownership chaining is off for the instance, cross-database ownership chaining is
ownership
disabled for all databases.
chaining
1 - cross db ownership chaining is on for the instance, cross-database ownership chaining is
on for all databases.
The cursor threshold optionspecifies the number of rows in the cursor set at which cursor
keysets are generated asynchronously. Possible Values are:
cursor
threshold* 1 - all keysets are generated synchronously.
0 - all cursor keysets are generated asynchronously.
The Database Mail XPs option enables Database Mail on this server. Possible values are:
Database
0 - Database Mail is not available (default).
Mail XPs*
1 - Database Mail is available.
default full-
The default full-text language option specifies a default language value for full-text indexed
text
columns. The default value of this option is the language of the server and requires an LCID value.
language*
default
The default language option to specify the default language for all newly created logins.
language
default trace
The default trace enabled option enables or disables the default trace log files.
enabled*
This option controls whether triggers return result sets.
disallow
When set to 1 (ON) any attempt by a trigger to return a result set fails, and the user receives
results from
an error message
triggers*
The default setting for this option is 0 (OFF).
Use the filestream access leveloption to change the FILESTREAM access level for this instance of
SQL Server. Possible values are:
filestream 0 - Disables FILESTREAM support for this instance.
access level
1 - Enables FILESTREAM for Transact-SQL access.
2 - Enables FILESTREAM for Transact-SQL and Win32 streaming access.
The fill factor option specifies how full Microsoft SQL Server should make each page when it
fill factor (%)*
creates a new index using existing data.
The ft crawl bandwidth option specifies the size to which the pool of large memory buffers can
ft crawl
grow. The max parameter value specifies the maximum number of buffers that the full-text
bandwidth
memory manager should maintain in a large buffer pool. If the max value is zero, then there is no
(max)*
upper limit to the number of buffers that can be in a large buffer pool.
The ft crawl bandwidth option specifies the size to which the pool of large memory buffers can
ft crawl grow. The min parameter specifies the minimum number of memory buffers that must be
bandwidth maintained in the pool of large memory buffers. Upon request from the Microsoft SQL Server
(min)* memory manager, all extra buffer pools will be released but this minimum number of buffers will
be maintained. If, however, the min value specified is zero, then all memory buffers are released.
The ft notify bandwidth option specifies the size to which the pool of small memory buffers can
ft notify
grow. The max parameter value specifies the maximum number of buffers that the full-text
bandwidth
memory manager should maintain in a small buffer pool. If the max value is zero, then there is no
(max)*
upper limit to the number of buffers that can be in a small buffer pool.Parameters Description
The in-doubt xact resolutionoption controls the default outcome of transactions that the
Microsoft Distributed Transaction Coordinator (MS DTC) is unable to resolve. Inability to resolve
transactions may be related to the MS DTC down time or an unknown transaction outcome at the
time of recovery. Possible Values are :
in-doubt xact
resolution* 0 - No presumption. Recovery fails if MS DTC cannot resolve any in-doubt transactions.
1 - Presume commit. Any MS DTC in-doubt transactions are presumed to have committed.
2 - Presume abort. Any MS DTC in-doubt transactions are presumed to have aborted.
The index create memory option controls the maximum amount of memory initially allocated for
index create creating indexes. If more memory is later needed for index creation, and the memory is available,
memory the server will use it, thus exceeding the setting of this option. If additional memory is not
(KB)* available, the index creation will continue using the memory already allocated. The default value
for this option is 0 (self-configuring).
The lightweight pooling option provides a means of reducing the system overhead associated
lightweight with the excessive context switching seen in symmetric multiprocessing (SMP) environments.
pooling* Possible Values:1 - causes SQL Server to switch to fiber mode scheduling. The default value for
this option is 0.
The locks option to set the maximum number of available locks, thereby limiting the amount of
memory used. Possible Values: 0 (Default) - allows the Database Engine to allocate and
locks* deallocate lock structures dynamically, based on changing system requirements. When locks is
not set to 0, lock escalation occurs when the number of locks reaches 40 percent of the value
specified for locks.
You can use the max degree of parallelism option to limit the number of processors to use in
parallel plan execution. Possible Values:
max degree 0 default value - allows SQL Server to use all the available processors up to 64 processors.
of
1 - To suppress parallel plan generation
parallelism*
greater than 1 - to restrict the maximum number of processors used by a single query
execution.
The max full-text crawl range option optimizes CPU utilization; you can specify the number of
max full-text
partitions that Microsoft SQL Server should use during a full index crawl. The default value of this
crawl range*
option is 4; the minimum value is 1, and the maximum value is 256.
max server Use the max server memory option to reconfigure the amount of memory (in megabytes) that is
memory managed by the SQL Server Memory Manager for a SQL Server process used by an instance of
(MB)* SQL Server.
The max text repl size option to specify the maximum size (in bytes) of text, ntext, varchar(max),
max text repl nvarchar(max), varbinary(max), xml, and image data that can be added to a replicated column or
size (B) captured column in a single INSERT, UPDATE, WRITETEXT, or UPDATETEXT statement. The default
is 65536. A value of -1 indicates no limit, other than the limit imposed by the data type.
The max worker threads option is used to configure the number of worker threads available to
max worker
Microsoft SQL Server processes. 0(default value)- allows SQL Server to automatically configure
threads*
the number of worker threads at startup. This setting is best for most systems.
The media retention option provides a system-wide default for the length of time to retain each
media
backup set. This option helps protect backups from being overwritten until the specified number
retention*
of days has elapsed. The default is 0 days.
min memory
The min memory per query option specifies the minimum amount of memory (in kilobytes) that
per query
will be allocated for the execution of a query.
(KB)*
min server The min server memory option is used to reconfigure the amount of memory (in megabytes) that
memory is managed by the SQL Server Memory Manager for a SQL Server process used by an instance of
(MB)* SQL Server. The default setting for min server memory is 0.
Use the nested triggersoption to control whether a trigger can cascade (perform an action that
initiates another trigger that initiates another trigger, and so on). Possible values:
nested
triggers 0 - triggers cannot cascade.
1 - triggers can cascade to as many as 32 levels.
network The network packet size option to set the packet size (in bytes) used across the entire network. If
packet size an application sends and receives small amounts of information, the packet size can be set to 512
(B)* bytes, which is sufficient for data transfers.Parameters Description
Use the Ole Automation Procedures option to specify whether OLE Automation objects can be
Ole instantiated within Transact-SQL batches. Possible Values:
Automation
0 - OLE Automation Procedures are disabled. Default for new instances of SQL Server.
Procedures*
1 - OLE Automation Procedures are enabled.
This option is still present in sp_configure, although its functionality has been disabled in
open Microsoft SQL Server. (The setting has no effect.) In SQL Server, the number of open database
objects* objects is managed dynamically and is limited only by the available memory. The open objects
option available in sp_configure for backward compatibility with existing scripts.
The optimize for ad hoc workloads option is used to improve the efficiency of the plan cache for
optimize for
workloads that contain many single use ad hoc batches. When this option is set to 1, the Database
ad hoc
Engine stores a small compiled plan stub in the plan cache when a batch is compiled for the first
workloads*
time, instead of the full compiled plan.
The PH timeout option to specify the time, in seconds, that the full-text protocol handler should
PH timeout
wait to connect to a database before timing out. The default value is 60 seconds. Increase the ph
(s)*
timeout value when connection attempts are timing out due to temporary network issues.
The precompute rank server-level advanced option to improve the performance of
FREETEXTTABLE queries that specify the top_n_by_rank parameter. When the option is set to 1,
precompute FREETEXTTABLE queries specified with top_n_by_rank use precomputed rank data stored in the
rank* full-text catalogs. When you use precomputed rank data, the result set that is returned by
top_n_by_rank may not contain the same results as those that are returned when the precompute
rank option is set to 0.
Use the priority boostoption to specify whether Microsoft SQL Server should run at a higher
Microsoft Windows 2000 or Windows 2003 scheduling priority than other processes on the same
computer. Possible Values:
priority
boost* 1 - SQL Server runs at a priority base of 13 in the Windows 2000 or Windows Server 2003
scheduler.
0 (default) - A priority base of 7.
Use the query governor cost limit option to specify an upper limit on the time period in which a
query
query can run. If you specify a nonzero, nonnegative value, the query governor disallows execution
governor
of any query that has an estimated cost exceeding that value. Specifying 0 (the default) for this
cost limit*
option turns off the query governor, and all queries are allowed to run without any time limitation.
The query wait option specifies the time in seconds (from 0 through 2147483647) that a query
query wait
waits for resources before timing out. If the default value of -1 is used, or if –1 is specified, then
(s)*
the time-out is calculated as 25 times of the estimated query cost.
Use the recovery interval option to set the maximum number of minutes per database that
recovery
Microsoft® SQL Server™ needs to recover databases. Keep recovery interval set at 0 (self-
interval
configuring) unless you notice that checkpoints are impairing performance because they are
(min)*
occurring too frequently. If this is the case, try increasing the value in small increments.
Use the remote accessoption to control the execution of stored procedures from local or remote
servers on which instances of Microsoft SQL Server are running. Possible Values:
remote 0 - to prevent local stored procedures from being run from a remote server or remote stored
access procedures from being run on the local server.
1 (default) - to grant permission to run local stored procedures from remote servers or remote
stored procedures from the local server
SQL Server provides a dedicated administrator connection (DAC). The DAC lets an administrator
access a running server to execute diagnostic functions or Transact-SQL statements, or to
remote troubleshoot problems on the server, even when the server is locked or running in an abnormal
admin state and not responding to a SQL Server Database Engine connection. Possible Values:
connections
0 - Indicates only local connections are allowed by using the DAC.
1 - Indicates remote connections are allowed by using the DAC.
Use the remote login timeout option to specify the number of seconds to wait before returning
remote login
from a failed attempt to log in to a remote server. The default setting for remote login timeout is
timeout (s)
20 seconds. A value of 0 allows for an infinite wait.
remote proc The remote proc trans option protects the actions of a server-to-server procedure through a
trans Microsoft® Distributed Transaction Coordinator (MS DTC) transaction.Parameters Description
Use the remote query timeout option to specify how long (in seconds) a remote operation can
remote query
take before Microsoft SQL Server times out. The default value is 600, which allows a 10-minute
timeout (s)
wait.
Replication
This option is for internal use only.
XPs*
The scan for startup procsoption to scan for automatic execution of stored procedures at
scan for Microsoft SQL Server startup time. Possible Values:
startup
1 - SQL Server scans for and runs all stored procedures defined on the server.
procs*
0 (default value) - do not scan
The server trigger recursionoption specifies whether to allow server-level triggers to fire
recursively. Possible values:
server trigger
recursion 1 (ON) - server-level triggers will be allowed to fire recursively.
0 (OFF)- server-level triggers cannot be fired recursively.
The set working set size option to reserve physical memory space for SQL Server that is equal to
set working
the server memory setting. Before setting set working set size to 1, set both min server memory
set size*
and max server memory to the same value, the amount of memory you want SQL Server to use.
show The show advanced options option to display the sp_configure system stored procedure
advanced advanced options. When you set show advanced options to 1, you can list the advanced options
options by using sp_configure. The default is 0.
Use the SMO and DMO XPs option to enable SQL Server Management Object (SMO) extended
stored procedures on this server. Possible Values are:
SMO and
DMO XPs* 0 - SMO XPs are not available.
1 - SMO XPs are available. This is the default.
Use the SQL Mail XPs option to enable SQL Mail on this server. The possible values are:
SQL Mail
0 indicating SQL Mail is not available (default)
XPs*
1 indicating SQL Mail is available
Use the transform noise wordsserver configuration option to suppress an error message if noise
words/stopwords, cause a Boolean operation on a full-text query to return zero rows. Possible
Values:
transform
noise words* 0-Noise words (or stopwords) are not transformed.
1-Noise words (or stopwords) are transformed. They are ignored, and the rest of the query is
evaluated
two digit The two digit year cutoff option to specify an integer from 1753 to 9999 that represents the
year cutoff* cutoff year for interpreting two-digit years as four-digit years.
user The user connections option specifies the maximum number of simultaneous user connections
connections* allowed.
The User Instance Timeout option that you can access through sp_configure is not supported in
user instance
Microsoft SQL Server 2008. This option works only with SQL Server 2008 Express (SQL Server
timeout*
Express).
user The user instance enabled option that you can access through sp_configure is not supported in
instances Microsoft SQL Server 2008. This option works only with SQL Server 2008 Express (SQL Server
enabled Express).Parameters Description
The user options option specifies global defaults for all users. The user optionsoption allows you
to change the default values of the SET options (if the server''s default settings are not
appropriate). Possible Values:
1- DISABLE_DEF_CNST_CHK - Controls interim or deferred constraint checking.
2- IMPLICIT_TRANSACTIONS - For dblib network library connections, controls whether a
transaction is started implicitly when a statement is executed. The IMPLICIT_TRANSACTIONS
setting has no effect on ODBC or OLEDB connections.
4 - CURSOR_CLOSE_ON_COMMIT - Controls behavior of cursors after a commit operation has
been performed.
8 - ANSI_WARNINGS - Controls truncation and NULL in aggregate warnings.
16 - ANSI_PADDING - Controls padding of fixed-length variables.
32 - ANSI_NULLS - Controls NULL handling when using equality operators.
64 - ARITHABORT - Terminates a query when an overflow or divide-by-zero error occurs
during query execution.
128 - ARITHIGNORE - Returns NULL when an overflow or divide-by-zero error occurs during a
user options
query.
256 - QUOTED_IDENTIFIER - Differentiates between single and double quotation marks when
evaluating an expression.
512 - NOCOUNT - Turns off the message returned at the end of each statement that states
how many rows were affected.
1024 - ANSI_NULL_DFLT_ON - Alters the session''s behavior to use ANSI compatibility for
nullability. New columns defined without explicit nullability are defined to allow nulls.
2048- ANSI_NULL_DFLT_OFF - Alters the session''s behavior not to use ANSI compatibility for
nullability. New columns defined without explicit nullability do not allow nulls.
4096 - CONCAT_NULL_YIELDS_NULL- Returns NULL when concatenating a NULL value with a
string.
8192- NUMERIC_ROUNDABORT- Generates an error when a loss of precision occurs in an
expression.
16384 - XACT_ABORT - Rolls back a transaction if a Transact-SQL statement raises a run-time
error.
The xp_cmdshell option is a server configuration option that enables system administrators to
xp_cmdshell* control whether the xp_cmdshell extended stored procedure can be executed on a system. By
default, the xp_cmdshell option is disabled on new installations and can be enabled.
AlwaysOn Availability Groups
Applications Manager lets you monitor the status of your SQL Server AlwaysOn resources by displaying all the
Availability Groups running in your SQL server. Click on the links below to view all the required details listed under
the following tables:
Availability Groups
Availability Replicas
Availability Databases
Availability Groups
Parameters Description
Name The name of an availability group for which the connected server instance hosts a replica.
Primary Replica Name of the server instance that is hosting the primary replica of the availability group.
Availability Replicas
On clicking the required availability group, you can view detailed information on various replicas available under
that group.
Parameters Description
Replica The name of the server instance that hosts the availability replica.Parameters Description
Indicates the current role of the availability replica. Possible values are Primary, Secondary and
Role
Resolving.
Availability Indicates the replica property that you set separately for each availability replica. Possible
Mode values are Synchronous and Asynchronous.
Displays the failover mode for which the replica is configured. Possible failover mode values
Failover Mode
are Automatic and Manual.
Synchronization Indicates the synchronization health of the replica. Possible values are Healthy, Partially
Health Healthy and Not Healthy.
Indicates whether a secondary replica is currently connected to the primary replica. If the
Connection
replica is primary, It indicates whether it connected with all the secondary replicas. Possible
Status
values are either Connected or Disconnected.
Indicates the current operational state of the secondary replica. Possible values are: Pending
State
failover, Pending, Online, Offline, Failed, Failed, No Quorum and Not Local.
Bytes Received
Rate at which data is received from the Primary Replica by the Secondary Replica (in MB/Sec).
from Primary *
Bytes Sent to
Rate at which data is sent to the Primary Replica by the Secondary Replica (in MB/Sec).
Primary *
* - Obtained after clicking over the required replica under Replica Stats.
Availability Databases
On clicking the required replica, you can view detailed information of various databases available under that
replica.
Primary Databases:
Database Status Information:
Parameters Description
Synchronization Indicates the Synchronization health of the database. Possible values are Healthy, Partially
Health Healthy and Not Healthy.
Indicates whether the availability database is currently synchronized with other replicas.
Synchronization
Possible values are Not Synchronizing, Synchronizing, Synchronized, Reverting and
State
Initializing.
Failover Indicates which availability database can be failed over with or without potential data loss.
Readiness Possible values are either Data Loss or No Data Loss.
Indicates whether the state at which the availability database is currently in. Possible values
State
are either Suspended or Resumed.
Performance Statistics:
Parameters Description
Redone Bytes The rate at which log records are redone on the primary database (in MB/Sec).
Log Bytes
The rate at which log records are received by the primary database (in MB/Sec).
Received
Amount of data written from the log cache to the physical transaction log file on the disk (in
Log Flushed
MB).
Secondary Databases:
Database Status Information:
Parameters Description
Synchronization Indicates the Synchronization health of the database. Possible values are Not Healthy, Partially
Health Healthy and Healthy.
Indicates whether the availability database is currently synchronized with other replicas.
Synchronization
Possible values are Not Synchronizing, Synchronizing, Synchronized, Reverting and
State
Initializing.
Failover Indicates which availability database can be failed over with or without potential data loss.
Readiness Possible values are either Data Loss or No Data Loss.Parameters Description
Indicates whether the state at which the availability database is currently in. Possible values
State
are either Suspended or Resumed.
Transaction Details:
Parameters Description
Log Send Indicates the amount of log records in the log files of the primary database that have not been sent
Queue to the secondary replica (in MB).
Redo Indicates the amount of log records in the log files of the secondary database that have not yet
Queue been redone (in MB).
Log Indicates the amount of data written from the log cache to the physical transaction log file on the
Flushed disk (in MB).
Log Send
Indicates the rate at which log records are being sent to the secondary database (in MB/Sec).
Rate
Redo Rate Indicates the rate at which the log records are being redone (in MB/Sec).
Performance Statistics:
Parameters Description
Send Indicates the amount of time taken by the Primary Replica to send all the log records to the
Latency Secondary Replica (in Sec).
Indicates the amount of time taken to redo the catch-up time (in Min). The catch-up time is the time
Redo Lag
taken for the secondary replica to catch up with the primary replica.
Indicates the amount of time delay observed in the last transaction log records between the
Sync Lag primary and the secondary replica (in Min). If the primary replica fails, all the transaction log
records within that time lag will be lost.
Redone Indicates the amount of log records that are redone on the secondary database in the last second
Bytes (in MB/Sec).
Log Bytes Indicates the amount of log records received by the secondary replica for the database in the last
Received second (in MB/Sec).
SQL Server - Cluster Details
Applications Manager lets you monitor the status of your SQL Server Clusters and Cluster resources. Click on the
monitor name to see all the Cluster details listed under the following links:
Cluster Details
Disk Utilization
Storage
Nodes
Networks
Resource Groups
Note: ''Cluster Details'' tab can be viewed only in Windows installations of Applications Manager.
Cluster Details
Parameters Description
Cluster Name/IP Address The name/IP Address of the cluster.
Quorum Owner Node The node in which the sql cluster configuration data is currently accessible.
Quorum Path The path to the quorum files.
The current quorum type. The following are the possible values:
Quorum Type Majority
No Majority
Number of Nodes The total number of nodes in a cluster.
Max Nodes The maximum number of nodes that can participate in a cluster.Parameters Description
Number of Networks The number of networks used by the server cluster for communication.
Resources Online The SQL server cluster resources that are currently online.
Resources Offline The SQL server cluster resources that are currently offline.
Resource Groups Online The SQL server cluster resource groups that are currently online.
Resource Groups Offline The SQL server cluster resource groups that are currently offline.
Disks in Use The number of disks currently in use in the cluster.
Disk Utilization
You can monitor the total Disk Utilization of a Cluster.
Parameters Description
Used Percentage The total percentage of used disk space in a Cluster.
Free Percentage The total percentage of free disk space in a Cluster.
Size The total size of disk memory, in megabytes.
Used The total used space in the disk, in megabytes.
Free The total free space available in the disk, in megabytes.
Storage
Parameters Description
Path The path (including the drive letter if present) of the clustered disk partition.
Volume Label Specifies access to the VolumeLabel property, which is the volume label of the partition.
Size The total size for the partition, in megabytes.
Used The total used space in the partition, in megabytes.
Free The total free space available for the partition, in megabytes.
Used Percentage The percentage of used space in the partition.
Free Percentage The percentage of free space in the partition.
Nodes
Parameters Description
Node Name Specifies the label by which the node is known.
Specifies the current state of a node. Node states can be:
Up - The node is physically plugged in, turned on, booted, and capable of executing programs.
Down - The node is turned off or not operational.
State
Joining - The node is in the process of joining a cluster.
Paused - The node is running but not participating in cluster operations.
Unknown - The operation was not successful.
Networks
Parameters Description
Name Specifies the name of the network.Parameters Description
Provides access to the network''s Role property i.e, the role of the network in the cluster. The
following are the possible values:
0 - None - The network is not used by the cluster.
1 - Cluster - The network is used to carry internal cluster communication.
Role
2 - Client - Not supported - Windows Server 2003: The network is used to connect client
systems to the cluster.
3 - Both - The network is used to connect client systems and to carry internal cluster
communication.
Specifies the current state of the network. The following are the possible values:
-1 - Unknown - The operation was not successful.
0 - Unavailable - All of the network interfaces on the network are unavailable, which means the
nodes that own the network interfaces are down.
State
1 - Down - The network is not operational; none of the nodes on the network can communicate.
2 - Partitioned - The network is operational, but two or more nodes on the network cannot
communicate. Typically a path-specific problem has occurred.
3 - Up - The network is operational; all of the nodes in the cluster can communicate.
Address Specifies the address for the entire network or subnet.
Resource Groups
Parameters Description
Name The name of the Resource group.
Current Node The node in which the sql server is currently running.
Preferred Node The node that is primarily responsible for hosting a cluster resource.
The current state of the resource group. The following are the possible values.
Unknown (-1)
Online (0)
State Offline (1)
Failed (2)
PartialOnline (3)
Pending (4)
IBM DB2 Server Monitoring
Overview
Creating a new IBM DB2 monitor
Monitored Parameters
Overview
IBM DB2 is a family of relational database management system (RDBMS) products from IBM that serve a number of
different operating system platforms. DB2 is designed to store, analyze and retrieve the data efficiently and is
supported across Linux, Unix, and Windows operating systems.
Applications Manager''s DB2 Server Monitoring capability helps database administrators (DBAs) monitor the
availability and performance of production databases.
Creating a new IBM DB2 monitor
Supported Versions: Applications Manager supports monitoring of IBM DB2 Versions 8, 9, 10 and 11.
Prerequisites for monitoring IBM DB2 metrics: Click here
Using the REST API to add a new IBM DB2 monitor: Click hereTo create a IBM DB2 database server monitor, follow the given steps:
Click on New Monitor link.
Select DB2 DB Server.
Enter the IP Address or hostname of the host.
Enter the SubNetMask of the network.
Enter the port number in which DB2 is running.
Choose SSL is enabled option if DB2 server is to be accessed via SSL port.
Provide the user name and password of user who has permission to access the DB2 database. The user name
specified for collecting the data from DB2 Server should have either System Administrator role or the user
should be the DB owner for master database. Else, you can select the required credentials from the Credential
Manager list by enabling the Select from Credential list option.
Specify the Database Name.
Enter the polling interval.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which you want to associate DB2 database server Monitor
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers DB2 database server from the network and starts monitoring them.
Monitored Parameters
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the individual monitors listed to view the following information in the below tabs:
Overview
Performance
Session
Overview
Monitor Information
Parameters Description
Name Specifies the name of IBM DB2 server monitor.
Health Specifies the health (Clear, Warning, Critical) of the IBM DB2 server.
Type Specifies the type you are monitoring.
Version Specifies the version of the database server.
Port Specifies the port number at which the database server is running.
Instance Name The name of the instance in which the database is present
Server Status The current status of the database server itself
Started Time The date and time that the database manager was started using the db2start command.
Host Name Specifies the host at which the database server is running.
Host OS Specifies the OS of the host where the database server is running.
Last Alarm Specifies the last alarm that was generated for the database server.
Last Polled at Specifies the time at which the last poll was performed.
Next Poll at Specifies the time at which the next poll is scheduled.
Availability Shows the current status of the server - available or not available.
Connection Statistics
Parameters Description
Connection Time Time taken to get connected to the IBM DB2 database server
Total The total number of local and remote connections that currently present in the database
Connections manager
Local The number of connections initiated from remote clients to the current instance of theConnections database manager
Remote The number of local applications that are currently connected to the database within the
Connections database manager
Agents Statistics
Parameters Description
The number of agents in the agent pool that are currently active and assigned to an
Active Agents
application
Idle Agents The number of agents in the agent pool that are currently unassigned to any application
Number of
The number of agents registered in the current database manager instance
Agents
The number of agents waiting for a token so they can execute a transaction in the database
Agents Waiting
manager
Database Information
Parameters Description
Database Name The real name of the database for which information is collected
Health Specifies the health (Clear, Warning, Critical) of the database.
Database Alias The alias of the database provided when calling the snapshot function
The full path of the location where the database is stored on the monitored
Database Path
system
Database Status The current status of the database
Connected Time The date and time when the activate database was issued
Deadlock Rate The total number of deadlocks that have occurred in the given polling interval
Percentage of Log Utilization The total amount of active log space used in bytes in the database
Percentage of Sorts
The percentage of sorts that have over flowed
Overflowed
Backup Age Amount of time elapsed since the last backup (in hour(s)).
Transaction Statistics
Parameters Description
Successful The total number of successful SQL statements executed at the database in the given polling
Queries interval
Failed The number of SQL statements that were attempted, but failed at the database in the given polling
Queries interval
Units of This represents the total number of sql commits, internal commits, sql roll backs and internal roll
Work backs done by the database manager in the given polling interval
Cache Performance
Parameters Description
The hit ratio is a percentage indicating how well the package cache is helping to avoid
Package Cache Hit
reloading packages and sections for static SQL from the system catalogs as well as
Ratio
helping to avoid recompiling dynamic SQL statements.
Catalog Cache Hit The hit ratio is a percentage indicating how well the catalog cache is helping to avoid
Ratio actual accesses to the catalog on disk
Buffer Statistics
Parameters Description
Buffer Pool The buffer pool hit ratio indicates the percentage of time that the database manager loaded the
Hit Ratio required page from buffer pool in order to service a page request
Index Page The Index Page hit ratio indicates the percentage of time that the database manager accessed the
Hit Ratio index pages present in the buffer pools.
Data Page The Data Page hit ratio indicates the percentage of time that the database manager accessed the
Hit Ratio data pages present in the buffer pools.Direct The number of read operations that do not use the buffer pool
Reads
Direct
The number of write operations that do not use the buffer pool
Writes
TableSpace Status
Parameters Description
Name Refers to the name of the Table space.
Allocated Bytes calculated from (tablespace_total_pages)*(tablespace_page_size) and converted to MB
Free Bytes calculated from (tablespace_free_pages)*(tablespace_page_size) and converted to MB
% of Free Bytes calculated from (tablespace_free_pages) /(tablespace_total_pages)*100
Performance
Parameters Description
Top 10 Long Running Query
Program
Name of the program/application that was running the query.
Name
User Name Name of the user executing the query.
DB Name The database name under which the query has been running.
Run Time Amount of time for which the query has been running (in seconds).
Activity State The current state of the activity.
The cumulative total amount of CPU time that has been spent in running the query (in
Total CPU
millisecond).
Query The query which consumed the maximum CPU time.
Session
Parameters Description
Top 100 Session Details per Database
PID Displays the process ID of the session running in the DB2 server.
User The login name of the user executing the process.
Host Name/IP The hostname of the machine where the session is running.
Program Name Name of the program/application that has established the session.
DB Name Displays the name of the database currently being used by the process.
Total CPU The cumulative CPU time taken for running the process (in milliseconds).
CPU I/O Amount of CPU time taken by the process to perform I/O operations (in milliseconds).
Network
Amount of time spent by the CPU on client-server communications (in milliseconds).
Communication CPU
The total amount of time spent by an application waiting within the DB2 database server
Total Wait Time
(in milliseconds).
Amount of time spent by an application queued to wait for an agent under concentrator
Agent Wait Time
configurations (in milliseconds).
Lock Wait Time Amount of time spent by an application waiting for locks (in milliseconds).
Client Idle Time Amount of time spent waiting for the client to send its next request (in milliseconds).
Start Time The date and time at which the session started.
IBM DB2 for i Monitoring
IBM DB2 for i - An Overview
Monitoring IBM DB2 for i - What we do
Adding a new IBM DB2 for i monitorMonitored Parameters
IBM DB2 for i - An Overview
DB2 for i is a member of IBM’s family of DB2 databases. It is an integrated relation database management system
for the IBM i platform. DB2 for i contains a rich set of security features and services that pertain to the goals of
authentication, authorization, integrity, confidentiality, and auditing.
Monitoring IBM DB2 for i - What we do.
Applications Manager aims to help database admins with tuning their DB2 and gather operating system level data
to understand performance issues. Let’s take a look at what you need to see to monitor IBM DB2 for i, the
performance metrics to gather and how you can ensure that your DB2 database is up and operating as expected
with Applications Manager:
Monitor Jobs status and health and also optimize your server''s resources by minimizing network traffic, disk
I/O and CPU time.
Track memory usage details and keep track of JVM metrics to correlate server performance.
Get instant notifications when there are performance issues with the components of your DB2.
Become aware of performance bottlenecks and take quick remedial actions before your end users experience
issues.
Adding a new IBM DB2 for i monitor
Prerequisites for monitoring IBM DB2 for i:
To monitor IBM DB2 Version 8 and 9, the minimum user privileges required is the ability to access the
SYSPROC procedures.
To monitor IBM DB2 Version 10, the minimum user privileges required is the ability to access the SYSIBMADM
functions.
To create a IBM DB2 for i database server Monitor, follow the given steps:
Click on New Monitor link.
Select DB2 for i Server.
Enter a Display Name for your monitor.
Enter the IP Address or hostname of the host.
Enter the Subnet Mask of the network.
Enter the port number in which DB2 is running.
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Provide the user name and password of user who has permission to access the DB2 database. The user name
specified for collecting the data from DB2 Server should have either System Administrator role or the user
should be the DB owner for master database.
Specify the Database Name.
Choose the Monitor Group from the combo box with which you want to associate the DB2 database server
Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers DB2 for i database server from the network and starts monitoring them.
Monitored Parameters
Overview
System Information
Jobs and JVM Information
Configuration
Overview
ATTRIBUTE DESCRIPTION UNITS
NAME
CPU DETAILSATTRIBUTE DESCRIPTION UNITS
NAME
Average
CPU The average CPU utilization for all the active processors. %
Utilization
The average CPU rate expressed as a percentage where 100% indicates the processor is
running at its nominal frequency. A value above or below 100% indicates how much the
Average
processor has been slowed down (throttled) or speeded up (turbo) relative to the nominal %
CPU Rate
frequency for the processor model. For instance, a value of 120% indicates the processor
is running 20% faster against its nominal speed.
Configured
The total number of configured CPUs. -
CPUs
The current processing capacity specifies the processor units that are being used in the
partition. For a partition sharing physical processors, the current processing capacity
Current CPU
represents the share of the physical processors in the pool it is running. For a partition GHz
Capacity
using dedicated processors, the current processing capacity represents the number of
virtual processors that are currently active in the partition.
SCHEMA DETAILS FOR TOP 10 SCHEMA BY SIZE
Schema Schema Name -
Table Count The number of tables in the schema -
Size The size of the Schema MB
Partition
The number of Partitions present in the Schema -
Count
Pages The number of 64K pages in all partitions or members of the table. -
Distinct The number of distinct indexes built over any partitions or members of the table. This
-
Indexes does not include maintained temporary indexes.
Insert The number of insert operations of all partitions or members of the table since the last IPL
-
Operations (Initial Program Load).
Update The number of update operations of all partitions or members of the table since the last
-
Operations IPL.
Delete The number of delete operations of all partitions or members of the table since the last
-
Operations IPL.
Logical The number of logical read operations of all partitions or members of the table since the
-
Reads last IPL.
System Information
ATTRIBUTE DESCRIPTION UNITS
NAME
SYSTEM DETAILS
Main Storage
The amount of main storage in the system. GB
Size
System ASP
The amount of ASP storage in the system. GB
Storage
System ASP
The amount of ASP Memory used by the System MB
Used
Partitions
The number of Partitions in the System -
Count
Active
Threads in The number of Active Threads in the System -
System
MEMORY POOL INFORMATIONATTRIBUTE DESCRIPTION UNITS
NAME
The name of the storage pool. The name may be a number, in which case it is a private
pool associated with a subsystem, or one of the following special values.
• MACHINE - The specified pool definition is defined to be the machine pool.
• BASE - The specified pool definition is defined to be the base system pool, which can
Pool Name be shared with other subsystems.
• INTERACT - The specified pool definition is defined to be the shared pool used for the
QINTER subsystem.
• SPOOL - The specified pool definition is defined to be the shared pool used for spooled
writers.
• SHRPOOLx - The specified pool definition is defined to be a shared pool.
Reserved The amount of storage in the pool reserved for system use (for example, for save/restore
GB
Size operations).
Current Size The amount of main storage in the pool. GB
Maximum
Active The maximum number of threads that can be active in the pool at any one time. -
Threads
Current
The number of threads currently using the pool. -
Threads
Elapsed Time The time since the measurement start time. Sec
Jobs and JVM Information
TOP 10 GARBAGE COLLECTIONS AND HEAP TIME USING JVM INFORMATION
ATTRIBUTE DESCRIPTION UNITS
NAME
JOB DETAILS
Active Jobs The number of jobs active in the system (jobs that have been started, but have not yet
-
in System ended), including both user and system jobs
Interactive
The percentage of interactive performance assigned to this logical partition. This value is
Jobs in %
a percentage of the total interactive performance available to the entire physical system.
System
The total number of user and system jobs that are currently in the system. The total
includes:
Total Jobs in • All jobs on job queues waiting to be processed.
System • All jobs currently active (being processed).
• All jobs that have completed running but still have output on output queues to be
produced.
The maximum number of jobs that are allowed on the system. When the number of jobs
reaches this maximum, you can no longer submit or start more jobs on the system. The
Maximum total includes:
Jobs in • All jobs on job queues waiting to be processed.
System • All jobs currently active (being processed).
• All jobs that have completed running but still have output on output queues to be
produced.
Job Name The name of Job that is running in DB2 Database -
Process ID The process identifier used by the kernel to uniquely identify the process. -
Total GC
The total time spent performing garbage collection tasks. Min
Time
Current Java
The current number of java threads within the JVM job. -
Threads
Current
The amount of memory currently allocated for heap space. MB
Heap Size
In Use Heap
The amount of memory currently in use by the heap. MB
Size
Max Heap
The maximum heap size available to the JVM code, MB
SizeConfiguration
ATTRIBUTE NAME DESCRIPTION
Aliases Alias is an alternative name for database objects.
Sequences The number of Sequences
Global Variables The number of Global Variables
Journals The number of Journals
Journal Receivers The number of Journal Receivers
Schemas The number of Schemas
Tables The number of Tables
Partitioned Tables The number of Partitioned Tables
Distributed Tables The number of Distributed Tables
Materialized Tables The number of Materialized Tables
Physical Files The number of Physical Files
Source Files The number of Source Files
Logical Files The number of Logical Files
DDM Files The number of DDM Files
External Triggers The number of External Triggers
SQL Procedures The number of SQL Procedures
External Procedures The number of External Procedures
SQL Procedures The number of SQL Procedures
IBM Informix Database Monitoring
IBM Informix - An Overview
Creating a new Informix monitor
Monitored Parameters
IBM Informix - An Overview
IBM Informix is one of the industry''s most widely used database servers with a comprehensive set of high
availability options, high levels of performance, data replication capabilities, scalability and minimal
administrative overhead for both simple and complex IT infrastructures. Applications Manager performs effective
monitoring, which is very critical in Informix administration, to collect system and database performance stats,
session details and to identify problems at an early stage for proactive troubleshooting and performance tuning.
Creating a new Informix monitor
Supported versions of Informix Server: Informix 10.x & above.
Prerequisite: Click here to know about the user previleges and other necessary prerequisites to monitor IBM
Informix database.
To create an Informix Server Monitor
Click on New Monitor link.
Select Informix under Database Servers.
Specify the Display Name of the Informix monitor
Enter the HostName or IP Address of the host where Informix server is installed.
Enter the port number for eg., 1526.
Enter the Database Server name i.e the name of the Informix database server to which you want to connect.
You can enter your own credential details or select preconfigured credentials from Credentials Manager. If you
wish to enter your own credentials, specify Informix username and password details for this monitor.
Set the Polling Interval.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which you want to associate Informix Server Monitor
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers Informix server from the network and starts monitoring them.Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Informix under the Database Servers
Table. Displayed is the Informix Database bulk configuration view distributed into three tabs:
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the server details listed under the following tabs:
Overview
Database
Sessions
Overview
Parameter Description
Response time The time taken to establish a JDBC connection with the Informix Server.
Database Space Details
Dbspace Name The unique name of the Database Space.
Allocated (MB) The total physical disk size allocated for the Database Space in MB.
Free (MB) The free physical disk size for the Database Space in MB.
Used % The percentage of physical disk utilization by the Database Space.
Disk Reads/sec The number of Disk Reads happening in the Database Space per second.
Disk Writes/sec The number of Disk Writes happening in the Database Space per second.
Database
Parameter Description
Name The name of the database.
DBSpace
The Database Space which stores data for this database.
Name
Owner The User ID of the creator of the database.
Created
The time at which the Database was created.
On
The current logging modes of a database:
Is Logging
Is Buff Log Unbuffered logging. Values are either 0 or 1. (1=Yes, 0=No)
Is ANSI Buffered logging. Values are either 0 or 1. (1=Yes, 0=No)
ANSI mode database. Values are either 0 or 1. (1=Yes, 0=No)
Is NLS
NLS support. Values are either 0 or 1. (1=Yes, 0=No)
Is Case
Indicates whether NCHAR and NVARCHAR columns are case-insensitive or not. Values are
Insens
either 0 or 1. (1=Case-insensitive, 0=Case-sensitive)
Sessions
Parameter Description
Session Id A unique identifier number assigned to the session.
User Name The User name of the Informix user account.
Host Name The host from which the user is connecting to the Informix database
Login Time The time at which the user connected to the database server.
SAP HANA MonitoringCreating a new SAP HANA monitor
Prerequisites for monitoring SAP HANA metrics: Click here
Using the REST API to add a new SAP HANA monitor: Click here
To create a SAP HANA DB server monitor, follow the steps given below:
Click on New Monitor link.
Select SAP HANA under Database Servers.
Specify the Display Name of the SAP HANA monitor
Enter Host Name of HANA server.
If Using SAP HANA Cloud Platform,
Select SAP HANA Cloud Platform.
Enter Cloud Account Name, UserName and Password.
Enter Port as IndexServer port, default port is 30015.
You can enter your own credential details or select pre-configured credentials from Credentials Manager. If
you wish to enter your own credentials, specify SAP HANA username and password details for this monitor.
Enter Database Username and Database Password.
Enter Instance Name.
Set the Polling Interval.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which you want to associate SAP HANA Server Monitor
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers SAP HANA server from the network and starts monitoring them.
Prerequisites:
Need to copy ngdbc.jar into the location /working/classes. ngdbc.jar can be copied from installed SAP HANA
Client folder. Click here to download SAP HANA Client
If HANA is running On-demand, in addition to the above, SAP Cloud Platform SDK is needed. However, this is
not needed for HANA On-premise. Click here to download SAP Cloud Platform SDK. The downloaded zip should
be extracted under /working/hanacloud folder. After extracting need to verify
whether /working/hanacloud/tools folder is available.
Need to restart APM after performing the above steps.
To effectively monitor SAP HANA, the SAP HANA DB User must have the below privileges,
System privilege CATALOG READ
Object privilege SELECT on the schema _SYS_STATISTICS
To grant these privileges to the user, execute the below statements in SAP HANA SQL console.(Replace
USER_NAME with actual HANA DB Username)
GRANT MONITORING to
CALL GRANT_ACTIVATED_ROLE (''sap.hana.admin.roles:Monitoring'','''')
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on SAP HANA under the Database Servers
Table. Displayed is the SAP HANA bulk configuration view distributed into three tabs:
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the server details listed under the following tabs:
Overview
Alerts
Caches
Jobs
Expensive Statements
Transactions
WorkloadBackup
Replication
Schema
Disk
Services
Overview
Parameter Description
Memory and CPU
Memory Utilization Percentage of Memory Utilized by HANA System as a whole
CPU Utilization Percentage of CPU Utilized by HANA System as a whole
CPU Available No. of CPU Available
CPU Used Used no. of CPU.
Total Physical Memory Total Physical Memory of HANA System
Used Physical Memory Memory Used by HANA System
Total Swap Memory Total Swap Memory allocated for HANA System
Connection Statistics
Active Connections Total No. of Active Connections
Inactive Connections Total No.of Inactive connections
Memory Details of Host
Total Physical Memory Total Memory for each host in the HANA system.
Free Physical Memory Free Memory Available in individual host
Used Physical Memory Used Memory in individual host (HANA+other appllications)
Swap Memory Swap Memory of individual host
Used Swap Memory Swap Memory used.
Peak Memory Peak Memory used in each host
Memory Used By HANA
Allocation Limit Memory allocated for HANA in each host
HANA used memory Memory Used only by HANA in each host (Total resident)
Memory Used by Column The amount of memory used for column tables. (A major part of the SAP HANA Used
Tables Memory is taken up by the data tables).
Memory Used by Row The total amount of memory used for row tables. (A major part of the SAP HANA
tables Used Memory is taken up by the data tables).
Code & Stack Memory Memory used by HANA Code and Stack
The amount of physical memory actually in operational use by a process. (When a
DataBase Resident part of the virtually allocated memory actually needs to be used, it is loaded or
mapped to the real, physical memory of the host, and becomes "resident".)
System Information
Version The version of the SAP HANA database that is installed on the system.
System Type A SAP HANA system can be configured as a single-host or multiple-host system.
All Services Started Indicates if all services are started and the system is operational and accessible.
Platform The operating system of the SAP HANA system.
Instance ID The instance ID of the SAP HANA database.
Services
Parameter Description
Service name The name of the service.
CPU used The percentage of CPU used by the service.
Memory Used The memory used by each service.Requests per sec The number of requests that are processed by the host computer.
The time (in milliseconds) that is taken by the service to respond to requests from
Response Time
the clients.
Active Requests count The number of active requests that are being processed by the service.
The number of requests that are waiting in a queue to be processed by a service in
Pending requests count
the SAP HANA database server.
Active Threads count The total number of active threads for the service.
The number of files that are currently opened through a service in the SAP HANA
Open File Count
database server.
Service status The status of the service. The status can be no, yes, unknown, starting,and stopping.
Disk
Parameter Description
The type of disk usage on the host computer. The usage types are log,data, trace,
Disk usage Type
data_backup, and log_backup.
Total Disk Space The total Space allocated for each Disk
Disk Used Disk Used
Disk Free percentage The free space percentage of the disk.
Disk Path The path to the disk, disk location.
Disk Volume size The total disk space in GB.
Disk Volume
Service Name The name of the service.
Volume ID The unique volume identifier.
File Type The type of file in the volume directories. Possible values are - DATA, LOG, TRACE.
File Name The name of the file,
Total Volume Size The total data volume sizes of the SAP HANA servers.
Used Volume Size The total data volume sizes used.
Free Size The free memory size of the module.
Volume IO Statistics
Service Name The name of the service.
Volume ID The unique volume identifier.
Volume Path The Filesystem path.
Disk Type The Filesystem type.
Blocked Write Requests The count of blocked write requests.
Total Reads Total number of file reads on the disk for all file types.
Total Failed Reads Total number of failed reads from the disk.
Total Read Size Total size of read data (in MB).
Total Read Time Total time taken to read data (in sec).
Total Appends Total number of file appends on the disk for all file types.
Total Writes Total number of file writes on the disk for all file types.
Total Failed Writes Total number of of failed writes.
Total Write Size Total size of written data (in MB).
Total Write Time Total time taken to write data (in sec).
Total I/O Time Total time taken to perform I/O operations (in sec).
Speed The I/O performance measured in MB/sec.
Schema
Parameter DescriptionNo.of Column Tables The number of Column Tables in this partition.
Size of Column Tables Allocated memory size for fixed-size and variable-size column table paritions.
No. of Row Tables The number of Row Tables in this partition.
Size of row tables Allocated memory size for fixed-size and variable-size row table paritions.
Replication
Parameter Description
Host Host name
Service Name Name of the Service
Site Name Logical site name
Secondary Host The secondary host name.
Secondary Site Name The secondary logical site name.
Replication Status Replication Status
Backup
Parameter Description
Backup Size The size of the backup.
Source Type name Type of persistence to be backed up: ''volume'', ''topology''.
Service Type Name Type of database service: ''indexserver'', ''nameserver'', ''statisticsserver''.
Classification of backup catalog entries: ''complete data backup'', ''data snapshot'',
Entry type Name
''log backup'', ''log missing''
Start time Time stamp when backup started
Total Time TimeTaken for Backup
Result of corresponding action: ''successful'', ''failed'', ''running'', ''cancel pending'',
Backup status
''canceled''
Backup Configuration
Max Recovery File Age The maximum recovery file age in seconds.
Log Replay Step Size The Log replay step size in bytes.
Max Recovery Backint
The max number of parallel backint channels per request during recovery.
Channels
Backint Executable Link The link name of the backint executable.
Backint Executable The filename of the backint executable.
Backint Data Backup Path The data backup directory for backint.
File Data Backup Path The default directory for file-based data backups.
File Log Backup Path The current directory for file-based log backups.
Latest Backup Details
Latest Backup ID The unique ID of a data backup or a log backup respectively.
Latest Backup Start Time The start time of the backup operation.
Latest Backup End Time The end time of the backup operation.
The classification of backup catalog entries. The following types are supported:
Latest Backup Entry Type
''complete data backup'', ''log backup'', ''log missing''.
Latest Backup Destination
The type of backup location. Possible values are - ''file'' or ''backint''.
Type
Latest Backup Size Specifies the size of the backup.
Workload
Parameter Description
Current Execution
The current statement execution count per minute.
Rate/minCurrent Compilation The current statement preparation count per minute.
Rate/min
Current Transaction
The current transaction count per minute.
Rate/min
Current Commit Rate/min The total number of commits per minute.
Current Rollback Rate/min The total number of rollbacks per minute.
Current Memory Usage
The total size of used memory per minute.
Rate/min
Transactions
The Blocked Transaction data set provides information about the transactions that are waiting to acquire
transaction locks held by another transaction, network, or disk.
Parameter Description
Blocked Transaction Id The connection ID of the blocked transaction.
Lock Owner Transaction Id The connection ID associated with the write transaction that is holding the lock.
Blocked Time The time from when the transaction is blocked.
Waiting Schema Name The name of the schema on which the lock is placed.
Waiting Object Name The type of the object on which the lock is placed.
The type of lock that is held by the blocking transaction. The lock type can be record,
Lock Type
object, and metadata.
The access level of transactions to the locked record, table, and database. The lock
Lock Mode
mode can be shared, exclusive, and intentional exclusive.
Blocked Statement The statement that is blocking the transaction.
Expensive Statements
The Expensive Statement data set provides information about the statements for which execution timewas greater
than the configured threshold.
Parameter Description
Statement Duration The time that is required for executing the statement.
Records The number of records in the database table.
Memory Size The memory required for computing the statement.
DB User The user name that is used to connect to the database.
Operation Type of operation: e.g. prepare, execute, fetch, close.
Statement The SQL statement that runs for duration longer than the defined threshold.
Error Code The error code associated with the query.
Error Message The error message associated with the error code.
Jobs
Parameter Description
Connection Id The connection that triggered the operation.
Schema name Schema of the object.
Object name Name of the object.
Job Name The type of the operation.
Start Time The time when the operation was started.
The current status of the operation. One of the following values is possible: inactive,
Current Job Progress
active, precommitted, aborting, partial_aborting, and active_prepare_commit.
Caches
Parameter DescriptionCache id The unique identifier for the cache.
Total Size Maximum available memory for each cache instance
Used Size Memory Used by Cache instance
Hits Count Number of cache hits for the cache instance.
Misses Count Number of cache misses for the cache instance.
Alerts
Parameter Description
Alert ID The ID of the current alert.
The severity of the alert occurrence. The severity might be different for each alert.
Alert rating The following values are possible: 1 (information message), 2 (warning level 1), 3
(warning level 2), 4 (warning level 3), 5 (error message).
Alert TimeStamp The time according to the local server time when the alert was occurred.
Description The information about the alert.
Sybase ASE Monitoring
Creating a new Sybase monitor
Supported Versions: Applications Manager supports monitoring of Sybase ASE 12.5.3 and above.
Prerequisites for monitoring Sybase metrics: Click here
Using the REST API to add a new Sybase monitor: Click here
To create a Sybase database server monitor, follow the given steps:
Click on New Monitor link.
Select Sybase.
Enter the IP Address or Host Name of the host.
Enter the SubNetMask of the network.
Enter the port number in which sybase is running.
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Provide the user name and password of user who has permission to access the Sybase database. The user
name specified for collecting the data from Sybase should have either System Administrator role or the user
should be the DB owner for master database.
Specify the Database Name.
Choose the Monitor Group from the combo box with which you want to associate Sybase database server
Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers Sybase database server from the network and starts monitoring them.
Monitored Parameters
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
Click on the following tabs listed to view the following information:
Monitor Information
Overview
Database
Performance
Process
Monitor Information
Parameters DescriptionName Specifies the name of Sybase server monitor.
Health Specifies the health (Clear, Warning, Critical) of the Sybase server.
Type Specifies the type you are monitoring.
Version Specifies the version of the database server.
Port Specifies the port number at which the database server is running.
Server Status The current status of the database server itself
Started Time The date and time that the database manager was started
Host Name Specifies the host at which the database server is running.
Host OS Specifies the OS of the host where the database server is running.
Last Alarm Specifies the last alarm that was generated for the database server.
Last Polled at Specifies the time at which the last poll was performed.
Next Poll at Specifies the time at which the next poll is scheduled.
Availability Shows the current status of the server - available or not available.
Overview
Parameters Description
CONNECTION TIME
Time taken to get connected to the Sybase database ASE server (in
Connection Time
milliseconds).
MEMORY UTILIZATION
Total Memory Total amount of memory available for the ASE server (in MB).
Used Memory Amount of memory used by the ASE server (in MB).
Free Memory Remaining amount of memory available for the ASE server (in MB).
Used Memory Percentage Amount of memory used by the ASE server (in percentage).
REMOTE CONNECTION STATISTICS
Max Remote Connections The number of max remote connections available in the ASE server.
Remote Connection Percentage of the amount of active remote connections after the ASE server has
Percentage restarted.
Active Remote Connections The number of active remote connections after the ASE server has restarted.
USER CONNECTION STATISTICS
Max User Connections The number of max user connections available in the ASE server.
Active User Connections The number of active user connections after the ASE server has restarted.
Percentage of the amount of active user connections after the ASE server has
User Connection Percentage
restarted.
LOCK STATISTICS
Max Locks Total number of locks configured to be held in the ASE server.
Active Locks Number of locks that are in active state.
Active Lock Percentage Percentage of active locks with total locks configured.
DISK I/O STATISTICS
Max Disk I/O Total number of disk I/O available in the ASE server.
Active Disk I/O Number of disk I/O that are active and currently in use.
Active Disk I/O Percentage Percentage of active disk I/O with the max disk I/O.
PROCEDURE CACHE USAGE
Max Procedure Cache Total amount of procedure cache allocated for Sybase ASE server.
Procedure Cache Used Amount of procedure cache that are currently in use.
Procedure Cache Used
Percentage of procedure cache used with the max procedure cache.
Percentage
Stored Procedure Request
Number of stored procedure requests processed per second.
RateDATA CACHE USAGE
Configured Data Cache Amount of data cache configured during the server startup (in MB).
Current Data Cache Amount of data cache that are currently in use (in MB).
CACHE HIT RATIO
Ratio of Logical Reads to Cache Searches performed for default cache (in
Data Cache Hit Ratio
percentage).
Ratio of difference between procedure requests and load to requests made (in
Procedure Cache Hit Ratio
percentage).
Database
Parameters Description
Database Details
DB Name Name of the database instances.
Total Size Total amount of space allocated for the database (in MB).
Used Size Amount of space used in the database (in MB).
Free Size Remaining amount of space available in the database (in MB).
Used Size (%) Amount of space used in the database (in percentage).
Log Size Amount of space allocated for logs in the database (in MB).
Log Used Amount of space used from the allocated log space in the database (in MB).
Log Used (%) Amount of space used from the allocated log space in the database (in percentage).
Creator Name of the user who created the database.
Health Health status of the database.
Database Backup Details
DB Name Name of the database.
Backup Status Status of the backup performed.
Backup Start Time Date and time at which backup was started.
Backup Age Amount of time elapsed since the last backup (in hours).
Number of processes that are currently suspended due to the database transaction log
Suspended Processes
being full.
Transaction Log Full Indicates whether the database transaction log is full. (Yes or No)
Last Checkpoint Date and time at which checkpoint was last run for this database.
Last Transaction Log
Date and time of this database’s most recently successful transaction log dump.
Dump
Transaction Details
Type The type of the transaction
Coordinator The coordinator of the transaction
State The state of the current transaction like it is started or in process or ended
Connection The type of connection
DB Name The database name in which the transaction is executed
Process Name The process which is executing the transaction
Transaction Name The name of the transaction
Start Time The time at which the transaction started
Performance
This tab displays the performace of top 10 queries in terms of various factors such as CPU Time, Memory Usage,
Run Time and Wait Time.
Top 10 queries by CPU - Displays the list of top 10 queries with high CPU Time.
Top 10 queries by Memory Usage - Displays the list of top 10 queries with high Memory Usage.
Top 10 slow running queries - Displays the list of top 10 queries with high execution time.Top 10 most waited query - Displays the list of top 10 queries with high Wait Time.
Below are the list of metrics that are displayed in this tab:
Parameters Description
Process ID ID of the process currently connected to ASE server.
DB Name Name of the database currently in use.
Query Displays the database query that is running.
CPU Time Amount of time taken by the CPU to execute the query (in milliseconds).
Wait Time Amount of time for which the task has waited to execute the query (in milliseconds).
Execution Time Amount of time taken for the query to be executed (in seconds).
Memory Usage(kB) Amount of memory utilized to execute the query (in kilobytes).
Physical Reads Number of buffers reads that have been performed from disk while executing the query.
Logical Reads Number of buffers reads that have been performed from cache while executing the query.
Process
Parameters Description
Command Process Details
Process ID ID of the process currently connected to ASE server.
Process Name The name of the process currently connected to ASE server
Host
The Host Name / IP address of the process connected to ASE
Name/IPAddress
User Name The name in which the process is connected to ASE
DB Name The name of the Database to which process is connected to ASE
The command executed by process connected to ASE (command shown here limits to 255
Command
chrs)
Status The current status of the process
Physical IO The Physical IO of the process
Memory Usage The memory used by the process
Time Blocked Amount of time blocked by the process (in seconds).
PostgreSQL Performance Monitoring
Overview
Applications Manager''s PostgreSQL monitoring tool plays a vital role in monitoring your PostgreSQL database
servers by providing end-to-end visibility into the performance of your database server in real-time. It aids you to
keep check over the health and availability of your PostgreSQL servers by monitoring various key metrics such as
database utilization, response time, query performance, session details and much more.
With proactive PostgreSQL performance monitoring tools like Applications Manager in place, you can ensure that
the performance of your PostgreSQL environments are kept on point. In this help document, you will learn how to
get started with PostgreSQL performance monitoring, along with the list of parameters that are monitored with
Applications Manager.
Creating a new PostgreSQL performance monitor
Supported Versions : 8.1 and above.
Prerequisites for monitoring PostgreSQL metrics : Click here
Rest API to add a new PostgreSQL performance monitor : Click here
To create a PostgreSQL database server monitor, follow the steps given below:
Click on New Monitor link.
Select PostgreSQL.
Enter the Display Name of the database server.Enter the IP Address or the Host Name of the host.
Enter the port number in which PostgreSQL is running.
Provide the user name and password of user who has permission to access the PostgreSQL database.
Specify the DBName.
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group with which you want to associate the PostgreSQL database server to, from the
combo box (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers PostgreSQL database server from the network and starts monitoring
them.
Monitored Parameters
Availability tab displays the availability history of the PostgreSQL database servers in your network for the
past 24 hours or 30 days.
Performance tab displays the health status and events for the past 24 hours or 30 days.
List view tab displays all the PostgreSQL servers that you monitor along with their current availability and
health status. You can also perform bulk admin configurations from this view.
Applications Manager''s PostgreSQL monitoring tool provides complete visibility into your database environments
based on the metrics listed in the following tabs:
Monitor Information
Overview
Performance
Database
Session
Replication
Configuration
Monitor Information
Parameter Description
Name Denotes the name of PostgreSQL database server monitor.
Type Denotes the type you are monitoring.
Health Denotes the health (Clear, Warning, Critical) status of the PostgreSQL server.
Last Polled at Specifies the time at which the last poll was performed.
Next Poll at Specifies the time at which the next poll is scheduled.
Availability Shows the current status of the server - available or not available.
Overview
Parameter Description
Connection Statistics:
Active Connections Number of currently active connections to the database
Total Users The total number of users active at the time of data collection
Lock Statistics:
Locks Held Number of locks held by the indicated session
Locks Wait Number of locks waiting in the database
Buffer Statistics:
Total buffer hits (i.e., block read requests avoided by finding the block already in
Buffer Hits/min
buffer cache) per minute
Block Reads/Min Total disk blocks read per minute
Cache Hit Ratio The current ratio of buffer cache hits to total requests
Disk Usage Details:Disk Usage Size of the on-disk representation of all tables in the database in MB
Index usage Size of the on-disk representation of all indexes in the database in MB
Index Scan Details:
Index scans/min Total number of index scans initiated per minute
Index Reads/min Total number of index entries returned by index scans per minute
Index Fetches/min Total number of live table rows fetched by simple index scans per minute
Query Statistics:
Row inserts/min Total numbers of rows returned by each type of scan per minute
Row Updates/min Total of row insertions and updates per minute
Row Deletes/min Total number of rows deleted per minute
Transaction Details:
Total Commits Total transactions committed
Total Rollbacks Total transactions rolled back
Commits/Min Total transactions committed per minute
Rollbacks/Min Total transactions rolled back per minute
Table Level Scan Details:
Sequential Scans/min Total number of sequential scans per minute
Table Index Scans/min Total number of index scans per minute
Sequential Scan Rows
Total number of rows returned by sequential scans per minute
Read/min
Table Index Scan Rows
Total numbers of rows returned by index scans per minute
Read/min
Primary Database Object Statistics:
Total Tables Total number of tables in the database server
Total Triggers Total number of triggers in the database server
Total Procedures Total number of procedures in the database server
Size of the Largest Table Size of the largest table in the database server
Largest Table(s) Largest table in the database server
Performance
Parameter Description
Top Queries by CPU:
Database
The database name under which the query has been executed.
Name
Total CPU The cumulative total amount of CPU time that has been spent in running the query (in
Time millisecond).
Average CPU
The average CPU time taken to execute the query (in millisecond).
Time
The maximum amount of time that was taken by the CPU to run the query (in millisecond).
Max CPU Time
(Available from Postgres 9.4)
Query The SQL query which consumed the maximum CPU time.
Long Running Query Details:
Process ID The identifier for the process caused by the query.
Runtime Amount of time for which the query has been running (in minutes).
User Name Name of the user executing the query.
Query The SQL query that was running.
Database
The database name under which the query has been running.
Name
Top 50 Table Row Details:
Table Name Name of the table.No. of Rows Number of rows available in the table.
Table Size Size of the table (in MB).
Database
Parameter Description
Database Details:
Database Name Name of the database instance.
DB Size Size of the database instance (in MB).
Connections Number of connections for the database instance.
TableSpace Name of the tablespace.
TableSpace Details:
Name Name of the tablespace.
Owner Owner who created the tablespace.
Location Location where the tablespace is created.
Size Current size of the tablespace (in MB).
Session
Parameter Description
Session Details:
Process ID Displays the process ID of the session running in the Postgres server.
Client Address IP address of the client connected to the server.
Application
The name of the application that has established the session. (Available from Postgres 9.0)
Name
Database Name Displays the name of the database currently being used by the process.
User The login name of the user executing the process.
State The state of the process in the Postgres server. (Available from Postgres 9.2)
Blocked Indicates whether the process is blocked or is currently waiting on lock.
Displays the Wait Event Name and Wait Event Type that is currently waiting. (Available from
Wait Event
Postgres 9.6)
Query The SQL query that was last executed in the process.
CPU Time The cumulative CPU time taken for the process running in the Postgres server (in millisecond).
Replication
Parameter Available Description
Versions
Replication Details:
WAL files count >=9.2 Number of WAL files present in WAL directory.
Current WAL
>=9.2 Gives the last inserted location.
Location
wal_level determines how much information is written to the WAL.
Default value = minimal (version < 10) minimal → writes only the
information needed to recover from a crash or immediate shutdown.
Default value = replica (version > 10) replica → writes enough data to
WAL level >=9.2
support WAL archiving and replication, including running read-only queries
on a standby server.
Other states: hot_standby → minimal state/replica state info + adds
information required to run read-only queries on a standby server.
WAL sync method >=9.2 Method used for forcing WAL updates out to disk. If fsync is off, then this setting
is irrelevant, since WAL file updates will not be forced out at all. Possible values
are: open_datasync (write WAL files with open() option O_DSYNC), fdatasync(call fdatasync () at each commit), fsync (call fsync () at each commit),
fsync_writethrough (call fsync () at each commit, forcing write-through of any
disk write cache)
checkpoints_timed >=9.2 Number of scheduled checkpoints that have been performed.
checkpoints_req >=9.2 Number of requested checkpoints that have been performed.
buffers_checkpoint >=9.2 Number of buffers written during checkpoints.
buffers_clean >=9.2 Number of buffers written by the background writer.
buffers_backend >=9.2 Number of buffers written directly from backend.
Client Address >=9.2 Address of client/standby server address.
TCP port number that the client is using for communication with this WAL
Client Port >=9.2
sender.
PID >=9.2 Process ID of a WAL sender process.
application name >=9.2 Name of the application that is connected to this WAL sender.
Current WAL sender state. Possible values are:
startup: This WAL sender is starting up.
catchup: This WAL sender''s connected standby is catching up with the
primary.
Sender State >=9.2
streaming: This WAL sender is streaming changes after its connected
standby server has caught up with the primary.
backup: This WAL sender is sending a backup. stopping: This WAL sender
is stopping.
Synchronous state of this standby server. Possible values are:
async: This standby server is asynchronous.
potential: This standby server is now asynchronous, but can potentially
Sync State >=9.2 become synchronous if one of the current synchronous ones fails.
sync: This standby server is synchronous.
quorum: This standby server is considered as a candidate for quorum
standbys.
Sending lag >=9.2 Lag in sending the transactions to standby
Last replay location >=9.2 Gives the last replayed location
Write lag >=9.2 Lag in writing transaction to disk in standby.
Flush lag >=9.2 Lag in flushing transactions to disk in standby.
Replay lag >=9.2 Lag in replaying the transactions on standby
Total lag >=9.2 Total lag sending from master to replaying transaction on standby.
Master Host >=9.6 Host details of master node.
Master Port >=9.6 Port of master node.
Master User >=9.6 User details of the master node.
Time lag between the last received transaction and the last replayed
Replication Delay >=9.1
transaction.
Replication Slots:
slot_name >=9.6 A unique, cluster-wide identifier for the replication slot.
slot_type >=9.6 The slot type - physical or logical.
active >=9.6 True if this slot is currently actively being used.
The address (LSN) of oldest WAL which still might be required by the consumer
restart_lsn >=9.6
of this slot and thus won''t be automatically removed during checkpoints.
The address (LSN) up to which the logical slot''s consumer has confirmed
confirmed_flush_lsn >=9.6 receiving data. Data older than this is not available anymore. NULL for physical
slots.
Configuration
Parameter DescriptionVersion Version of the PosgreSQL Server.
Config File Location of Postgres server configuration file.
Data Directory Location of data directory used by the Postgres server.
External PID File Location of external PID file.
hba File Location of hba file.
ident File Location of ident file.
Apache HBase Monitoring
Apache HBase - An Overview
Monitoring Apache HBase - What we do
Adding a new Apache HBase monitor
Monitored Parameters
Apache HBase - An Overview
Apache HBase is a distributed, scalable, data store. Being open-sourced and non-relational, HBase is the database
for you when you need random, real-time read/write access to your Big Data. Apache HBase provides Google''s
Bigtable-like capabilities on top of Hadoop and HDFS.
Monitoring Apache HBase - What we do.
Applications Manager aims to help Apache HBase administrators monitor the cluster in terms of region
distribution. Let’s take a look at what you need to see to monitor Apache HBase, the performance metrics to gather
and how you can ensure that your HBase database is up and operating as expected with Applications Manager:
Track HBase cluster metrics - Monitor HBase clusters to make sure your HBase cluster is up and running and
is continuously operating as expected. Track the average load, requests, and the number of dead, live and
overall number of region servers.
Memory and JVM usage - Track memory usage details such as available memory, free and total swap space
size, the committed virtual memory size, etc. Keep track of JVM metrics to correlate server performance.
Guage Region servers performance - Get metrics about the block cache, the cache hit and miss counts and
the hit ratio. Look at compaction metrics and and the total size of storage files that have been compacted.
Fix performance problems faster - Get instant notifications when there are performance issues with the
components of Apache HBase components. Become aware of performance bottlenecks and take quick
remedial actions before your end users experience issues.
Apache HBase - Adding a new monitor
Supported versions: HBase version 1.x
Prerequisites for monitoring Apache HBase:
JMX MBeans are used to collect HBase metrics. To enable JMX, open HBase/conf/HBase-env.sh and
uncomment/add the below JVM arguments.
export HBase_JMX_BASE="-Dcom.sun.management.jmxremote.ssl=false -
Dcom.sun.management.jmxremote.authenticate=false"
export HBase_MASTER_OPTS="$HBase_MASTER_OPTS $HBase_JMX_BASE -
Dcom.sun.management.jmxremote.port=10101"
export HBase_REGIONSERVER_OPTS="$HBase_REGIONSERVER_OPTS $HBase_JMX_BASE -
Dcom.sun.management.jmxremote.port=10102"
Using the REST API to add a new Apache HBase monitor: Click here
To create an Apache HBase Monitor, follow the steps given below:
Click on New Monitor link. Choose Apache HBase.
Enter Display Name of the monitor.
Enter the IP Address or hostname of the host in which HBase is running.
Enter the JMX Port in the JMX Port field. For default installations of HBase, the JMX port number is 10101 for
Master and 10102 for RegionServer.Enter the credential details like user name, password and JNDIPath or select credentials from a
Credential Manager list. If no authentication is required, then leave the fields blank.
Enter the polling interval time in minutes.
Click Test Credentials button, if you want to test the access to Apache HBase Server.
Choose the Monitor Group from the combo box with which you want to associate Apache HBase Monitor
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers Apache HBase from the network and starts monitoring.
Note:
In case you are unable to add the monitor even after enabling JMX, try providing the below argument:
-Djava.rmi.server.hostname=[YOUR_IP]
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on HBase under the Database Table.
Displayed is the HBase bulk configuration view distributed into three tabs:
Availability tab, gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the server details listed under the following tabs:
Overview
IPC
Master
Region Server Details
RegionServer
Region Details
Region Server Details
HLog
Configuration
Overview
Parameter Description
HBase MASTER OVERVIEW
Average Load The average number of regions served by each region server.
Dead Region Servers
The number of dead region servers.
Count
Region Servers Count The number of online region servers.
Cluster Requests / Min The total number of requests from all region servers to a cluster per minute.
HBase JVM METRICS
Total Heap Memory Calculates the total heap memory in MB.
Used Heap Memory Calculates the heap memory used in MB.
Committed Heap
Calculates the heap memory committed in MB.
Memory
Total Garbage
Total JVM garbage collection.
Collections
MEMORY DETAILS
Free Physical Memory
The amount of free physical memory in Megabytes.
Size
Free Swap Space Size Total amount of free swap space in Megabytes.
Total Physical Memory Total amount of physical memory in Megabytes.Size
Total Swap Space Size Total amount of swap space in Megabytes.
Committed Virtual The amount of virtual memory that is guaranteed to be available to the running process
Memory Size in Megabytes.
THREAD DETAILS
Timed Waiting Threads The number of threads that are waiting for another thread to perform an action for up to
Count a specified waiting time.
Waiting Threads Count The number of threads waiting for another thread to perform a particular action.
Blocked Threads Count The number of threads that are blocked waiting for a monitor lock.
Runnable Threads
The number of threads that are being executed in the JVM
Count
IPC
Parameter Description
IPC DETAILS
Number of Open Connections The number of open connections at the RPC layer.
Total Call Time The total call time, including both queued and processing time.
Number of Active RPC Handlers The number of RPC handlers actively servicing requests.
Number of Calls In Replication The number of currently enqueued operations received from replication.
DATA TRANSFERRED
Sent Data The number of bytes of sent data in the call queues.
Received Data The number of bytes of recieved data in the call queues.
EXCEPTIONS
Out of Order Scanner Exception
Unknown Scanner Exception
Region Too Busy Exception The region server is too busy exception.
Master - RegionServer
Parameter Description
REGIONS IN TRANSITION
Regions in Transition Counts the number of regions in transition.
Regions in Transition Counts the number of regions in transition that exceed the threshold as defined by the
over Threshold property rit.metrics.threshold.time.
REGION SERVERS
Name The name of the region server.
Start Time The HBase master start time.
Region Server - Region Details
Parameter Description
STORE FILES
Store File Count The number of store files in the RegionServer.
Store File Size The total size of the store files (data files) in the RegionServer.
MEMSTORE
Memstore Size The total Memstore memory size of the RegionServer.
COMPACTION DETAILS
Compactions Completed Count Total number of compactions completed since startup by the nodes.
Num Bytes Compacted Count The number of bytes compacted across all this entity''s hregions.
Num Files Compacted Count The number of files compacted across all this entity''s hregions.HLog COUNT
Delete Count The total number of Delete requests in the RegionServer.
Increment Count The total number of Increment requests in the RegionServer.
Append Count The total number of Append requests in the RegionServer.
Mutate Count The total number of Mutate requests in the RegionServer.
OPERATIONAL LATENCY - SCAN NEXT
Scan Next Num Operations The numer of Scan Next operations across all this entity''s hregions.
Scan Next Min The minimum latency for Scan operation in the RegionServer.
Scan Next Max The maximum latency for Scan operation in the RegionServer.
Scan Next Mean The mean latency for Scan operation in the RegionServer.
Scan Next Median The median latency for Scan operation in the RegionServer.
OPERATIONAL LATENCY - GET
Get Num Operations The total number of Get requests per second in the RegionServer.
Get Min The minimum latency for Get operation in the RegionServer.
Get Max The maximum latency for Get operation in the RegionServer.
Get Mean The mean latency for Get operation in the RegionServer.
Get Median The median latency for Get operation in the RegionServer.
Region Server Details
Parameter Description
CACHE DETAILS
Block Cache Count The number of Store Files cached in the block cache.
Block Cache Eviction Count The total number of blocks that have been evicted from the block cache.
Block Cache Free Size The number of bytes that are free in the block cache.
Block Cache Express Hit
The block cache hit percent for requests where caching was turned on.
Percent
Block Cache Hit Count The total number of block cache hits for requests, regardless of caching setting.
Block Cache Count Hit Percent The block cache hit percent for all requests regardless of the caching setting.
The total number of block cache misses for requests, regardless of caching
Block Cache Miss Count
setting.
Block Cache Size The number of bytes used by cached blocks.
SLOW OPERATIONS COUNT
Slow Append Count The number of appends that took more than 1000 ms to complete.
Slow Get Count The number of gets that took more than 1000 ms to complete.
Slow Put Count The number of puts that took more than 1000 ms to complete.
Slow Increment Count The number of increments that took more than 1000 ms to complete.
Slow Delete Count The number of deletes that took more than 1000 ms to complete.
HLog
Parameter Description
HLog FILES SPLIT TIME
HLog Split Time Mean The average time to split the total size of a write-ahead log file.
HLog Split Time Min The minimum time to split the total size of a write-ahead log file.
HLog Split Time Max The maximum time to split the write-ahead log file after a restart.
HLog Split Time Num Operations The time to split write-ahead log files.
HLog FILE SPLIT SIZE
HLog Split Size Mean The average time to split the total size of an HLog file.
HLog Split Size Min The minimum time to split the total size of an HLog file.HLog Split Size Max The maximum time to split the total size of an HLog file.
HLog Split Size Num Operations The size of write-ahead log files that were split.
Configuration
Parameter Description
CONFIGURATION
VM Name The Java virtual machine implementation name.
Boot Class Path The boot class path that is used by the bootstrap class loader to search for class files.
VM Vendor The Java virtual machine implementation vendor.
Spec Version The version of the JMX specification implemented by this product.
SAP MaxDB Monitoring (Add-On)
SAP MaxDB - An Overview
Monitoring SAP MaxDB - What we do
Adding a new SAP MaxDB Monitor
Monitored Parameters
SAP MaxDB - An Overview
The SAP MaxDB database (formerly SAP DB), developed and supported by SAP AG, is a compliant relational
enterprise database system available on Microsoft Windows, Linux and Unix, and other prominent hardware
platforms.
Monitoring SAP MaxDB - What we do
Applications Manager''s SAP Monitoring aims to help database admins with tuning their SAP MaxDB, ensuring the
availability and performance of production databases, and gathering operating system level data to understand
performance issues from your infrastructure and applications to your end-user experience.
System And Memory Details - Check which operational state the database is in, gather information about the
size and efficiency of the caches of the database. Track the number of accesses to caches and cache hit rates
Data and Log Area Stats - Regularly check data and log volume and confirm that there is sufficient free space
in the data and log areas and know if the maximum number of database sessions has been reached.
Data Cache and OMS Heap Usage - Analyze the Data Cache with Hit-rate metrics and OMS Heap
consumption
Lock Activity and Session Management - Get information about the maximum number of available database
locks (entries) so you can raise the value of maximum locks allowed when the set number approaches the
number of available locks. Monitor Schema Statistics like table sizes and growth. Identify the top tables in
MaxDB query.
Backups and Backup Template Metrics - Regularly check whether your backups are intact and have not
failed. Generate the backup history to display backups have been carried out and whether they were
successful. Monitor the log backup and the archiving for the backup files. Check regularly that automatic log
backup is activated.
Creating a new SAP MaxDB monitor
Prerequisites for setting up SAP MaxDB monitoring:
sapdbc.jar should be copied to Appmanager_Home\working\classes folder. By default, this jar will be
available under \runtime\jar\sapdbc.jar.
Note: X-Server in SAP MaxDB should be running when the user sets up the SAP MaxDB Monitor
Creating a new Monitor
To create a new SAP MaxDB monitor, follow the steps given below:
Click on New Monitor link.Select SAP MaxDB under the Database category.
In the add monitor window, enter the Host Name of MaxDB server.
Enter the Port as X-Server port (default port is 7210).
Enter your Database Username and Password.
Enter the Schema /Database Name.
Enter Timeout in minutes i.e the Session Timeout.
Click Add Monitor.
Monitored Parameters
Overview
Data Area
Log Area
Session
Cache Stats
OMS Heap
Schema and Tables
Resource Monitor
Locks
Backup
Overview
Parameter Description
SYSTEM DETAILS
The State of the Database. A database can be in one of the following operational
states.
ONLINE: The database is running and can be used by database system
Database State administrator, DBM operators and database users with the corresponding
authorizations.
ADMIN: The database is only available for administration tasks.
OFFLINE: The database is not running.
The database instance type:
Instance Type OLTP
LiveCache (You can only use liveCache technology with SAP applications)
DB Speed
The run directory of the MaxDB database where the database system saves
Running Directory
configuration and log files.
Kernel Version The database kernal version.
MEMORY OVERVIEW
The I/O buffer cache is the alloted working memory area used by the database
I/O Buffer Cache
system for I/O operations (data cache, converter and other caches).
Data Cache The alloted size of the data cache.
Converter The alloted size of the converter cache.
File/Directory Used Size The space currently used by the file directories in MB.
The size of the catalog cache that is available for the database user to maintain the
Catalog Cache
frequently accessed sections of the catalog.
The size of shared SQL caches. The shared SQL caches hold already executed SQL
Shared SQL Data
queries, thus memory is kept to a minimum.
The size of sequence cache. The sequence cache stores current values of database
Sequence Cache
sequences.
OMS Heap The size of the OMS heap portion of main memory.
Log Queue Cache The size of the log queues. The log queue contains the log entries of the current
transactions (redo log entries) and writes them to the log volumes using the logwriter.
Block Allocator The amount of memory currently used by block allocators in MB.
The free space in the I/O buffer cache in MB. Ideally, this value should be high. A
Unused Size
very low value of this measure indicates the need to reset the CACHE_SIZE.
IO Management The current size of the I/O management.
Index Creation The current rate at which indexes were being created.
DATA CACHE
Data Cache The alloted size of the data cache.
OMS Data The size of the OMS heap.
SQL Data The size of area occupied by SQL data.
The size of the used pin area. (Data that is to be kept for a longer time from being
Used Pin Area displaced from the data cache is held in a special area of the data cache, the pin
area.)
History/Undo
Changed Data
Data Area
Parameter Description
DATA AREA INFO
Total Data Area The total size of the data area in MB.
Used Data Area The memory in data area that is currently used for data.
Used Data Area The percentage of memory in data area that is currently used for data.
Free Data Area The data area that is currently available for data.
Free Data Area The percentage of data area that is currently available for data.
Permanent Data Size The data area that is currently used for permanent data.
Temporary Data Size The data area that is currently used for temporary data.
Permanent Converter Size The space in the I/O buffer cache that is permanently used by the converter.
Temporary Converter Size The space in the I/O buffer cache that is temporarily used by the converter.
Size of an incremental The size of an incremental backup. An incremental backup contains only data that is
backup new or has changed since the last backup, regardless of the type.
Shadow Data Size
DATA VOLUME
Volume Id The unique identifier of the Data Volume.
Total Volume Size (MB) The total size of the data volume, both used and free.
Used Volume Size (MB) The amount of data that has been written to the volume in the data area.
Used Volume Size (%) The percentage amount of data that has been written to the volume in the data area.
Path The Data Volume Path.
Log Area
Parameter Description
LOG AREA INFO
The logging status, i.e if logging is currently happening (The database system
writes the redo log entries of transactions in the log segments of the log area.)
Possible values are:
Logging Status
Yes= Logging is currently happening.
No= Logging is not happening.
Auto Overwrite Specifies whether overwrite mode is activated for the log area. Possible Values are:
YES= The Log area is overwritten cyclically, log backup is not possible;
NO= The log area is not in overwrite mode.Specifies if Log Writer is Enabled. The log writer writes the redo log entries from the
log queues to the log area. The log writer is a task in the user kernel thread. Possible
Values are:
Log Writer Status
YES= The Log Writer is not enabled.
NO= The Log Writer is enabled.
The state of the device. Possible Values are:
Device State Active
Passive
Specifies if the log area is full (no space left on the log volumes). Possible Values
are:
Is Log Area Full
YES - The log area is full.
NO - The log area is not full.
Flush Mode
Total Log Area The total area taken up by all the log volumes in a database instance.
Used Log Area The size of the log area currently utilized in MB.
Used Log Area The percentage size of the log area currently utilized.
LOG VOLUMES
Volume Id The unique identifier of the Log Volume.
Total Size (MB) The total size of the log volume, both used and free in MB.
Used Volume Size (MB) The amount of logs that has been written to the volume in the log area in MB.
Used Volume Size (%) The percentage amount of logs that have been written to the volume in the log area.
Path The Log Volume path.
Session
Parameter Description
SESSION
Max No.of Sessions The maximum number of sessions a user can open on the database.
Used Sessions The number of currently active database sessions.
Used Sessions Percentage The percentage of currently active database sessions.
Cache Stats
Parameter Description
CACHE HIT RATE
Cache Name The name of the cache.
The time data was retrieved from the database cache in the last measurement
Hit Rate
period.
CACHE STATISTICS
Name The name of the cache.
Access Count The number of times the cache was accessed.
Successful Access Count The number of times the cache was successfully accessed.
Unsuccessful Access
The number of times the cache access was unsuccessful.
Count
The percentage of time data was retrieved from the database cache in the last
Hit Rate (%)
measurement period.
OMS Heap
Parameter DescriptionOMS HEAP STATISTICS
Allocator Name The name of the memory allocating process.
Reserved Memory (KB) The total memory allocated by the process.
Used Heap (KB) The current memory usage.
Used Heap (%) The percentage of current memory usage.
Max Heap Usage (KB) The maximum value allowed for the size of the heap.
Schema and Tables
Parameter Description
SCHEMA DETAILS
Schema Name The name of the schema.
Tables Count The number of system tables in the Schema.
Schema Used Size (MB) The space used for tables and indexes that belong to the schema in MB.
TOP 10 LARGE TABLES
Schema Name The name of the schema.
Table Name The name of the table.
Table Used Size (KB) The amount of space used by the table in KB.
Row Count The number of rows in the table.
Resource Monitor
Parameter Description
TOP 10 FREQUENTLY CALLED QUERIES
Cmd ID The command ID.
SQL Query The SQL Query called.
Called Count The number of queries called.
Row Reads The number of full-row reads.
Virtual Reads The number of reads (page accesses).
Collision on SQL Locks The number of SQL lock requests that could not be satisfied.
Collision on internal Locks The number of internal lock requests that could not be satisfied.
I/O access The number of I/O accesses to disk (reading and writing).
Rows fetched The number of rows fetched.
Locks
Parameter Description
LOCKS USAGE
Maximum Locks The number of available locks in the lock list
Used Locks The number of used locks.
LOCK STATISTICS
The number of situations where at least two transactions collided with each other
DeadLocks due to held and requested locks in such a way that this collision can be resolved only
by implicitly ending a transaction.
SQL Lock Collisions The number of SQL lock requests that could not be satisfied (immediately).
OMS Lock Collisions The number of OMS lock requests that could not be satisfied (immediately).
Lock Escalations The number of lock escalations
Row Locks The number of row locks held.
Table Locks The number of table locks held.
SQL Request Timeout The number of SQL lock requests that could not be satisfied because they had
Locks exceeded the maximum wait time.OMS Request Timeout The number of OMS lock requests that could not be satisfied because they had
Locks exceeded the maximum wait time.
Backup
The number of pages read/written during the I/O operation
Parameter Description
LAST/CURRENT BACKUP DETAILS
Latest ThreadID The Id of the latest SAP MaxDB thread created inside the SAP MaxDB kernel process.
Latest Backup Thread The name of the latest SAP MaxDB thread created inside the SAP MaxDB kernel
Name process.
Specifies if Automatic Log Backup is enabled. If you have activated Automatic Log
Automatic Log Backup
Backup, the database system backs up the redo log entries automatically
Latest Backup IO Count The number of I/O operations.
Latest Backup IO Page
The number of pages read/written during the I/O operation.
Count
Latest Backup IO Time The total time of the I/O operations.
Latest Backup Pending IO
The number of pending I/O operations.
Count
Latest Backup Path The latest data backup path.
RECENT BACKUP TEMPLATE DETAILS
The name of the backup template. This has no influence on the name of the backup
Backup Template Name
created later using this backup template.
Backup ID The template ID.
The backup action that is scheduled in the template (for example, data backups, log
Backup Action backups, updates of SQL Optimizer statistics, and database structure checks).
These are then performed at the specified time.
Backup Start Time The start time of the backup.
Backup End Time The end time of the backup.
Backup Size (Pages) The size of full and incremental backups together.
Backup Result Result obtained in last template backup.
Backup Error Result obtained in last template backup, if any.
Sybase Replication Server Monitoring
Overview
Sybase Replication Server is a ‘data movement’ product, which moves data from one place to another. More
specifically, it captures database transactions in one database and then applies these to another database.
Creating a new Sybase Replication Server monitor
Supported Versions: Applications Manager supports monitoring of Sybase Replication Server v15.7 and above.
Using the REST API to add a new Sybase replication server monitor: Click here
To create a Sybase replication server monitor, follow the given steps:
Click on Add New Monitor link under New Monitor.
Select Sybase Replication.
Enter the display name of the monitor.
Enter the Host Name or IP Address of the host.
Enter the SubNetMask of the network.
Enter the port number in which sybase is running.
Enter the polling interval time in minutes.
Enter the credential details like user name and password for authentication along with the database name, or
select the required credentials from the Credential Manager list by enabling the Select from Credential list
option.
If you are adding a new monitor from an Admin Server, select a Managed Server.Choose the Monitor Group from the combo box with which you want to associate Sybase database server
Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers Sybase replication server from the network and starts monitoring them.
Monitored Parameters
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
Click on the following tabs listed to view the following information:
Overview
Threads
Connections
Configuration
Overview
Parameters Description
CONNECTION TIME
Connection Time Time taken to get connected to the Sybase replication server (in milliseconds).
MEMORY UTILIZATION
Current Memory
Amount of memory currently being used by replication server (in MB).
Usage
Max Memory Usage The maximum amount of memory allocated for use to the replication server (in MB).
Memory Usage Amount of memory used by the replication server (in percentage).
Disk Utilization
Partition Name & ID Name of the partition and its corresponding ID.
Partition Location Location of the partition on the disk.
Current state of the partition. Possible values are
ON-LINE – The device is normal
State OFF-LINE – The device cannot be found
DROPPED – The device has been dropped but has not disappeared (some queues
are using it)
Total Segments (MB) Total amount of segments available on the partition (in MB).
Used Segments
Amount of segments currently in use from the partition (in MB).
(MB)
Free Segments (MB) Remaining amount of segments available after use on the partition (in MB).
Disk Used (%) Amount of disk space utilized by the partition (in percentage).
Disk Free (%) Remaining amount of disk space available after use on the partition (in percentage).
Disk Usage Graphical representation of amount of disk utilized by the partition (in percentage).
Threads
Parameters Description
Thread Details
PID A unique process identifier for a thread running in the replication server.
Name Name of the thread running in the replication server.
Current status of the thread. Possible values are Active, Awaiting Command, Awaiting I/O,
State Awaiting Message, Awaiting Wakeup, Connecting, Down, Getting Lock, Inactive, Initializing, or
Suspended.
Info Displays information about threads running in the replication server.Connections
Parameters Description
Logical Connection Details
PID A unique process identifier for the connection running in the replication server.
Logical Connection
The logical data server and database names for the connection.
Name
Active Connection
The data server and the database names for the current active database connection.
Name
Active Connection Status of the active connection. Possible values are Active, Suspended, or Suspended by
State error.
Standby Connection
The data server and the database names for the current standby database connection.
Name
Standby Connection Status of the standby connection. Possible values are Active, Suspended, Suspended by
State error, or Waiting for marker.
Replication Server
Name of the replication server.
Name
The description of the operation in process. Possible values are None, Switch Active, or
Operation
Create Standby.
Operation State State of the operation in process.
Configuration
Parameters Description
Configuration Details
RSSD/ERSSD Dataserver Name of the RSSD/ERSSD dataserver.
Intallation Information Displays the installation information of the replication server.
Log File Displays the name and location of the log file.
NoSQL Database Servers
NoSQL databases defined as a non-relational, distributed database, are gaining recognition as an alternative
mode to the relational database management system among the organizations.
Inspite of the fact that NoSQL databases have a number of significant advantages, they share almost an equal set
of setbacks. However when used appropriately, NoSQL databases can offer real benefits. How will you ensure a
smooth and unruffled operation of these boundless unstructured data?
Applications Manager provides NoSQL database monitoring, helping you to keep track of how the database is
used and alerts you on any threshold breaches ensuring the performance of the database to the highest standards.
The Applications Manager functionality includes the ability to collect metrics like Bytes received / sent per minute
helping to monitor the network traffic, Transaction details, response time, number of open connections, items
cached, etc., from the NoSQL database and present them using our dashboard in a simple and impactful manner.
The different NoSQL database servers supported are:
CassandraDB Server
CouchBase Server
MongoDB Server
Redis Server
Memcached Database Server
Oracle NoSQL
Browse through the different database servers that provide server information and their parameters being
monitored.
Cassandra Database ServersCreating a new Cassandra DB monitor
Using the REST API to add a new Cassandra monitor: Click here
To create a Cassandra database server monitor, follow the steps given below:
Click on New Monitor link.
Select Cassandra.
Specify the Display Name of the Cassandra monitor
Enter the HostName or IP Address of the host where Cassandra server runs
Enter the JMX Port where the server is running. By default, it will be 7199 or else check in cassandra-env.sh file
for the JMX_PORT.
If you want to discover only this node, disable the option Discover all nodes in the Cluster. By default, it is
enabled which means all the nodes in the cluster are discovered by default
Check the Is Authentication Required field, to give the JMX credentials to be used to connect to the
Cassandra server. Now enter the UserName and Password of the credential
Specify the Polling Interval in minutes
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group with which you want to associate the Cassandra server to, from the combo box
(optional). You can choose multiple groups to associate your monitor
Click Add Monitor(s). This discovers the Cassandra server from the network and starts monitoring it
Note:
In case you are unable to add the monitor even after enabling JMX, try providing the below argument:
-Djava.rmi.server.hostname=[YOUR_IP]
Monitored Parameters
Applications Manager monitors attributes of your Windows Server Cluster components - nodes in a cluster, cluster
networks, resource groups and critical cluster events. You can also configure thresholds to the numerical attributes
monitored by the server based on these details.
Availability tab shows the Availability history of the Cassandra database for the past 24 hours or 30 days.
Performance tab shows the Health Status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
Click on the individual monitors listed to view the following information in the below tabs:
Monitor Information
Performance
Pending Tasks
Cluster Stats
Messages
Configurations
Monitor Information
This tab displays the basic information like the name of the server, host name and the JMX port where the server is
running. Additional parameters like Token, Gossip Active, Load, Generation No, Uptime, DataCenter, Rack Name
are also displayed. These are the equivalent of the Nodetool result got using the command ''nodetool.bat/sh -h -p
info''
Performance
Parameters Description
Availability and Performance History Displays the availability and performance history for the last six hours.
CPU Usage (available till version
Specifies the usage of CPU in percentage.
2.1.13)
Memory Utilization Specifies the used, free and total memory of the server in mega bytes
Exceptions (available till version Count of various exceptions such as not found, invalid, unavailable,
2.1.13) timed out, etc.Parameters Description
Storage Stats Specifies the storage load in GB.
Operation Stats (available till version Number of range, read and write operations per second since executor
2.1.13) start.
Operation Latency (available till The latency of range, read and write operations since the last time the
version 2.1.13) attribute was read.
Bloom Filter Statistics (available from Version 2.0.9 onwards)
Number of false positives (Occurs when the bloom filter says a non-
Bloom Filter False Positives
existential row exists)
Bloom Filter False Positive Ratio Fraction of all bloom filter checks resulting in a false positive
Bloom Filter Disk Space Used The size of the bloom filter files on disk
Memtable Statistics (available from Version 2.0.9 onwards)
Memtable Columns Count Total number of columns present in memtable
Memtable Data Size Amount of data stored in memtable, including column-related overhead
Memtable Switch Count Number of times flushing results in the memtable being switched out
Client Details
Connected Native Clients Number of Native Clients currently connected to the server instance
Connected Thrift Clients Number of Thrift Clients currently connected to the server instance
Average Operational Latency (available till version 2.1.13)
Average Range Latency The average latency per range operation since the last poll
Average Read Latency The average latency per read operation since the last poll
Average Write Latency The average latency per write operation since the last poll
Operational Timeouts (available till version 2.1.13)
Number of read, write and range slice operation timeouts since the last
Recent Timeouts
poll
Pending Tasks
Parameters Description
COMMITLOG/COMPACTION - PENDING TASKS (available till version 2.1.13)
Commitlog -
Number of Commitlog tasks waiting in the queue to be executed.
Pending Tasks
Compaction -
Number of Compaction tasks waiting in the queue to be executed.
Pending Tasks
COMMANDS/RESPONSES - PENDING TASKS (available till version 2.1.13)
Commands -
Number of Command tasks waiting in the queue to be executed.
Pending Tasks
Responses -
Number of Response tasks waiting in the queue to be executed.
Pending Tasks
Task Statistics of
Status of various stages of thread pools like active and pending tasks, completed and
Thread Pools
blocked tasks are being displayed. These are equivalent of the Nodetool result got using
(available till
the command ''nodetool.bat/sh -h -p tpstats''.
version 2.1.13)
Cluster Stats
Parameters Description
Cluster Details Specifies details on live, leaving, moving, joining and unreachable nodes.
Cluster Node Details Health status and storage load (in GB) of the nodes in the cluster.
Messages
This tab contains the Dropped Message and Message Timeout statistics:Parameter Description
Recent Total Timeouts Number of timeouts since last poll
Configurations
This tab contains the configuration values of files that are part of cassandra.yaml config file.
CouchBase Monitoring
Overview
CouchBase Server is an open-source, distributed NoSQL document-oriented database and key-value store that is
optimized for interactive applications. CouchBase is designed to provide easy-to-scale key-value or document
access with low latency and high sustained throughput. Applications Manager helps to actively monitor all aspects
of a CouchBase server like health, availability, response time etc., and helps take informed decisions in case of
downtimes.
Creating a new CouchBase server monitor
Using the REST API to add a new CouchBase monitor: Click here
To create a CouchBase server monitor, follow the steps given below:
Click on New Monitor link.
Select CouchBase from Database Servers.
Specify the Display Name of the CouchBase monitor.
Enter the HostName or IP Address of the host where CouchBase process runs.
Enter the Port where the server is running.By default, it will be 8091.
Specify the Polling Interval in minutes.
Choose the Monitor Group with which you want to associate the CouchBase server to, from the combo box
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the CouchBase server from the network and starts monitoring it.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on CouchBase under the Database table.
Displayed is the CouchBase bulk configuration view distributed into three tabs:
Availability tab, gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the database details listed under the following tabs:
Monitor Information
Performance Overview
Server Nodes
Data Buckets
Monitor Information:
This tab contains all general information regarding the monitor like Monitor name, port, hostname, username,
associated groups etc.
Performance Overview
Parameters Description
Total Memory (MB) Total memory available for the cluster.
Used Memory (MB) RAM usage of the cluster.
Free Memory (MB) Free memory available.Cluster Disk Utilization (GB) Total disk usage of the cluster.
Total Cluster Storage (GB) Total disk space available for the cluster.
Other Data (GB) Disk used by other data other than Couchbase.
Usable Free Space (GB) Maximum free space available for Couchbase server.
Server Nodes
Parameters Description
Server Node Name Server IP address where the Couchbase is running.
RAM Usage RAM usage of the server.
Swap Usage Swap usage of the server
CPU Usage CPU usage of the server.
Data Usage Data usage of this node.
Disk Usage Disk usage of this node.
Node Memory Utilization Memory Utilization of the alloted memory.
Active Items Active data is the data written in this node.
Replica Items Replica item is the copy of item from another node.
Node Disk Usage Individual node disk consumed by Couchbase.
Background Data Fetches Data not in cache and pulled from the disk.
Data Buckets
Parameters Description
Data Buckets
Bucket Name Name of the bucket.
Bucket Type Bucket type can be either Memcached or CouchBase.
Nodes Number of nodes available in the CouchBase server.
Item Count Number of objects stored in the bucket.
Used RAM Quota Memory used from the given quota (in MB).
RAM Quota Memory allocated for this bucket (in MB).
Quota Memory
Amount of memory utilized from the available quota (in %).
Utilization
Data Usage Data used by this bucket (in MB).
Disk Usage Disk used by this bucket (in MB).
Docs Indicates how much fragmented data is to be compacted compared to real data for the
Fragmentation data files in this bucket (in %).
Number of back-offs sent per second to client SDKs due to "out of memory" situations from
OOM/sec
this bucket.
Current
The number of connections per host.
Connections
Resident item ratio Ratio of items that are kept in memory versus stored on disk.
Total disk drain
Number of items actually written to disk from the disk queue.
rate
Memory Headroom This value indicates when you need to allocate more memory to a bucket.
Bucket Operation Details
Bucket Name Name of the bucket.
Ops/sec Number of operations per second for this data bucket.
Gets/sec Number of reads (GET operations) per second from this bucket.
Total Gets/sec Total number of GET operations per second from this bucket.
Sets/sec Number of writes (SET operations) per second to this bucket
Deletes/sec Number of delete operations per second for this bucketCAS Ops/sec Number of operations with a CAS ID per second for this bucket.
Ratio of the objects fetched from disk as opposed to memory (in %). Value should be as for
Cache Miss Ratio
be as close to 0 performance.
Bucket Disk Details
Bucket Name Name of the bucket.
Disk Creates/sec Number of new items created on disk per second for this bucket.
Disk Updates/sec Number of items updated on disk per second for this bucket.
Disk Reads/sec Number of reads per second from disk for this bucket.
Disk Fetches/sec Number of operations required to fetch the items from disk.
Disk Write Queue Number of items waiting to be written to disk in this bucket.
Disk Write Failures Number of disk write failures.
Disk Read Failures Number of disk read failures.
Disk Usage Disk used by this bucket (in MB).
MongoDB Database Monitoring
MongoDB - An Overview
Adding a new MongoDB monitor
Monitored Parameters
MongoDB - An Overview
MongoDB is a NoSQL database designed for ease of development and scalability to support massive data
processing and storage. With Applications Manager''s MongoDB monitoring capability, we''re letting users gain in-
depth visibility into critical metrics to optimize their data infrastructures. Users can collect statistical data like
Memory Utilizations statistics, open connections statistics, CPU usage, database operation performance and
latency, transaction details, response time, lock current queue and journaling statistics. Applications Manager
features graphs, custom dashboards and automated alerts to track performance and resource utilization of your
database systems from a centralized console.
Creating a new MongoDB monitor
Supported Versions MongoDB 4.2 and older versions. We support mongod services and mongos services
Prerequisites for monitoring MongoDB: Click here
Using the REST API to add a new MongoDB monitor: Click here
To create a Mongo database server monitor, follow the steps given below:
Click on New Monitor link.
Select Mongo.
Specify the Display Name of the Mongo monitor.
Enter the HostName or IP Address of the host where MongoDB/mongo process runs.
Enter the Port where the server is running.By default, it will be 27017.
To discover only this node and not all nodes in the ReplicaSet / Sharding disable the option Discover all nodes
in the ReplicaSet / Sharding. By default, it is enabled.
Check the Is Authentication Required field, to give the credentials to be used to connect to the MongoDB
server. Now enter the UserName and Password of the credential.
Specify the Polling Interval in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group with which you want to associate the MongoDB server to, from the combo box
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the MongoDB server from the network and starts monitoring it.
Monitored Parameters
MongoDB is monitored based on the parameters or the attributes listed below. These attributes provide
information about the functioning of the monitors of MongoDB. You can also configure thresholds to the numerical
attributes monitored by the server based on these details.Go to the Monitors Category View by clicking the Monitors tab. Click on MongoDB under the Database Table.
Displayed is the Mongodb bulk configuration view distributed into three tabs:
Availability tab, gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Following are the list of tabs that are shown in MongoDB monitor:
Monitor Snapshot
Server Stats
Replica Stats
Operation Details
Cache Details
Configuration
Monitor Snapshot
The Monitor Snapshot tab displays the availability and performance history for the past 6 hours. The business
view will help you have an integrated high-level view of the links between the different nodes in the replica set or
sharding server. However, this view will not be available for single servers that are not part of any replica set or
sharding server.
Server Stats
Parameters Description
Performance Status Specifies the used and free memory of the server in percentage.
Memory Utilization Specifies the used, free and total memory of the server in mega bytes.
Number of used and available connections in the database server. This will
Current Connections
help to asses the current load and capacity requirements of the server.
Specifies the amount of network traffic sent and received by the database, in
Network Traffic bytes per second. This value will help you ensure that network traffic sent to
and by the mongod process is consistent.
The total number of various database operations (insert, get, query, update,
Database Operations Counter command) per second since the mongod instance last started. This data helps
to analyze and track the load on the database.
The number of asserts (regular, warning, message, user, rollover) per
Assert Errors
second raised since the server process started.
Lock Statistics The time, in seconds, since the database last started.
Number of operations that are currently queued and waiting for the read-lock/
Lock Current Queue Details
write-lock.
Number of active client connections to the database, performing read/ write
Lock Active Client Details
operations.
Background Flushes Number of times the database has flushed all writes to disk per second.
Total number of seconds that the mongod processes have spent writing data
Background Flushes Statistics
to disk.
Number of transactions written to the journal during the last journal group
commit interval. A Journal is a sequential, binary transaction used to bring the
database into a consistent state in the event of a hard shutdown. MongoDB
Journaling Commits
performs group commits when journaling, i.e., a series of operations are
committed at once over many milliseconds. This is done to achieve high
performance.
Number of data in megabytes (MB) written to journal during the last journal
Journaling Data
group commit interval.
Number of seconds spent for each phase of journaling in the last journal group
Journaling Statistics
commit interval.
Note: All the metrics above in Server Stats will be displayed for a mongod device. Whereas for a mongos device,
only the first six metrics will be displayed.Following are the list of metrics that are monitored in this tab:
Cursors
Index Counters
Page Faults
Cursor Timeout
Memory Details
Latency Details
Global Lock Details
Database Lock Details
Database Statistics
Cursors
Parameters Description
The maximum number of open cursors a session can have at once. You can use
Number of open cursors this parameter to prevent a session from opening an excessive number of
cursors.
Number of timed-out cursors The number of timed out cursors since the last server restart.
Index Counters
Parameters Description
Index Accessed The number of indexes accessed by a MongoDB statement.
Indexes that reside in memory and when queried, will be served from memory
Index served from Memory
as long as the whole set fits in the memory.
Index served from Disk Indexes that don''t fit in the memory and must be served from disk.
The ratio of hits to misses. The misses is the total number of times that an
operation tried to access an index that was not in memory per collection. The
Miss Ratio
hits is the total number of times that indexes have been accessed and the
mongod was able to return the index from memory per collection.
Page Faults
Parameters Description
The total number of page faults that occured when MongoDB reads from or
Total Page Faults writes data to parts of its data files that are not currently located in physical
memory or when physical memory is exhausted .
MongoDB on Windows counts both hard and soft page faults. The MongoDB
Page Faults Counter page fault counter may increase dramatically in moments of poor
performance and may correlate with limited physical memory environments.
Cursor Timeout
Parameters Description
Cursor Timeout Timeout value set for the cursor (in ms).
Memory Details
Parameters Description
Memory Size Total memory size of the node (in bits).
Resident Memory Amount of resident memory currently used by the database process (in MiB).
Virtual Memory Amount of virtual memory currently used by the database process (in MiB).
Mapped Memory Amount of mapped memory currently used by the database process (in MiB).
Latency Details
Parameters Description
Output Latency Read Latency statistics for read requests (in hrs).Parameters Description
Output Latency Write Latency statistics for write requests (in hrs).
Global Lock Details
Parameters Description
Global Read Lock Number of read locks that are present globally.
Global Write Lock Number of write locks that are present globally.
Database Lock Details
Parameters Description
Database Read Lock Number of read locks that are present for the database.
Database Write Lock Number of write locks that are present for the database.
Database Statistics
Parameters Description
Database Name The name of the database whose statistics are being monitored.
The number of the Collections, i.e a group of MongoDB documents, in the
Collections
database.
Objects All the json data and performance objects in a collection.
Avgerage Object Size The average size of all the KEY:VALUE objects contained within the shard.
Data Size The size of data stored in a collection in MB.
Indexes The total number of indexes in the database.
Index Size The total size of all indexes on the database in KB.
File Size The size of the files that hold the database contents in MB.
Replica Stats
Parameters Description
Status information for MongoDB’s replica set configuration. Only when the
Replication Details
current host has replication enabled these values will be displayed.
Total number of various database replication operations (insert, update,
Replication Operations Counter delete, getmore, command) per second since the mongod instance last
started. These values will help to analyze the load on the replica.
Total number of various database sharding and notsharding operations
Sharding Operations Counter -
(insert, update, delete, getmore, command) per second since the mongos
Sharded/ NotSharded
instance last started.
Replication Buffer Count The current number of operations in the OpLog buffer.
REPLICA AND SHARD
Replica Count Number of replicas present in the database.
Shard Count Number of shards present in the database.
REPLICATION OPLOG DETAILS
Total OpLog size (in MB) configured by the customer or the default value
Configured oplog size
configured which is 50 MB.
Log length start to end The difference between the first and last operation in the OpLog (in seconds).
OpLog first event time Timestamp of the first record present in OpLog.
OpLog last event time Timestamp of the latest record present in OpLog.
Note: The Replica Stats tab displays only replication details for a mongod device and sharding details for a
mongos device.
Operation Details
Parameters DescriptionParameters Description
OPERATION SCAN AND ORDER
The total number of queries that return sorted numbers that cannot perform
Operation Scan
the sort operation using an index.
Write Conflicts The total number of queries that encountered write conflicts.
Cache Details
Parameters Description
CACHE SIZE
Cache Configured Size Maximum size configured for the cache (in GB).
Cache Current Size Size of the data currently present in cache (in GB).
DIRTY CACHE
Dirty Cache Size Size of the dirty data in the cache (in GB).
Dirty Cache Pages Number of dirty pages into the cache (in GB).
CACHE PAGES DETAILS
Cache Pages Read Number of pages read into the cache.
Cache Pages Write Number of pages write into the cache.
UnModified Evicted Pages Main statistics for page eviction.
Threads Cache Pages A document that returns statistics on yields during page acquisitions.
CACHE READ AND WRITE DETAILS
Cache Read Size Amount of cache read (in GB).
Cache Write Size Amount of cache write (in GB).
Configuration
Parameters Description
CONFIGURATION DETAILS
HostName Host name on which the database is running.
Version Version of the Mongodb database.
Running Process Number of processes that are running.
Process ID The process ID number.
Redis Server Monitoring
Creating a new Redis monitor
Supported Versions: Redis 2.4 and above
Using the REST API to add a new Redis monitor: Click here
To create a Redis database server monitor, follow the steps given below:
Click on New Monitor link.
Select Redis.
Specify the Display Name of the Redis monitor
Enter the HostName or IP Address of the host where Redis server runs.
Enter the Port where the server is running.By default, it will be 6379. Or else you can also check it in the
redis.conf file.
To discover only this node and not all nodes in the cluster disable the option Discover all nodes in the cluster.
By default, it is enabled.
Check the Is Authentication Required field, to give the credentials to be used to connect to the Redis server.
Now enter the Password of the credential.
Specify the Polling Interval in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group with which you want to associate the Redis server to, from the combo box
(optional). You can choose multiple groups to associate your monitor.Click Add Monitor(s). This discovers the Redis server from the network and starts monitoring it.
If you have added Monitors and not associated them with a Monitor Group, you can do this manually anytime. For
information on associating a Monitor with a Monitor Group, refer to Associating Monitor with Monitor Groups topic.
Monitored Parameters
Redis database server is monitored based on the parameters or the attributes listed below. These attributes
provide information about the functioning of Redis database. You can also configure thresholds for the attributes
monitored by the server based on these details.
Availability tab shows the availability history of the Redis database for the past 24 hours or 30 days.
Performance tab shows the Health Status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
Click on the individual monitors listed to view the following information:
Monitor Information
Persistence
Replication
Monitor Information
This tab displays the basic information like the name of the server, host name and the port where the server is
running. Additional parameters like ProcessID, RunID, uptime and associated groups are also displayed.
Performance
Parameters Description
Availability and
Displays the availability and performance history for the last six hours.
Performance History
System CPU Usage Amount of CPU used by system initiated processes (in percentage).
User CPU Usage Amount of CPU used by user initiated processes (in percentage).
Memory Utilization
Amount of memory utilized by the Redis server (in percentage).
Percentage
System CPU
Amount of CPU used by system initiated processes (in milliseconds/minute).
Usage/Min
User CPU Usage/Min Amount of CPU used by user initiated processes (in milliseconds/minute).
The CPU consumed by the background processes (like SORT, SUNION, BGSAVE,
Children CPU Usage
BGREWRITEAOF).
Memory Utilization Specifies the used, free and total memory of the server in mega bytes.
Memory The ratio between the number of bytes that Redis allocated as seen by the operating
Fragmentation Ratio system and the total number of bytes allocated by Redis using its allocator.
Connected/ Blocked
Number of client connections and number of clients pending on a blocking call.
Clients
Rejected Connections Number of connections rejected because of maxclients limit.
Connections Stats Number of connections accepted by the server per second.
Operations Stats Number of commands processed per second.
Keyspace Stats Specifies the number of successful and failed lookup of keys in the main dictionary.
Keyspace Hit
Percentage of the number of successful and failed lookup of keys in the main dictionary.
Percentage
Expired/ Evicted Key Displays the total number of key expiration events and the number of evicted keys due to
Stats max memory limits.
Publish Subscribe
The global number of pub/sub channels with client subscriptions.
Stats
PersistenceParameters Description
Displays the details about RDB and AOF persistence states like the status of the last RDB
Persistence Stats
save operation, status of the AOF rewrite operation, etc.
Displays the details about the database, like the db name, total number of keys and
Database Stats
number of expired keys.
Replication
Parameters Description
Displays if the replication role is master or slave. In case of slave, master node details
Replication Details
like master host, master port and status of the link, etc., are displayed.
Specifies the number of slaves connected. This graph will be populated in case of
Slave Connections
master node alone.
Memcached Servers
Creating a new Memcached monitor
Supported Versions: Memcached v1.2 and above.
To create a Memcached database server monitor, follow the steps given below:
Click on New Monitor link.
Select Memcached under Cloud Computing/Virtualization category.
Specify the Display Name of the memcached server
Enter the HostName or IP Address of the host where Memcached server runs.
Enter the Port where the server is running.
If you want to enable Transaction test, select ''Yes'' radio button, otherwse select ''No'' button.
Set the Polling Interval.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group with which you want to associate the Memcached server to, from the combo box
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the Memcached server from the network and starts monitoring it.
Monitored Parameters
Memcached Servers are monitored based on the parameters or the attributes listed below. These attributes
provide information about the functioning of the monitors of Memcached server. You can also configure thresholds
to the numerical attributes monitored by the server based on these details.
Availability tab shows the Availability history of the Memcached server for the past 24 hours or 30 days.
Performance tab shows the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the individual monitors listed to view the following information:
Parameters Description
Monitor Details
Availability Shows the current status of the Memcached server - available or not available
Performance Status
Used Memory Specifies the used memory of the server in percentage
Free Memory Specifies the free memory of the server in percentage
Hit Ratio Refers to the hit ratio in percentage
Memory Utilization
Used Memory Specifies the used memory of the server in mega bytes
Free Memory Specifies the free memory of the server in mega bytes
Total Memory Specifies the total memory of the server in mega bytes
CPU Utilization
User CPU* Specifies the accumulated user time for a process in secondsSystem CPU* Specifies the accumulated system time for a process in seconds
Cached Hits and Misses
Hits/min Number of keys that have been requested and found present per minute
Misses/min Number of items that have been requested and not found per minute
GET and SET Requests
Gets/min Number of retrieval requests per minute
Sets/min Number of storage requests per minute
Cached Items
Items cached Current number of items stored by server
Evictions Number of valid items removed from cache to free memory for new items
Network Traffic
Bytes Received Number of bytes read by this server from network per min
Bytes Sent Number of bytes sent by this server to network per min
Current Connections
Connections Number of open connections
Response Time
The time taken by Applications Manager to execute the STATS command on the memcached
Response Time
server
Version Version of Memcached server
Transaction
SET-Time The time taken by Applications Manager to set the content on the memcached server
GET-Time The time taken by Applications Manager to fetch the content from the memcached server
DELETE-Time The time taken by Applications Manager to delete the content from the memcached server
Total Transaction The total time taken to connect to memcached server, set content, fetch content and delete
Time content from the server
* - not supported in Memcached installed in Windows
Oracle NoSQL Database Server Monitoring
Overview
Applications Manager provides out-of-the-box performance metrics and helps you visualize the health and
availability of an Oracle NoSQL server farm. Database administrators can login to the web client and visualize the
status and Oracle NoSQL performance metrics.
Creating a new Oracle NoSQL monitor
Using the REST API to add a new Oracle NoSQL monitor: Click here
Follow the given steps to create a Oracle NoSQL server monitor:
Click on New Monitor link.
Select Oracle NoSQL.
Enter the Display Name of the monitor
Enter the IP Address or hostname of the host.
Enter the JMX Port in which the JMX is running.
Enter the Additional JMX Port in which the JMX is already running in any of the other machine of the same
cluster.
Choose the Credential Details either use below credentials or select from credential list
Enter the Username and Password of the Oracle NoSQL.
Enter JNDI Path ex. /jmxrmi
Enter the polling interval time in minutes.
Choose the Monitor Group from the combo box with which you want to associate Oracle database server
Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers Oracle database server from the network and starts monitoring them.
Note:Ensure that you enable JMX for Oracle NoSQL monitoring. To create a new Oracle NoSQL monitor, you
should have admin privileges.
In case you are unable to add the monitor even after enabling JMX, try providing the below argument:
-Djava.rmi.server.hostname=[YOUR_IP]
Setting up JMX for Oracle NoSQL monitoring
Oracle NoSQL Database allows Java Management Extensions (JMX) or Simple Network Management Protocol
(SNMP) agents to be optionally available for monitoring, in addition to the native monitoring provided by the Admin
CLI and the Admin Console. These agents provide interfaces on each storage node that allow management clients
to poll them for information about the status, performance metrics, and operational parameters of the storage
node and its managed services, including replication nodes and admin instances. Both these management agents
can also be configured to push notifications about changes in the status of any of the services, and for violations of
preset performance limits. The JMX interface can be enabled in either the Community Edition or the Enterprise
Edition. To use SNMP, however, you must have the Enterprise Edition. The JMX service exposes MBeans for the three
types of components. These MBeans are the java interfaces StorageNodeMBean, RepNodeMBean, and
AdminMBean in the package oracle.kv.impl.mgmt.jmx. For more information about the status reported for each
component, see the javadoc for these interfaces.
The same information that is reported via JMX can also be reported through SNMP. In this case, the information is
organized according to the Management Information Base (MIB) named OracleNosqlMIB, which is included with
the Enterprise Edition, in the file lib/nosql.mib.
Simple Network Management Protocol (SNMP) and Java
Management Extensions (JMX)
Both the SNMP and JMX agents in NoSQL Database are read-only interfaces and allow you to poll the storage
nodes for information about the storage node and about any replication nodes or admins that are hosted on the
storage node. The available information includes service status (such as, RUNNING, STOPPED etc.), operational
parameters, and performance metrics. SNMP and JMX traps/notifications are also delivered for particular events.
Notifications are sent for every service status state change; and for violations of performance limits.
Enabling Monitoring
Monitoring can be enabled on a per-storage node basis in two different ways:
In the Bootfile
You can specify that you want to enable JMX or SNMP in the storage node''s boot configuration file. Usually, these
files are created by using the makebootconfig utility, which has the following options to control these features:
[-mgmt {snmp|jmx|none} -pollport ]
-traphost ]
-trapport ]
Note: When you specify -mgmt snmp, you must also specify -pollport. The SNMP agent listens for connections
from SNMP management clients on this port. You may also optionally specify -traphost and -trapport to
indicate the destination address for notifications. This would be the hostname and port number of an SNMP
management service that is configured to receive notifications at that address.
Note: When you specify -mgmt jmx, you do not have to specify -pollport. A storage node''s JMX agent uses the
RMI registry at the same port number as is used for all other RMI services managed by the storage node. (This
port number is specified as the -port argument to makebootconfig.)
By Changing Storage Node Parameters
You can still enable JMX or SNMP after a store is deployed, by changing the storage node parameters
"mgmtClass", "mgmtPollPort", "mgmtTrapHost", and "mgmtTrapPort". Similar to configuring via makebootconfig,
the "mgmtPollPort", "mgmtClass", "mgmtTrapHost", and "mgmtTrapPort" are used only for SNMP; and the
parameter "mgmtPollPort" must be set when enabling SNMP.
The value of the "mgmtClass" parameter may be one of the following class names:
To enable JMX:
oracle.kv.impl.mgmt.jmx.JmxAgentTo enable SNMP:
oracle.kv.impl.mgmt.snmp.SnmpAgent
To enable neither JMX nor SNMP:
oracle.kv.impl.mgmt.NoOpAgent
For example, you could issue the following command in the Admin CLI to enable SNMP on a storage node:
plan change-parameters -service sn1 -wait -params \
mgmtClass=oracle.kv.impl.mgmt.snmp.SnmpAgent \
mgmtPollPort=5002 mgmtTrapHost=192.168.26.42
mgmtTrapPort=32767
Note: Only a single implementation of the management agent may be enabled at a particular time. If you
enable SNMP on a storage node where JMX is already enabled; the JMX agent shuts down, and the SNMP agent
takes its place.
Displaying the NoSQL DB MBeans
To view the NoSQL Database JMX Mbeans in a monitoring tool such as JConsole, connect using the hostname and
registry port for each Storage Node that you would like to view. This is the port that is named by the "-port"
argument to the java -jar kvstore.jar makebootconfig command. It is also used in the deploy-sn plan during
configuration. The documentation examples use 5000 as the registry port.
For example, you would specify localhost:5000 to the JConsole Remote Process connection box in the New
Connection tab.
Monitored Parameters
Note:
To create a new Oracle NoSQL monitor, you should have admin privileges.
Jconsole can also be used to access the Mbeans
Oracle NoSQL Monitoring Metrics:
Admin Attributes
Storage Attributes
Replicated Node Table Attribute
Admin Attributes
Attribute Name Description
Admin ID Number of an Admin instance.
HttpPort The port number used by the Admin Console web application.
LogFileCount Number of log files that are kept.
LogFileLimit The maximum size of log files.
Master Whether this Admin is the master among Admin instances.
PollPeriodMillis The polling period for collecting metrics.
ServiceStatus The reported service status of the Admin.
Storage Attributes
Attribute Name Description
The number of Replication Nodes that can be hosted on this
Capacity
Storage Node.
AdminHttpPort The http port used by the Admin Console web application.
The name of the network interface used for communication
HostName
between Replication Nodes
The range of port numbers available for assigning to Replication
HAPortRange
Nodes that are hosted on this Storage Node.HostingAdmin True if this Storage Node hosts an Admin instance
The amount of memory known to be available on this Storage Node,
MemoryMB
in megabytes.
A list of file system mount points on which Replication Nodes can
MountPoints
be deployed
NumCPUs The number of CPUs known to be available on this Storage Node.
RegistryPort The port number of the Storage Node''s RMI registry.
RootDirPath The pathname of the store''s root directory
SnId The StorageNodeId number of this Storage Node.
The configured name of the store to which this Storage Node
StoreName
belongs.
Replicated Node Table Attribute
Attribute Name Description
CacheSize The size of the BDB-JE cache, in MBytes.
If true, then the underlying BDB-JE subsystem will dump statistics
CollectEnvStats
into a local .stat file.
Average commit lag(in milliseconds) for a given replication node''s
CommitLag
update operations during a given time interval.
RepNodeId The RepNodeId, in its String form
Average commit lag (in milliseconds) for a given replication node
during a given time interval exceeds the value returned by this
CommitLagThreshold
method, a notification event will be sent to any parties that have
registered interest.
CumulativeEnd The timestamp at the end of a cumulative measurement period.
CumulativeLatAvg The average latency for single operations since service startup.
The highest latency measured for single operations since service
CumulativeLatMax
startup.
The timestamp at the beginning of a cumulative measurement
CumulativeStart
period
CumulativeThroughput Single operations per second since service startup.
CumulativeTotalOps The total number of single operations since service startup.
HeapMB The size of the Java heap for this Replication Node, in MB.
IntervalLatAvg Average Latency of Operations in the given Interval
ERP Monitoring
Below are the list of ERP monitoring tools that are monitored in Applications Manager:
Oracle EBS
SAP CCMS
SAP Server
SAP Business One
Siebel
Microsoft Dynamics CRM / 365 (On-Premise)
Microsoft Dynamics AX
Browse through the different ERP servers that provide server information and their parameters being monitored.
Oracle E-Business Suite MonitoringOracle EBS - An Overview
Creating a new Oracle EBS monitor
Monitored Parameters
Oracle EBS - An Overview
Oracle E-Business Suite (Oracle EBS) monitor allows you to monitor the availability and performance of Oracle EBS
from a centralized web console. Data of Oracle E-Business Suite are collected using DMS stands for Dynamic
Monitoring Service (a web application which get data from the fusion middleware components). Data that is
created and updated by DMS-enabled applications and components is accessible through the DMS Spy Servlet.
Only users having administrator rights can access this servlet.
Creating a new Oracle EBS monitor
Oracle EBS Versions Supported: R11i, R12.0, R12.1.3, R12.2.0, R12.2.5 & above.
Prerequisites for monitoring Oracle EBS: Applications Manager uses the Dynamic Monitoring Service (DMS)
provided by Oracle Application Server to monitor the same. For this reason, the DMS Servlet has to be made
accessible to the system where the Applications Manager is running. Refer Prerequisites Section.
Using the REST API to add a new Oracle EBS monitor: Click here
Follow the steps given below to create a new Oracle EBS monitor in Applications Manager:
Go to New Monitor. Click on Oracle EBS.
Enter Display Name.
Provide Host Name & Port.
Select the EBS Server Version - R11i, R12.0, R12.1.3, R12.2.0, 12.2.5 & above.
If you select Version R12.2.0/R12.1.3/R12.2.5 & above, a username and password details are mandatory. You
can enter your own credential details or select preconfigured credentials details in Credentials Manager. If you
wish to enter your own credentials, specify username and password details for this monitor.
For version R12.1.3, you will have to specify whether SSL is enabled, the instance name(service name) and
concurrent request filter. Concurrent request filter can be selected from the drop down list which holds values
such as pending, running and inactive.
Choose SSL Enabled checkbox if SSL authentication is enabled on the server connection channel.
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box to which you want to associate the Monitor (optional). You can
choose multiple groups to associate your monitor.
Click Add Monitor(s). Upon adding the Oracle EBS monitor, you can view the details of the newly added
Oracle monitor.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Oracle EBS under the ERP Table.
Displayed is the Oracle EBS bulk configuration view distributed into three tabs:
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the server details listed under the following tabs:
For Oracle E-Business Suite R11i:
Performance Overview
For Oracle E-Business Suite R12.0:
Performance Overview
Process Information
Applications
For Oracle E-Business Suite R12.2.0, R12.2.5 & above:
Performance OverviewProcess Information
Clusters
Servers
Applications
Forms
Oracle Process Manager and Notification Server
Web Cache
For Oracle E-Business Suite R12.1.3:
Performance Overview
Applications
Forms details
Workflow Manager
Concurrent Manager
For Oracle E-Business Suite R11.0
Performance Overview
Parameter Description
Name The name of Oracle EBS monitor.
Health The health (Clear, Warning, Critical) of the server
Type The type you are monitoring.
Last Polled at The time at which the last poll was performed.
Next Poll at The time at which the next poll is scheduled.
Availability The current status of the server - available or not available.
Connection Statistics
Connections per Minute Number of times an HTTP connection was established.
Active Connections Number of connections that are active.
Requests Statistics
Active Requests Number of requests that are active
Completed Requests per min Number of HTTP request completed per minute
Response Time
Average Response Time Average Response time of the request
Minimum Response Time Minimum Response time for the request
Maximum Response Time Maximum Response time for the request
Process Stats
Process Name Name of the process like BDMSProcess
Heap Size Heap memory size of the process
For Oracle E-Business Suite R12.0
Performance Overview
Parameter Description
Active Requests Number of child servers currently in the request processing phase.
Completed Requests per min Number of HTTP request completed per minute
Average Response Time Average time required to service an HTTP request
Min Response Time Minimum time required to service an HTTP request
Max Response Time Maximum time required to service an HTTP request
Active Connections Number of connections currently openConnections per Minute Number of times an HTTP connection was established.
Virtual Host Processes
Virtual Host Name Specifies Virtual host name.
Active Requests Total time spent processing requests for this virtual host.
Completed Requests Per Minute Number of requests processed completely per minute.
Average Response Time Average time spent processing requests for this virtual host.
Applications
Parameter Description
Applications Requests
The echo of the value specified as the path for OC4J Mount directive in
Applications
mod_oc4j.conf.
Success Requests per Specifies the number of requests per minute, both session and non-session together,
Minute that mod_oc4j successfully routed to an OC4J instance.
The number of requests per minute, both session and non-session, that mod_oc4j
Error Requests per Minute
failed to route to an OC4J.
Sessions Success Specifies the number of session requests per minute that mod_oc4j successfully
Requests per Minute routed to an OC4J instance.
Sessions Error Requests
The number of session requests per minute that mod_oc4j failed to route to an OC4J.
per Minute
Non-Sessions Success Specifies the number of non-session requests per minute that mod_oc4j successfully
Requests per Minute routed to an OC4J instance.
Non-Sessions Error The number of non-session requests per minute that mod_oc4j failed to route to an
Requests per Minute OC4J.
Process Information
Parameter Description
Process Details
Process ID The process ID for the process.
Process Name The process name.
Heap Size The heap size of the process in MB.
For Oracle E-Business Suite R12.2.0, R12.2.5 & above
Performance Overview
Parameter Description
Server Name The name of the Server.
Process Name of the process. For eg, opmn:/EBS_web_VIS_OHS.
Min Response Time (ms) Minimum time required to service an HTTP request.
Max Response Time (ms) Maximum time required to service an HTTP request.
Average Response Time (ms) Average time required to service an HTTP request.
Active Requests Child servers currently in the request processing phase.
Completed Requests per minute Number of HTTP request completed per minute.
Active Connections Number of connections currently open
Connections per Minute Number of times an HTTP connection was established.
Virtual Hosts Process Stats
Virtual Host Name Host name of the virtual host.
Server Name The name of the Server.
Active Requests Number of requests currently being processed by this host.Average Response Time Average time spent processing requests for this virtual host
Completed Requests Per Minute Number of requests processed completely per minute
Process Information
Parameter Description
Process Details
Process Name of the process. For eg, opmn:/EBS_web_VIS_OHS.
Host Name The name of the host where the process is running.
Server name The name of the Server.
Heap Size The heap size of the process.
Clusters
Parameter Description
Cluster Statistics
Cluster
Specifies Cluster Name
Name
Number of managed servers in running state. Servers in the following states are taken as running
servers:
RUNNING
STARTING
Running ADMIN
Servers
STANDBY
RESUMING
SUSPENDING
FORCE_SUSPENDING
Number of managed servers in shutdown state. Servers in the following states are taken as
Shutdown servers:
Shutdown
Servers SHUTTING_DOWN
SHUTDOWN
Failed
Number of managed servers in failed state
Servers
Server Status
Server
Specifies Server Name
Name
Server Specifies state of the server. Possible States are:
State
Starting - During the STARTING state, a WebLogic Server instance transitions from SHUTDOWN
to STANDBY, as a result of a Start, Start in Admin, or Start in Standby command.
Resuming - The WebLogic Server performs the operations required to move itself from the
STANDBY or ADMIN state to the RUNNING state.
Running -The WebLogic Server is fully functional, offers its services to clients, and can operate
as a full member of a cluster.
Admin - In the ADMIN state, WebLogic Server is up and running, but available only for
administration operations, allowing you to perform server and application-level administration
tasks.
StandBy - The WebLogic Server instance transitions from SHUTDOWN to STANDBY. A server
instance in STANDBY does not process any request—its regular Listen Port is closed.
Suspending - The WebLogic Server performs the operations required to place itself in the
ADMIN state, suspending a subset of WebLogic Server subsystems and services, and
completing a predefined portion of the application work currently in process
Force_Suspending - The WebLogic Server performs the operations required to place itself in the
ADMIN state, suspending a subset of WebLogic Server subsystems and services in an orderedfashion. During the FORCE_SUSPENDING state, WebLogic Server does not complete in-flight
work; application work in progress is abandoned.
Shutdown - The WebLogic Server instance is configured but inactive. The WebLogic Server
completes the suspension of subsystems and services and does not accept application or
administration requests.
Shutting_Down - The WebLogic Server is in the process of shutting down.
Failed - A running server instance can fail as a result of out-of-memory exceptions or stuck
application threads, or if one or more critical services become dysfunctional.
Cluster
Name of the cluster
Name
Servers
Parameter Description
Threads in JVM
Server Name The name of the Server.
Active Threads The number of active threads.
Daemon Threads The number of daemon threads.
Deadlock Threads The number of threads which are deadlock.
Self-Tuning Thread Pool
Server Name The name of the Server.
Hogged Threads The number of threads that are being held by a request right now.
Idle Threads The number of idle threads in the pool.
Pending Requests The number of pending user requests in the priority queue.
StandBy Threads The number of threads in the standby pool.
Active Threads The total number of threads in the pool.
Server Login Rate
Server Name Specifies the server where metrics come
Success Logins Percentage of successful logins
Failed Logins Percentage of failed logins
Blocked Logins Percentage of blocked logins
Forms Resource Usage
Server Name The name of the Server.
Instance Name The name of the FMW instance home.
CPU Usage The Percentage of CPU space used.
Memory Usage Percentage of Total Memory Used.
Private Memory Usage The total private memory used by the run-time process in MB.
Resource Usage of Forms JVM
Server Name Specifies server name from where metrics come
CPU Usage by JVM Percentage of CPU used by form''s JVM processes
Memory Usage by JVM Memory used by form''s JVM processes in MB.
Applications
Parameter Description
Applications Status
Server Name The name of the Server.
Applications The name of the cluster application
Cluster Name The name of the cluster in which the application is deployed
Status The current status of the applicationForms
Parameter Description
Form Application Details
Server Name The name of the Server.
Form Applications The name of the Forms Application.
Instance Name The name of the FMW instance home.
Process The process where metrics come.
Number of Sessions The total number of sessions in the application.
Status The status of the application.
Oracle Process Manager and Notification Server
Parameter Description
OPMN Components Resource Usage
Server Name The name of the Server.
Component Name The name of the component in server.
Memory Usage The percentage of memory space used by component.
CPU Usage The percentage of CPU used by the component.
Web Cache
Parameter Description
WebCache Performance
Server Name The name of the Server.
Process Name The processes where metrics are monitored.
The average amount of time for client requests forwarded by Oracle Web Cache to
Average Latency
be resolved.
Processed Requests Per The number of client requests forwarded by Oracle Web Cache processed by origin
Minute server
The number of client requests forwarded by Oracle Web Cache that resulted in an
Failed Requests Per Minute
error.
WebCache Requests Filter
Site Name The name of the website
Server Name The processes where metrics are monitored.
Instance Name The name of the instance
Cache Size The size of the objects currently stored in the cache
Hit Rate The percentage of requests resolved by cache content
Denied Request Per Minute The number of requests denied by request filters.
Served Request Per Minute The number of requests that Oracle Web Cache has served.
For Oracle E-Business Suite R12.1.3
Performance Overview
Parameter Description
Session Details
Active Sessions Number of Active Sessions
Inactive Sessions Number of Inactive Sessions
Session Usage Sessions Usage in %
Concurrent Request Count Details
Pending Concurrent Request Number of Concurrent Requests which are pendingRunning Concurrent Request Number of Concurrent Requests which are running
Inactive Concurrent Request Number of Concurrent Requests which are inactive
Notification Mailer Count Details
Pending Notification Mailer Request Number of Notification Mailer Requests which are pending
Running Notification Mailer Request Number of Notification Mailer Requests which are running
Inactive Notification Mailer Request Number of Notification Mailer Requests which are inactive
Database Details(Average)
Name Name of the Database attribute
Value Data value
Unsuccessful Login Unsuccesful login attempt details
Applications
Parameter Description
Application Details
Application ID Application ID
Application Name Name of the application
Application Code Application code
Basepath Basepath
Product Code Product Code
Created By ID of the user who created the application
Creation Time Time at which the application was created
Last Updated By ID of the user who modified the application recently
Last Update Time Time at which the application was modified recently
Forms Details
Parameter Description
Forms Details
Form Id Form ID
Form Name Name of the form
User Form Name Name of the form which is displayed to the users
Last Updated Time Time at which the Form was modified recently
Description Details about the form
Workflow Manager
Parameter Description
Workflow Manager
Component Name Name of component
Component Type Type of component
Component Status Status of the component
StartUp Mode Mode of start up
Last Update Time Time at which it was updated recently
Creation Time Time at which it was created
Concurrent Manager
Parameter Description
Concurrent Manager
Concurrent Manager Name Name of the Concurrent ManagerConcurrent Queue Name Name of the Concurrent Queue
Actual Processes Number of actual processes running
Target Processes Number of target processes which are supposed to run
Minimum Process Minimum number of processes which are supposed to run
Cache Size Size of the cache
Sleep Seconds No of seconds it can rest
Manager Type Type of manager
Running Status Status of the Manager- shows whether it''s running or not
SAP CCMS Monitors
Creating a new SAP CCMS monitor
Prerequisites for monitoring SAP CCMS Monitors: SAP JavaConnector (JCo) should be present in Applications
Manager''s classpath. Learn More
Using the REST API to add a new SAP CCMS monitor: Click here
Follow the steps given below to add a SAP CCMS monitor in Applications Manager:
Click on New Monitor. Click on SAP CCMS monitor.
Enter Display Name.
Provide Host Name / IP Address.
Check the Connect using Router String checkbox to enter the SAP Router String through which SAP Server is
connected.
Enter the SAP Logon client.
Enter the SAP System number.
Enter the SAP Logon language like EN for English.
Enter the polling interval time in minutes.
Enter the credential details like user name and password for authentication, or select the required credentials
from the Credential Manager list by enabling the Select from Credential list option.
Select CCMS Monitor Sets by clicking on Click Here link. It then displays a list of CCMS monitor sets present
in SAP server. Select a CCMS monitor set from the list which you would like to monitor.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box to which you want to associate the Monitor (optional). You can
choose multiple groups to associate your monitor.
Click Add Monitor(s). Upon adding the SAP CCMS monitor, you can view the details of the newly added SAP
CCMS monitor.
Monitored Parameters
Note: While creating a SAP monitor, you need a SAP user profile with the following authorization objects:
S_RFC, S_XMI_LOG and S_XMI_PROD which are minimum prerequisities for adding a SAP monitor.
Applications Manager''s SAP Monitoring allows you to monitor the availability and connection time of SAP CCMS
monitors from a centralized web console.
Availability tab gives the availability history for the past 24 hours or 30 days.
Performance tab gives the health status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
The Connection time refers to the time taken by Applications Manager to connect to SAP server. You can also add
performance / status / log attributes in the same page by clicking on link ''Add Attributes'' or by clicking on ''Add
Custom Attributes'' under Quick Links section.
The following parameters are monitored for SAP CCMS:
Parameter Description
Monitor Information
Health Specifies the health of the monitor based on its dependencies
Type Type of the Monitor
Host Name Specifies the host in which SAP is runningHost OS The Operating System of the host
Last Polled at The time at which last polling happened
Next Polled at The time at which the next polling is scheduled
Availability The current status of the SAP CCMS Monitor - whether it is up or down.
Adding SAP CCMS Attributes
To add a SAP CCMS monitor set''s attributes, follow the steps given below:
Click on Add Attributes or Add Custom Attributes link in SAP CCMS monitor page.
In the Add Attributes screen, you will find the entire set of CCMS monitoring tree elements (MTE) listed below.
Click on MTE which you would like to monitor, and this will expand the entire set of attributes available inside
the monitor set.
Similarly, you can also select various MTE and its attributes inside available CCMS monitors.
If there are no attributes present inside MTE, an error message appears: "There are no Performance / Status /
Log Attributes present in this Node"
Click on Add Attributes button to complete the process.
If you would like to delete exisiting attributes, click on Add Custom Attributes link. In SAP Custom Attributes
screen, Applications Manager will list the exisiting attributes that are being monitored and provides you the
option to delete attributes. You can also enable / disable reports for the attributes in the same screen.
SAP Server Monitoring
Overview
SAP Monitoring allows you to monitor the availability and performance of SAP environment from a centralized web
console. SAP monitor takes advantage of the SAP CCMS (Computer Center Management System) architecture to
give insightful information about the SAP system along with fault management and reporting capabilities.
Creating an SAP Server Monitor
Prerequisites for monitoring SAP Server: SAP JavaConnector (JCo) should be present in Applications Manager''s
classpath. Learn more
Using the REST API to add a new SAP server monitor: Click here
Follow the steps given below to create an SAP server monitor in Applications Manager:
Click on New Monitor. Click on SAP Server.
Provide Host Name/IP Address.
Enter the SubNetMask of the network.
Check the Connect using Router String checkbox to enter the SAP Router String through which SAP Server is
connected (optional).
Enter the SAP Logon client.
Enter the SAP System number.
Enter the SAP Logon language like EN for English.
Enter the polling interval time in minutes.
Enter the credential details like user name and password for authentication, or select the required credentials
from the Credential Manager list by enabling the Select from Credential list option.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box to which you want to associate the Monitor (optional). You can
choose multiple groups to associate your monitor.
Click Add Monitor(s). Upon adding the SAP monitor, you can view the details of the newly added SAP monitor.
Note: While creating an SAP monitor, you need an SAP user profile with the following authorization objects:
S_RFC, S_XMI_LOG and S_XMI_PROD which are minimum prerequisites for adding an SAP monitor.
Monitored Parameters
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
The following parameters are monitored for SAP:Overview
Buffer
OS
Processes
Background
Dialog
Enqueue
Spool
Update
Alarms
Background Jobs
RFC
Overview
Parameter Description
Monitor Information
Health Specifies the health of the monitor based on its dependencies
Type Type of the Monitor
Host Name Specifies the host in which SAP is running
Host OS The Operating System of the host
Last Polled at The time at which last polling happened
Next Polled at The time at which the next polling is scheduled
Availability The current status of the SAP Monitor - whether it is up or down.
System Information
CPU Utilization Amount of CPU utilized by the SAP server (in percentage).
Memory Utilization Amount of memory utilized by the SAP server (in percentage).
Disk Utilization Amount of disk utilized by the SAP server (in percentage).
Spool Utilization Amount of spool work processes utilized by the SAP server (in percentage).
Amount of background work processes utilized by the SAP server (in
Background Utilization
percentage).
Buffer
Parameter Description
Percentage of the database queries that were met from the buffer (hit rate)
Hit Ratio and did not have to be passed on to the database for different buffer types like
Program, Repository, Table & GUI
Percentage usage of the directory (number of entries) for different buffer
Directory Used
types like Program, Repository, Table & GUI
Percentage usage of the buffer storage for different buffer types like Program,
Space Used
Repository, Table & GUI
Swaps due to a full buffer per minute for different buffer types like Program,
Swap
Repository, Table & GUI
Operating System
Parameter Description
CPU Utilization Average usage of the CPU in a host system
Disk Utilization Average usage of the disk in a host system
Extended Memory Utilization of the extended memory as a percentage.
Private Memory Utilization of the private memory as a percentage.Roll Area Usage Usage of the roll area as a percentage
Average number of page-ins per second; a page-in occurs if a process must
Page In
access a data page that is not available in the main memory
Average number of page-outs per second (page-out occurs if a page is stored
Page Out out of the main memory to make room for the pages required by other
processes)
Number of messages per minute that appeared in the system log of an
Syslog Frequency
application server.
Processes
Parameter Description
Work Processes Overview
Total Work Processes Number of total work processes.
Running Work Processes Number of running work processes.
Waiting Work Processes Number of waiting work processes.
Stopped Work Processes Number of stopped work processes.
SAP Work Process Information
Server Name Name of the server.
The internal ID number of a process. Used to identify messages that belong to
No
a work process in the system log.
The type of work process. Possible values are:
DIA - Work process for executing dialog steps in user transactions
UPD - Update process for making V1 (time-critical) database changes
UP2 - Update process for executing V2 (not time-critical) database
Type
changes
ENQ - For locking or releasing SAP lock objects
BTC - For processing background jobs
SPO - For spool formatting processes
PID Process ID of the work process (on the operating system).
Current status of the work process. Possible statuses are:
Running - Process is executing a request
Waiting - Process is idle and waiting for a request.
Hold- Process is held for one user. A work process can only serve a single
user.
Status If too many processes are on Hold, then system performance suffers.
You can then use the Reason field to identify holds that perhaps can
be released.
Stopped - Process is aborted. (Start set to No)
Shutdown - Process terminated because of a shutdown.
Reserved - Process is reserved.
Reason Reason displayed if a work process is in Hold status.
Indicates whether the process should be automatically restarted if a process
Start
ends prematurely.
Indicates how many times a work process has aborted since the instance was
Error
started.
Indicates the number of the semaphore for which a work process is waiting.
Sem
Normally, this field should be empty.
CPU Cumulative CPU time used by a work process since it was started.
Indicates the elapsed time used by a work process for the dialog step that it is
Time
currently being processed.
Report ABAP program or report that is currently being executed.User User whose request is currently being processed
Action that is being performed by the program that is running. The actions that
Action
are displayed are those that are recorded by the SAP performance monitor.
Table Name of the table that is being accessed by the database.
Background
Parameter Description
Background Processing
Background Utilization Percentage of the background processing capacity currently utilized.
Number of jobs that are ready to be executed, have start authorization and
have no target server specified for which there are no free background work
System Wide Queue Length
processes, averaged over all application servers with background work
processes.
System Wide Free Processes Number of free background work processes
Number of released jobs that are explicitly to be executed on this application
Server Specific Queue Length
server, but for which there are no free background work processes
Background work processes
Number of background work processes on an application server
count
Number of errors in background work processes since the monitoring segment
Error count
was created (that is, since the application server was started)
Error frequency Number of errors in background work processes per minute
Terminated on error count Number of background work processes terminated after an error
Number of jobs that are ready to be executed, have start authorization and
Running Background Work have no target server specified for which there are no free background work
Processes processes, averaged over all application servers with background work
processes.
Waiting Background Work
Number of free background work processes
Processes
Stopped Background Work Number of released jobs that are explicitly to be executed on this application
Processes server, but for which there are no free background work processes
Dialog
Parameter Description
Average time that a user waits at the front end for the processing of his or her
Frontend Response Time
request
Database Request Time Average time for processing logical database requests
Load And Generation Time Average load and generation time of CUA objects
Response Time Average response time of the dialog service
Time used in the network during the first data transfer from the front end to the
Network Time application server and during the last data transfer from the application server
to the front end.
Users Logged In Number of users logged on
Queue Time Average time in the dispatcher wait queue
Total Dialog Work Processes Number of total dialog work processes.
Running Dialog Work Processes Number of running dialog work processes.
Waiting Dialog Work Processes Number of waiting dialog work processes.
Stopped Dialog Work Processes Number of stopped dialog work processes.
Enqueue
Parameter Description
Enqueue Requests Number of lock requestsEnqueue Request Rejects Number of rejected lock requests
Enqueue Requests Errors Number of errors that occurred during lock requests
Dequeue Requests Number of release requests
Dequeue Requests Errors Number of errors that occurred when releasing locks
Dequeue All Requests Number of releases of all locks of an LUW
CleanUp Requests Number of releases of all locks of an application server
Backup Requests Number of update calls for which locks were forwarded to the update.
Reporting Requests Number of operations for reading the lock table.
Owner Names Actual Utilization Current number of lock owners in the lock table
Granule Arguments Actual
Current number of different lock arguments in the lock table
Utilization
Granule Entries Actual
Current number of elementary locks in the lock table
Utilization
Update Queue Actual Current number of open update requests with locks
Time spent in the critical path of the lock table for lock operations (in seconds
Recent Lock Time (per minute)
per minute)
Recent Lock Wait Time (per Wait time of parallel processes before entering the critical path of the lock
minute) table (in seconds per minute)
Recent Server Time (per minute) Total time spent in the enqueue server (in seconds per minute)
Enqueue operations (logical data locks) per minutes that are coming from
Enqueue Frequency
another instance to the central instance
Total Enqueue Work Processes Number of total enqueue work processes.
Running Enqueue Work
Number of running enqueue work processes.
Processes
Waiting Enqueue Work
Number of waiting enqueue work processes.
Processes
Stopped Enqueue Work
Number of stopped enqueue work processes.
Processes
Spool
Parameter Description
Spool Utilization Utilization of the spool work processes as a percentage
Spool Work Processes Count Number of spool work processes
Spool Work Processes Errors Number of errors in spool work processes
Spool Work Processes
Number of spool work processes that terminated after errors
Terminated
Dispatcher Queue Utilization Used area of the dispatcher queue as a percentage
Request Queue Utilization Used area of the spool request queue as a percentage
Used area of the spool request queue for processing in chronological order as
Service Queue Priv
a percentage
Service Queue Pages Number of pages in the spool request queue
Device Cache Used Used area of the entire device cache as a percentage
Device Cache Fixed Used area of the fixed device cache as a percentage
Host Spool List Used Used area of the host spool request list as a percentage
Shows all the alerts under System Errors tree node of SAP CCMS monitor [RZ
20].
Alerts
When you set an alert to completed status, it is deleted from the active alerts
that are shown in the Alert Monitor and the Alert Browser.
Running Spool Work Processes Number of running spool work processes.
Waiting Spool Work Processes Number of waiting spool work processes.
UpdateParameter Description
Total Update Work Processes Number of total update work processes.
Running Update Work Processes Number of running update work processes.
Waiting Update Work Processes Number of waiting update work processes.
Stopped Update Work
Number of stopped update work processes.
Processes
Alarms
Parameter Description
Date The date at which the alerts were generated.
Time The time at which the alerts were generated.
System System ID of the SAP instance.
Context Name of the monitoring context to which the MTE belongs.
Object Name Name of an ABAP Dictionary Object.
Module Name Short name of the MTE.
Severity Severity of the alarm.
Alarm Message Displays the detailed information for the alert shown.
In addition, you can also perform the following operations with respect to the alarms in SAP server monitor:
Complete Alarms: The Alert Monitor generates an alert for every status that deviates from the norm and traces
it until you set the status to complete. Clicking on the Complete Alarms button will clear the displayed alarms
from the SAP Server by completing the alarms.
Filter Alarms: Allows you to filter the alerts generated in SAP server by monitoring only the selected set of
filters in Alarms tab. Clicking the Filter Alarms button opens up a new popup window, wherein the following
details will be displayed in their respective dropdowns:
The Object Name dropdown displays the list of object names of the Monitor Tree Elements (MTEs).
The Module Name dropdown displays the list of module names based on the object name selected from
the dropdown in the form of Module Name(Object Name).
Select the respective Object and Module Names based on which the alarms need to be filtered. Upon
clicking Save, the alarms will be filtered and monitored in the Alarms tab.
Background Jobs
Parameter Description
Job Name The name of the background job monitored.
The current status of the background job. Possible Statuses are:
No Released Job Exists,
Current Status Scheduled,
Released,
Active.
The status of the background job during last execution.
Possible Statuses are:
Last Run Status Finished,
Terminated,
- (No Status If it is executed for first time)
Last Run Date & Time The date & time of the last executed background job.
The runtime in seconds ( the difference between starttime and endtime) of the
Runtime (Sec)
last executed background job.
Delay(Sec) The delay in seconds ( the difference between scheduled starttime and
starttime) of the last executed background job.Age Time since last execution of the background job in minutes.
Note: Click the icon to view the logs of a terminated background job and it''s history.
SAP RFC Monitoring
Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls
a function to be executed in a remote system. Applications Manager monitors metrics pertaining to Queued RFCs
(qRFC) and Transactional RFC (tRFC) like:
QOUT Scheduler (SMQS) - The QOUT Scheduler processes qRFC outbound queues and controls the sending
of qRFC calls. This information can be used to monitor the QOUT Scheduler.
QIN Scheduler (SMQR) - The QIN Scheduler processes qRFC inbound queues and controls the processing of
inbound qRFC calls.This information can be used to monitor the QIN Scheduler.
QOUT Data (SMQ1) - QOUT Data can be used to monitor the Individual qRFC Outbound queues.
QIN Data (SMQ2) - QOUT Data can be used to monitor individual qRFC inbound queues.
Transactional RFC (SM58) - Every transactional RFC that is executed in a monitored SAP Server is listed here.
Parameter Description
QOUT Scheduler (SMQS)
Client The Logon Client.
The status of the Scheduler at the moment when SMQS is executed. Possible
State states are: SYSFAIL, CPICERR, INACTIVE, WAITING, WAITCONN, STARTING,
ACTIVE.
Time The time of last update.
Group The group to which this scheduler belongs.
Host The host in which this scheduler is running.
QIN Scheduler (SMQR)
Client The Logon Client.
The status of the Scheduler. Possible states are: SYSFAIL, CPICERR, INACTIVE,
State
RESOURCE LACK, WAITING, BATCH , ACTIVE,STARTING.
Time The time of last update.
Group The group to which this scheduler belongs.
Host The host in which this scheduler is running.
QOUT Data (SMQ1)
Client The Logon Client.
Queue Name The name of the queue.
Destination The target destination of the queue.
The current state of the queue. Possible states are: SYSFAIL, CPICERR, STOP,
SYSLOAD, VBERROR, READY, RUNNING, NOSEND, NOSENDS, WAITING,
State
WAITSTOP, WAITUPDA, RETRY, ARETRY, ANORETRY, MODIFY, EXECUTED,
AFINISH, FINISH.
Message The message while executing the queue.
Time The time of last update.
QIN Data (SMQ2)
Client The logon Client.
Queue Name The name of the queue.
The current state of the queue. Possible States are:SYSFAIL, CPICERR, STOP,
State READY, RUNNING, WAITING, WAITSTOP, RETRY, ARETRY, ANORETRY, MODIFY,
EXECUTED, NOEXEC, AFINISH, FINISH, SAVED.
Message The message while executing the queue.
Time The time of last update.
Transactional RFC (SM58)
Transactional ID The identifier of the Transaction.Functional Name The name of the function that executed for transaction.
Destination The target destination where this function is executed.
Caller The user who called this transaction.
The state of the transaction. Possible States are : CPICERR, SYSFAIL, CONFAIL,
State RECORDED, VBERROR, SYSLOAD, RETRY, ARETRY, ANORETRY, EXECUTED,
MAILED, READ, VBRECORD, SENDED, DEBUG, VXRECORD
Message The message while executing the transaction.
Time The time of last update.
Tcode The Tcode from where this transaction is called.
Note:
Data Retention: For Transactional RFC, only 2 hours of RAW data will be retained. After two hours the collected
RAW data available in Applications Manager database will be deleted. This is because of the HUGE volume of
transaction data available in SAP system. Applications Manager database will not scale the huge volume of
transaction data.
Data Archiving: Data archiving of transaction data will not happen due to the following reasons.
The RAW data is deleted after two hours.
Archiving huge volume of transaction data is not a scalable option.
The alert history will be available but no reporting is possible for Transactional RFC.
SAP Business One Monitoring
Overview
SAP Business One ERP is designed for small and mid-sized business. It provides solution for accounting and
financials, purchasing, inventory, sales, customer relationships, project management, operations, and human
resources. SAP Business One is based on a two-tier client/server architecture. Most of the application resides on
the client (fat client). This means that processing is carried out locally and is largely independent of server
performance.
Creating a new SAP Business One monitor
Prerequisites for monitoring SAP Business One metrics: Integration Framework should be launched for SAP
Business One.
Using the REST API to add a new SAP Business One monitor: Click here
Follow the steps given below to create a new SAP Business One monitor in Applications Manager:
Click on Add New Monitor under New Monitor.
Select SAP Business One under ERP category.
Enter the display name for the monitor to be added.
Provide Host Name/IP Address.
Enter the port number in which the integration framework is running. (Default port is 8080)
Enter the credential details like user name and password of the integration framework for authentication, or
select the required credentials from the Credential Manager list by enabling the Select from Credential list
option.
Enter the timeout value in minutes.
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box to which you want to associate the monitor (optional). You can
choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers SAP Business One integration framework from the network and starts
monitoring them.
Monitored Parameters
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.The following parameters are monitored for SAP Business One monitor:
Overview
SLD
BizStore
Scenario
Users
Transaction
Errors & Conflicts
Overview
Parameter Description
SYSTEM INFORMATION (B1iP)
Database Size Database size allocated for the integration platform (in GB).
Used Memory Amount of memory utilized by the integration platform (in MB).
Used Memory Percentage Amount of memory utilized by the integration platform (in percentage).
Maximum Memory Maximum amount of memory available for the integration platform (in MB).
Detected CPU Cores Number of CPU Cores or Processors detected.
Scheduler Threads Number of scheduler threads available in the integration platform.
Last Start of B1iP Date and time at which the integration platform was last started.
Last crashed time Date and time at which the integration platform was last crashed.
Deployed B1i Apps Number of B1i apps that are deployed in the integration platform.
QUEUES
DB Queues Number of available database queues.
DBQ Streams Number of available database queue streams.
DBQ Messages Number of available database queue messages.
Blocked Queues Number of queues that are blocked.
SLD
Parameter Description
System Landscape Directory (SLD) Details
SLD System ID System ID of the SLD.
SLD Name Name of the SLD.
Adapter Adapter name of the SLD.
System Type System type of the SLD.
Status Connectivity status of the SLD.
In addition, you can also choose to filter systems based on specific adapters. Using the Choose Adapters option,
systems under System Landscape Directory (SLD) can be filtered based on the selected adapters. Updated
systems for the selected adapters will be available in the next poll data.
BizStore
Parameter Description
BIZSTORE
BizStore Datasets Number of BizStore datasets available.
BizStore Groups Number of BizStore groups available.
BizStore Documents Number of BizStore documents available.
DOCUMENT CACHE
Doc Cache Accesses Number of accesses given to BizStore document cache.Doc Cache Hit Rate Hit rate of BizStore document cache (in percentage).
Scenario
Parameter Description
SCENARIO DETAILS
Scenario Transactions Number of scenario transactions available.
Total Scenario Packages Total number of scenario packages available.
INTERNAL PROCESS STEPS
Stopped steps due to errors Number of stopped internal process (IPO) steps due to errors.
Stopped steps due to recovery Number of stopped internal process (IPO) steps due to recovery.
Manually stopped steps Number of manually stopped internal process (IPO) steps.
Stopped steps due to
Number of stopped internal process (IPO) steps due to deployment.
deployment
Users
Parameter Description
User Details
User Name Name of the user.
The roles assigned to the user. (Administrator, Developer, Configurator or
Roles
Supervisor)
Status Current status of the user. (Active or Locked)
DaysToExpire Number of days remaining for the user entry to expire.
Transaction
Parameter Description
TRANSACTION STATUS
Completed Transactions Number of successfully completed transactions.
In Commit Transactions Number of transactions with in-commit status.
Cancelled Transactions Number of cancelled transactions.
In Rollback Transactions Number of transactions with rollback status.
Aggregated Transaction Data (Last 1 day)
Status Status of the transaction.
Duration Time duration of the aggregated transaction (in ms).
No. of processed messages Number of processed messages for the aggregated transaction.
Size of inbound messages Size of inbound messages for the aggregated transaction (in KB).
Errors & Conflicts
Parameter Description
ERRORS
Error Inbox: Receiver System
Number of receiver systems with error messages.
with Error
Error Inbox: Technical Errors Number of technical error messages in error inbox.
CONFLICTS
Activation Conflicts Number of activation conflicts occurred.
Namespace Conflicts Number of namespace conflicts occurred.
APP ERRORS & WARNINGS
App Init Errors Number of errors occurred during last app initialization.App Init Warnings Number of warnings occurred during last app initialization.
Siebel Server Monitoring
Overview
Applications Manager lets you monitor the status of Siebel server components that are essential to keeping the
application up and running. You can monitor as far down as the process level CPU and memory utilization of a
Siebel task. Auto-discover your entire Siebel Enterprise; get out-of-the-box performance graphs showing
Application Object Manager and Enterprise Application Integration Stats of processes within your enterprise.
Creating a new Siebel monitor
Using the REST API to add a new Siebel server monitor: Click here
Follow the steps given below to create a new Siebel Enterprise Server monitor in Applications Manager:
Copy the APMSiebelCommands.txt file (located under /working/resource
directory) and paste it under /bin directory.
Click on Add New Monitor under New Monitor in the Applications Manager web client.
Click on Siebel Enterprise Server under ERP.
Enter the Display Name of the monitor.
Provide the Host Name or IP Address of the server where Siebel is installed.
Select the Mode of Monitoring (SSH or WMI).
If SSH, provide the port number (default is 22), username and password information of the Siebel server.
You have an option to configure Public Key Authentication (Username and Private Key). You can also give
a Passphrase if the private key is protected with one. Also, you can specify the command prompt value,
which is the last character in your command prompt. Default value is $ and possible values are >, #, etc.
If WMI, provide the username and password of the Siebel server.
Enter the credential details like user name and password for authentication, or select the required credentials
from the Credential Manager list by enabling the Select from Credential list option.
Enter the Siebel Gateway Server and Enterprise Server names.
Enter the Siebel administrator name (administrator or equivalent user) and Password.
Enter the path to the Siebel Installation Directory.
Specify the Timeout in minutes. Default value is 10 minutes.
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box to which you want to associate the Monitor (optional). You can
choose multiple groups to associate your monitor.
Click Add Monitor(s). Upon adding the Siebel Server monitor, you can view the details of the newly added
Siebel Server monitor.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Siebel server under the ERP Table.
Displayed is the Siebel Server bulk configuration view distributed into three tabs:
Availability tab, gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the server details listed under the following tabs:
Monitor Information
Performance
Components
AOM Statistics
DB Statistics
InfraStructure
EAI Statistics
Task
Active SessionsMonitor Information
Parameters Description
Name Name of the Siebel server monitor
Last Polled at Specifies the time at which the last poll was performed.
Next Poll at Specifies the time at which the next poll will be performed.
Associated Groups Denotes the monitor groups associated with the Siebel server monitor.
Performance
Parameters Description
Availability history for last 6
Name of the Siebel server monitor
hours
Performance history for last 6
Specifies the time at which the last poll was performed.
hours
CPU Utilization Displays the current CPU utilization of the server.
Memory Utilization Displays the current memory utilization of the server.
Statistic Name Siebel application statistic name.
Statistic Value Siebel application statistic value.
Description Description of the statistic.
Transactions from PIM in
Number of inprocess transactions from PIM
Progress
Global Data Cursor Cache
Number of global data cursor cache misses
Misses
Tests Successful Number of tests that were successful
Global Data Cursor Cache
Number of objects currently in the global data cursor cache
Objects
Transactions form Siebel in
Number of inprocess transactions from Siebel
Progress
Maximum OOB Component
Maximum OOB Component Time
Time
Total CPU time spent on creating global data cursor objects in cache (in
Global Data Cursor Cache CPU
seconds)
Failed Transactions from Siebel Number of failed transactions from Siebel
Global Data Cursor Cache
Total memory spent on creating global data cursor objects in cache (in bytes)
Memory
Global Data Cursor Cache Hits Number of global data cursor cache hits
Events Processed Total number of events processed
Data Cursor Cache Objects Number of objects currently in the data cursor cache
Failed Transactions from PIM Number of failed transactions from the PIM
Events Processed Rate Rate of Processing the events
Data Cursor Cache Memory Total memory spent on creating data cursor objects in cache (in bytes)
Number of Component Crashes The number of times a process of the component has crashed.
Data Cursor Cache Misses Number of SQL data cursor cache misses
Number of Component Restarts The number of times a process of the component has restarted.
Number of Errors Total number of level 0 and 1 errors.
This statistics represents the cumulative number of records assigned by this
Number of object rows assigned
component since the server was started
PSP Cache Hit Total Total PSP Cache Hit Number
PSP Cache Miss Total Total PSP Cache Miss Number
SQL Object Cache Memory Total memory spent on creating SQL object objects in cache (in bytes)
Data Cursor Cache CPU Total CPU time spent on creating data cursor objects in cache (in seconds)Completed Transactions from Number of completed transactions from Siebel
Siebel
Completed Transactions from
Number of completed transactions from the PIM Server
PIM
Average OOB Queue Size Average OOB Queue Size
SearchEvents Processed Rate Rate of Processing the records during indexing
Average OOB Component Time Average OOB Component Time
SearchEvents Processed Total number of records processed during indexing
Tests Failed Number of tests that failed
Tests Attempted Number of tests that were started
Data Cursor Cache Hits Number of SQL data cursor cache hits
Components
Parameters Description
Component Specifies the name of the Siebel component.
Component Group Specifies the name assigned to the Siebel component group.
Specifies the value returned for the state of the component. An example value
RunState
of RunState is offline
ActiveMTSProcess The number of running multi-threaded shell (MTS) processes.
RunningTasks The current number of running tasks for the component.
AOM Statistics
Application Object Manager Statistics
Parameters Description
The time required to perform all the activities required to establish an
Average Connect Time interactive session (such as authentication, initialization, and allocating the
necessary resources) with Object Manager.
The average (mean) time required to respond to an end-user action. If
Average Response Time
application performance is deteriorating, the metric value increases.
Statistic Name Siebel application statistic name.
Statistic Value Siebel application statistic value.
Description Description of the statistic.
Average Request Size The average size of request messages (in bytes)
Average Reply Size The average size of reply messages (in bytes)
Average Requests Per Session The average number of requests per Object Manager session
Total Think Time The total end-user think time (in seconds)
Average Think Time The average end-user think time between requests (in seconds)
Object Manager Errors The number of errors encountered during Object Manager session
Reply Messages The number of reply messages sent by the server
Request Messages The number of request message received by the server
Total Database Response Time The total Database Response/Processing Time (milliseconds)
Total Reply Size The total size (in bytes) of reply messages
Total Request Size The total size (in bytes) of request messages
Total Response Time The total Object Manager response time (msec)
Database Statistics
Parameters Description
Average Execution The average (mean) amount of time the database requires to process the SQL statement
Time after the statement is parsed.Average Fetch The average (mean) amount of time the database requires to fetch records by an SQL
Time statement after the statement is parsed.
Statistic Name Siebel application statistic name.
Statistic Value Siebel application statistic value.
Description Description of the statistic.
SQL Cursor Cache
The number of SQL cursor cache misses
Misses
SQL Cursor Total
The total CPU time spent on creating SQL cursor objects in cache (in seconds)
Cpu
SQL Parse Time The total elapsed time for SQL parse operations (in seconds)
Number of SQL
The total number of SQL fetch operations
Fetches
SQL Object Cache
The number of objects currently in the SQL object cache
Objects
Number of SQL
The total number of SQL execute operations
Executes
SQL Object Cache
The number of SQL object cache misses
Misses
SQL Cursor Cache
The number of SQL cursor cache hits
Hits
Number of SQL
The total number of SQL parse operations
Parses
SQL Object Cache
The number of SQL object cache hits
Hits
SQL Object Cache
The total CPU time spent on creating SQL object objects in cache (in seconds)
CPU
SQL Fetch Time The total elapsed time for SQL fetch operations (in seconds)
Avg SQL Parse
The average time for SQL parse operations (in seconds)
Time
SQL Execute Time The total elapsed time for SQL execute operations (in seconds)
InfraStructure
Parameters Description
Statistic Name Siebel application statistic name.
Statistic Value Siebel application statistic value.
Description Description of the statistic.
Tasks Exceeding Configured Capacity The number of tasks stated that exceeded configured capacity
CPU Time The total CPU time for component tasks (in seconds)
Num of DLRbk Retries The number of Retries due to Deadlock Rollbacks
Num of Exhausted Retries The number of Times All Retries are Exhausted
Elapsed Time The total running time elapsed for component tasks (in seconds)
Number of Sleeps The total number of sleeps for component tasks
FDR Avg time between aging Avg Seconds per buffer wrap
Sleep Time The total amount of sleep time for component tasks (in seconds)
FDR Buffer Life in seconds Seconds since buffer was created
Num of DBConn Retries The number of retries due to DB Connection Loss
Minimum Peak Memory Usage Peak Mem used by task. Rolls up differently than MaxPeakMemory
Maximum Peak Memory Usage The Peak Memory used by task. Rolls up differently from MinPeakMemory
Total Tasks The total number of tasks completed for server components
FDR Buffer Wraps The number of buffer wraps
EAI StatisticsParameters Description
Statistic Name Siebel application statistic name.
Statistic Value Siebel application statistic value.
Description Description of the statistic.
EAI Receiver Total Messages The total number of messages processed by the Enterprise Application
Processed Integration receiver.
Siebel Adapter Total Query
The total cumulative size of output property sets (in KB) for all queries
Calls
Siebel Adapter Total The total number of non-query (synchronize, upsert, update or insert) calls made
Sync/Upsert Calls to Siebel Adapter
Total XML Converter Size of
The total cumulative size of input buffer (in KB)
Input Buffer
Siebel Adapter Total Query
The total cumulative size of output property sets (in KB) for all queries
Size
Siebel Adapter Total Sync The total cumulative size of input property sets (in KB) for all non-query calls
Size (synchronize, upsert, update or insert)
Total XML Parser Calls The total number of XML parser calls
Total XML Converter Size of
The total cumulative size of output buffer (in KB)
Output Buffer
Total XML Generator Calls The total number of XML generator calls
Tasks
Parameters Description
Tasks Running The current number of concurrent task instances running in the Siebel component.
Tasks Paused The tasks that have been temporarily placed in a suspended state.
Tasks Completed The tasks that have run to completion.
Tasks Exited with Errors The tasks that encountered an error during its processing and exited.
Tasks Killed The tasks that were not able to shut down cleanly, and were forced to shut down.
Error Tasks
Component Name of the Siebel component.
TaskID The operating system identification number assigned to the task.
Run State Current run state for the Siebel task (Running, Paused, Stopping,
A task may be in one of four states
Running
Task Status Paused
Stopping
Completed
Task Label The task label.
Start Time The time when this task started.
End Time The time when this task ended.
Active Sessions
Parameters Description
Component Specifies the name of the Siebel component.
TaskID Siebel task ID for the application OM that handles the user session.
Run State The running state of the users'' sessions for the selected Siebel Server.
Hung State The state of the users'' sessions for the selected Siebel Server not responding.
DB Session ID A unique session number created for the user
OM Login Object Manager login ID of the user.Task Status Current status of the task i.e running or paused.
Microsoft Dynamics CRM / 365 (On-Premise)
Monitoring
Microsoft Dynamics CRM / 365 (On-Premise) - An Overview
Adding a new monitor
Monitored Parameters
An Overview
Dynamics CRM/365 is Microsoft''s fully integrated customer relationship management system that helps
organizations attract and develop new profitable relationships with customers while managing ongoing
relationships from a single operating platform. Microsoft Dynamics CRM/365 offers both on-premise and cloud-
based options, tight integration with Microsoft Office and Outlook, and all-out customization flexibility.
As a system administrator you need to be able to to respond quickly to critical events and prevent service outages.
Applications Manager helps you track the set of counters that generate data about how various components
perform as they run in the Microsoft Dynamics CRM/365 environment. You can monitor the WMI Performance
counters, Services, Transactions and Eventlogs for CRM Applications. You can get deeper insight into the
performance of CRM''s Authentication, Outlook Sync, e-mail Router, Discovery, Locator, Platform Services,
Sandbox counters and Async Services.
Creating a new Monitor
Supported versions of Microsoft Dynamics CRM / 365 (On-Premise): CRM 2011, CRM 2013, CRM 2016 and
Dynamics 365
Prerequisites for monitoring Microsoft Dynamics CRM / 365 (On-Premise): Click to know about the user
previleges and other necessary prerequisites to monitor Microsoft Dynamics CRM/365.
Note: Powershell script execution must be enabled on Applications manager server for data collection. Click
here to know how
Follow the steps given below to create a new Dynamics CRM/365 Application monitor:
Click on New Monitor link.
Select Microsoft Dynamics CRM / 365 (On-Premise) under ERP category.
Specify the Display Name of the Dynamics CRM/365 Application.
Enter the Host Name or IP Address of the host where the Dynamics CRM/365 Application runs.
Select the Version number from the drop-down menu.
If you choose the Use Below Credentials option, then enter the credentials - UserName and Password of the
Host Machine.
UserName - To monitor a Microsoft Dynamics CRM/365 application, use Administrator user account
which has the permission to execute WMI queries on ''root/CIMV2'' namespace of the Dynamics CRM/365
Server.
Password - Password of the above user who has the permissions to execute WMI Queries.
If you choose the Select from credential list option, then select the respective credential from preconfigured
credential list.
Select Enable Event Log Monitoring if you wish to monitor event logs.
Specify the Polling Interval in minutes.
Choose the Monitor Group with which you want to associate the Dynamics CRM/365 monitor to, from the
combo box (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the Dynamics CRM/365 Application from the network and starts
monitoring it.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Microsoft Dynamics CRM / 365 (On-
Premise) under the ERP Table. Displayed is the Microsoft Dynamics CRM/365(On-Premise) bulk configuration
view distributed into three tabs:
Availability tab, gives the Availability history for the past 24 hours or 30 days.Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the server details listed under the following tabs:
Overview
Server
Requests
Sandbox
Async Services (Only for CRM 2011 and CRM 2013)
Performance
SQL Server
Web Traffic
.NET CLR
Events
OVERVIEW
Parameter Description
AUTHENTICATION FAILURES IN LAST MINUTE
Claims
Authentication The total number of failed authentication requests processed per minute using claims. This
Failures In The counter measures the whole deployment including all organizations.
Last Minute
Config DB
Windows The number of unsuccessful authentication requests per minute that are processed by using
Authentication Active Directory authentication credentials. This counter measures the entire Microsoft
Failures In The Dynamics CRM deployment including all organizations.
Last Minute
CRM Post
The number of unsuccessful authentication requests per minute that are processed by using
Authentication
Microsoft Dynamics CRM authentication credentials. This counter measures the entire
Failures In The
deployment including all organizations.
Last Minute
Passport
The number of failed authentication requests per minute that are processed by using Microsoft
Authentication
account authentication credentials. This counter measures the entire Microsoft Dynamics CRM
Failures In The
deployment including all organizations. This counter is CRM Online - specific.
Last Minute
The number of unsuccessful authentication requests per minute. There are several possible
Windows causes for authentication failure. For example, the user may have been authenticated
Authentication successfully by Active Directory but Microsoft Dynamics CRM authentication failed to
Failures In The communicate with the Kerberos servers, or a token expired, or the user''s credentials are
Last Minute incorrect. This counter measures the entire Microsoft Dynamics CRM deployment including all
organizations.
OUTLOOK SYNC REQUESTS
Current MAPI
The number of MAPI sync requests currently executing.
Sync Requests
Current
Offline Sync The number of offline sync requests currently executing.
Requests
Current
Outlook Sync The number of Microsoft Office Outlook sync requests currently executing.
Requests
The total number of Address Book Provider (ABP) synchronization requests made from CRM for
Total ABP Sync
Outlook to a Microsoft Dynamics CRM server; a high count indicates a high client load on the
Requests
Asynchronous Processing Service.
The total number of offline synchronization requests made from CRM for Outlook to a Microsoft
Total Offline
Dynamics CRM server; a high count indicates a high client load on the Asynchronous Processing
Sync Requests
Service.Parameter Description
Total Outlook The total number of ABP Sync Requests and the Offline Sync Requests; a high count indicates a
Sync Requests high client load on the Asynchronous Processing Service.
Total The number of successful offline synchronization requests made from CRM for Outlook to a
Succeeded Microsoft Dynamics CRM server; a count that is much lower than the total number of offline
Offline Sync synchronization requests may indicate a problem with clients that try to synchronize with the
Requests server.
The number of failed offline synchronization requests made from CRM for Outlook to a Microsoft
Total Failed Dynamics CRM server. This is calculated from ''Total Offline Sync Requests'' and ''Total
Offline Sync Succeeded Offline Sync Requests'' . A count greater than ''Total Succeeded Offline Sync
Requests Requests'' or a count close to ''Total Offline Sync Requests'' may indicate a problem with clients
that try to synchronize with the server.
SERVICES
The name of the service. Note that the display name and the service name (which is stored in the
Name
registry) are not always the same.
The Start mode of the service. The different start modes are:
Boot - The device driver is started by the operating system loader (valid only for driver
services).
System - The device driver started by the operating system initialization process. This value
is valid only for driver services.
Start Mode Auto - The service to be started automatically by the service control manager during system
startup. Auto services are started even if a user does not log on.
Manual - The service to be started by the Service Control Manager when a process calls the
StartService method. These services do not start unless a user logs on and starts them.
Disabled - The service that cannot be started until its StartMode is changed to either Auto or
Manual.
The current state of the base service. The values are: Stopped, Start Pending, Stop Pending,
State
Running, Continue Pending, Pause Pending, Paused, Unknown.
SERVER
Parameter Description
SERVER
Number of
The number of organizations that are currently active.
Organizations
Failed
Internal
The total number of failed web service requests to Microsoft Dynamics CRM InProc calls that are
Organization
made by applications that use the methods described in the Microsoft Dynamics CRM SDK.
Service
Requests
Failed
Organization
The total number of metadata requests received by the Microsoft Dynamics CRM Organization
Service
Web Service that failed because of a time-out or other SOAP failure.
Metadata
Requests
Failed
Organization The total number of requests to the Microsoft Dynamics CRM Organization Web Service that
Service failed because of a time-out or other SOAP failure.
Requests
Failed Report
The number of requests to render Microsoft SQL Server Reporting Services reports that failed
Render
because of a time-out or error.
Requests
The total number of error reports generated by the web client and CRM for Outlook. This counter
is reset weekly to zero. This counter is an indicator of high script error frequency. If a large
Script Error
number of error reports are received in a short time, the operations team should investigate to
Reports
determine which pages are producing errors. We recommend that you set a monitoring alert to
notify you if there are more than 500 error reports in a 10-minute period.
REQUESTSParameter Description
DISCOVERY SOURCE
Failed The number of requests to the Microsoft Dynamics CRM Discovery service that are unsuccessful
Discovery for any reason. For example, a request may fail because the requesting party is not recognized as
Service a user in the organization. A high count may indicate that the system is possibly under a denial-of-
Requests service (DoS) attack, or there is some problem with the Discovery service configuration.
Successful
Discovery The number of requests to the Microsoft Dynamics CRM Discovery service that completed
Service successfully.
Requests
Total
The total number of requests (successful and unsuccessful) received by the Microsoft Dynamics
Discovery
CRM Discovery service. This counter can be used to track traffic patterns for Discovery service
Service
capacity planning.
Requests
LOCATOR SERVICES
The number of LocatorService cache flush requests that were unsuccessful for any reason. For
Failed example, a request may fail because it was for an invalid cache entry, or the cache may not flush
Cache Flush because of an incorrect cache state. A high count may indicate a problem with the LocatorService
Requests cache, or a problem with the connection to CONFIG_DB. For information about the cause, review
the event log for errors.
Total Cache
Flush The total number of successful LocatorService cache flush requests that have been received.
Requests
ROUTER SERVICE REQUEST
AppFabric
Request The number of time-outs seen making requests to Windows Azure.
Timeout
Router
Request The number of requests made on the faulted channel to the router.
Faulted
Router
Request
The number of requests received by the router.
Received
(Throughput)
Router
Request The number of time-outs seen making requests to the router.
Timeout
PLATFORM
The average time that is required to process Microsoft Dynamics CRM data import requests.
Average
Import requests are resource-intensive SQL Server operations. If the average time is too high and
Time Of
the number of concurrent imports is high, some organizations may have to be moved to a different
Import
deployment. Also, you may want to consider processing import jobs during a maintenance
Request
window to reduce the performance effect on users.
Number Of
The number of import requests that have been submitted by organizations in the deployment in
Import
the past hour. This counter is useful to indicate how many import requests are being processed
Requests Per
concurrently.
Hour
Number Of
The number of requests that have been submitted by organizations in the deployment in the past
Publish
hour. This counter is useful to indicate how many publish requests are being processed
Requests Per
concurrently.
Hour
SANDBOX
Parameter Description
SANDBOX HOST
Worker Processes Crashed
The percentage of Sandbox Worker processes that have crashed.
Percentage
Worker Processes The percentage of Sandbox Worker processes that have been terminated due to
Terminated Percentage excessive resource usage or no response.Parameter Description
Active Assemblies The number of plug-in assemblies currently in use.
Active Organizations The number of organizations that currently have a Sandbox Worker process active.
Active Plugins The number of plug-ins currently in use.
Handles The total handle count used by all Sandbox Worker processes.
CPU Usage Percentage The total CPU percentage used by all Sandbox Worker processes.
Assembly Cache Hits
The assembly cache hit rate percentage.
Percentage
Assembly Cache Usage
The percentage of the total assembly cache disk space that is in use.
Percentage
Execute Failures
The incoming execution failure rate percentage in the Sandbox Host.
Percentage
SDK Failures Percentage The outgoing Request failure rate percentage in the Sandbox Host.
Assembly Cache Disk
The total disk space used by all plug-in assemblies in the assembly cache, in KB.
Space (KB)
Memory Usage (MB) The total memory used by all Sandbox Worker processes, in MBytes.
SANDBOX CLIENT
Execute Failures
The outgoing execution failure rate percentage in the Sandbox Client.
Percentage
SDK Failures Percentage The incoming SDK Request failure rate percentage in the Sandbox Client.
ASYNC SERVICES (Only for CRM 2011 and CRM 2013)
Parameter Description
ASYNC SERVICES
Active The total number of organizations in the Microsoft Dynamics CRM deployment that are actively
Organizations being polled by the Microsoft CRM Asynchronous Processing Service.
Total The number of organizations being monitored for the entire Microsoft Dynamics CRM
Organizations deployment.
Capacity Per The number of asynchronous operations to be removed from the processing queue that are
Organization currently allocated to an organization.
Items In
The maximum number of asynchronous operations to hold in memory for processing.
Memory (high)
Items In
The threshold of asynchronous operations to trigger loading of additional operations.
Memory (low)
The number of threads currently employed in the processing of asynchronous operations for all
Threads In Use
organizations in the deployment.
Total
Operations The total number of asynchronous operations that failed for all organizations in the deployment.
Failed
PERFORMANCE
Parameter Description
The Percent Processor Time i.e, the percentage of the time the processor is busy doing non-
CPU Utilization
idle threads.
Memory
The amount of memory immediately available for allocation to a process or for system use.
Utilization
Disk I/O Statistics
Devices The display name of the disks.
Transfers/Sec The rate of read and write operations on the disk per second.
Writes/Sec The rate at which bytes are transferred to the disk during write operations.
Reads/Sec The rate of write operations on the disk.Parameter Description
The percentage of elapsed time that the selected disk drive is busy servicing read or write
% Busy Time
requests.
Avg. Queue The average number of both read and write requests that were queued for the selected disk
Length during the sample interval.
Network Interface
Name The display name of the network connector
Speed (MBps) The interface''s current bandwidth in megabits per second (MBps).
Input Traffic
The rate at which bytes are received on the interface, including framing characters.
(MBps)
Output Traffic
The rate at which bytes are sent on the interface, including framing characters.
(MBps)
Port Connectivity
Port Name The name of the port monitored.
Port Number The port number specified for that port.
Connectivity
Specifies if the connection is UP / DOWN.
Status
Response
The time taken to check the connectivity status in milliseconds.
Time(ms)
Follow these steps to add, remove or edit the TCP ports monitored:
Go to \working\conf\application\script\powershell folder and open
DynamicsPorts.ps1 file in an editor.
To add new TCP port to be monitored, add the port name and port number in the below format along
with the other ports:
":"
Example: "DNS:53"
To remove any TCP ports which are monitored, comment the respective line by using ''#'' in the beginning
of the line.
Example: # "DNS:53"
If any ports have been changed from the default port number in the server, please edit the respective
port numbers.
Save the file after the changes are done.
Changes will be effective from the next poll in the monitor.
SQL SERVER
Parameters Description
General Statistics
Total Active
The total number of active transactions
Transactions
Transactions/Sec Number of transactions started for the database per second
Dynamic Server
Total amount of dynamic memory, in kilobytes, that the server is currently consuming
Memory
User Connections Number of users connected to the system
SQL Statistics
SQL
Compilations / Number of SQL Server query compilations per second
Sec
SQL Re-
Compilations / Number of SQL Server query re-compilations per second
SecParameters Description
Batch Requests /
Number of SQL Server batch request executed per seconds
Sec
Buffer Manager
Buffer Cache Hit
Percentage of pages that were found in memory, this not requiring a physical I/O operation
Ratio
Free List Stalls /
The number of requests per second that had to wait for a free page
Sec
Lazy Writes / Sec Pages written to the disk during the LazyWriter process freeing up SQL cache.
Page Life
Estimated number of seconds a page will stay in the buffer pool before it is written out
Expectancy
Page lookups /
Indicates the number of requests per second to find a page in the buffer pool
Sec
Lock Statistics
Lock Requests /
Number of new locks and lock conversions per second requested from the lock manager
Sec
Lock Memory The total amount of memory in kilobytes, that is allocated to locks
Access Method Metrics
Forwarded
The number of records fetched through forwarded record pointers
Records / Sec
FreeSpace Scans The number of scans per second that were initiated to search for free space within pages
/ Sec already allocated to an allocation unit to insert or modify record fragment
Either table or Index is fully scanned. This could be caused because of wrong or unhelpful
Full Scans / Sec
indexes
WorkFiles
The number of work files created per second
Created / Sec
WorkTables The number of worktables created in tempdb per second. Worktables are used for queries
Created / Sec that use various spools (table spool, index spool, etc)
WEB TRAFFIC
Parameter Description
Bytes Received/Sec The rate at which bytes are received by the web service.
Bytes Sent/Sec The rate at which bytes are sent by the web service.
Current Connections The current number of connections established with the web service.
Connection Attempts/Sec The rate at which connections using the web service are being attempted.
Files Received/Sec The rate at which files are received by the web service.
Files Sent/Sec The rate at which files are sent by the web service.
.NET CLR
Parameter Description
The total number of exceptions thrown since the start of the application. These include both
Exceptions/sec
.NET exceptions and unmanaged exceptions.
The elapsed time that was spent in performing a garbage collection (GC) since the last GC
Time in GC
cycle.
Current Queue
The total number of threads currently waiting to acquire some managed lock in the application.
length
Contention
The rate at which threads in the runtime attempt to acquire a managed lock unsuccessfully.
Rate/sec
Logical
The number of current .NET thread objects in the application.
Threads
Physical The number of native OS threads created and owned by the CLR to act as underlying threads for
Threads .NET thread objects.Parameter Description
JIT compilation
The percentage of elapsed time spent in JIT compilation since the last JIT compilation phase.
time
EVENTS
Event Log from the Dynamics CRM/365 Application can be monitored by creating EventLog Rules in Applications
Manager.
Parameter Description
EVENTS
Rule Name The name of the event log rule
Log File Indicates the Log File Type (i.e) Application, system, security, file replication service, DNS Server or
Type directory service.
Source The Application which created the event.
Event Id The Event ID associated with the Event Log File.
Indicates the Event Type (i.e) Error, Warning, Information or Event of Any Type. In case of Security
Type
Events, the types would vary between Success Audit and Failure Audit.
User Name The system component or User account that was running the process which caused the event.
Description A description of the event.
Generated
The time when the event entry was submitted.
Time
Microsoft Dynamics AX Monitoring
Microsoft Dynamics AX - An Overview
Monitoring Microsoft Dynamics AX - What we do
Creating a new Microsoft Dynamics AX monitor
Monitored Parameters
Microsoft Dynamics AX - An Overview
Microsoft Dynamics AX 2012 is an Enterprise Resource Planning (ERP) system suitable for midsize to large
enterprises. It provides your enterprise with comprehensive core functionality like financial, human resources and
operations management so that your business can thrive. Microsoft Dynamics AX offers complete functionality for
inventory control, warehouse management, transportation management, demand and supply chain planning,
material requirements planning, production management, quality assurance, product lifecycle management,
asset management, and business intelligence so you can make important business decisions.
Monitoring Microsoft Dynamics AX - What we do
To actively monitor the behavior of the Microsoft Dynamics AX application and related applications, Applications
Manager effectively collects information pertaining to the performance of each component of the system
architecture, i.e.: Application Object Server (AOS), the SQL Database Server, and their Server Stats.
Creating a new Microsoft Dynamics AX monitor
Supported versions : Microsoft Dynamics AX 2012, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012
R3
Prerequisites for monitoring Microsoft Dynamics AX metrics : Click here
Rest API to add a new Microsoft Dynamics AX monitor : Click here
To create a new Dynamics AX monitor, follow the steps given below:
Click on New Monitor link.
Select Microsoft Dynamics AX under ERP category.
Specify the Display Name of the Dynamics AX Application.
Enter the AX Host Name or IP Address of the host where the AX Server runs.
Select the Version number from the drop-down menu.
Select the AX Services to be monitored from the drop down list.If you choose the Use Below Credentials option, then enter the credentials - Username and Password of the
Host Machine.
Username - To monitor a Microsoft Dynamics AX application, use Administrator user account which has
the permission to execute WMI queries on ''root/CIMV2'' namespace of the AX Server.
Password - Password of the above user who has the permissions to execute WMI Queries.
If you choose the Select from credential list option, then select the respective credential from preconfigured
credential list.
Choose Remote SQL Server option if the MSSQL of Dynamics AX is in a remote server other than the AX server.
If this option is enabled, enter the following details:
SQL Server Host Name - Enter the hostname of the remote SQL server
SQL Server Credentials Details - Choose if you want to use the same AX Server Credentials or Enter new
credentials for the SQL server.
SQL Server Username - Use Administrator user account which has the permission to execute WMI
queries on ''root/CIMV2'' namespace of the SQL Server.
SQL Server Password - Password of the above user who has the permissions to execute WMI Queries
of the SQL Server.
Specify the Polling Interval in minutes.
Choose the Monitor Group with which you want to associate the Dynamics AX monitor to, from the combo box
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This starts monitoring the Dynamics AX Server Application from the network.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on the Microsoft Dynamics AXmonitor
under the ERP Table. Displayed is the Microsoft Dynamics AX bulk configuration view distributed into three tabs:
Availability tab displays the availability history for the past 24 hours or 30 days.
Performance tab displays the health status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the server details listed under the following tabs:
Overview
Application Object Server (AOS)
AOS Data Cache
SQL Server
Server Statistics
Overview
Parameters Description
AOS Active Sessions
Active
The number of currently active server sessions
Sessions
Total
The total number of active sessions since the AOS instance started
Sessions
Microsoft Dynamics AX and MSSQL Services
Service The name of the service. Note that the display name and the service name (which is stored in the
Name registry) are not always the same.
Availability The current state (Running or stopped) of the base service.
Application Object Server (AOS)
Parameters Description
AOS TrafficParameters Description
Bytes Received/Sec The number of bytes received by the AOS instance per second
Bytes Sent/Sec The number of bytes sent by the AOS instance per second
Request Statistics
Total Client Requests The number of client-to-server requests since the AOS instance started
Client requests/Min The number of client-to-server requests per minute
Client requests processed/Sec The number of client-to-server requests processed per second
Server responses/Min The number of server-to-client requests that have been processed per minute
AOS Data Cache
Parameters Description
Hits & Miss
The number of times a record was found successfully in the cache per
Hits/Min
minute
Miss/Min The number of times a record was not found in the cache
Data Cache Clears(Total)
Total Number of Clears The total number of times the cache was cleared of all contents
Clears due to AOS The total number of times the cache was cleared because of AOS
Synchronization(Total) synchronization
Deletes from Data Cache(Total) The total number of times records were deleted from the data cache
Cache flushes due to Size(Total) The total number of times the cache was flushed due to size
Selects on Cached Tables(Total) The total number of selects on tables that are cached
Data Cache Clears(Rate)
Number of Clears / Min The number of times the cache was cleared of all contents per minute
The number of times the cache was cleared because of AOS
Number of Clears by AOS / Min
synchronization per minute
Deletes from Data Cache / Min The number of times records were deleted from the data cache per minute
Cache Flush due to Size / Min The number of times the cache was flushed due to size per minute
Selects on Cached Tables / Min The number of selects on tables that are cached per minute
SQL Server
Parameters Description
General Statistics
Total Active
The total number of active transactions
Transactions
Transactions/Sec Number of transactions started for the database per second
Dynamic Server
Total amount of dynamic memory, in kilobytes, that the server is currently consuming
Memory
User Connections Number of users connected to the system
SQL Statistics
SQL
Compilations / Number of SQL Server query compilations per second
Sec
SQL Re-
Compilations / Number of SQL Server query re-compilations per second
Sec
Batch Requests /
Number of SQL Server batch request executed per seconds
Sec
Buffer ManagerParameters Description
Buffer Cache Hit
Percentage of pages that were found in memory, this not requiring a physical I/O operation
Ratio
Free List Stalls /
The number of requests per second that had to wait for a free page
Sec
Lazy Writes / Sec Pages written to the disk during the LazyWriter process freeing up SQL cache.
Page Life
Estimated number of seconds a page will stay in the buffer pool before it is written out
Expectancy
Page lookups /
Indicates the number of requests per second to find a page in the buffer pool
Sec
Lock Statistics
Lock Requests /
Number of new locks and lock conversions per second requested from the lock manager
Sec
Lock Memory The total amount of memory in kilobytes, that is allocated to locks
Access Method Metrics
Forwarded
The number of records fetched through forwarded record pointers
Records / Sec
FreeSpace Scans The number of scans per second that were initiated to search for free space within pages
/ Sec already allocated to an allocation unit to insert or modify record fragment
Either table or Index is fully scanned. This could be caused because of wrong or unhelpful
Full Scans / Sec
indexes
WorkFiles
The number of work files created per second
Created / Sec
WorkTables The number of worktables created in tempdb per second. Worktables are used for queries
Created / Sec that use various spools (table spool, index spool, etc)
Server Statistics
Parameters Description
Processor
% Privileged Time The percentage of non-idle processor time spent in privileged mode
% User Time The percentage of non-idle processor time spent in user mode
Memory
The amount of physical memory available to processes running on the computer in
Available bytes
megabytes
Committed bytes The amount of committed virtual memory in megabytes
Page Faults / Sec The average number of pages faulted per second
Disk
Average Queued The average number of both read and write requests that were queued for the selected
Requests disk during the sample interval.
% Disk Time Measures how busy a physical array is.
Average time / Disk
The average time in seconds for a read of data from the disk.
Read
Average time / Disk
The average time in seconds for a write of data from the disk.
Read
Network
Segments Sent / Sec The rate at which segments are sent.
Segments Received /
The rate at which segments are received.
Sec
Segments Re-
The rate at which segments are re-transmitted.
transmitted / Sec
Mail ServersBelow are the list of mail servers that are monitored in Applications Manager:
Exchange Server
Mail Server
Browse through the different mail servers that provide server information and their parameters being monitored.
Exchange Server Monitoring
Exchange Server Versions Supported: Exchange 2019, Exchange 2016, Exchange 2013, Exchange 2010,
Exchange 2007, Exchange 2003 and older versions.
Prerequisites for monitoring Exchange Server: Monitoring of Exchange Server is possible only if Applications
Manager is running in a Windows System. Refer Prerequisites Section.
Using the REST API to add a new Exchange server monitor: Click here
Attributes Monitored: Refer Exchange Server Parameters to know more about the attributes monitored.
To create a Exchange Server Monitor, follow the given steps:
Click on New Monitor link. Choose Exchange Server under Mail Servers.
Enter a Display name for the new monitor that you''re going to add.
Enter the IP Address or hostname of the host in which the Exchange Server is running.
Select Exchange Server Version - Exchange 2019, Exchange 2016, Exchange 2013, Exchange 2010, Exchange
2007, Exchange 2003 or below.
Select the Server Role to be monitored.
Choose the Exchange Server Services you want to monitor from the list.
Select the Exchange Server Services you want to monitor.
Provide the authentication details such as User Name, Domain Name, and Password for the system in which
Exchange server is running.
You can enter your own credential details or select preconfigured credentials details in Credentials Manager. If
you wish to enter your own credentials, specify username and password details for the monitor.
Choose the Mode of Monitoring - Powershell or WMI. By default, the connectionURI will be detected. If
neccessary, it can be customized.
Know more about using the Powershell option
Provide the port number in which Exchange Server is running. Also, you can provide multiple ports separated
by commas.
Enable the Use CredSSP Authentication option only if you want to fetch Exchange Queues metrics for non-
mailbox roles in versions 2010 and above where the Applications Manager and Exchange server are in different
domains. Know more about using CredSSP authentication
Specify the timeout value in seconds. Value should be greater than 120 seconds. However, this is applicable
only in Powershell mode of monitoring.
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box to which you want to associate the Monitor (optional). You can
choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the Monitor from the network and starts monitoring them.
Know more about Exchange Server''s component-specific performance counters that Applications Manager
monitors.
Note:
Monitoring of Exchange Server is possible only if Applications Manager is running in a Windows System. Also,
Exchange Server monitor will work only if WMI is enabled in the remote machine in which Exchange Server is
running.
Exchange Monitoring now supports data collection in two ways :
WMI - For users who have not installed / do not require powershell
In the new monitor page, choose the WMI Mode of Monitoring
Mailbox and Database Statistics for Mailbox Server Role is not available for this setting.
Powershell:
In the new monitor page, Choose the Powershell Mode of Monitoring and provide the connectionURI. To
use Powershell for data collection make sure the proper steps have been followed to enable powershell
remoting.
If the user has not modified any ports or connectionURI, it need not be customized. Default value for
connectionURI will be used.
Use CredSSP Authentication needs to be enabled only for fetching Exchange Queues in non-mailboxroles in versions 2010 and above where the Applications Manager and Exchange server are in different
domains. Click here for the steps to enable CredSSP
Applications Manager lets you effectively monitor the different versions of your Exchange Server and report on
performance, availability, and the working of its server roles. You can collect Exchange component-specific
performance counters in one central location, detect issues, send alerts and thus prevent possible service outages
or configuration problems. Users can proactively manage Exchange servers and identify issues before they
become critical.
Applications Manager gathers data related to each of your Exchange Server Roles:
Mailbox Server Role - Monitor your mailbox and public folder databases and diagnose issues pertaining to
all related messaging data.
Client Access Server Role - Monitor overall client access like ActiveSync, .NET, OWA, Web Services
connections and hardware performance.
Unified Messaging Server Role - Track integrated dial-in access performance and monitor e-mail, voicemail,
fax, calendar information and contacts.
Hub Transport Server Role - Monitor the mail flow, routing, and delivery within the Exchange
organization and identify disk performance bottlenecks.
Edge Transport Server Role - Monitor EdgeSync services, Active Directory Application Mode, SMTP
connection authentication, transport queue databases and logs.
Applications Manager supports monitoring of counters relevant to the following server roles:
Exchange Server 2019 Server roles:
Mailbox Server Role Counters
Edge Transport Server Role Counters
Exchange Server 2016 server roles:
Mailbox Server Role Counters | Mailbox and Database Statistics ( This includes Client Access Role
Counters too because Mailbox server in Exchange 2016 includes all of the server components from
Exchange 2013 Mailbox and Client Access roles )
Edge Transport Server Role Counters
Exchange Server 2013 Server roles:
Mailbox Server Role Counters | Mailbox and Database Statistics
Client Access Server Role Counters
Edge Transport Server Role Counters
Exchange Server 2010 and 2007 Server roles:
Mailbox Server Role Counters | Mailbox and Database Statistics
Client Access Server Role Counters
Hub Transport Server Role Counters
Edge Transport Server Role Counters
Unified Messaging Server Role Counters
Exchange Server 2003 and older versions
Performance Counters
Common Counters (For all versions and roles)
Exchange Services and Active-Directory Access Domain Controllers
Host Performance Counters
Queues
Exchange Server - Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Exchange Server under the Mail
Servers Table. Displayed is the Exchange Server bulk configuration view distributed into three tabs:
Availability tab, gives the Availability history for the past 24 hours or 30 days.Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Mailbox Role Counters Exchange Server Version
Attribute Description 2007 2010 2013 2016 2019
name
POP & IMAP Connections
Current POP The total number of POP connections opened since the
Connections computer was last started.
Current
The total number of POP connections opened since the
IMAP
computer was last started.
Connections
SMTP Connections
Inbound
The total number of currently inbound connections.
Connections
Outbound
The number of connections that were currently outbound.
Connections
Messages
Sent Per The rate at which outbound messages are being sent.
Second
Messages
Received The rate at which inbound messages are being received.
Per Second
Latency Requirements Counters
Database
The rate of page faults that can''t be serviced because there are
PageFault
no pages available for allocation from the database cache. This
Stalls Per
counter should be 0 on production servers.
Second
Database
The average time, in ms, to read from the database file. The
I/O Reads
average value should be below 200 ms. Maximum values
Average
shouldn''t be higher than 1,000 ms.
Latency
Database The average time, in ms, to write to the database file. This
I/O Writes latency should be less than the MSExchange Database\I/O
Average Database Reads (Recovery) Average Latency when battery-
Latency backed write caching is utilized.
I/O Log
The number of times data was read from a log file. Specific to
Reads Per
log replay and database recovery operations.
Second
I/O Log
The number of times a log buffer was written to the active log
Writes Per
file. Specific to log replay and database recovery operations
Second
The number of log records that can''t be added to the log buffers
Log Record
per second because the log buffers are full. The average value
Stalls Per
should be below 10 per second. Maximum values shouldn''t be
Second
higher than 100 per second.
The number of threads waiting to complete an update of the
Log Threads
database by writing their data to the log. The average value
Waiting
should be less than 10 threads waiting.
Message Queuing Counters
Mailbox
The current number of submitted messages not yet processed
Messages
by the transport layer. The threshold value should be below 50
Queued For
at all times. Shouldn''t be sustained for more than 15 minutes.
Submission
Public
The current number of submitted messages not yet processed
Messages
by the transport layer. The threshold value should be less than
Queued For
20 at all times.
Submission
Information Store RPC Processing CountersIS RPC The latency, in ms, averaged for the past 1,024 packets.
Requests
IS RPC
The number of client requests currently being processed by the
Averaged
RPC Client Access service.
Latency
Cache Statistics
Number Of
Cache The number of active connections in all data connection pools
Active created for a specific PowerPivot service application instance.
Connections
Number Of
The number of idle connections in all data connection pools
Cache Idle
created for a specific PowerPivot service application instance.
Connections
Number Of
Cache The number of connections to the server stored in the cache.
Connections
Cache Total
The size of the cached server connection pool.
Capacity
RPC Client Throttling & Client Activity Counters
Client RPC RPC Average Latency is server RPC latency, in ms, averaged for
Average the past 1,024 packets. The threshold value should be less than
Latency 50 ms on average for each client.
The rate that the server notifies the client to back-off. Higher
RPC Client
values may indicate that the server may be incurring a higher
BackOff Per
load resulting in an increase in overall averaged RPC latencies,
Second
causing client throttling to occur.
Client: RPCs
The client-reported rate of failed RPCs since the store was
Failed Per
started.
Second
Client: RPCs The client-reported number of failed RPCs since the store was
Failed started.
Content Indexing Counters
Percentage The amount of processor time being consumed to update
Processor content indexing within the store process. Full crawls increase
Time of overall processing time, but should never exceed overall store
indexing CPU capacity.
Average
Document The average, in ms, of how long it takes to index documents.
Indexing The threshold value should be less than 30 seconds at all time.
Time
This counter is used to determine if a full crawl is occurring for
any specified database. Possible values are
Full Crawl
Mode Status 1 - going through a full crawl
0 - not going through a full crawl
Average
Latency of The average latency, in ms, of the most recent RPCs to the
RPCs used Information Store service. These RPCs are used to get content
to Obtain for the filter daemon for the specified database.
Content
Crawler Any value of 1 or higher indicated the mailboxes in the database
Mailboxes are being crawled but when the crawl is completed, the value is
Remaining set to 0.
Client-Related Search Counters
The rate at which the slower FindRow needs to be used in the
mailbox store. The threshold value should be no more than 10
Slow Find
for any specific mailbox store. Higher values indicate
Row Rate
applications are crawling or searching mailboxes, which is
affecting server performance.
Search Task The number of search tasks created per second. The thresholdRate value should be less than 10 at all times.
The number of query processor threads currently running
Slow QP
queries that aren''t optimized. The threshold value should be
Threads
less than 10 at all times.
The number of search threads currently running queries that
Slow Search
aren''t optimized. The threshold value should be less than 10 at
Threads
all times.
Database Counters
Log Bytes
The rate of bytes written to the log. The threshold value should
Writes Per
be less than 10,000,000 at all times.
Second
The percentage of database file page requests fulfilled by the
database cache without causing a file operation. If this
percentage is too low, the database cache size may be too
Database
small. The threshold value should be over 90% for companies
Cache
with majority online mode clients. The threshold value should
Percent Hit
be over 99% for companies with majority cached mode clients.
If the hit ratio is less than these numbers, the database cache
may be insufficient.
The amount of system memory, in megabytes (MB), used by the
Database database cache manager to hold commonly used information
Cache Size from the database files to prevent file operations. Maximum
in MB value is RAM-2GB. Use this counter along with store private
bytes to determine if there are store memory leaks.
Version The total number of version buckets allocated. The threshold
Buckets value should be less than 12,000. The maximum default version
Allocated is 16,384.
The number of threads waiting for their data to be written to the
log to complete an update of the database. If this number is too
Log Threads high, the log may be a bottleneck. The threshold value should
Waiting be less than 10 on average. Regular spikes concurrent with log
record stall spikes indicate that the transaction log disks are a
bottleneck.
Represents the amount of work in the log file count that needs to
be redone or undone to the database files if the process fails.
Log
The threshold value should be below 500 at all times for the
Generation
Mailbox server role. A healthy server should indicate between
Check Point
20 and 30 for each database instance. If checkpoint depth
Depth
increases continually for a sustained period, this indicates
either a long-running transaction, or a bottleneck.
Database
I/O Reads The average length of time, in ms, per database read operation.
Average The threshold value should be 20 ms on average.
Latency
Database The average length of time, in ms, per database write operation.
I/O Writes The threshold value should be 50 ms on average. Maximum
Average values of up to 100 ms are acceptable if not accompanied by
Latency database page fault stalls.
Mailbox Assistant Counters
Percentage
Processor
Percentage Processor Time of Mailbox Assistant. The threshold
Time of
value should be less than 5% of overall CPU capacity.
Mailbox
Assistant
Average
Event
The average processing time of the events chosen. The
Processing
threshold value should be less than 2 at all times.
Time in
Seconds
The number of events in the in-memory queue waiting to be
Events in
processed by the assistants. The threshold value should be a
Queue
low value at all times. High values may indicate a performance
bottleneck.Events
The number of events polled per second. Determines current
Polled Per
load statistics for this counter.
Second
Mailboxes
The rate of mailboxes processed by time-based assistants per
Processed
second. Determines current load statistics for this counter.
Per Second
Resource Booking Counters
Average
Resource
The average time to process an event in the Resource Booking
Booking
Attendant. High values may indicate a performance bottleneck.
Processing
Time
Requests
The total number of failures that occurred while the Resource
Failed in
Booking Attendant was processing events. The threshold value
Resource
should be 0 at all times.
Booking
Calendar Attendant Counters
Average
Calendar
The average time to process an event in the Calendar Attendant.
Attendant
High values may indicate a performance bottleneck.
Processing
Time
Requests
The total number of failures that occurred while the Calendar
Failed in
Attendant was processing events.The threshold value should be
Calendar
0 at all times.
Attendant
Store Client Request Counters
The average latency, in ms, of RPC requests. The average is
RPC Latency
calculated over all RPCs since exrpc32 was loaded. The
Average
threshold value should be less than 100 ms at all times.
ROP
The total number of outstanding remote operations requests.
Requests
Used for determining current load.
Outstanding
RPC
Requests The current number of outstanding RPC requests.
Outstanding
RPC
Requests The total number of outstanding RPC requests. Used for
Sent Per determining current load.
Second
Percentage The percentage of failed requests in the total number of RPC
RPC requests. Failed means the sum of failed with error code plus
Requests failed with exception. The threshold value should be less than 1
Failed at all times.
Percentage The percentage of slow RPC requests among all RPC requests. A
RPC Slow slow RPC request is one that has taken more than 500 ms. The
Requests threshold value should be less than 1 at all times.
HUB Servers The number of Hub Transport servers in retry mode. The
in Retry threshold value should be 0 at all times.
Successful
The number of currently successful mail submission per
Submission
second.
Per Second
Failed
Submission The number of failed submissions per second.
Per Second
Temporary
Submission
The number of temporary submission failures per second.
Failures Per
Second
RPC The current number of RPC operations occurring per second.
OperationsPer Second
Information Store Counters
Client: RPC
The number of RPC operations per second for each client type
Operations
connection.
Per Second
JET Log The rate that database log records are generated while
Records Per processing requests for the client. Used to determine current
Second load.
JET Pages The rate that database pages are read from disk while
Read Per processing requests for the client. Used to determine current
Second load.
Directory
The current rate that LDAP reads occur while processing
Access:
requests for the client. Used to determine the current LDAP read
LDAP Reads
rate per protocol.
Per Second
Directory
The current rate that LDAP writes occur while processing
Access:
requests for the client. Used to determine the current LDAP read
LDAP Writes
rate per protocol.
Per Second
Messages
The rate that messages are delivered to all recipients. Indicates
Delivered
current message delivery rate to the store.
Per Second
Messages
The rate that messages are sent to transport. Used to determine
Sent Per
current messages sent to transport.
Second
Messages The rate that messages are submitted by clients. Used to
Submitted determine current rate that messages are being submitted by
Per Second clients.
User Count The number of users connected to the information store. Used
of IS to determine current user load.
Replication
Receive The number of replication messages waiting to be processed.
Queue Size
Mailbox and Database Statistics Counters Exchange Server Version
Attribute Description 2007 2010 2013 2016 2019
name
Top Mailboxes By Size
Mailbox
Username for Exchange Mailbox User.
User Name
Total Item
Specifies used mailbox size, in MB.
Size
Item Count Specifies number of items in mailbox.
Inactive Mailbox Users
Mailbox
Username for Exchange Mailbox User.
User Name
Last Logon
Time of Last Login by Mailbox User.
Time
Database Statistics (2010, 2013, 2016 & 2019)
Master
Specifies if the Mailbox Database is part of a DAG/ Server.
Type
The Database Accessibility Group (DAG) name. DAG allows you
DAG Name to replicate
/ Server your database where your mail is stored across any number of
servers.
Database
Name of the mailbox database.
NameMount The mount status of the mailbox stores on the server. Mailboxes
Status contained in unmounted mailbox stores cannot receive incoming
messages.
Mailbox The total number of mailboxes that reside in all mailbox stores
Count and public folders.
Database
The size of the mailbox database.
Size (GB)
Available
New
The disk space consumed by the mailbox stores on this server in
Mailbox
GB.
Space
(GB)
Last Full Detailed information about backups performed on storage
Backup groups on the connected server.
Circular Specifies whether or not circular logging is enabled. Circular
Logging Logging saves storage on your Exchange Server by preventing
Enabled transaction logs from building up on the Server.
Days Since
Indicates the number of days passed since the last full backup
Last Full
operation was performed.
Backup
Database Statistics (2007)
Database
Name of the mailbox database
Name
The mount status of the mailbox stores on the server. Mailboxes
Mount
contained in unmounted mailbox stores cannot receive incoming
Status
messages.
Mailbox The total number of mailboxes that reside in all mailbox stores
Count and public folders.
The exchange storage group name. A Storage Group is a
Storage
grouping of one or more Mailbox Databases along with Log Files
Group
and a Checkpoint File. Not available for versions later than 2007.
Database Availability Groups
Database
Availability
The name of the database availability group.
Group
Name
DAG
The database availability group members.
Members
DAG
The number of members in the particular database availability
Members
group.
Count
Database Copy Statistics
Database
The name of the mailbox database.
Name
Database The current status of the database. Possible Statuses are:
Status
Failed - The mailbox database copy is in a Failed state
because it is not suspended, and it is notable to copy or
replay log files. While in a Failed state and not suspended,
the system will periodically check whether the problem that
caused the copy status to change to Failed has been
resolved. After the system has detected that the problem is
resolved, and barring no other issues, the copy status will
automatically change to Healthy.
Seeding - The mailbox database copy is being seeded, the
content index for the mailbox database copy is being
seeded, or both are being seeded. Upon successful
completion of seeding, the copy status should change to
Initializing.
SeedingSource - The mailbox database copy is being used
as a source for a database copy seeding operation.Suspended - The mailbox database copy is in a Suspended
state as a result of an administrator manually suspending
the database copy by running the Suspend-
MailboxDatabaseCopy cmdlet.
Healthy - The mailbox database copy is successfully copying
and replaying log files, or it has successfully copied and
replayed all available log files.
ServiceDown - The Microsoft Exchange Replication service
is not available or running on the server that hosts the
mailbox database copy.
Initializing - The mailbox database copy will be in an
Initializing state when a database copy has been created,
when the Microsoft Exchange Replication service is starting
or has just been started, and during transitions from
Suspended, ServiceDown, Failed, Seeding,
SinglePageRestore, LostWrite, or Disconnected to another
state. While in this state, the system is verifying that the
database and log stream are in a consistent state. In most
cases, the copy status will remain in the Initializing state for
about 15 seconds, but in all cases, it should generally not be
in this state for longer than 30 seconds.
Resynchronizing - The mailbox database copy and its log
files are being compared with the active copy of the
database to check for any divergence between the two
copies. The copy status will remain in this state until any
divergence is detected and resolved.
Mounted - The active copy is online and accepting client
connections. Only the active copy of the mailbox database
copy can have a copy status of Mounted.
Dismounted - The active copy is offline and not accepting
client connections. Only the active copy of the mailbox
database copy can have a copy status of Dismounted.
Mounting - The active copy is coming online and not yet
accepting client connections. Only the active copy of the
mailbox database copy can have a copy status of Mounting.
Dismounting - The active copy is going offline and
terminating client connections. Only the active copy of the
mailbox database copy can have a copy status of
Dismounting.
DisconnectedAndHealthy - The mailbox database copy is no
longer connected to the active database copy, and it was in
the Healthy state when the loss of connection occurred. This
state represents the database copy with respect to
connectivity to its source database copy. It may be reported
during DAG network failures between the source copy and
the target database copy.
DisconnectedAndResynchronizing - The mailbox database
copy is no longer connected to the active database copy,
and it was in the Resynchronizing state when the loss of
connection occurred. This state represents the database
copy with respect to connectivity to its source database
copy. It may be reported during DAG network failures
between the source copy and the target database copy.
FailedAndSuspended - The Failed and Suspended states
have been set simultaneously by the system because a
failure was detected, and because resolution of the failure
explicitly requires administrator intervention. An example is
if the system detects unrecoverable divergence between the
active mailbox database and a database copy. Unlike the
Failed state, the system will not periodically check whether
the problem has been resolved, and automatically recover.
Instead, an administrator must intervene to resolve the
underlying cause of the failure before the database copy can
be transitioned to a healthy state.SinglePageRestore - This state indicates that a single page
restore operation is occurring on the mailbox database copy.
Based on these values, we want the Status attribute to be either
Mounted (true for the server where the database is mounted) or
Healthy (for the servers that hold a copy of it). For the
ContentIndexState attribute, we want it to be always Healthy.
The Copy Queue Length shows the number of transaction log
Copy
files waiting to be copied to the passive copy log file folder. A
Queue
copy is not considered complete until it has been checked for
Length
corruption.
The state of Microsoft Exchange Server content indexes:
Crawling - Database is in the process of indexing database
content. Depending on the size of the database, this process
could take some time to complete.
Disabled - Indexing for the database has been disable by an
administrator.
Failed - An error has occurred causing the content index to
fail.
FailedAndSuspended - The Failed and Suspended states
have been set simultaneously by the system because a
Content failure was detected, and because resolution of the failure
Index explicitly requires administrator intervention.
State
Healthy - This indicates the Content Index is up to date and
has not detected any issues. This is the only state in which a
failover (automatic process) to a specific database copy can
occur.
Seeding - A database copy is in the process of updating its
Content Index from another database copy.
Suspended - The Suspended status occurs if an
administrator manually pauses or suspends it from receiving
updates from the active copy. This might be done to update
a failed Content Index or to perform troubleshooting for
other issues.
Latest Full
Backup Last full backup time for the mailbox database
Time
Active If the database copy is active "True" is shown else,if Passive,
Copy "False" is shown
Days Since
Indicates the number of days passed since the latest full backup
Latest Full
operation was performed.
Backup
Client Access Server Role Counters Exchange Server Version
Attribute name Description 2007 2010 2013 2016 2019
Outlook Web Access Counters
The number of users currently logged on to Outlook Web
Access. This value monitors the number of unique active
Current Users user sessions, so that users are only removed from this
counter after they log off or their session times out.
Determines current user load.
Outlook Requests The number of Outlook requests processed each
Persec second. Determines current user load.
Average Search The average time elapsed while waiting for a search to
Time complete.
Searches timed out The number of Outlook requests timed out.
Average response The average time (in milliseconds) that elapsed
time between the beginning and end of an OEH or ASPX
request. Used to determine the latency that a client isexperiencing. The threshold value should be less than
100 ms at all times. Higher values may indicate high
user load or higher than normal CPU time.
ASP.NET Counters
The number of times the application has been restarted
Application Restarts
during the Web server''s lifetime.
Worker Process The number of times a worker process has restarted on
Restarts the computer.
The number of ms the most recent request was waiting
Request Wait Time
in the queue.
Availability Service Counters
The number of requests in the application request
queue per second. The request can be only for free/busy
Availability
information or include suggestions. One request may
Requests sec
contain multiple mailboxes. Determines the rate at
which Availability service requests are occurring.
Average Time to The average time to process a free/busy request in
Process a Free Busy seconds. A single request may contain multiple
Request mailboxes.
The number of HTTP requests waiting to be assigned to
Current requests
a thread.
Mailbox Session
The number of hits in a mailbox session.
Hits Per Second
Public Folder Queries per second is the number of
Public Folder
mailboxes for which free busy information is requested
Queries Per Second
from the public folders per second.
Public Folder
The number of public folder free busy requests failed
Request Failures Per
per second.
Second
ActiveSync Service Counters
ActiveSync
The number of HTTP requests waiting to be assigned to
Requests Per
a thread. (Average of 50-100.)
second
The number of ping commands currently pending on
Ping Commands the server. Ping Commands Pending are the number of
Pending hanging requests, which should be almost equal to the
number of Direct Push and hanging sync users.
The number of sync commands currently pending on
Sync Commands the server. Sync Commands Pending are the number of
Pending hanging requests, which should be almost equal to the
number of Direct Push and hanging sync users.
Requests Queued The number of HTTP requests queued in a thread.
CAS OAB Download Counters
The number of OAB download tasks queued since the
Download Task
File Distribution service started. The threshold value
Queued
should be 0 at all times.
The number of OAB download tasks completed since
Download Tasks the File Distribution service started. The default value is
Completed every 480 minutes or 8 hours. The threshold value
should be less than or equal to 3 per day.
WebService Counters
Current The current number of connections established with the
Connections Web service. Determines current user load.
Connection
The rate that connections to the Web service are being
Attempts Per
attempted. Determines current user load.
Second
The rate that Internet Server API (ISAPI) extension
Current ISAPI
requests are received by the Web service. Determines
Extension Requests
current user load.Other Request The rate HTTP requests are made that don''t use the
Methods Per OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE,
Second MOVE, COPY, MKCOL, PROPFIND, PROPPATCH,
SEARCH, LOCK, or UNLOCK methods. Determines
current user load.
Requests Per The number of requests processed each second.
Second Determines current user load.
Completed
The number of requests completed each second.
requests Per
Determines current user load.
Second
Autodiscover Counters
Autodiscover
The number of Autodiscover service requests processed
Requests Per
each second. Determines current user load.
Second
Unified Messaging Counters
Percentage of failed
The percentage of mailbox connection attempts that
mailbox connection
failed in the last hour. The threshold value should be
attempts over the
less than 5%.
last hour
Percentage of
inbound calls
The percentage of inbound calls that were rejected by
rejected by the
the Microsoft Exchange Unified Messaging service over
Unified Messaging
the last hour
service over the last
hour.
Percentage of
inbound calls
rejected by the The percentage of inbound calls that were rejected by
Unified Messaging the UM worker process over the last hour.
worker process over
the last hour
Percentage of
messages The percentage of messages that were successfully
successfully processed by the Microsoft Exchange Unified
processed over the Messaging service over the last hour.
last hour
Percentage of
partner voice
message The percentage of voice messages for which
transcription transcription failed in the last hour.
failures over the last
hour
Unified Messaging
calls disconnected The number of calls disconnected after an internal
on irrecoverable system error occurred.
internal error
Unified Messaging
The total number of calls disconnected after too many
calls disconnected
user entry failures.
by user failure
Unified Messaging The number of calls that are currently connected to the
current calls UM server.
Unified Messaging
Total Calls per Second is the number of new calls that
total calls per
have arrived in the last second.
second
User Response Latency is the average response time, in
Unified Messaging milliseconds, for the system to respond to a user
user response request. This average is calculated over the last 25
latency calls. This counter is limited to calls that require
significant processing.
Exchange Control Panel Counters
Explicit Sign-On The average time (in ms) that requests sent to a
Outbound Proxy secondary Client Access server took to complete duringRequests - Average the sampling period. The threshold value should be
Response Time under 6,000 ms.
The average time (in ms) the Exchange Control Panel
Requests - Average
took to respond to a request during the sampling
Response Time
period. The threshold value should be under 6,000 ms.
ASP.net Request The number of failures per second detected by ASP.NET
Failures Per Second in the Exchange Control Panel.
Powershell The average time (in seconds) that a Windows
Runspaces - PowerShell runspace stays active while executing
Average Active cmdlets in the Exchange Control Panel during the
Time sampling period.
Powershell
The number of Windows PowerShell runspaces created
Runspaces Per
per second in the Exchange Control Panel.
Second
RBAC sessions Per The number of RBAC sessions loaded per second in the
Second Exchange Control Panel.
Hub/Edge Transport Role Counters Exchange Server Version
Attribute Description 2007 2010 2013 2016 2019
name
Transport Database Counters (HUB,EDGE)
IO Log Writes The rate of log file write operations completed. Determines
Per Second the current load.
IO Log Reads The rate of log file read operations completed. Determines
Per Second the current load.
Log
Generation The amount of work (in count of log files) that needs to be
Checkpoint redone or undone to the database files if the process fails.
Depth
Version Total number of version buckets allocated. Shows the default
Buckets backpressure values as listed in the edgetransport.exe.config
Allocated file.
IO Database
The rate of database read operations completed. Determines
Reads Per
the current load.
Second
IO Database
The rate of database write operations completed. Determines
Writes Per
the current load.
Second
The number of log records that can''t be added to the log
Log Record
buffers per second because they are full. If this counter is
Stalls Per
nonzero most of the time, the log buffer size may be a
Second
bottleneck.
The number of threads waiting for their data to be written to
Log Threads
the log to complete an update of the database. If this number
Waiting
is too high, the log may be a bottleneck.
Transport Dumpster Counters (HUB,EDGE)
Dumpster The total size (in bytes) of mail items currently in the transport
Size dumpster on this server.
Dumpster The rate at which items are inserted into the transport
Inserts Per dumpster on this server. Determines the current rate of
Second transport dumpster inserts.
The total number of mail items currently in the transport
Dumpster
dumpster on this server. Shows the current number of items
Item Count
being held in the transport dumpster.
Dumpster The rate at which items are deleted from the transport
Deletes Per dumpster on this server. Determines the current rate of
Second transport dumpster deletions.
Transport Queue Length Counters (HUB,EDGE)Aggregate The number of messages queued for delivery in all queues.
Delivery The threshold should be less than 3,000 and not more than
Queue Length 5,000.
All Queues
Active Remote
The number of messages in the active remote delivery
Delivery
queues. The threshold should be less than 250.
Queue Length
Active
Mailbox The number of messages in the active mailbox queues. The
Delivery threshold should be less than 250.
Queue Length
The number of messages in the submission queue. The
Submission threshold should be less than 100. If sustained high values
Queue Length occur, investigate Active Directory and Mailbox servers for
bottlenecks or performance-related issues.
Active Non-
The number of messages in the drop directory used by a
SMTP Delivery
Foreign connector. The threshold should be less than 250.
Queue Length
Retry Mailbox The number of messages in a retry state attempting to deliver
Delivery a message to a remote mailbox. The threshold should be less
Queue Length than 100.
Retry Non- The number of messages in a retry state in the non-SMTP
SMTP Delivery gateway delivery queues. The threshold should be less than
Queue Length 100.
Retry Remote
The number of messages in a retry state in the remote delivery
Delivery
queues. The threshold should be less than 100.
Queue Length
Unreachable The number of messages in the Unreachable queue. The
Queue Length threshold should be less than 100.
Largest The number of messages in the largest delivery queues. The
Delivery threshold value should be less than 200 for the Edge
Queue Length Transport and Hub Transport server roles.
Poison Queue The number of messages in the poison message queue. The
Length threshold value should be 0 at all times.
Transport Load Assessment Counters (HUB,EDGE)
Messages The number of messages queued in the Submission queue
Submitted Per per second. Determines current load. Compare values to
Second historical baselines.
Messages
Completed The number of messages delivered per second. Determines
Delivery Per current load. Compare values to historical baselines.
Second
Inbound Local The number of local delivery attempts per second.
Delivery Calls Determines current load. Compare values to historical
Per Second baselines.
The average number of message bytes per inbound message
Average Bytes
received. Determines sizes of messages being received for an
Per Message
SMTP receive connector.
Messages The number of messages received by the SMTP server each
Received Per second. Determines current load. Compare values to
Second historical baselines.
Messages
The number of messages sent by the SMTP send connector
Sent Per
each second. Determines current load.
Second
Items Queued
The number of messages queued for delivery per second.
for Delivery
Determines current load.
PerSecond
Inbound The number of attempts for delivering transport mail items
Message per second. Determines current load. Compare values to
Delivery historical baselines.Attempts Per
Second
Messages
The number of messages queued for delivery per second.
Queued for
Determines current load. Compare values to historical
Delivery Per
baselines.
Second
Edge Sync Counters(EDGE)
Total topology
Exchange topology updates found by EdgeSync
updates
Exchange
Total number of Exchange Servers found by EdgeSync.
servers total
Edge servers
Total number of Edge Transport servers found by EdgeSync.
total
Hub transport
Total number of Hub Transport servers found by EdgeSync.
servers total
Edge servers
Total number of Edge Transport servers leased by EdgeSync.
leased total
Edge objects
added Per The rate of Edge objects added per second by EdgeSync.
Second
Edge objects
deleted Per The rate of Edge objects deleted per second by EdgeSync.
Second
Edge objects
updated Per The rate of Edge objects updated per second by EdgeSync.
Second
Scan jobs
completed The total number of scan jobs completed successfully by
successfully EdgeSync.
total
Scan jobs
failed
The total number of EdgeSync scan jobs that failed because
because
EdgeSync could not extend its lease of an Edge Transport
could not
server.
extend lock
total
Scan jobs
failed
because of The total number of EdgeSync directory errors.
directory error
total
Scan jobs
failed
The total number of Scan jobs failed because could not lock
because
total.
could not lock
total
Source
objects The rate of Active Directory objects scanned per second by
scanned Per EdgeSync.
Second
Target objects
scanned Per The rate of Edge objects scanned per second by EdgeSync.
Second
Recipient Filter Agent Counters(EDGE)
Recipients
rejected by
Show the number of recipients rejected by recipient
recipient
validation per second.
validation Per
Second
Recipients Show the number of recipients rejected by block list per
rejected by second.block list Per
Second
Sender Filter Agent Counters(EDGE)
Messages
filtered by Show the number of messages filtered by the Sender Filter
sender filter agent per second.
Per Second
DNS queries The number of DNS queries per second performed by the
Per Second Sender Id agent.
Attachment Filtering Counters(EDGE)
Messages The number of messages that were blocked, stripped of
attachment attachments, or silently deleted (as per configuration) by the
filtered attachment filtering agent.
The number of messages per second that the attachment
Messages filtering agent blocked, stripped of attachments, or silently
filtered Per deleted. If this rate rises greatly beyond what is “normal” for
Second the Exchange server, it may indicate that the organization is
being flooded with malicious e-mail.
Content Filter Agent Counters(EDGE)
Messages The total number of messages that were deleted by Content
deleted Filter Agent.
Messages The total number of messages that were quarantined by
quarantined Content Filter Agent.
Messages The total number of messages that were rejected by Content
rejected Filter Agent.
Messages that
bypassed The total number of messages that bypass scanning.
scanning
Messages
scanned per The number of messages scanned per second.
second
Active Directory Application Mode (ADAM) Counters (EDGE)
LDAP The number of Lightweight Directory Access Protocol (LDAP)
Searches Per search requests issued per second. Used to determine the
Sec current LDAP search rate.
LDAP Writes
The rate at which LDAP clients perform write operations.
Per Sec
Edge Transport Role Counters Exchange Server Version
Attribute name Description 2007 2010 2013 2016 2019
Exchange-Agents
Agent Name The Name of the agent counters.
Average Agent
The average agent processing time in seconds per event.
Processing Time
The threshold value should be less than 20
in sec
Total Agent The total number of invocations since the last restart. The
Invocations current invocation rate.
Message Hygiene Counters
Average time taken to perform scanning of mailboxes as
Average Scan part of the message hygiene using scheduled and on-
Time demand scans. A high value could indicate a bottleneck in
scanning.
Scan Requests
The number of scan requests in this application pool’s
Rejected Per
queue that were rejected.
Second
Scan Requests
The number of scan processes currently running.
Being ScannedScan Requests The amount of time spent in processing a request.
Processing Time
Per Request
Antimalware
The amount of time taken for the Antimalware engine to
Processing Time
process an item.
Per Request
Unhealthy
Antimalware Antimalware engines with errors in engine functioning.
engines
Indicates what percentage of scan requests submitted
Scan Requests
encountered errors that prevented the processing of those
Fatal Errors
scan requests.
Scan Request The number of scan requests that timed out in the last
Timeouts minute.
Scan Processes
The number of scan processes currently running.
Running
Scan Time Per
The scan time per request.
Request
Scan Requests
Processed Per The number of scan requests processed per second.
Second
Scan Request
The time for which a scan request waits in the internal
Wait Time Per
queue.
Request
Scan Requests The number of scan requests that are currently in the
Queued internal queue.
Scan Requests The number of scan requests submitted per second,
Submitted Per including requests accepted and rejected by the scanning
Second system.
SafetyNet Counters
Resubmission Average time spent to resubmit each message when
Latency processing a Safety Net resubmit request.
SafetyNet The number of messages resubmitted from Safety Net.
Resubmission Resubmit requests are generally triggered by HA but can
Rate also be requested manually via New-ResubmitRequest.
SafetyNet
Number of resubmit requests that were made to safety net
Resubmit
during the sampling period.
Request rate
Shadow Total number of messages resubmitted from Shadow
SafetyNet Safety Net. Shadow resubmit requests occur when a
Resubmission primary Safety Net server cannot be reached for several
Rate hours.
Shadow
SafetyNet Number of shadow resubmit requests that were made to
Resubmit shadow safety net during the sampling period.
Request rate
Resubmit Total number of resubmit requests encountered per
Request rate resubmit request state.
Unified Messaging Server Role Counters Exchange
Server
Version
Attribute name Description 2007 2010
Unified Messaging Counters
Percentage of failed
mailbox connection The percentage of mailbox connection attempts that failed in the last
attempts over the last hour.
hourPercentage of inbound The percentage of inbound calls that were rejected by the Microsoft
calls rejected by the Exchange Unified Messaging service over the last hour.
um service over the
last hour
Percentage of inbound
calls rejected by the The percentage of inbound calls that were rejected by the UM worker
um worker process process over the last hour.
over the last hour
Percentage of
messages
The percentage of messages that were successfully processed by the
successfully
Microsoft Exchange Unified Messaging service over the last hour.
processed over the
last hour
Percentage of partner
voice message The percentage of voice messages for which transcription failed in the
transcription failures last hour.
over the last hour
Directory access
The number of times that attempts to access Active Directory failed.
failures
Calls disconnected on
irrecoverable internal The number of calls disconnected after an internal system error occurred.
error
The number of all UM operations that took more than six seconds to
Operations over six
complete. This is the time during which a caller was waiting for UM to
seconds
respond.
Calls disconnected by
The number of calls during which the caller disconnected while Unified
callers during um
Messaging was playing the audio hourglass tones.
audio hourglass
Total inbound calls
The total number of inbound calls that were rejected by the Microsoft
rejected by the um
Exchange Unified Messaging Service since the service was started.
service
Total inbound calls
The total number of inbound calls that were rejected by the UM Worker
rejected by the um
process since the service was started.
worker process
Call answer queued
The number of messages created and not yet submitted for delivery.
messages
Direct access failures The number of times that attempts to access Active Directory failed.
The number of times that attempts to access a Hub Transport server
Hub transport access
failed. This number is only incremented if all Hub Transport servers were
failures
unavailable.
Unhandled exceptions The number of calls that were disconnected after an internal system error
Per Second occurred in the last second.
The number of notifications that have been created and not yet submitted
Queued ocs user event for delivery. Represents the number of missed call notifications that have
notifications been generated in the Office Communications Server environment and
have not been submitted for delivery.
Mailbox server access
The number of times the system did not access a Mailbox server.
failures
Overview - Common Counters Exchange Server Version
Attribute Description 2007 2010 2013 2016 2019
name
Server Component States
Component
Specifies the Exchange Component name.
Name
State Specifies the Exchange Component Status.
Availability Specifies the availability of the Exchange Component.
Exchange ServicesService Specifies the Exchange Agent Service name.
Name
Status Specifies the Exchange Agent Service Status.
Availability Specifies the availability of the Exchange Agent Service.
AD Access Domain Controllers
Domain
The specified domain controller
Controller
The time in milliseconds that a LDAP read request takes to be
LDAP Read
fulfilled. The average value should be under 50 milliseconds.
Time
Maximum values should not exceed 100 milliseconds.
The time in milliseconds that it takes a Lightweight Directory
LDAP
Access Protocol (LDAP) search request to be fulfilled. The
Search
threshold values should be below 50 ms. Maximum values
Time
should not be higher than 100 ms.
LDAP The number of LDAP searches that returned LDAP_Timeout
searches during the last minute. The threshold value should be below 10
timed-out at all times for all roles. Higher values may indicate issues with
per Minute Active Directory resources.
Long- The number of LDAP operations on this domain controller that
running took longer than the specified threshold per minute. The default
LDAP threshold value is 15 seconds. The threshold values should be
operations below 50 ms. Higher values may indicate issues with Active
Per Minute Directory resources.
Host Performance Counters Exchange Server Version
Attribute name Description 2007 2010 2013 2016 2019
Disk Utilization
Percent Free
The percentage of free Space on the disk.
Space
Number of disk reads per second on the physical disk. This
Disk Reads Per
counter should be well under the maximum capacity for the
Second
disk device.
Number of disk writes per second on the physical disk. This
Disk Writes Per
counter should be well under the maximum capacity for the
Second
disk device.
Memory Utilization
Used Memory
The memory space used by the server
Space
Free Physical
The amount of free physical memory available.
Memory
Used Memory
The percentage of memory space used by the server
Percent
Total Visible Total amount of physical memory available to the operating
Memory Size system.
Exchange Domain Controllers Connectivity Counters
Cache Hits Per
The number of object found in cache events per second.
Second
Cache Misses The number of objects not found in cache events per
Per Second second.
LDAP Searches The number of LDAP search requests issued by a process
Per Second per second.
Outstanding
Asyncronous The number of outstanding LDAP read requests.
Reads
Memory Pages
Pages Input/sec The rate at which pages are read from disk to resolve hardpage faults.
The rate at which pages are written to disk to free up space
Pages
in physical memory. A high rate of pages output might
Output/sec
indicate a memory shortage.
The rate at which pages are read from or written to disk to
Total Pages/sec resolve hard page faults. This counter is a primary indicator
of the kinds of faults that cause system-wide delays.
The number of read operations, without regard to the
Page Reads/sec
number of pages retrieved in each operation.
The number of write operations, without regard to the
Page Writes/sec
number of pages written in each operation.
Transition Pages The rate at which the number of transition cache pages
Repurposed/sec were reused for a different purpose.
Queues Exchange Server Version
Attribute Description 2007 2010 2013 2016 2019
name
Exchange Queues *
Queue The identity of the queue in the form of \ . Learn
Name more
The current queue status. A queue can have one of the following
Status status values: Active, Connecting, Suspended, Ready, or Retry.
Learn more
Message
The number of messages in the queue.
Count
The drain rate of the queue, calculated by subtracting the value of
Velocity
Incoming Rate from the value of Outgoing Rate. Learn more
Represents how the Transport service intends to transmit the
message to the next hop, which could be the ultimate destination
of the message, or an intermediate hop along the way. The value
Delivery
External indicates the next hop for the queue is outside the
Type
Exchange organization. The value Internal indicates the next hop
for the queue is inside the Exchange organization. Possible values:
Internal, External, Undefined
The next domain where the messages hops from the current queue.
For delivery queues, the value of this field is effectively the name of
Next Hop
the queue. The value of NextHopDomain isn''t always a domain
Domain
name. For example, the value could be the name of the target
Active Directory site or database availability group (DAG).
* Metrics for Exchange Queues are mapped under Admin → Performance Polling → Optimize Data
Collection.
Exchange 2003 Performance Counters
Attribute name Description
SMTP Connections
Inbound
The total number of connections that were currently inbound.
Connections
Outbound
The number of connections that were currently outbound.
Connections
SMTP statistics
Local Retry Queue
The number of messages in the local retry queue.
Length
Remote Retry
The number of messages that were in the retry queue for remote delivery.
Queue Length
Remote Queue The number of messages that were in the remote queue.Length
Messages Pending
The number of messages that were categorized but not routed.
Routing
Messages in Local The number of messages that were currently being processed by a server event sink for
Delivery local delivery.
Currently
Undeliverable The number of messages that were reported as currently undeliverable by routing.
Messages
Categorizer Queue
The number of messages in the categorizer queue waiting to be categorized.
Length
POP & IMAP Connections
Current POP
The total number of POP connections opened since the computer was last started.
Connections
Current IMAP
The total number of IMAP connections opened since the computer was last started.
Connections
Information Store Mailbox statistics
The number of messages in the mailbox''s receive queue. The threshold value should be
Receive Queue Size
below 500 at all times.
The number of messages in themailbox''s send queue. In a server with no mail-enabled
Send Queue Size
mailbox, it should be below 10. Otherwise, it should be below 500 at all times.
Active Client
The active client logons to Mailbox Stores during the specified time period.
Logons
Client Logons The client logons to Mailbox stores during the specified time period.
Logon Operations
The number of logon operations to Mailbox stores per minute.
Per Min
Message Recipients The message delivery rate. System Monitor data should match the Exchange Load
Delivered Per min Generator predicted value for message received rate.
Messages Delivered
The message submission rate.
Per min
Messages Sent Per
The message sent rate.
min
Mailbox Used
The amount of space used by the Mailbox.
Space
Information Store Public Folder statistics
Send Queue Size The number of messag es in the public store''s send queue.
Receive Queue Size The number of messag es in the public store''s receive queue.
Active Client
The active client logons to Public Folder Stores during the specified time period.
Logons
Client Logons The client logons to Public Folder Stores during the specified time period.
Logon Operations
The number of logon operations to Public Folders per minute.
Per Min
Messages Delivered
The message delivery rate.
Per min
Message Recipients The message recipients delivery rate. System Monitor data should match the Exchange
Delivered Per min Load Generator predicted value for message received rate.
Messages Sent Per
The message sent rate.
minute
Messages
Submitted Per The message submission rate.
minute
Public Folders Used
The amount of space used by Public Folders.
Space
Information Store Connections & Users
Information Store
Active Connection The number of connections that have shown some activity in the last 10 minutes.
CountInformation Store The number of client processes connected to the information store.
Connection Count
Information Store
The number of user connectio ns that have shown some activity in the last 10 minutes.
Active User Count
MTA statistics
MTA Work Queue The number of messages in the MTA work queue. This indicates the number of messages
Length not yet processed to completion by the MTA.
MTA Message Bytes
The rate at which message bytes are processed.
Per Min
MTA TCP/IP
Received Bytes Per The rate at which bytes are received over a TCP/IP connection.
Min
MTA TCP/IP
Transmit Bytes Per The rate at which bytes are transmitted over a TCP/IP connection.
Min
MTA Total
The maximum number of recipients permitted in the MTA queues.
Recipients Queued
MTA Work Queue
The total volume of messages (in MB) stored in the message transfer agent (MTA).
Bytes
Information Store statistics
Current Pending
Messages currently pending in the MTA Queue
Local Delivery
Current message
from Messages currently in transit from MSExchangeMTA to Exchange Store
MSExchangeMTA
Currentmessages to
Messages currently in transit to MSExchangeMTA from Exchange Store
MSExchangeMTA
Messages Received
The number of messages received by the SMTP server each min
Per Min
Messages Sent Per
The number of messages sent by the SMTP server each min
Min
HSOT Cache Hits The number of objects found in cache events per second.
Directory & Event Service statistics
Pending Replication The number of directory synchronizations that are queued for this server. This counter
Synchronizations helps identify replication backlogs - the higher the number, the larger the backlog.
Remaining
The number of directory synchronizations remaining. This counter helps identify
Replication
replication backlogs - the higher the number, the larger the backlog.
Updates
Notify Queue The queue of store notifications waiting to be processed.
Address Lists
The number of entries in the Address List queue.
Queue Length
Message Transfer Agent Connections
MTA Queue Length The number of outstanding messages queued for transfer
The total volume of message content (in MB) that is stored in the queue of the Message
MTA Queued Bytes
Transfer Agent.
MTA Current The number of inbound (remotely initiated) associations between the MTA and the
Inbound connected MTA. MTAs can open multiple associations, if additional transfer throughput is
Associations necessary.
MTA Current The number of inbound (locally initiated) associations between the MTA and the
Outbound connected MTA. MTAs can open multiple associations, if additional transfer throughput is
Associations necessary.
Mail Server Monitoring
To create a Mail Server Monitor, follow the steps given below:
Click on New Monitor link. Choose Mail ServerSelect a Display Name.
Enter the IP Address or hostname of the host in which the SMTP server is running.
You can check the Secure Connection(SSL) option to enable TLS for securing data transmission between
Applications Manager & other applications.
Enter the SMTP Port number.
Enter an email address available in that SMTP server.
If the SMTP server requires authentication, specify the User Name and Password by clicking SMTP Server
requires Authentication field.
If the POP/Imap service is in a different host, specify its POP/Imap Host (host where POP service runs) and POP
Port. Also provide the authentication details User Name and Password for the POP service. If the SMTP and
POP/Imap service are running in the same host, then ignore this step. Check the Secure Connection(SSL)
option to enable TLS for securing data transmission
Enter the message to appear in the subject of the mail.
Enter the timeout in seconds.
Enter the polling interval time in minutes, in Polling Interval field.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which you want to associate Mail Server Monitor (optional).
You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers the Mail server from the network and starts monitoring them.
If you have added Monitors and not associated them with a Monitor Group, you can do this manually anytime. For
information on associating a Monitor with a Monitor Group, refer to Associating Monitor with Monitor Groups topic.
Connects to the Mail Server and performs both SMTP and POP operations, by sending and fetching test mails.
Checks both SMTP and POP servers to ensure availability.
Enables performance management by monitoring the response time of the server and updates the status
based on a given threshold.
Middleware / Portal
Applications Manager monitors middleware software servers and applications to detect performance problems
before they could affect the system. Applications Manager provides Middleware monitoring that monitors system
resources. It also provides proactive measures by notifying system operators about potential problems.
The different middleware / portal supported are:
Microsoft Message Queue (MSMQ)
Microsoft Office Sharepoint Server
WebLogic Integration
IBM WebSphere MQ
WebSphere MQ Message Broker
VMware vFabric RabbitMQ
Microsoft Biztalk
Oracle Tuxedo
Azure Service Bus
Microsoft Skype for Business
Apache Kafka
Apache ActiveMQ
Browse through the different servers that provide server information and their parameters being monitored.
Microsoft MQ (MSMQ) Monitoring
Creating a new MSMQ monitor
Prerequisites for monitoring MSMQ metrics: Click here
Using the REST API to add a new MSMQ monitor: Click here
Follow the steps given below to create a new Microsoft MQ monitor:Click on New Monitor link.
Select Microsoft MQ (MSMQ) under Middleware/Portal category.
Enter the display name of the host.
Enter the HostName of the MSMQ server.
Select the Mode of Monitoring (WMI or Powershell).
Provide the monitor-specific authentication information, such as User Name and Password.
Enter the Timeout value in seconds. The value should be between 60 and 900 seconds. However, this is
applicable only in Powershell mode of monitoring. (Default value is 300 seconds.)
Enter the polling interval time in minutes.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group with which you want to associate the Microsoft MQ server to, from the combo box
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers Microsoft MQ server from the network and starts monitoring it.
Monitored Parameters
Applications Manager monitors the critical components of Microsoft Message Queue (MSMQ) servers to detect
any performance problems. These components include message stats, session stats, Microsoft message queue
stats, etc.
Availability tab shows the availability history of the MSMQ for the past 24 hours or 30 days.
Performance tab shows the response time of the MSMQ as well as the health status and events for the past 24
hours or 30 days.
List view tab lists all the MSMQ servers monitored by Applications Manager along with their overall
availability and health status. You can also perform bulk admin configuration from this view.
Click on the individual monitors listed to view detailed performance metrics.
Parameters Description
Monitor Information
Name The name of the Microsoft Message Queue Server (MSMQ) monitor.
Type Describes the type of monitor.
Health Represents the health (Clear, Warning, Critical) status of the MSMQ server.
Last Polled at Specifies the time at which the last poll was performed.
Next Poll at Specifies the time at which the next poll is scheduled.
Shows the overall availability status of the monitor for the day. You can also
Today''s Availability
view 7/30 reports and the current availability status of the monitor.
Microsoft Message Queue Services
Service Name The name of the message queue service.
Status The current status of the message queue service.
Messages Stats
The rate at which incoming Message Queuing messages are placed in queues
Incoming messages/sec
on the selected computer by the Message Queuing service.
The rate at which outgoing Message Queuing messages are sent from the
Outgoing messages/sec
selected computer by the Message Queuing service.
The total number of incoming Message Queuing messages placed in queues
MSMQ Incoming Messages
on the selected computer by the Message Queuing service.
The total number of outgoing Message Queuing messages sent from the
MSMQ Outgoing Messages
selected computer by the Message Queuing service.
The total number of bytes in all Message Queuing messages residing in active
Total bytes in all Queues
queues on the selected computer.
The total number of Message Queuing messages residing in active queues on
Total messages in all Queues
the selected computer.
Session Stats
Sessions The total number of open network sessions involving the selected computer.
IP Sessions The number of open IP sessions involving the selected computer.
The number of open incoming multicast sessions involving the selected
Incoming Multicast Sessions
computer.Parameters Description
The number of open outgoing multicast sessions involving the selected
Outgoing Multicast Sessions
computer.
Outgoing HTTP Sessions The number of open outgoing HTTP sessions involving the selected computer.
Microsoft Message Queue Stats
Queue Name The name of the Message queue.
The total number of bytes in all Message Queuing messages that currently
Bytes in Journal Queue
reside in the selected journal.
The total number of bytes in all Message Queuing messages that currently
Bytes in Queue
reside in the selected queue.
The total number of Message Queuing messages that currently reside in the
Messages in Journal Queue
selected journal.
The total number of Message Queuing messages that currently reside in the
Messages in Queue
selected queue.
Azure Service Bus Monitoring (Classic) (Deprecated)
Azure Service Bus is a cloud based messaging system for connecting applications, services and devices
irrespective of their locations. Applications running on Azure, on-premise systems, or both, can commmunicate,
message delivery can be managed and numerous applications can be accessed with minimum response time.
With Applications Manager, monitoring Azure Service Bus becomes more easier. Usage and throughput statistics
of Queues, Relays, Topics, Event Hubs and Subscriptions are accurately displayed that help you track your
connectivity and monitor the exchange of messages between various devices. Configure alarms for various
metrics and get notified in case of irregularities and take necessary corrective actions.
Creating a new monitor
To add an Azure Service Bus Monitor for a Namespace, follow the steps given below:
Enter the Subscription ID for your Microsoft Azure account.
Enter the Service Bus Namespace to be monitored.
Specify a Timeout interval in seconds.
Specify the Polling Interval in minutes.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Azure Service Bus under
the Middleware/Portal Table. Displayed is the Azure Service Bus bulk configuration view distributed into three
tabs:
Availability tab, gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Monitored Parameters
Click on the monitor name to see all the server details listed under the following tabs:
Monitor Information
Overview
Queues
Topics
Subscriptions
Event Hubs
Relays
Monitor InformationLists out all the basic details about the monitor like monitor name, associated groups, next poll time, last poll time
etc. Custom fields can be added or removed from here.
Overview
Group/ Table Name Metric Description
Namespace The Service Bus Namespace name.
The location/ region of the Service Bus
Location
Namespace.
Current status of the Service Bus
Namespace. Can be one of the
following values:
Active
Status
Creating
Suspended
Service Bus Namespace Deleting
Configuration
Whether the Namespace is enabled or
Namespace Enabled
disabled.
Messaging
Namespace Type
Notification hub
Specifies the Resource Group of the
Resource Group
Service Bus Namespace.
Specifies whether Event Hub is
Event Hub Enabled
enabled or not.
Queues Number of Queues being used.
Topics Number of Topics being used.
Namespace Usage Subscriptions Number of Subscriptions being used.
Event Hubs Number of Event Hubs being used.
Relays Number of Relays being used.
Queues
Group/ Table Name Metric Description
Queue Usage Queue Specifies the Name of the Queue.
Specifies the percentage of space
Used Percentage
used in Queue.
Specifies the percentage of space
Free Percentage
free in the Queue.
Specifies the size used in the Queue in
Used Size (MB)
MB.
Specifies the free size in the Queue in
Free Size (MB)
MB.
Length of the Queue specifies the
Length total number of messages in the
Queue.
The number of active messages in the
Active Message Count
Queue.
The number of messages that are
Dead Letter Message Count
dead letters.
The number of scheduled messages
Scheduled Message Count
in Queue.
Transfer Dead Letter Message The number of messages transferred
Count into dead letters.Transfer Message Count The number of messages transferred
to another Queue
Current state of the Queue entity.
Active
Disabled
Status SendDisabled
ReceiveDisabled
When the Queue is disabled, it cannot
be used to send or receive messages.
Queue Specifies the name of the Queue.
Rate of incoming messages in the
Incoming Rate (Messages/Sec)
Queue.
Rate of outgoing messages in the
Outgoing Rate (Messages/Sec)
Queue.
Queue Throughput Failed Requests Total number of requests failed.
Requests Failed Internal Server Number of requests failed due to
Errors internal server errors.
Requests failed -Server Busy Number of requests failed due to
Errors Server Busy errors
Number of requests failed due to
Requests failed -Other Errors
Other errors.
Topics
Group/ Table Name Metric Description
Topic Specifies the Name of the Topic
Specifies the percentage of space
Used Percentage
used in Topic.
Specifies the percentage of space
Free Percentage
free in the Topic.
Specifies the size used in the Topic in
Used Size (MB)
MB.
Specifies the free size in the Topic in
Free Size (MB)
MB.
The number of active messages in the
Active Message Count
Topic.
The number of messages that are
Dead Letter Message Count
dead letters.
Topic Usage
The number of scheduled messages
Scheduled Message Count
in Topic.
Transfer Dead Letter Message The number of messages transferred
Count into dead letters.
The number of messages transferred
Transfer Message Count
to another Topic.
Current state of the Queue entity.
Active
Disabled
Status
SendDisabled
When the Topic is disabled, it cannot
be used to send or receive messages.
Topic Throughput Topic Specifies the name of the Topic
Incoming Rate (Messages/Sec) Rate of incoming messages in theTopic.
Failed Requests Total number of requests failed.
Requests Failed Internal Server Number of requests failed due to
Errors internal server errors.
Requests failed -Server Busy Number of requests failed due to
Errors Server Busy errors
Number of requests failed due to
Requests failed -Other Errors
Other errors.
Subscriptions
Group/ Table Name Metric Description
Specifies the Name of the
Subscription
Subscription
Specifies the name of the Topic to
Topic
which the Subscription belongs.
Specifies the percentage of space
Used Percentage
used in Subscription.
Specifies the percentage of space
Free Percentage
free in the Subscription.
Specifies the size used in the
Used Size (MB)
Subscription in MB.
Specifies the free size in the
Free Size (MB)
Subscription in MB.
Length of the Subscription specifies
Length the total number of messages in the
Subscription.
The number of active messages in the
Active Message Count
Subscription Usage Subscription.
The number of messages that are
Dead Letter Message Count
dead letters.
The number of scheduled messages
Scheduled Message Count
in Topic.
Transfer Dead Letter Message The number of messages transferred
Count into dead letters.
The number of messages transferred
Transfer Message Count
to another Subscription.
Current state of the Queue entity.
Active
Disabled
Status
SendDisabled
When the Subscription is disabled, it
cannot be used to send or receive
messages.
Subscription Throughput Specifies the name of the
Subscription
Subscription
Rate of incoming messages in the
Incoming Rate (Messages/Sec)
Subscription.
Failed Requests Total number of requests failed.
Requests Failed Internal Server Number of requests failed due to
Errors internal server errors.
Requests failed -Server Busy Number of requests failed due to
Errors Server Busy errors
Requests failed -Other Errors Number of requests failed due to
Other errors.Event Hubs
Group/ Table Name Metric Description
Event Hub Specifies the name of the Event Hub.
Rate of incoming messages in the
Incoming Rate (Messages/Sec)
Event Hub.
Rate of outgoing messages in the
Outgoing Rate (Messages/Sec)
Event Hub.
Failed Requests Total number of requests failed.
Event Hub Throughput
Requests Failed Internal Server Number of requests failed due to
Errors internal server errors.
Requests failed -Server Busy Number of requests failed due to
Errors Server Busy errors
Number of requests failed due to
Requests failed -Other Errors
Other errors.
Relays
Group/ Table Name Metric Description
Listener Specifies the name of the listener.
Specifies the type of Relay
used.Supported Relays are:
RelayType NetTcp
NetOneWay
Http
Number of listeners for the particular
Listener Count
Relay.
The data size in bytes sent through
Relay Bytes
the Relay.
Specifies the number of connection
Listeners Connection Attempts
attempts made by the listener.
Specifies the number of disconnects
Disconnects
by the listener.
Already Exists errors Number of Already Exists errors.
Does Not Exist errors Number of Does Not Exist errors.
Internal Errors Number of Internal Errors.
Other Errors Number of Other Errors.
Quota Exceeded errors Number of Quota Exceeded errors.
Unauthorized Errors Number of Unauthorized Errors.
Up- The listener is activeDown- The
Availability
listener is inactive.
Microsoft Office Sharepoint Servers
Office Sharepoint - Overview
Applications Manager provides comprehensive monitoring for key SharePoint performance indicators. Monitor
underlying server resources for CPU, memory, and disk constraints as well as SharePoint services, requests queued
and infrastructure performance for virtual machines and server hardware health. The monitoring details of
Microsoft Office Sharepoint Servers are represented graphically that helps to understand the parameters with
ease. Administrators can configure thresholds to the attributes monitored, pinpoint and fix problems before users
notice performance issues.Office Sharepoint - Adding a new monitor
Microsoft Office SharePoint Server Versions Supported: 2007, 2010, 2013, 2016, and 2019
Prerequisites for monitoring Microsoft Office SharePoint Server: Click here to know the prerequisites for
monitoring MS Office SharePoint server. To use Powershell for data collection, make sure the proper steps have
been followed to enable powershell remoting.
Attributes Monitored: Refer SharePoint Server Parameters to know more about the attributes monitored.
To create a Office SharePoint Server Monitor, follow the steps given below:
Click on New Monitor link.
Select MS Office SharePoint.
Give the Display Name.
Enter the Hostname of the host where Office SharePoint Server runs.
Select the Version of Microsoft Office SharePoint Server - 2007, 2010, 2013, 2016 or 2019.
Choose the Features to be monitored for the different versions (Click on the Features textbar to display a drop-
down features menu).
To use powershell for data collection, tick the Use Powershell checkbox. Checking this option will display
Installation Type option:
SharePoint Farm Server: Select this option if server has Farm setup. If the monitor is added as a
SharePoint Farm Server setup, Applications Manager will discover all other servers in the farm and will
add them automatically as separate monitors. A monitor group will be created for the farm and all
discovered monitors will be added in the monitor group with the name same as the Farm name.
PowerShell is required for discovering servers in the farm.
SharePoint Server: Select this option if server has Stand-Alone setup.
You can enter your own credential details or select preconfigured credentials details in Credentials Manager. If
you wish to enter your own credentials, specify username and password details for this monitor.
Enter the Username and Password for the server.
Set the Poll interval.
If you are adding a new monitor from an Admin Server, select a Managed Server.
Choose the Monitor Group from the combo box with which you want to associate MS Office SharePoint server
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers MS Office SharePoint server from the network and starts monitoring
them.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on MS Office SharePoint under
the Middleware/Portal Table. Displayed is the MS Office SharePoint bulk configuration view distributed into three
tabs:
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the monitor name to see all the server details listed under the following tabs:
Performance Overview
Web Applications
Databases
Timer Jobs
Access Services
Visio Web Access Services
InfoPath Services
Excel Services (For Versions 2007, 2010 and 2013)
Office Search Gatherer (For Versions 2007, 2010 and 2013)
Search Services (For Version 2016 and 2019)
Performance Overview
Parameter DescriptionActive Server Pages
The total number of errors per second including runtime, preprocessor and
Errors/sec
script compilation errors.
Requests Queued The number of requests waiting for service from the queue.
Requests Rejected The total number of requests not executed due to insufficient resources.
Requests/sec The number of requests executed per second.
Current Sessions The current number of sessions being serviced.
Transactions/sec Transactions started per second.
Pending Transactions The number of transactions still in progress.
Server Stats
Free Memory in MB The physical memory available for allocation.
Page Faults Per Sec The number of times that data was not found in memory per second.
Percentage of Committed Bytes
The ratio committed to commit limit.
In Use
Percentage of Processor Time The percent processor time.
SharePoint Server Services
Service Name The name of the SharePoint Server Service.
Status The status of the service.
Availability The availability status of the service
Office Search Archival Plugin (For Versions 2010 and 2013)
The current number of queues that are committing changes and completing
Queries Commiting
uploads.
Queues Filtering The current number of queues that are being used by the filter threads.
The current number of queues that are waiting to flush data to the property
Queues Waiting
store.
Retried Microsoft Office
The number of documents which were marked for retry from the plugin.
Sharepoint Serverss
Total Microsoft Office Sharepoint
The total number of documents which have used the first queue.
Serverss
Blocked Microsoft Office
The number of documents waiting for a queue.
Sharepoint Serverss
Active Queue The currently active queue.
Bulk Insert Sessions The number of active bulk insert sessions to the database server.
Office Search Archival Plugin (For Version 2007)
Active Docs in First Queue The number of documents actively using the first queue.
Total Docs in First Queue The total number of documents which have used the first queue.
Active Docs in Second Queue The number of documents actively using the second queue.
Total Docs in Second Queue The total number of documents which have used the second queue.
Total Microsoft Office Sharepoint
The number of documents processed.
Serverss
Error Microsoft Office Sharepoint
The number of documents which returned errors from the plug-in.
Serverss
Active Queue The currently active queue.
Bulk Insert Sessions The number of active bulk insert sessions to the database server.
Web Content Management-Publishing Cache
Publishing Cache Hit Ratio The ratio of hits to misses on the Publishing cache.
The total number of items that have been removed from the Publishing cache
Total Object Discards
due to cache compaction.
Publishing Cache Hits / sec The hit rate on the Publishing cache.
Publishing Cache Misses / sec The miss rate on the Publishing cache.
Publishing Cache Flushes / sec The rate that we are updating the cache due to site changes.Web Applications
Parameter Description
SharePoint Web Applications
DisplayName The display name of the web application.
URL The URL to access the web application.
The number of Content Databases processed during profile
Content database
synchronization.
Jobs Succeeded The number of timer jobs succeeded related to the web application
Jobs Failed The number of timer jobs failed related to the web application
Status The status of the web application, if it is online or offline.
Databases
Parameter Description
SharePoint Content Databases
Name The name of the content database
Server The server in which the database is stored
Disk Size Required (GB) The size allocated by the database on disk
Web Application The web applications which use the database
Current Site Count The number of sites that are stored in the database
Status The status of the content database, if it is online or offline
Timer Jobs
Parameter Description
Timer Jobs
Jobs Succeeded The total number of timer jobs succeeded
Jobs Failed The total number of timer jobs failed
SharePoint Failed Timer Jobs
DisplayName The name of the timer job
Status The status of the content database (online or offline).
LastRunTime The last time when the timer job was executed
ErrorMessage The error due to which the timer job failed.
Access Services
Parameter Description
Access Data Services Applications Server
The total number of active requests being processed by Excel
Active Requests
Calculation Services at sampling time.
The number of active sessions by Excel Calculation Services at sampling
Active Sessions
time.
The average processing time for a request by Excel Calculation Services
Average Request Processing Time
between sampling times.
Access Services Data Access Layer
Average Data Fetch Duration The average time (in seconds) that is spent to retrieve data.
Average Delete Duration The average time (in seconds) that is spent to delete data.
Average Insert Duration The average time (in seconds) that is spent to insert data.
Average Update Duration The average time (in seconds) that is spent to update data.
Failed Insert Requests / sec The current number of insert requests that failed per second.
Failed Delete Requests / sec The current number of delete requests that failed per second.Get Data Requests / sec The current number of data query requests per second.
Delete Requests / sec The current number of delete requests per second.
Insert Requests / sec The current number of insert requests that are active.
Update Requests / sec The current number of update requests per second.
Visio Web Access Services
Parameter Description
Visio Web Access Services
The average processing time for a request to Excel Web Front End
Request Processing Time
component. Large value indicates high response time.
The total number of requests per second to Excel Web Front End
Requests Received / Sec
component.
The number of requests that are returned with errors. Higher rate of
Requests with Errors / Sec errors indicate unexpected behavior of an Excel Calculation Services
that directly affects the performance.
InfoPath Services
Parameter Description
Infopath Forms Services
The average time to complete a form-filling session, summed up over
Average Session Duration
all transactions in the form-filling session.
Data Connection Submit Failure Rate The rate of failures for data connection submits in form-filling sessions.
Session Completed Rate The rate at which form-filling sessions completed.
Transactions Completed Rate The rate at which transactions completed in form-filling sessions.
Excel Services (For Versions 2007, 2010 and 2013)
Parameter Description
Excel Services Web Frontend
The number of active requests being processed on Excel Calculation
Active Requests - Excel Web FrontEnd
Services at sampling time
The number of requests received per second on Excel Calculation
Requests Per Second
Services between sampling times
Excel Webaccess
The Excel Web Access Average Request time between the last two
Excel Web Access Request Time
samples
The number of requests for chart images served by Excel Web Access
Chart Image Requests per Second
per second
The average time it takes between the request for a chart image and the
Average Chart Image Request Time
issuance of the response to the web browser by Excel Web Access
Excel Calculation Services
Requests With Errors / Sec - Excel The number of requests that are returned with errors per second on
Calculation Excel Calculation Services between sampling times
The average number of sessions opened per second between the last
Sessions Per Second
two samples
Cached Charts Requested Per Sec The number of charts that are provided from a cached image
The number of active sessions on Excel Calculation Services at
Active Sessions
sampling time
Rendered Charts Requested Per Sec The number of chart requests per second
The number of active requests being processed on Excel Calculation
Active Requests
Services at sampling time
Requests Received per Sec The number of requests received per second on Excel CalculationServices between sampling times
Office Search Gatherer (For Versions 2007, 2010 and 2013)
Parameter Description
Office Search Gatherer
Delayed Microsoft Office Sharepoint
The number of documents delayed due to site hit frequency rules.
Serverss
The number of threads waiting for a response from the filter
Threads Accessing Network
process.
Idle Threads The number of threads waiting for documents.
Microsoft Office Sharepoint Serverss
The number of documents that will be retried after time-out.
Delayed Retry
Search Services (For Version 2016 and 2019)
Parameter Description
Office Search Gatherer
The number of documents delayed due to site hit frequency
Delayed Microsoft Office Sharepoint Serverss
rules.
The number of threads waiting for a response from the filter
Threads Accessing Network
process.
Idle Threads The number of threads waiting for documents.
Microsoft Office Sharepoint Serverss Delayed
The number of documents that will be retried after time-out.
Retry
Search Query Processor
Query Client Failures The number of client failures per second.
Query Consecutive Failures The number of consecutive query failures per second.
Query Direct Probe Failures The number of Probe Failures per second.
Query Load Balancer Errors The number of Load Balancer Errors per second.
Query Load Balancer Retries The number of Load Balancer Retries per second.
Query Network Failures The number of Network Failures per second.
Query Server Failures The number of Server Failures per second.
Note: To fetch data in the following tabs ''Web Applications'', ''Databases'', ''Timer Jobs'' & ''SharePoint
Services'', make sure you have selected the Use Powershell checkbox when adding the monitor. Data for these
tabs cannot be collected using ''WMI'' mode. To view the above said tabs for an existing monitor, click Edit
Monitor and select the Use Powershell option for datacollection. For more help on enabling Powershell
Remoting, click here.
WebLogic Integration Server Monitoring
Creating a new WebLogic Integration Server monitor
Supported Versions: WebLogic Integration Server 8.x
Prerequisites for monitoring WebLogic Integration Server metrics: Click here
Using the REST API to add a new WebLogic Integration server monitor: Click here
To create a WebLogic Integration Server monitor, follow the steps given below:
Click on New Monitor link.
Select WebLogic Integration.
Enter the IP Address/hostname of the host.
Enter the SubNetMask of the network.
Enter the port number in which WebLogic Integration Server is running.
Enter the polling interval time in minutes.If you are adding a new monitor from an Admin Server, select a Managed Server.
Provide the monitor-specific authentication information, such as user name and password.
Note: WebLogic Integration Server needs some additional configuration and conditions to be followed for
monitoring.
For monitoring WebLogic Integration Server 8.x, you should set the weblogic.disableMBeanAuthorization
and weblogic.management.anonymousAdminLookup system variable to true for enabling data
collection. Follow the steps given below:
Edit startWLS.cmdsh present in the /server/bin directory and add the following
argument -Dweblogic.disableMBeanAuthorization=true and -
Dweblogic.management.anonymousAdminLookupEnabled=true (click on the link to view the sample
startWLS.cmdsh file)
Restart the WebLogic Integration Server for the changes to take effect.
Copy weblogic.jar from folder /weblogic81/server/lib in Remote WebLogic server version 8 and place
it under \working\classes\weblogicversion8 folder in the machine
where Applications Manager is running.
Choose the Monitor Group from the combo box with which you want to associate WebLogic Integration Server
Monitor (optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers WebLogic Integration server from the network and starts monitoring
them.
Monitored Parameters
WebLogic Integration servers are monitored based on a parameters/ attributes like Business Process Details,
Application Integration details & Message Broker details. These attributes provide information about the
functioning of WebLogic Integration server monitor and you can receive alarms based on the thresholds
configured on the attributes of the server.
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
Click on the individual monitors listed, to view the following information.
Parameters Description
Business Process Details
Process
Name of the Process.
Name
Health Health of the process, depends on the below given parameters.
Avg
Specifies the average elapsed time of the process. Elapsed time is the time elapsed since all the
Elapsed
instances started.
Time
Completed
Specifies the number of instances completed per minute.
Instances
SLA
Exceeded Shows the number of instances where SLA exceeded per minute.
Instances
Running
Shows the number of instances running currently per minute.
Instances
Aborted
Shows the number of instances that were aborted - threw an unhandled exception per minute.
Instances
Frozen Shows the number of instances running frozen - failed but can be unfrozen per minute. When an
Instances instance is unfrozen, it resumes from the point where it failed.
Terminated
Shows the number of instances that were terminated per minute.
Instances
Application Integration Details
AppView
Application View ID
Name
Health Health of the Application
Service Number of service invocations since the service counter was last resetCount
Service Number of service errors since the service counter was last reset plus the number of event delivery
Error Count errors since the event counter was last reset.
Avg. Average elapsed time in milliseconds for service invocations. This number averages elapsed time
Service for both synchronous and asynchronous services. For asynchronous services, elapsed time includes
Elapsed only time spent communicating with the adapter and excludes time spent waiting on the
Time asynchronous request queue..
Event Count Number of events delivered since the event counter was last reset.
Event Error
Number of event delivery errors since the event counter was last reset.
Count
Message Broker Details
Channel
Specifies the name of the Channel
Name
Specifies the health of the Channel, depends on the Message Count, Subscriber Count & Dead
Health
Letter Count
Message
Specifies the number of messages delivered to this channel.
Count
Subscriber
Specifies the number of process or Web service types that can subscribe to the channel.
Count
When the Message Broker is unable to determine the URI to send a message to (that is, no
Dead Letter subscribers are found), the message is sent to the appropriate deadletter channel:
Count /deadletter/xml, /deadletter/string, or /deadletter/rawData. The Dead Letter Count specifies the
number of messages sent to the dead letter channels since the count was last reset.
IBM WebSphere MQ Monitoring
Creating a new IBM MQ monitor
Prerequisites for monitoring IBM MQ metrics: Click here
Using the REST API to add a new IBM MQ monitor: Click here
To create a IBM WebSphere MQ Monitor, follow the steps given below:
Click on New Monitor link.
Enter the Queue Manager Name.
Give the Hostname of the host where IBM WebSphere MQ runs.
Enter the Listener Port.
Give the Coded Character Set Identifier (CCSID).
Enter the ServerConnection Channel.
SSL Enabled checkbox - If SSL authentication is enabled on the server connection channel, then select this
option and also provide SSL Cipher specifications. To configure SSL authentication in Applications Manager,
refer here.
Authentication Enabled checkbox - Provide the monitor-specific authentication information, such as
Username and Password.
If the timezone of the MQ server is different from that of Applications Manager, select the appropriate
Timezone from the dropdown. If both have the same timezone, then choose the timezone as Default.
Filter System Objects checkbox - Add the System Objects to Monitor. This option to Include / Exclude the
SYSTEM Queues, Channels and Inactive Channels is added will be helpful in reducing unnecessary data in
monitor details page. User can use either INCLUDE_QUEUES or EXCLUDE_QUEUES, INCLUDE_CHANNELS or
EXCLUDE_CHANNELS and INCLUDE_INACTIVE_CHANNELS: true/false.
INCLUDE_QUEUES: SYSTEM.DEAD.*, *.ADMIN.COMMAND.QUEUE
EXCLUDE_CHANNELS: SYSTEM.AUTO.SVRCONN
INCLUDE_INACTIVE_CHANNELS:true/false. (Note: if this entry is not available in filters then it will be
considered as false by default.)
ConfigManagerProxy.jar located at \classes directory.
ibmjsseprovider2.jar located at \jre\lib directory.
Check the Discover Message Broker checkbox to discover the broker. For Version10.x and Above, you can
provide the Broker Port. If Broker Authentication is Enabled, provide the Broker username and password.
Set the Polling Interval.
Click Test Credential.
If you are adding a new monitor from an Admin Server, select a Managed Server.Choose the Monitor Group from the combo box with which you want to associate IBM WebSphere MQ Monitor
(optional). You can choose multiple groups to associate your monitor.
Click Add Monitor(s). This discovers IBM WebSphere MQ from the network and Applications Manager starts
monitoring it.
Know the Prerequisites that are required to monitor IBM WebSphere MQ ( jar files must be added to the
respective locations).
Discover Message Broker checkbox:
To discover Message Broker, the following jars are required: Copy the two jar files to \working\jre\lib\ext directory.
Monitored Parameters
IBM WebSphere MQ servers are monitored based on the attributes such as listener stats, channel monitoring, etc.
and the different web applications and EJB deployed in the server. You can also monitor the operation of the queue
managers through event logs. The monitoring details of IBM WebSphere MQ server are represented graphically
that helps to understand the parameters with ease. You can also configure thresholds to the attributes monitored
by the server based on these details.
Availability tab gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view tab enables you to perform bulk admin configurations.
The WebSphere MQ server attributes monitored are classified under the following tabs in Applications Manager:
Monitor Information
Performance Overview
Queues
Channels
Listeners
Services
Event Log
Configuration
Monitor Information
Parameter Description
Name The Display name of the Monitor
Health Represents the health status
Last Polled at Time at which the previous poll had started
Next Poll at Time at which the next poll has been scheduled
Availability Shows the current status of the server - available or not available.
Performance Overview
Parameter Description
Name The Display name of the monitor
Health Represents the health status
Command Server Specifies the status the command server. It used to check whether the command server on
Status the target queue manager is running or not
Channel Initiator Specifies the status the channel initiator. It used to check whether the channel initiator on
Status the target queue manager is running or not
Active Connections The current number of connections to the queue manager.
Graphical View of Count of events occurred in the below category in last data collection.
Events Count
Queue Manager
Channel
PerformanceConfiguration
Command
Logger
Queues
Parameter Description
Queue Monitoring
Queue Name Name of the Queue
Current Depth Current queue depth.
% of Queue
Percentage of Queue Depth occupied against the max Queue Depth.
Occupied
Open Input Count Open input count (parameter identifier: MQIA_OPEN_INPUT_COUNT).
Open Output Count Open output count (parameter identifier: MQIA_OPEN_OUTPUT_COUNT)
Health Health of the Queue based on all the above attributes
Queue Usage Graph Graphical view queue depth percentage against the max Queue Depth
% of Queue Free Percentage of Queue Depth free against the max Queue Depth
It indicates whether there are any uncommitted changes (puts and gets) pending for the
queue.
Uncommitted
Messages YES - There are uncommitted changes pending.
NO - There are no uncommitted changes pending.
The interval, in seconds, between messages being put on the queue and then being
Latency
destructively read.
It indicates whether the triggering on the queue enabled or not.
Trigger Control On triggering enabled for this queue.
Off triggering not enabled for this queue.
Queue Statistics
Queue Name Name of the Queue
Last Get Time Date and time at which the GET operation was last performed.
Last Get Since Amount of time elapsed since the last GET operation was performed (in minutes).
Last Put Time Date and time at which the PUT operation was last performed.
Last Put Since Amount of time elapsed since the last PUT operation was performed (in minutes).
Oldest Message Age The age of the oldest message on the queue (in seconds).
Channels
Parameter Description
Channel
Name of the Channel
Name
Status Status of the channel - running
Bytes Sent Number of bytes sent
Bytes
Number of bytes Received
Received
Buffers Sent Number of buffers sent
Buffers
Number of buffers Received
Received
Availability of Channel,based on the status attribute.If the status of the channle is RUNNING then
Availability it is considered to be available .If the channel is in other states
then it is considered to be down.
Health Health of the Channel based on all the above attributes
Compression The amount of time per message, displayed in milliseconds, spent during compression orTime decompression.
Compression
Rate of compression achieved in percentage.
Rate
Listeners
Parameter Description
Listener Name Specifies the name of the listener
The current status of the listener. The value can be:
Initializing
Status
Running
Stopping
Session Count The number of sessions that the listener can use. This is valid only on Windows.
Backlog The number of concurrent connection requests that the listener supports.
Health Health of the Listener based on all the above attributes
Services
Parameter Description
Name Name of the service
Specifies on which mode the service was started
Manual - The service is not to be started automatically or stopped automatically. It is to be
controlled by user command.
Mode Queue Manager - The service is to be started and stopped at the same time as the queue
manager is started and stopped
Queue Manager Start - The service is to be started at the same time as the queue manager is
started, but is not request to stop when the queue manager is stopped.
Type of the service
Type Server - Only one instance of the service can be executed at a time
Command - Multiple instances of the service can be started
Start Time Specifies at which time the service was started.It is applicable only for Server type of service
Alteration
Specified at which time the service configuration was last altered.
Time
Status of the service:
Starting
Status Running
Stopped
It is applicable only for the server type of service
Event Log
WebSphere MQ events provide information about errors, warnings, and other significant occurrences in a queue
manager. You can monitor the operation of the queue managers by analyzing these events. When an event occurs,
the queue manager puts an event message on the appropriate event queue. The event message contains
information about the event.
Search Options :
We have provided the On-demand event search with multiple search options in ''Event Log'' tab. You can also export
the event search result to PDF.
Event Category
From Date
To DateEvent Type
Any keyword in the event message
Note:
All the messages in the event queue will be cleared when you restart the queue manager.
If the event queue reaches the max depth limit then the further events will not be stored in the queue. So
set the threshold for ''% of Queue Occupied'' property for the event queues to avoid loss of event message.
All the events are not enabled by default. You can check the enabled or disabled events in the Event Log
tab of the MQ monitor details page. Events can be enabled using MQSC commands.
Enable only necessary events. Because it will slightly affect the performance of the queue manager. Check
the following link to control events: http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?
topic=%2Fcom.ibm.mq.csqzax.doc%2Fmo10670_.htm
Currently, we are only displaying the count of events occurred in each category. We do not have the option
to monitor the events.
Events & Corresponding Queues
Events Queues
SYSTEM.ADMIN.QMGR.EVENT Local, Remote, Inhibit, Authority, Start & Stop
SYSTEM.ADMIN.CHANNEL.EVENT IMS Bridge, Channel, SSL
SYSTEM.ADMIN.PERFM.EVENT Performance
SYSTEM.ADMIN.CONFIG.EVENT Configuration
SYSTEM.ADMIN.COMMAND.EVENT Command
SYSTEM.ADMIN.LOGGER.EVENT Logger
Event Categories:
Events Queues
Event Name Identifier Reason Code
Start and Stop Events Queue Manager Active MQRC_Q_MGR_ACTIVE 2222
Queue Manager Not Active MQRC_Q_MGR_NOT_ACTIVE 2223
Event Name Identifier Reason Code
Queue Depth High MQRC_Q_DEPTH_HIGH 2224
Queue Depth Low MQRC_Q_DEPTH_LOW 2225
Performance Events
Queue Full MQRC_Q_FULL 2053
Queue Service Interval High MQRC_Q_SERVICE_INTERVAL_HIGH 2226
Queue Service Interval OK MQRC_Q_SERVICE_INTERVAL_OK 2227
Event Name Identifier Reason Code
Change Object MQRC_CONFIG_CHANGE_OBJECT 2368
Configuration Events Create Object MQRC_CONFIG_CREATE_OBJECT 2367
Delete Object MQRC_CONFIG_DELETE_OBJECT 2369
Refresh Object MQRC_CONFIG_REFRESH_OBJECT 2370
Channel Auto Definition
DISABLED
Events
Channel Events Reason
Event Name Identifier
Code
Channel Activated MQRC_CHANNEL_ACTIVATED 2295
Channel Auto-Definition
MQRC_CHANNEL_AUTO_DEF_ERROR 2234
Error
Channel Auto-Definition OK MQRC_CHANNEL_AUTO_DEF_OK 2233
Channel Blocked MQRC_CHANNEL_BLOCKED 2577Channel Conversion Error MQRC_CHANNEL_CONV_ERROR 2284
Channel Not Activated MQRC_CHANNEL_NOT_ACTIVATED 2296
Channel Not Available MQRC_CHANNEL_NOT_AVAILABLE 2537
Channel Started MQRC_CHANNEL_STARTED 2282
Channel Stopped MQRC_CHANNEL_STOPPED 2283
Channel Stopped By User MQRC_CHANNEL_STOPPED_BY_USER 2279
Event Name Identifier Reason Code
Command Events MQSC command is executed MQRC_COMMAND_MQSC 2412
PCF command is executed MQRC_COMMAND_PCF 2413
Event Name Identifier Reason Code
SSL Events Channel SSL Error MQRC_CHANNEL_SSL_ERROR 2371
Channel SSL Warning MQRC_CHANNEL_SSL_WARNING 2552
Reason
Event Name Identifier
Code
Default Transmission Queue Type
MQRC_DEF_XMIT_Q_TYPE_ERROR 2198
Error
Default Transmission Queue Usage
MQRC_DEF_XMIT_Q_USAGE_ERROR 2199
Error
Queue Type Error MQRC_Q_TYPE_ERROR 2057
Remote Events Remote Queue Name Error MQRC_REMOTE_Q_NAME_ERROR 2184
Transmission Queue Type Error MQRC_XMIT_Q_TYPE_ERROR 2091
Transmission Queue Usage Error MQRC_XMIT_Q_USAGE_ERROR 2092
Unknown Default Transmission
MQRC_UNKNOWN_DEF_XMIT_Q 2197
Queue
Unknown Remote Queue Manager MQRC_UNKNOWN_REMOTE_Q_MGR 2087
Unknown Transmission Queue MQRC_UNKNOWN_XMIT_Q 2196
Event Name Identifier Reason Code
Authority Events
Not Authorized Type MQRC_NOT_AUTHORIZED 2035
Event Name Identifier Reason Code
Inhibit Events Get Inhibited MQRC_GET_INHIBITED 2016
Put Inhibited MQRC_PUT_INHIBITED 2051
Event Name Identifier Reason Code
Logger Events
Logger Status MQRC_LOGGER_STATUS 2411
Event Name Identifier Reason Code
Alias Base Queue Type Error MQRC_ALIAS_BASE_Q_TYPE_ERROR 2001
Local Events
Unknown Alias Base Queue MQRC_UNKOWN_ALIAS_BASE_Q 2082
Unknown Object Name MQRC_UNKNOWN_OBJECT_NAME 2085
Event Name Identifier Reason Code
Bridge Events Bridge Started MQRC_BRIDGE_STARTED 2125
Bridge Stopped MQRC_BRIDGE_STOPPED 2126
Configuration
Parameter Description
Name The Display name of the Monitor
Queue Manager Name of the Queue Manager
Command Queue Name of the Command Input QueueDead Letter Queue Name of the Dead Letter Queue
Transmission Queue Name of the Transmission Queue
Max length of Message Specifies length of the longest message that the queue manager can handle
Specifies the maximum number of open handles that any one task can use
Max Number of Handles
concurrently
Max Uncommitted Specifies the maximum number of uncommitted messages that can exist within a
Messages unit of work.
Specifies the time interval (in milliseconds) used to restrict the number of trigger
Max Trigger Interval
messages
Platform The operating system on which the queue manager is running
Version Version number of the queue manager
IBM WebSphere Message Broker Monitoring
Overview
WebSphere Message Broker is an enterprise service bus providing connectivity and universal data transformation
for service-oriented architecture (SOA) and non-SOA environments. It performs comprehensive range of
operations on data, including routing, filtering, enrichment, multicast for publish-subscribe, sequencing, and
aggregation.
Monitored Parameters
Applications Manager monitors availability and performance of the Message Broker, execution group and
message flow and memory usage of the execution group. You can also collect Message Flow Accounting and
Resource Statistics and configure thresholds to the attributes monitored by the server based on these details. The
monitoring details of IBM WebSphere Message Broker are represented graphically that helps to understand the
parameters with ease.
Availability tab, gives the Availability history for the past 24 hours or 30 days.
Performance tab gives the Health Status and events for the past 24 hours or 30 days.
List view enables you to perform bulk admin configurations.
The WebSphere Message Broker attributes monitored are classified under the following tabs in Applications
Manager:
Performance Overview
Execution Group
Message Flow
Performance Overview
Parameter Description
Execution Group Running - Number of execution groups in running
Graphical view of Execution Group state
status Execution Group Stopped - Number of execution groups in stopped
state
Message Flow Running - Number of message flows in running state
Graphical view of Message Flow
status Message Flow Stopped - Number of message flows in stopped
state
Execution Group
Parameter Description
Name Name of the Execution Group
Used Memory In MB The amount of memory that is currently in use.Free Memory In MB The amount of memory that is currently free.Its value might be undefined.
Committed Memory In
The amount of memory that is allocated to the JVM by the operating system.
MB
The maximum amount of memory that can be used for memory management. Its value
Max Memory In MB
might be undefined.
Garbage Collection The total number of garbage collections that have occurred per minute for this instance
per Min of the JVM
Garbage Collection
The garbage collection elapsed time in seconds for this instance of the JVM
Time
Status Status of the Execution Group
Message Flow
Parameter Description
Name Name of the Message Flow
Execution Group Name Name of the Execution Group
Messages Processed per Min Total number of messages that are processed
MQ Errors per Min Total Number of MQGET errors
Total Commits per Min Number of transaction commits that occur when processing a message
Total Back outs per Min Number of transaction backouts that occur when processing a message.
Timeouts per Min Number of transaction timeouts that occur when processing a message
Processing Time in milliseconds CPU time in milliseconds spent processing an input message
Status Status of the message flow
You can also compare the values between the various attributes.
Message Flow Accounting and Statistics
Message flow accounting and statistics data is the information that can be collected by a broker to record
performance and operating details of message flow execution. Use the below commands to trigger statistics and
reports for the message flows.
mqsichangeflowstats -a -e -j -c active -o xml -n basic (enable statistics for
particular execution group)
[OR]
mqsichangeflowstats