Have you been introduced to the newest version of HP Operations manager for UNIX (HP OM for UNIX)? This work horse of the Systems Management group of products in the Business Service Management (BSM) suite of products, had a new version released early June. Now that you have been properly introduced, let’s examine how version 9.20 can help you with your IT Operations Management.
I will briefly present the important features introduced with this version which can be categorized into these broad areas:
Reduced cost of ownership with PostgreSQL DB support
HP OM needs a DB at the backend to store its data. Until now, this was typically Oracle. HP OM 9.20 also supports PostgreSQL as the main DB.
PostgreSQL is an object-relational database management system (ORDBMS) that is released under the PostgreSQL License, a liberal Open Source license, and is therefore free and open source software. This would result in huge savings on the Oracle license.
These are the features which make the HP OM server more robust:
HP OM Health Monitoring component
Health monitoring consists of health monitoring and health status forwarding. The health of the HP Operations management server is monitored by registered monitors (extendable tools for monitoring the status of a particular resource) and the health status is forwarded to all registered clients. Registered clients send health data to a file, a database, or a remote application (depending on the type of registered client).
The Agent Running and Reachable (ARR) component is a health monitor that can be controlled by the health monitoring component. The ARR shows each node’s status in the following events when enabled: NODE_DOWN, AGENT_DOWN, AGENT_FAILURE, AGENT_BUFFERING, OK. These events are forwarded to the clients through the HP OM health monitoring component.
The Health Check (HC) component is responsible for controlling a continuous message flow from managed nodes to management servers and for monitoring the HP Operations agent health status that is received from managed nodes. It ensures that HPOM operator is notified when a serious problem occurs on the Operation Agent (e.g. message flow is suddenly broken, some agent process aborts or fails, Self-Monitoring policies detects a failure).
The Event Storm Filter (ESF) program provides a mechanism to filter HPOM events when an event storm (that is, a large number of events in a short time) is detected and other OM means of message filtering are not applicable.
It ensures that an event storm generated at a single customer site (or multiple sites) does not negatively affect Trouble Ticketing and Notification systems.
In environments with multiple management servers, you can now synchronize HP Operations management server data between the primary server and the other servers by using the opccfgsync command line tool.
Apart from protection from SQL injection these are some of the security and accessibility features introduced in HP OM 9.20:
Smart Card Authentication
The certificate authentication feature introduced with HPOM 9.11 has been expanded to support not only CAC but any kind of smart card or certificate. By configuring smart card authentication on HPOM, access to the HPOM user interfaces is restricted to operators who provide a valid certificate. Therefore, security is increased and access procedures are simplified.
You can now run the HPOM management server processes under a non-root user account. A non-root user is a user with limited authority in comparison to the root user. When running HPOM as a non-root user, you can perform most of the tasks that were by now performed only by the root user.
Creating a dynamic filter for messages in the Java GUI
Administration UI and Java GUI images, have corresponding alternative texts
Visual focus and keyboard access improvements
Several keyboard shortcuts now available in the Java GUI
Instrumentation categories can be assigned to node groups (in addition to policies, policy groups, and nodes)
Message modifying functionality is improved. You can now modify additional message attributes (object, application, service name, message group, severity, and message text). You can also remove a custom message attribute.
Message modify functionality: It is now possible to set additional message attributes: object, application, service name, message group, severity and message text. It is also possible to remove a custom message attribute (CMA).
Instrumentation categories can now also be assigned/deassigned to node groups, previously they can be assigned to nodes, policies and policy groups.
New keyword "SKIPLOGONLY" is introduced in the message-forwarding policy. When used, matched log only messages will be moved directly into history browser on local server and will not be forwarded.
Exclude specific processes from auditing.
Automatically add an annotation when a message is owned.
New option to the opchbp CLI: Use '-status' to provide more information about HBP status for all nodes. It shows nodename, HBP status, errorID if status is not ok, last status (previous status), status change time, last time OK and runstatus (denotes the phases of the HBP check).
New opcdistchk tool is available to perform a crosscheck of the instrumentation and policies currently installed on a node against the ones that are assigned to it in the HPOM database.
startInitialSync.sh utility has a new option to sync a single file.
Possible to set the Service discovery max heap size using the new config variable SVCDISC_MAXHEAP.