PureApplication integration with existent monitoring

 

In IBM PureApplication the monitoring is divided in three parts, system, middleware and hardware.  At the hardware level we have system Management, Tivoli agents and SNMP events. At middleware we have workload, base and an extended monitoring (you should purchase to use it).  In system monitoring there are availability, audit and events.  All of three levels of monitoring can be done by an external monitor agent; you can choose to send the SNMP events which include hardware, workloads and audit monitoring. If you choose an ITM agent you will get hardware and workloads data.

The monitoring in PureApplication system is performed by PureApplication System Agent, and provides the tools that allow you to monitor and troubleshoot the system. The PureApplication System Agent collects data from system and presents the data in the user interface of PureApplication monitoring portal. The data indicates the overall health status of IBM PureApplication System. You can use the data to troubleshoot problems in your system and prevent problems from occurring. The monitoring data collected by the PureApplication System Agent is presented in a workspace.

The level of monitoring information that is available to each user of IBM PureApplication System is determined by the role that each user is assigned. For example, the following types of monitoring information are available to users with the following user roles:

  • Cloud user
    Users with the Cloud user role can view monitoring information that includes metrics on middleware and database virtual system patterns that they deploy.
  • Operators
    Users with the Operator role can view monitoring information about all of the user deployments within a cloud group.
  • Administrators
    Users with the Administrator role can view hardware monitoring information and all of the monitoring information that is available to operator.

Many external enterprise monitoring solutions can be used with PureApplication Server.  For example, an IBM Tivoli/Omnibus external server can be configured as a subscriber to SNMP events from PureApplication. These events include hardware events from the compute nodes, chassis, network, storage devices and software events from the management infrastructure, from deployments, VM start/stop events, events from the operating system, WebSphere Application Server and from DB2. A single PureApplication Server MIB is provided for external enterprise monitoring solutions and a set of OMNIbus rules are provided for IBM Tivoli NetCool/OMNIbus.

For integration with existing ITM 6.2.2 or later environments outside the rack, PureApplication Server provides an ITM agent which provides an “appliance” view of the rack, including hardware metrics and high-level deployment details, such as status, VM information, and IP addresses. Within PureApplication Server itself, you can use the monitoring as a service provided within the rack.  These services provide drill-down into detailed metrics collected for operating systems, WebSphere Application Server, DB2 and other products, along with the hardware metrics, including compute nodes, chassis, network, and storage devices.

Leave a comment
Fabio Albertoni

About Fabio Albertoni

Fabio Albertoni is a Senior IT Specialist working in Integrated Technology Delivery SSO, in Hortolandia, Brazil. He has twelve years of experience in the IT and banking industries. He has spent the last eight years developing and implementing integrated solutions using WebSphere Application Server and MQ Series. He holds a degree in Data Processing from FATEC University of Ourinhos and a Masters degree in Computer Engineering from Instituto de Pesquisas Tecnologicas of Sao Paulo, Brazil. Follow Fabio on Twitter @fxalbertoni
This entry was posted in application system, Cloud, Management, middleware and tagged , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>