Configuring your environment

If your monitoring agent requires configuration or you want to review the default settings for an agent, follow the steps provided for your agent.

Common topics
Some topics are common when you configure agents and data collectors.
Configuring Amazon EC2 monitoring
The Amazon EC2 agent provides you with a central point of monitoring for the health, availability, and performance of your Amazon Elastic Compute Cloud (EC2) Instances. The agent displays a comprehensive set of metrics to help you make informed decisions about your EC2 environment. These metrics include CPU usage, Elastic Block Store (EBS) usage, network usage, Amazon Web Services (AWS) maintenance updates, and disk performance.
Configuring AWS Elastic Load Balancer monitoring
The Amazon ELB agent provides you with a central point of monitoring for the health, availability, and performance of your AWS Elastic Load Balancers. The agent displays a comprehensive set of metrics for each load balancer type-application, network and classic-to help you make informed decisions about your AWS Elastic Load Balancer environment.
Configuring Azure Compute monitoring
The Azure Compute agent provides you with a central point of monitoring for the health, availability, and performance of your Azure Compute instances. The agent displays a comprehensive set of metrics to help you make informed decisions about your Azure Compute environment. These metrics include CPU usage, network usage, and disk performance.
Configuring Cassandra monitoring
You must configure the Cassandra agent so that the agent can collect data from the nodes within the cluster to monitor the health of the Cassandra Database.
Configuring Cisco UCS monitoring
The Monitoring Agent for Cisco UCS monitors the Cisco UCS Virtual Infrastructure by connecting to the Cisco UCSM. You must configure the Cisco UCS agent so that the agent can collect the Cisco UCS data.
Configuring Citrix Virtual Desktop Infrastructure monitoring
The Citrix VDI agent provides a central point of monitoring for your Citrix XenDesktop or XenApp resources, including delivery groups, catalogs, applications, desktops, users, and sessions. Before the agent can be used, you must configure the agent to collect data through the delivery controller.
Configuring DataPower monitoring
To monitor DataPower appliances, you need to first complete some configuration tasks on your appliances, and then configure the Monitoring Agent for DataPower®.
Configuring Db2 monitoring
The Monitoring Agent for Db2® monitors the availability and performance of the Db2 server. You can monitor multiple servers from the Cloud APM console; each server is monitored by a Db2 agent instance. Remote monitoring is also supported by Db2 agent.
Configuring Hadoop monitoring
You must configure the Monitoring Agent for Hadoop so that the agent can collect data of a Hadoop cluster that it monitors. The agent can monitor a single node Hadoop cluster and a multi-node Hadoop cluster.
Configuring HMC Base monitoring
The Monitoring Agent for HMC Base provides you with the capability to monitor the Hardware Management Console (HMC). The agent monitors the availability and health of the HMC resources: CPU, memory, storage, and network. The agent also reports on the HMC inventory and configuration of Power® servers, CPU pools, and LPARs. The CPU utilization of the Power servers, LPARs, and pools are monitored by using HMC performance sample data.
Configuring HTTP Server monitoring
Configure the HTTP Server monitoring to enable the monitoring solution of your HTTP Server.
Configuring IBM Cloud monitoring
The Monitoring Agent for IBM® Cloud collects virtual machine inventory and metrics from your IBM Cloud (SoftLayer) account. Use the IBM Cloud agent to track how many virtual devices you have configured and running in IBM Cloud. You can see what resources are allocated to each virtual device in the detailed dashboard page, which also shows information like the data center a device is located in, the operating system, and the projected public network bandwidth for the month.
Configuring IBM Integration Bus monitoring
The IBM Integration Bus agent is a multiple instance agent. You must create a first agent instance and start it manually.
Configuring IBM MQ Appliances monitoring
The MQ Appliance agent is a multi-instance agent. After installation, you must configure the agent by creating an agent instance before you can start monitoring with the agent.
Configuring InfoSphere DataStage monitoring
You must configure the DataStage® agent so that the agent can collect data to monitor the health and performance of the DataStage server resources.
Configuring Internet Service Monitor
The Internet Service Monitoring Agent offers the capability to determine whether a particular service performs adequately, identify problem areas and report service performance measured against Service Level agreements. Internet Service Monitoring works by emulating the actions of a real user. It regularly polls or tests Internet services to check their status and performance.
Configuring J2SE monitoring
To collect resource monitoring and diagnostic data from the on-premises Java™ applications that are being monitored, you must configure the J2SE data collector.
Configuring JBoss monitoring
The Monitoring Agent for JBoss monitors the resources of JBoss application servers and the JBoss Enterprise Application platform. Use the dashboards that are provided with the JBoss agent to identify the slowest applications, slowest requests, thread pool bottlenecks, JVM heap memory and garbage collection issues, busiest sessions, and other bottlenecks on the JBoss application server.
Configuring Liberty monitoring
You can use the Liberty data collector to monitor your Liberty.
Configuring Linux KVM monitoring
You must configure the Monitoring Agent for Linux® KVM to collect data of the Red Hat Enterprise Virtualization Hypervisor (RHEVH) and Red Hat Enterprise Virtualization Manager (RHEVM) servers. After you install the agent on a server or a virtual machine, you must create the first instance, and start the agent manually.
Configuring MariaDB monitoring
You must configure the MariaDB agent so that the agent can collect data to monitor the availability and performance of MariaDB server resources. Refer the following prerequisites to configure the MariaDB agent for both remote and local monitoring.
Configuring Microsoft Active Directory monitoring
The Monitoring Agent for Microsoft Active Directory is automatically configured and started after installation.
Configuring Microsoft Cluster Server monitoring
You must configure the Monitoring Agent for Microsoft Cluster Server so that the agent can collect the cluster server data. Use the silent response file to configure the agent.
Configuring Microsoft Exchange monitoring
You must configure the Monitoring Agent for Microsoft Exchange Server to monitor the availability and performance of Exchange Servers.
Configuring Microsoft Hyper-V monitoring
When you install the Monitoring Agent for Microsoft Hyper-V Server, the agent is automatically configured and started with the default configuration settings. Use the silent response file to modify the default configuration settings.
Configuring Microsoft IIS monitoring
When you install the Monitoring Agent for Microsoft Internet Information Services, the agent is automatically configured and starts with the default configuration settings.
Configuring Skype for Business Server monitoring
When you install the Monitoring Agent for Skype for Business Server (formerly known as MS Lync Server), the agent will be in the unconfigured state. To start the agent, you need to configure it.
Configuring Microsoft .NET monitoring
The Monitoring Agent for Microsoft .NET monitors .NET applications. The agent starts automatically after installation to collect resource monitoring data. However, to collect transaction tracking and diagnostics data, you must complete some configuration tasks.
Configuring Microsoft Office 365 monitoring
You must configure the Microsoft Office 365 agent to monitor the availability and performance of Microsoft Office 365 subscriptions of the organization.
Configuring Microsoft SharePoint Server monitoring
When you install the Monitoring Agent for Microsoft SharePoint Server, the agent is automatically configured and started with the default configuration settings. Use the silent response file to modify the default configuration settings.
Configuring Microsoft SQL Server monitoring
You must configure the Monitoring Agent for Microsoft SQL Server so that the agent can collect data from the application that is being monitored.
Configuring MongoDB monitoring
The Monitoring Agent for MongoDB requires an instance name. You must manually configure and start the agent instance. The MongoDB agent supports local as well as remote monitoring. Refer the following prerequisites for configuring MongoDB agent for both remote and local monitoring.
Configuring MySQL monitoring
The Monitoring Agent for MySQL requires an instance name and the MySQL server user credentials. You can change the configuration settings after you create the first agent instance.
Configuring NetApp Storage monitoring
The Monitoring Agent for NetApp Storage monitors the NetApp storage systems by using the NetApp OnCommand Unified Manager, the OnCommand API Services, and the OnCommand Performance Manager.
Configuring Node.js monitoring
You can use either the Node.js agent or the stand-alone Node.js data collector to monitor your Node.js applications. If you want a simpler installation process and transaction tracking function, use the Node.js data collector.
Configuring OpenStack monitoring
You must configure the Monitoring Agent for OpenStack before the agent can automatically monitor the OpenStack agent environment.
Configuring Oracle Database monitoring
The Monitoring Agent for Oracle Database provides monitoring capabilities for the availability, performance, and resource usage of the Oracle database. You can configure more than one Oracle Database agent instance to monitor different Oracle databases. Remote monitoring capability is also provided by this agent.
Configuring OS monitoring
The Monitoring Agent for Linux OS, Monitoring Agent for UNIX OS, and Monitoring Agent for Windows OS agents are configured automatically. You can configure log file monitoring for the OS agents so that you can monitor application log files. You can run the OS agents as a non-root user. Also, there are some additional configuration options for the Linux OS agent.
Configuring PHP monitoring
You must configure the Monitoring Agent for PHP so that the agent can collect data from the PHP application that is being monitored.
Configuring PostgreSQL monitoring
You must configure the Monitoring Agent for PostgreSQL so that the agent can collect data from the PostgreSQL database that is being monitored.
Configuring Python monitoring
Both on-premises and IBM Cloud Python applications can be monitored. Complete the corresponding configuration steps based on your application type.
Configuring RabbitMQ monitoring
The Monitoring Agent for RabbitMQ monitors the health and performance of the RabbitMQ cluster resources, such as the nodes, queues, and channels of the cluster. You must configure the RabbitMQ agent so that the agent can collect the RabbitMQ data.
Configuring Response Time Monitoring
The Response Time Monitoring agent monitors HTTP and HTTPS transactions on your HTTP server. Real browser-based user transactions (browser timings) are also monitored.
Configuring Ruby monitoring
You can monitor both on-premises and IBM Cloud Ruby applications. To monitor on-premises Ruby applications, configure the Ruby agent. To monitor IBM Cloud Ruby applications, configure the Ruby data collector.
Configuring SAP monitoring
To monitor a SAP system, the Monitoring Agent for SAP Applications must connect to an application server in the system to be monitored so that the agent can access the Advanced Business Application Programming (ABAP) code that is provided with the product.
Configuring SAP HANA Database monitoring
You must configure the SAP HANA Database agent so that the agent can collect data of the SAP HANA database server that is being monitored.
Configuring SAP NetWeaver Java Stack monitoring
You must configure the SAP NetWeaver Java Stack agent so that the agent can collect resource monitoring data of the SAP NetWeaver Application Server that is being monitored. To monitor transaction tracking and diagnostics data, you must complete some configuration tasks.
Configuring Siebel monitoring
The Siebel agent provides a central point of monitoring for your Siebel resources, including Siebel statistics, user sessions, components, tasks, application server, Siebel Gateway Name Server, process CPU and memory usage, and log event monitoring.
Configuring Sterling Connect Direct monitoring
You must configure the Sterling Connect Direct agent so that the agent can collect data from the Connect Direct servers to monitor the statistics of file transfer and health of Connect Direct servers.
Configuring Sterling File Gateway monitoring
The Monitoring Agent for Sterling File Gateway monitors the IBM Sterling File Gateway application by using the business-to-business (B2B) REST APIs and file gateway database. You must configure the Sterling File Gateway agent so that the agent can collect data from the data sources and monitor the statistics and health of the Sterling File Gateway application. You can configure the agent on Windows and Linux systems.
Configuring Sybase Server monitoring
The Sybase agent offers a central point of management for distributed databases. It collects the required information for database and system administrators to examine the performance of the Sybase server system, detect problems early and prevent them. Database and system administrators can set the required threshold levels and flags to trigger alerts when the system reaches these thresholds. You must configure the Monitoring Agent for Sybase Server to monitor Sybase server.
Configuring Synthetic Playback monitoring
You must configure the Synthetic Playback agent so that the agent can collect data on the availability and performance of internal web applications. This data is displayed in the Application Performance Dashboard.
Configuring Tomcat monitoring
You can configure the Monitoring Agent for Tomcat with the default or custom settings to monitor the resources of Tomcat application servers. The agent can be configured on Windows and Linux systems.
Configuring VMware VI monitoring
After installing the Monitoring Agent for VMware VI, you must create the first instance, and manually start the agent so that the agent can collect data of the VMware Virtual Infrastructure that is being monitored.
Configuring WebLogic monitoring
The Monitoring Agent for WebLogic provides you with a central point of monitoring for the health, availability, and performance of your WebLogic server environment. The agent displays a comprehensive set of metrics to help you make informed decisions about your WebLogic resources, including Java virtual machines (JVMs), Java messaging service (JMS), Java Database Connectivity (JDBC).
Configuring WebSphere Applications monitoring
Configuring WebSphere® Applications monitoring involves configuring a data collector for your application servers. The data collector can be either stand-alone or embedded with the WebSphere Applications agent.
Configuring WebSphere Infrastructure Manager monitoring
Configure the WebSphere Infrastructure Manager agent to monitor the performance of WebSphere Deployment Manager and Node Agent.
Configuring WebSphere MQ monitoring
Before you can start the agent, you must assign an instance name to the agent and complete the several configuration tasks for the user ID and managed system names. Optionally you can also enable transaction tracking for the agent.