r56 - 2019-05-08 - 17:50:12 - TimFeeneyYou are here: TWiki >  Deployment Web > DeploymentMonitoring
Deployment monitoring involves several dimensions:
  • System monitoring: How well is the server hardware servicing the application load?
  • Basic system responsiveness: How well is the server responding from an individual client's point of view? (Note that this is the simplest place to start and includes both server and network performance. )
  • Web application server monitoring: How well is the web application server handling requests and resource pools?
  • Jazz server monitoring: What is the Jazz-based server application being asked to do by the overall user population and how well is it doing it?

constantchange16.png Monitoring: Where to Start?

Enterprise Monitoring

The key to a stable, reliable distributed system is to monitor the moving parts of the system. It is strongly recommended for CLM Deployments to deploy professional monitoring tools for production.

Application Managed Beans constantchange16.png

As part of our serviceability strategy for the CLM product suite, we provide detailed instrumentation and best practices for collecting data on how your system is behaving.

Managed beans (MBeans) are "Java objects that represent a manageable resource, such as an application, a service, a component, or a device" (1). These objects are available through a MBean Server or Java Management Extensions (JMX) agent.

Over the last few releases, we have been working to instrument the CLM applications using managed beans. We have implemented MXBeans. MXBeans use a predefined set of data types which make consuming data from the beans easier (2). There is no need to introspect the bean before collecting the data.

CLM Server Monitoring (Feature) deprecated in v6.0.3updated16.png

CLM Server Monitoring was removed in 6.0.3.

CLM Server Monitoring, a performance monitoring utility included in versions 5.0.2 and later, was removed in 6.0.3. Version 6.0.3 includes a new, lightweight monitoring utility that uses industry-standard MBeans and that can be consumed by other application monitoring services. For more information about server peformance and monitoring, see Plan Item 396673, Work Item 392897, and the Deployment wiki article about Known Expensive Scenarios.
  • CLM Server Monitoring is a CLM solution feature developed to directly monitor Jazz Foundation-based Application server activity in more detail, enabling CLM Administrators to be informed and proactively notified about issues related to scalability, performance, and availability. CLM Server Monitoring can be used with a provided CLM Server Monitoring Agent, or with a larger monitoring solution through JMX.

Jazz server monitoring

  • JMonitoring and TroubleShooting Guide provides a general view into the monitoring capabilities available for checking system stability and troubleshooting problems across the CLM application and software stack.
  • JTSMon will help you make more sense out of Jazz server traffic patterns by turning web service reports into time trend spreadsheets and graphs. To get a copy of JTSMon see the JTSMonFAQ.
  • Jazz monitoring through JMX provides how to set up JMX to monitor a Jazz Server.

Web and Application Server monitoring

Basic system responsiveness

  • Health Check is a provided optional dashboard widget that can be used to periodically check on server responsiveness.
  • Metronome is a feature in the RTC client that provides understanding as to what the web services are doing and how the services are used by the individual RTC client with each user action.

System monitoring

  • NMON (AIX/Linux) gives you a wealth of system performance statistics and automatically creates graphs for CPU, memory, disk, and network usage.

Java Virtual Machine monitoring

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r57 < r56 < r55 < r54 < r53 | More topic actions...
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.