Monitoring features

The Monitoring is available with a base license or an advanced license. The following components are included:

Monitoring server

For more information, see the Monitoring topic.

IBM Monitoring DataProvider Management (formerly called IBM Cloud Pak for Multicloud Management Cloud Native Monitoring)

To monitor a Kubernetes managed cluster, you can install Monitoring DataProvider Management, which was formerly called Cloud Native Monitoring. Through the application management function, monitoring data collectors can be deployed onto Kubernetes clusters and configured to connect to Monitoring server.

Agents

For more information, see the agents Overview topic.

Monitoring Data Collectors

Contains: Kubernetes data collector and runtime data collectors, including Go data collector, J2SE data collector, Liberty data collector, Node.js data collector, Python data collector, and Ruby data collector. For more information, see the agents Overview topic.

Unified Agent

The Unified Agent is a cost effective solution for development and maintenance. It integrates the open source technologies and provides the capacity to collect metrics, tracing, and events. The Unified Agent provides a lightweight plug-in architecture, supports cloud native environment, and can be expanded.

Use the Unified Agent to collect, process, aggregate, and write metrics to your IBM Cloud Pak for Multicloud Management environment. It is based on Telegraf. For more information, see the agents Overview topic.

Agent Extension Pack

The Extension Pack extends system monitoring to other environments. The extension pack starts with the SAP HANA Database agent, which provides usage data such as memory and CPU usage, database locks, and critical alerts. Database administrators can use the information that is collected by the SAP HANA Database agent to complete monitoring and other tasks such as responding to alerts. The extension pack is available with both a base and advanced license.

Note: The event source integration features (marked with an asterisk (*) in the following table) comes from the bundled IBM Cloud Event Management product.

For more information about part numbers, see the Part numbers topic.

The following table lists the features and capabilities:

Feature	Base	Advanced	Links
View metering metrics			How to
Create thresholds			How to
Native event source integration			How to
Event source integration with Datadog*			How to
Event source integration with New Relic Legacy*			How to
Event source integration with Amazon Web Services*			How to
Event source integration with Microsoft™ Azure*			How to
Event source integration with Netcool OMNIbus			How to
Event source integration with Jenkins*			How to
Event source integration with Pingdom *			How to
Event source integration with AppDynamics *			How to
Event source integration with Nagios XI *			How to
Event source integration with SolarWinds *			How to
Event source integration with Splunk Enterprise *			How to
Event source integration with Webhook *			How to
Event source integration with Logstash *			How to
Event source integration with Elasticsearch *			How to
Event source integration with Dynatrace Splunk *			How to
Event source integration with IBM Urban Code Deploy *			How to
Create event policies and runbooks for internal event sources			How to
Create event policies and runbooks for external event sources			How to
Send incident details to Alert Notification			How to
Send incident details to Netcool/OMNIbus			How to
Send incident details to Slack			How to
Send incident details to Webhook			How to
Send incident details to Microsoft teams			How to
Send incident details to Stride			How to
Send incident details to Service Now			How to
Send incident details to GitHub			How to
Send incident details to Watson Workspace			How to
View, investigate, and resolve incidents			How to
Use the Applications view to visualize application resource state, properties, and relationship and their changes.			How to
Use the Resources view to visualize the metrics that are related to Agents and Data Collectors.			How to
Use the Resources dashboard to visualize metrics gathered by the Cloud data collectors for: - Kubernetes (NGINX, Redis)			How to
Use the Resources dashboard to visualize metrics gathered by the Runtime data collectors: - Go data collector, J2SE data collector, Liberty data collector, Node.js data collector, Python data collector, Ruby data collector			How to
Use the Resources dashboard to visualize metrics gathered by the Unified Agent: - UA plug-in for Jaeger and Zipkin, UA plug-in for NGINX, UA plug-in for Redis, UA plug-in for IBM API Connect(APIC), UA plug-in for IBM App Connect Enterprise(ACE), UA plug-in for IBM MQ, UA plug-in for DEM, UA plug-in for OpenShift			How to
Go back in time to visualize the state of each Kubernetes resource layer at the time an event was fired			How to
Create synthetic tests and monitor response time and availability for your Rest API websites.			How to
Digital Experience Monitoring (DEM): Digital experience monitoring (DEM) can be enabled to monitor web-based resources and real user experience. It can discover and track traffic, user behavior, and other metrics to help analyze the application performance and usability. There are two ways to enable DEM. You can enable DEM for Liberty data collector, and install the DEM plug-in for HTTP Server to monitor IBM HTTP Server and Apache HTTP Server.			How to
Transaction Tracking: The transaction tracking feature enables topology views and instance level transaction monitoring. By distributed tracking infrastructure, transaction tracking can detect bottleneck issues, including latency problems and errors, and filter or sort traces based on application. Transaction tracking can also filter views based on length of trace, timestamp, interactions, errors, and transaction comparisons. For more information, see Transaction tracking.			How to