r51 - 2020-06-02 - 15:12:59 - TimFeeneyYou are here: TWiki >  Deployment Web > DeploymentMonitoring > CLMServerMonitoring

CLM Server Monitoring (DEPRECATED: CLM Server Monitoring is no longer supported and was dropped in version 6.0.3.)

updated.png Authors: JorgeAlbertoDiaz , Boris Kuschel (BorisKuschel), Gerald Mitchell (GeraldMitchell)
Build basis: Collaborative Lifecycle Management 4.0.6 and later for CSM plugin, Collaborative Lifecycle Management 5.0.1 and later for CSM Agent

CLM Server Monitoring is no longer supported and was dropped in version 6.0.3. Version 6.0.3 includes a new, lightweight monitoring utility that uses industry-standard MBeans that can be consumed by other application monitoring services. For more information about server performance and monitoring, go to this Jazz.net article https://jazz.net/library/article/91590

Why CLM Server Monitoring

The CLM Server Monitoring (CSM) feature tries to answer the question “What is the server doing?” by monitoring CLM application activities and resources, and notifies users when CLM applications have scalability, performance, and availability issues.
The CLM Server Monitoring solution is based on two main "pieces" that are used.
  1. "CLM Server Monitoring Plug-in" - the monitoring feature runs in the same JVM as the CLM application it monitors, exposing the information gathered and alerts generated via JMX.
  2. "CLM Server Monitoring Agent" - an optional performance information client based on Jazz application technology which consumes the information and exposes it to the CLM administrators.

What's new with CLM Server Monitoring in CLM 6.0.1

New in CLM 6.0.1, we have made some changes and additions to the CLM Server Monitoring.
  • Ability to run on, and monitor, CLM deployments on WebSphere Liberty.
  • Serviceability improvement for CSM monitors and the CSM Agent

What's new with CLM Server Monitoring in CLM 6.0

New in CLM 6.0, we have made some changes and additions to the CLM Server Monitoring.
  • More Jazz-based applications supported.
  • MBean Domain change, to better align with standards. Note that if you are using something other than CSM Agent to monitor your solution you may need to initiate additional steps to continue utilizing the CSM plugin in your monitoring capabilities. See the plugin specifics for more information.
  • Permanent Licensing available for CLM Server Monitoring Agent. See the CSM Agent licensing section on this page for more information.

CLM Server Monitoring overview

CLM Server Monitoring provides performance monitoring of CLM servers to help with, and ease, the resolution of CLM system management and performance issues by real-time monitoring of the different CLM application component activity and providing detailed information for these purposes:
  • Collect supporting information of the server activity for issue resolution and system resources accommodation
  • Provide detailed insight of server activity and operations to allow introspective analysis
  • Collect historical performance metric response times such as averages, maximums, minimums
  • Generate alerts based on exceeding tolerances for real-time activity duration

CLM Server Monitoring plug-in

CLM Server Monitoring plug-in : This is the main solution component, responsible for gathering the CLM application performance data and metrics
  • The core "plug-in" component resides in the CLM application JVM process space as part of the standard installation for CLM 4.0.6 and later, and is disabled by default.
    • You do not need to install additional components in the CLM application.
  • The plugin uses byte-code weaving to measure and inspect CLM applications in the JVM, and collect system and JVM information.
  • Data is collected and provided to the CSM Agent or other monitoring solution via JMX.
  • You can also access the CLM Server Monitoring Plugins through JMX, using tools such as JConsole or monitoring solutions like IBM Tivoli Monitoring.
Read CLM Server Monitoring plug-in to understand how you can enable JMX in your CLM application and connect using JMX enabled monitoring solutions.
To enable the CLM Server Monitoring plugin, read CLM Server Monitoring plug-in How-to section.

CLM Server Monitoring Agent

CLM Server Monitoring Agent : Provides data collection from the feature and responsiveness to configured thresholds
  • Runs on a separate JVM process on the same or different node as the CLM application
  • Connects to the CLM Server Monitoring Plugin via JMX
    • Monitors the CLM applications on each JVM it is connected to
    • Gets notified of performance problems via JMX notifications
    • Can invoke JMX methods to perform certain operations
  • CLM Server Monitoring agent is available from CLM starting in version 5.0.1 and is available in the standard installation manager launchpad as well as a separate download.
  • The latest version of CLM Server Monitoring Agent is included in CLM 6.0.1, available here. CLM Server Monitoring Agent 6.0.1 can monitor CLM version 4.0.6 to CLM version 6.0.0 environments.
  • A note on Monitoring CLM 4.0.6 and 4.0.7
    • CLM 4.0.6.x and 4.0.7.x can be monitored, as they have available CLM Server Monitoring Plugins, however their capabilities and rules structure are different that 5.x.
    • CLM Server Monitoring Agent 5.0.1 and later can be used to monitor CLM 4.0.6x and CLM4.0.7.x environments.
  • The CLM Server Monitoring Plugin is required on all CLM applications that are to be monitored, meaning that all CLM applications must be at 4.0.6 or greater on the JVM to be monitored.
  • The CLM Server Monitoring Plugin must be enabled prior to connection by the CLM Server Monitoring Agent

Follow the instructions in CLM Server Monitoring Agent to understand how to quickly start with the CLM Server Monitoring feature.

CLM Server Monitoring versions and licensing

Compatibility for agent to plugin

CLM Server Monitoring Agent 6.0.x and 5.0.2 are backwards compatible, which means that they can monitor CLM Server Monitoring plugins from version 4.0.6 to the version of the CLM Server Monitoring Agent being used..

Licensing for CLM Server Monitoring Agent

As of CLM 6.0, CLm Server Monitoring Agent now has permanent and term authorized user licenses available. When you generate a permanent or term authorized user license or floating license for a CLM product from the License Key Center, the license includes the CLM Server Monitoring authorized user license. Note that CLM Server Monitoring Agent authorized user licenses are not available if you are only using token licenses; in that case, before the trial expires, contact IBM Support. See more information in the CLM 6.0 New & Noteworthy.

CLM Server Monitoring Version change table

CLM Version Plug-in supported in release Agent supported in release Plug-in changes Agent changes CSM Agent version to use to monitor
4.0.5 not available not available not available not available Not applicable
4.0.6 supported Tech Preview (see Note) created created 5.0.1 or higher
4.0.7 supported not available none not available 5.0.1 or higher
5.0.0 supported Tech Preview (see Note) rules changes installation changes 5.0.1 or higher
5.0.1 supported supported RDNG monitoring installation changes 5.0.1 or higher
5.0.2 supported supported none none 5.0.2 or higher recommended
6.0.0 supported supported MBean domain licensing 6.0.0 or higher recommended
6.0.1 supported supported Liberty support Liberty as platform 6.0.1 or higher recommended

Note: For Technology Preview versions of the CSM Agent, please now use the supported CSM Agent versions 5.0.1 and higher. The Technology Preview versions have expired.

Related topics:
CSM Agent setup and usage
External links:

Additional contributors: None

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r51 < r50 < r49 < r48 < r47 | More topic actions
Deployment.CLMServerMonitoring moved from Deployment.SmarterServer on 2013-08-06 - 20:37 by Main.geraldmi -
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.