Welcome to the Application Performance Management Blog, where you can read the perspectives from APM experts. This Blog provides insights into the Application Performance Management solution, as well as technical details about specific IBM products.
One of the big difference between IM81 and ITM 6.x agents is about configuration, in IM81 the agents have to be configured with the Server information before they can be installed. Otherwise, we will get an error message running the “installAPMAgents.sh/bat” : "This installation image is not pre-configured to connect to your instance of the Monitoring Infrastructure Node. Use the “/opt/ibm/ccm/make_configuration_packages.sh” script on your IBM Monitoring server to generate a pre-configuration package. Then,... [More]
After a colder than normal winter in North Carolina, Spring is finally here. While today's high of 45F is nearly 20 degrees below normal, this past Saturday gave a taste of Spring with a beautiful, sunny 74F day. After hibernating most of the Winter, these turtles came out in force at a local pond to see what is new under the sun.
So what else is new this Spring? It is the new ITM HMC Base agent v126.96.36.199, and it might replace your CEC Base agent. If you have used the CEC Base agent, you have probably know the requirement that the AIX... [More]
A poorly written situation can have large impact on CPU usage of IBM Tivoli Monitoring 6.2.x OS Agents main processes (kuxagent, klzagent and kntcma.exe). Using wildcard characters (*) and MISSING function in situations is one of the most common source of high impact on CPU usage related to situations evaluation. There are two main suggestions to follow while rewriting situations in order to reduce ITM OS Agents CPU usage: situation with this simple pattern 'LIKE "*/process"' can be re-written as 'SCAN "/process"' put the... [More]
This scenario describes how you can use the WebSphere MQ Monitoring agent to monitor multiple alias queues that are used by different applications. Background: The XYZ company uses WebSphere MQ network to enable communication between multiple applications. In their WebSphere MQ environment, there are 150 alias queues pointing at one local queue. They want to know the impact that each alias queue has on the local queue with the WebSphere MQ Monitoring agent. Especially when the local queue is overloaded, they expect to know which of the alias... [More]
Before IBM tivoli Monitoring 6.2.2 FP03, the max length for a process name
to be monitored using ITM OS Agent on Unix was limited to 768 characters; it didn't allow
to monitor processes like Java that have a command line longer than 768 characters;
with the above limitation, critical processes like WebSphere processes were not monitored
and users were not alerted if the process was running or not.
Starting from ITM 6.2.2 FP03, a new attribute has been introduced in order to allow
to monitor the availability of processes with a name... [More]
The new Agent Builder version 188.8.131.52 is now available for download. The new release introduces really important features hereafter described: The Socket data source allows data to be easily provided to the agent from an external application on the same system. The Java™ application programming interface (API) data source enables data to be collected in a long-running process that is separate from the agent process, allowing greater flexibility in the type of data that can be collected. The number of agent versions available has increased... [More]
Introduction : Managing the short term history file, one need to be very careful how to configure the system so that the short term history is not compromised. Care is required to set the correct disk space and to avoid performance issues caused by data loss. ... [More]
ITM 6.3 Fix Pack 4 has arrived! All the info you need to download now and get the benefits of the new fix pack! Happy downloading!!! LIVE and direct Download links, APAR and packages all listed below! Happy downloading!!! All of the links in the below tables are live. They will take you directly to the download location of the package you require, or the IBM official technote for one of the APARs included in this fix pack (if you wish to know more about the APAR) What Each Package Contains... [More]
One of the more common problems reported by customer's with their OS agents is high CPU utilization. Often it is not the agent itself that is causing the problem. The OS agent is the mechanism that makes the problem visible. This blog will provide some steps that can help you resolve the problem or help identify the cause with the assistance of IBM support. Symptom: Windows OS agent high CPU message During the initialization phase the agent performs a set of sanity checks on the performance counters it is going to use and it is capable of... [More]
Download Links: https://www.ibm.com/developerworks/mydeveloperworks/blogs/0587adbc-8477-431f-8c68-9226adea11ed/resource/OPALBestPracticesOracleExtendedAgent23Oct2012.pdf Contents iii List of Figures v List of Tables vi Revision History vii 1 Overview 1 1.1 Planning your enterprise monitoring infrastructure 1 1.2 Reference sample Oracle database environment 1 2 Strategy of Monitoring 3 2.1 Local Monitoring or Remote Monitoring 3 2.2 Oracle Instant Client or Oracle Home 3 2.3 Database Connection... [More]
The User's Guide for the Tivoli Log File Agent, Version 184.108.40.206, released on December 16, 2011 can be found here: Tivoli Log File Agent, Version 220.127.116.11 User's Guide The User's Guide contains information on installing, configuring, using, and troubleshooting the Tivoli Log File Agent ,as well as details about what is new in this release. Please let us know if there is anything we can do to help you use the documentation.
New technotes have been published to help you solve the problems
that you encounter when using the WebSphere MQ Monitoring agent to get
queue statistics data.
Problem: Alias queue data is available in the Recent Queue Statistics workspace, but the Historical Queue Statistics workspace is empty. Solution: Refer to this technote to figure out how to get historical data for alias queues. Problem: The "Queue Monitoring"
attributed value is OFF in TEP workspaces, which means real-time queue
monitoring is disabled on some... [More]
An interim fix that applies to the following ITCAM for Applications agents of version 7.0.0 fix pack 3 is available now: ITCAM Agent for WebSphere Message Broker ITCAM Agent for WebSphere MQ ITCAM Configuration Agent for WebSphere MQ You can find detailed information and installation instructions about this interim fix for different distributed system from this technote .
A new article has been published at http://www.ibm.com/developerworks/wikis/pages/viewpage.action?pageId=157615912 This article discusses the types of data collected by agents built by Agent Builder, the modes the agents can run in, and how to tune their data collection. Agent Builder agents can support two types of data and two basic methods of data collection for the most common type of data. Data collection times will vary for different Agent Builder agents and for different attribute groups in a single agent.
There may be times when you need to modify or replace an Agent Builder agent and after running the installation for the "modifed" agent, child navigator items are not displaying properly in the TEP GUI. The workaround is to create SQL DELETE statements which are run against the TEPS database and then to re-run the installation of application support for the Agent Builder agent. So how do you know what the DELETE statements should be? Start with a saveexport from the TEPS. Generating a saveexport: ... [More]