IBM Performance Management on Cloud: User's Guide

IBM Cloud Application Performance ManagementMarch 2017

User's Guide

SC27-8737-01

IBM

NoteBefore using this information and the product it supports, read the information in Notices on page 42.

This edition applies to the March 2017 version of IBM Cloud Application Performance Management and to allsubsequent releases and modifications until otherwise indicated in new editions.

Copyright IBM Corporation 2014, 2017.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. What's new . . . . . . . . 1

Chapter 2. Product overview . . . . . 15Architecture overview . . . . . . . . . . . 15User interface. . . . . . . . . . . . . . 17Offerings and add-ons . . . . . . . . . . . 17

Offering details . . . . . . . . . . . . 19Agents and data collectors . . . . . . . . . 21

Capabilities . . . . . . . . . . . . . 21Descriptions . . . . . . . . . . . . . 24

Features . . . . . . . . . . . . . . . 34Integration . . . . . . . . . . . . . . 39Documentation . . . . . . . . . . . . . 40

Conventions used in the documentation . . . . 41

Chapter 3. System requirements. . . . 47Synthetic Playback agent hardware requirements . . 47

Chapter 4. Tutorial: Downloading andinstalling an agent. . . . . . . . . . 49

Chapter 5. Tutorial: Downloading andconfiguring a data collector. . . . . . 55

Chapter 6. Scenarios. . . . . . . . . 59Scenario: Monitoring the IBM Java application stack 59

Monitoring the IBM Java application stack . . . 59Adding web applications to the ApplicationPerformance Dashboard . . . . . . . . . 59Associating the IBM Java application stack withthe web application. . . . . . . . . . . 60Viewing results of IBM Java application stackmonitoring . . . . . . . . . . . . . 61Diagnosing problems in your environment . . . 65

Scenario: Monitoring the IBM integration stack . . 66Monitoring the IBM integration stack . . . . . 66Adding middleware applications to theApplication Performance Dashboard . . . . . 67Viewing results of IBM integration stackmonitoring . . . . . . . . . . . . . 68Diagnosing problems in your environment . . . 72

Chapter 7. Downloading your agentsand data collectors . . . . . . . . . 75

Chapter 8. Agent and data collectordeployment. . . . . . . . . . . . . 77

Chapter 9. Installing your agents . . . 83Installing agents on AIX systems . . . . . . . 83

Preinstallation on AIX systems . . . . . . . 83Installing agents . . . . . . . . . . . . 85

Installing agents on Linux systems . . . . . . 87

Preinstallation on Linux systems . . . . . . 88Installing agents . . . . . . . . . . . . 91

Installing agents on Windows systems . . . . . 94Preinstallation on Windows systems . . . . . 95Installing agents . . . . . . . . . . . . 96

Installing agents as a non-root user . . . . . . 98Securing the agent installation files . . . . . . 99Installing agents silently . . . . . . . . . . 100Bypassing the prerequisite scanner . . . . . . 101Uninstalling your agents . . . . . . . . . 101

WebSphere Applications agent: Unconfiguringthe data collector . . . . . . . . . . . 103Node.js agent: Removing the monitoring plug-in 111Microsoft .NET agent: Removing the .NET datacollector . . . . . . . . . . . . . . 111

Chapter 10. Configuring yourenvironment . . . . . . . . . . . . 113Network connectivity. . . . . . . . . . . 113

Secure communication . . . . . . . . . 113Configuring agents to communicate through aforward proxy . . . . . . . . . . . . 113

Configuring agents . . . . . . . . . . . 115Using agent commands . . . . . . . . . . 115Using the IBM Cloud Application PerformanceManagement window on Windows systems . . . 119Agent Configuration page . . . . . . . . . 119Configuring agents as a non-root user . . . . . 120Configuring the Amazon EC2 agent . . . . . . 121Configuring the Cassandra agent . . . . . . . 122

Configuring the agent on Windows systems . . 122Configuring the agent on Linux systems . . . 123Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 123Configuration parameters of the agent . . . . 124

Configuring the Cisco UCS agent. . . . . . . 124Configuring the agent on Windows systems . . 125Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 125Configuring the agent by responding toprompts . . . . . . . . . . . . . . 127Configuration parameters for the agent. . . . 127Configuration parameters for the data provider 128Enabling SSL communication with Cisco UCSdata sources . . . . . . . . . . . . . 128Increasing the Java heap size . . . . . . . 129

Configuring the Citrix VDI agent . . . . . . . 130Enabling Citrix read-only administratorprivileges. . . . . . . . . . . . . . 132

Configuring the data collectors for Bluemixapplications . . . . . . . . . . . . . . 133

Obtaining data collectors for Bluemixapplications . . . . . . . . . . . . . 133Configuring the Bluemix Liberty data collector 134Configuring the Bluemix Node.js data collector 135

Copyright IBM Corp. 2014, 2017 iii

Configuring the Bluemix Python data collector 136Configuring the Bluemix Ruby data collector 137Reconnecting the data collector to the CloudAPM server . . . . . . . . . . . . . 137Data collectors for Bluemix applications: Runtime configuration. . . . . . . . . . . 139Sample manifest.yml file . . . . . . . . 146

Configuring DataPower monitoring . . . . . . 146Configuring the DataPower agent . . . . . 146Configuring DataPower Appliances . . . . . 149

Configuring the DB2 agent . . . . . . . . . 157Configuring the agent on Windows systems . . 158Configuring the agent on Linux or Unix systems 159Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 159Granting privileges for viewing DB2 metrics 161Configuring local environment variables . . . 161

Configuring the Hadoop agent . . . . . . . 164Configuring the agent on Windows systems . . 165Configuring the agent on Linux and AIXsystems . . . . . . . . . . . . . . 166Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 168Configuring the dashboard for viewing Hadoopevents . . . . . . . . . . . . . . . 169Granting permission to non-admin users . . . 169

Configuring the HMC Base agent . . . . . . 170Setting up the SSH connection. . . . . . . 171Configuring the HMC Console Server formonitoring Virtual I/O . . . . . . . . . 172Enabling the CPU and memory utilizationmonitoring . . . . . . . . . . . . . 173

Configuring the HTTP Server agent . . . . . . 173IBM HTTP Server Response Time module . . . 175HTTP Server agent code samples . . . . . . 175

Configuring the IBM Integration Bus agent . . . 177Configuring the IBM Integration Bus agent . . 178Configuring IBM Integration Bus for dataenablement . . . . . . . . . . . . . 182Disabling snapshot data collection for the agent 186Configuring transaction tracking for the IBMIntegration Bus agent. . . . . . . . . . 186Removing the KQIUserExit user exit . . . . 187Monitoring IBM Integration Bus in a Dockercontainer . . . . . . . . . . . . . . 187

Configuring the JBoss agent . . . . . . . . 190Enable JMX MBean server connections . . . . 191Add a JBoss server management user . . . . 192Enable Web/HTTP Statistic Collection . . . . 193Configuring the agent on Windows systems . . 194Configuring the agent by responding toprompts . . . . . . . . . . . . . . 197Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 198Configuration parameters for the JBoss agent 199Setup the JBoss agent transaction tracking datacollector . . . . . . . . . . . . . . 200Additional configuration for JBoss agenttransaction tracking . . . . . . . . . . 201

Configuring the Linux KVM agent . . . . . . 203

Creating a user and granting requiredpermissions . . . . . . . . . . . . . 203Configuring protocols . . . . . . . . . 204Configuring a connection to the RHEVM server 208Configuring a connection to the RHEVH server 209Configuration parameters to connect to theRHEVM server . . . . . . . . . . . . 210Configuration parameters to connect to theRHEVH server . . . . . . . . . . . . 211

Configuring the Microsoft Active Directory agent 213Running the Microsoft Active Directory agent asan administrator user. . . . . . . . . . 213Configuring local environment variables . . . 214

Configuring the Microsoft Cluster Server agent . . 215Creating a generic service cluster resource onWindows Server 2008 and 2012 systems . . . 215Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 216Changing the user account . . . . . . . . 217

Configuring the Microsoft Exchange Server agent 217Creating users . . . . . . . . . . . . 218Assigning administrator rights to the ExchangeServer user . . . . . . . . . . . . . 220Making the Exchange Server user a localadministrator . . . . . . . . . . . . 222Configuring the Exchange Server forreachability . . . . . . . . . . . . . 223Configuring the agent to run under the domainuser . . . . . . . . . . . . . . . 224Configuring the agent locally . . . . . . . 225Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 228Configuring local environment variables for theagent . . . . . . . . . . . . . . . 229

Configuring the Microsoft Hyper-V Server agent 229Configuring the Microsoft IIS agent . . . . . . 230

Configuring the agent on Windows systems . . 231Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 231Changing the user account . . . . . . . . 232

Configuring the Microsoft Lync Server agent . . . 233Configuring the agent on Windows systems . . 233Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 234Changing the user account . . . . . . . . 235Configuration parameters for the agent. . . . 235

Configuring the Microsoft .NET agent . . . . . 236Registering the data collector . . . . . . . 237Enabling collection of transaction tracking anddiagnostics data . . . . . . . . . . . 238Enabling the collection of diagnostics data byusing the configdc command . . . . . . . 238Enabling transaction tracking in agentcoexistence environment. . . . . . . . . 239Activating the configuration updates . . . . 240Performance tuning of data collector . . . . 240

Configuring the Microsoft Office 365 agent . . . 243Verifying reachability of configured users . . . 244Configuring the agent on Windows systems . . 245Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 246

iv IBM Cloud Application Performance Management: User's Guide

Changing the user account . . . . . . . . 247Monitoring the Skype QoS . . . . . . . . 247

Configuring the Microsoft SharePoint Server agent 248Changing the user account . . . . . . . . 249

Configuring the Microsoft SQL Server agent . . . 249Creating a user and granting permissions . . . 250Selecting the databases for monitoring . . . . 252Configuring local environment variables . . . 259Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 264Running the agent in a cluster environment . . 265

Configuring the MongoDB agent . . . . . . . 267Configuring the agent with default settings . . 269Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 269Configuring the agent by responding toprompts . . . . . . . . . . . . . . 270

Configuring the MySQL agent. . . . . . . . 271Configuring the agent on Windows systems . . 271Configuring the agent on Linux systems . . . 272Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 273

Configuring the NetApp Storage agent . . . . . 273Downloading and installing the NetAppManageability SDK JAR file . . . . . . . 274Configuring the agent on Windows systems . . 275Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 275Configuring the agent by responding toprompts . . . . . . . . . . . . . . 277Configuration parameters for the data provider 277Configuration parameters for the OnCommandUnified Manager . . . . . . . . . . . 278Configuration parameters for the OnCommandAPI Service . . . . . . . . . . . . . 279

Configuring the Node.js agent . . . . . . . . 279Configuring the Node.js agent to monitorNode.js applications . . . . . . . . . . 279Configuring the Node.js agent data collector 281Configuring the diagnostics data collector . . . 283

Configuring the Oracle Database agent . . . . . 284Configuring the agent on Windows systems . . 286Configuring the agent by responding toprompts . . . . . . . . . . . . . . 289Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 293Granting privileges to the Oracle Databaseagent user . . . . . . . . . . . . . 296

Configuring the OS agents . . . . . . . . . 298Running the OS agents as a non-root user . . . 298Configuring OS agent log file monitoring . . . 300

Configuring the PHP agent . . . . . . . . . 323Configuring the PostgreSQL agent . . . . . . 325Configuring Python monitoring . . . . . . . 327

Configuring the Python agent . . . . . . . 328Python agent: Runtime configuration . . . . 331Configuring Python data collector . . . . . 332Python data collector: Run time configuration 333

Configuring the RabbitMQ agent . . . . . . . 336Configuring the agent on Windows systems . . 337Configuring the agent on Linux systems . . . 337

Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 338

Response Time Monitoring agent . . . . . . . 339Response Time Monitoring Components . . . 339Planning the installation. . . . . . . . . 340Planning the configuration . . . . . . . . 341JavaScript Injection . . . . . . . . . . 342Reconfiguring the Response Time Monitoring onWindows . . . . . . . . . . . . . . 343Reconfiguring the Response Time Monitoring onAIX and Linux . . . . . . . . . . . . 344Configuring using the Agent ConfigurationPage . . . . . . . . . . . . . . . 344Viewing Response Time Monitoring data . . . 346Configuring the IBM HTTP Server ResponseTime module . . . . . . . . . . . . 347Packet Analyzer roadmap . . . . . . . . 354Customizing End User Transaction locationvalues . . . . . . . . . . . . . . . 362User and Session ID reference values . . . . 363

Configuring the Ruby agent . . . . . . . . 363Configuring the Ruby agent to monitor Rubyapplications . . . . . . . . . . . . . 364Installing the data collector . . . . . . . . 365Configuring the diagnostics data collector . . . 366Enabling method trace and adjusting the pathdisplay . . . . . . . . . . . . . . 369Increasing the JVM heap size . . . . . . . 370Disabling or enabling diagnostics data for Rubyapplications . . . . . . . . . . . . . 370

Configuring the SAP agent . . . . . . . . . 371Configuring the agent on Windows systems . . 371Configuring the agent on Linux or AIX systems 372Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 373Configuration parameters of the agent . . . . 374Importing the ABAP transport on the SAPsystem . . . . . . . . . . . . . . 376Deleting the ABAP transport from the SAPsystem . . . . . . . . . . . . . . 382Verifying agent configuration . . . . . . . 382Adding Database Communication Port number 386

Configuring the SAP HANA Database agent . . . 387Configuring the SAP NetWeaver Java Stack agent 389

Configuring the agent on Windows systems . . 390Configuring the agent on Linux or AIX systems 390Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 391Configuring the data collector . . . . . . . 392Enabling the collection of transaction trackingand diagnostics data . . . . . . . . . . 393Removing the data collector configuration. . . 394Configuration parameters of the agent . . . . 394

Configuring the Siebel agent . . . . . . . . 395Verify Siebel user account . . . . . . . . 396Enabling Per Component Statistics Monitoring 397Configuring the agent on Windows systems . . 397Configuring the agent by responding toprompts . . . . . . . . . . . . . . 401Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 402

Contents v

Configuration parameters for the Siebel agent 403Siebel component logs that are alwaysmonitored . . . . . . . . . . . . . 405

Configuring the Synthetic Playback agent . . . . 405Configuring the Tomcat agent . . . . . . . . 406

Configuring the Tomcat agent with the defaultsettings . . . . . . . . . . . . . . 407Configuring the agent on Windows systems . . 407Configuring the Tomcat agent on Linux systems 408Configuring the Tomcat agent by using thesilent response file. . . . . . . . . . . 408

Configuring the VMware VI agent . . . . . . 409Sizing and planning the VMware VI agentdeployment . . . . . . . . . . . . . 410Enabling SSL communication with VMware VIdata sources . . . . . . . . . . . . . 411Configuring the agent on Windows systems . . 412Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 413Configuring the agent by responding toprompts . . . . . . . . . . . . . . 414Configuration parameters for the data source 414Configuration parameters for the data provider 415Increasing the Java heap size . . . . . . . 416

Configuring the WebLogic agent . . . . . . . 417Configuring the agent on Windows systems . . 418Configuring the agent by responding toprompts . . . . . . . . . . . . . . 421Configuring the agent by using the silentresponse file . . . . . . . . . . . . . 422Configuration parameters for the WebLogicagent . . . . . . . . . . . . . . . 423

Configuring the WebSphere Applications agent . . 423Fast track: Configuring the data collector forWebSphere Applications agent. . . . . . . 424Checking user access requirements . . . . . 426Handling other existing data collector in theapplication server . . . . . . . . . . . 426Configuring the data collector with the simpleconfiguration utility . . . . . . . . . . 427Configuring or reconfiguring the data collectorwith full configuration utilities . . . . . . 429Manually configure the data collector if theconfiguration utilities fail . . . . . . . . 442(Agent coexistence) Configuring the WebSphereApplications agent and the data collector . . . 445Reconfiguring the data collector if you changethe offering type on Cloud APM server . . . 452Monitoring WebSphere Application ServerLiberty inside a Docker container. . . . . . 453Manually configuring the data collector tomonitor dynamic cluster servers . . . . . . 454Dynamically configuring data collection onAgent Configuration page . . . . . . . . 461Enabling memory leak monitoring . . . . . 462Configuring the PMI . . . . . . . . . . 463Advanced configuration with variousconfiguration files . . . . . . . . . . . 464Restoring the application server configurationfrom a backup . . . . . . . . . . . . 494

Configuring the WebSphere Infrastructure Manageragent . . . . . . . . . . . . . . . . 495Configuring the WebSphere MQ agent . . . . . 496

Authorizing the user IDs to run the agent . . . 497Configuring IBM MQ (WebSphere MQ) for dataenablement . . . . . . . . . . . . . 498Configuring the WebSphere MQ agent . . . . 500Specifying unique managed system names formultiple queue managers . . . . . . . . 502Configuring transaction tracking for theWebSphere MQ agent . . . . . . . . . 504Monitoring a queue manager in a Dockercontainer . . . . . . . . . . . . . . 504Remotely monitoring queue managers on MQAppliance . . . . . . . . . . . . . 507Remotely monitoring HA queue managers onMQ Appliance . . . . . . . . . . . . 509

Chapter 11. Integrating with otherproducts and components. . . . . . 513Integrating with IBM Tivoli Monitoring V6.3 . . . 513

Cloud APM agent and Tivoli Monitoring agentcoexistence . . . . . . . . . . . . . 513Hybrid Gateway . . . . . . . . . . . 516

Integrating with OMEGAMON . . . . . . . 525Integrating with Netcool/OMNIbus . . . . . . 526

Installing and configuring the Integration Agentfor Netcool/OMNIbus . . . . . . . . . 526Configuring the integration forNetcool/OMNIbus . . . . . . . . . . 528

Integrating with Operations Analytics - LogAnalysis . . . . . . . . . . . . . . . 530Integrating with Operations Analytics - PredictiveInsights . . . . . . . . . . . . . . . 530Integrating with Alert Notification . . . . . . 531Integrating with Control Desk . . . . . . . . 531Integrating with IBM Bluemix . . . . . . . . 533

Chapter 12. Upgrading your agents 535Preserving agent configuration changes. . . . . 537Agents on AIX: Stopping the agent and runningslibclean before you upgrade. . . . . . . . 538HMC Base agent on AIX: Stopping the agent as anon-root user and running slibclean before youupgrade . . . . . . . . . . . . . . . 538Node.js agent: Removing the data collectorplug-ins before you upgrade . . . . . . . . 539Response Time Monitoring agent: upgrading IBMHTTP Server Response Time module . . . . . 539Microsoft .NET agent: Removing the .NET datacollector before you upgrade . . . . . . . . 539Ruby agent: Removing the data collector plug-insbefore you upgrade . . . . . . . . . . . 539WebSphere Applications agent: Migrating the datacollector . . . . . . . . . . . . . . . 540

Migrating the data collector interactively . . . 540Migrating the data collector in silent mode . . 542

Chapter 13. Administering . . . . . . 545Starting the Cloud APM console . . . . . . . 545

vi IBM Cloud Application Performance Management: User's Guide

Thresholds and resource groups . . . . . . . 546Thresholds background information . . . . . 546Tutorial: Defining an eventing threshold . . . 550Threshold Manager . . . . . . . . . . 552Using the Threshold Management Service API 557Resource Group Manager . . . . . . . . 558Using the Resource Group Management ServiceAPI. . . . . . . . . . . . . . . . 560Sending email in response to an event . . . . 561

Managing user access . . . . . . . . . . 562Roles and permissions . . . . . . . . . 563Accessing and using the Role Based AccessControl Service API . . . . . . . . . . 569

Administering your agents . . . . . . . . . 570Starting agents as a non-root user . . . . . 570Event thresholds for Transaction Monitoring . . 571Managing OS agent events . . . . . . . . 574Guidelines to maximize agent and serverperformance for log file monitoring . . . . . 583

Managing synthetic transactions and events . . . 587Recording synthetic scripts . . . . . . . . 587Structuring complex scripts. . . . . . . . 589Managing synthetic transactions . . . . . . 590Viewing synthetic transaction data in theApplication Performance Dashboard . . . . 596Managing synthetic events . . . . . . . . 597

Exploring the APIs . . . . . . . . . . . 600Advanced Configuration . . . . . . . . . 601

Chapter 14. Using the dashboards 605All My Applications - Application PerformanceDashboard . . . . . . . . . . . . . . 605

Searching log files . . . . . . . . . . . 607Application - Application Performance Dashboard 608

Manipulating the Aggregate TransactionTopology widget . . . . . . . . . . . 612

Group and Instance - Application PerformanceDashboard . . . . . . . . . . . . . . 612

Editing the Components dashboard groupwidgets . . . . . . . . . . . . . . 616Adjusting and comparing metrics over time . . 617Viewing and managing custom charts and tables 618

Event Status . . . . . . . . . . . . . . 624Investigating anomalies with OperationsAnalytics - Predictive Insights . . . . . . . 626

Managing applications . . . . . . . . . . 627Adding an application . . . . . . . . . 628Editing an application . . . . . . . . . 630Deleting an application . . . . . . . . . 632Viewing and removing offline agents . . . . 633

Custom views . . . . . . . . . . . . . 638Creating and managing custom pages . . . . 639Viewing custom pages . . . . . . . . . 641

Dashboard utilities . . . . . . . . . . . 642Copying the dashboard URL . . . . . . . 643Setting a trace . . . . . . . . . . . . 643Locking the Cloud APM console . . . . . . 644Usage Statistics . . . . . . . . . . . . 645

Reports . . . . . . . . . . . . . . . 646Response Time Monitoring Agent reports . . . 646Generating Synthetic Playback agent reports . . 650WebSphere Applications agent reports . . . . 655

Chapter 15. PDF documentation . . . 659

Chapter 16. Troubleshooting andsupport . . . . . . . . . . . . . . 661Collecting monitoring agent logs for IBM Support 661

Accessibility features . . . . . . . . 663

Notices . . . . . . . . . . . . . . 665Trademarks . . . . . . . . . . . . . . 667Terms and conditions for product documentation 667IBM Online Privacy Statement. . . . . . . . 668

Contents vii

viii IBM Cloud Application Performance Management: User's Guide

Chapter 1. What's new

New features, capabilities, and coverage are available in each release.

Latest release

New Application Performance Management Developer CenterThe APM Developer Center is a central location from which you can access resources for theAPM products: blogs, videos, documentation, support, events, IBM Marketplace, and other

resources. The Cloud APM console

Help menu has a convenient link to the APM DeveloperCenter.

Product rebranding and simplification

IBM Performance Management on Cloud was rebranded to IBM Cloud Application PerformanceManagement. The component names have also changed. For example, Cloud APM console andCloud APM server were called the Performance Management console and PerformanceManagement server in earlier releases.

IBM Performance Management on Cloud subscription offerings have been consolidated andrenamed:

Offering name October 2016 release and earlier Offering name March 2017 and later

Monitoring on Cloud Cloud APM, Base

Application Performance Management on Cloud Cloud APM, Advanced

Application Diagnostics on Cloud Cloud APM, Advanced

Application Performance Management Advanced onCloud

Cloud APM, Advanced

Some product extensions have been consolidated and renamed:

Extension name October 2016 release and earlier Extension name March 2017 and later

Data Analytics Extension Pack(Hadoop agent)

Base Extension Pack(adds the new Cassandra agent and Microsoft Office 365agent)

SAP Extension Pack(SAP HANA Database agent and SAP NetWeaver JavaStack agent)

Advanced Extension Pack(adds the new RabbitMQ agent)

OS support

Windows 2016 operating systemsAdded support for Windows 2016 operating systems. For more information, see theSoftware Product Compatibility Report (SPCR) for all agents: http://ibm.biz/agents-pm-systemreqsFind your operating system in the Windows section of the report and click thecomponent icon for a list of supported agents.

New extension pack available

IBM Cloud Application Performance Management z Systems Extension Pack

The z Systems Extension Pack enables support for your IBM OMEGAMON agents inyour Cloud APM offering. OMEGAMON agent data is sent to the Cloud APM server bythe Hybrid Gateway. The Hybrid Gateway retrieves the OMEGAMON agent data and

Copyright IBM Corp. 2014, 2017 1

https://developer.ibm.com/apm/https://developer.ibm.com/apm/https://developer.ibm.com/apm/http://ibm.biz/agents-pm-systemreqshttp://ibm.biz/agents-pm-systemreqs

events from the IBM Tivoli Monitoring infrastructure that the OMEGAMON agents areconnected to. As a result, you can view monitoring data and events for yourOMEGAMON agents in the Cloud APM console.

The Cloud APM z Systems Extension Pack is available if you have either of the CloudAPM offerings.

To integrate this extension pack with Cloud APM, complete the steps in Integrating withOMEGAMON on page 525.

New agents and data collectors available

Data collectors for Bluemix applications

You can use the data collectors for Bluemix applications to monitor the health andperformance of the following types of your applications on Bluemix:v Liberty applicationsv Node.js applicationsv Python applicationsv Ruby applications

You can view both resource and diagnostics monitoring data, such as resource utilization,throughput, and detailed information about requests and methods.

Monitoring Agent for Cassandra

You can use the Cassandra agent to monitor the health and performance of the Cassandracluster resources, such as the nodes, keyspaces, and column families.

Monitoring Agent for Microsoft Office 365

You can use the Microsoft Office 365 agent to monitor the health and performance of theOffice 365 resources, such as the Office 365 subscribed services, Office 365 portal, mailboxusers, SharePoint sites, and OneDrive storage.

Monitoring Agent for NetApp Storage

You can use the NetApp Storage agent to monitor the health, availability, andperformance of the NetApp storage systems by using the NetApp OnCommand UnifiedManager (OCUM). The monitoring agent performs the following tasks:v Identifies poorly performing storage system objectsv Performs discovery and monitoring by using the OCUM server at the focal point

Monitoring Agent for RabbitMQ

You can use the RabbitMQ agent to monitor the health and performance of the RabbitMQcluster resources, such as the nodes, queues, and channels of the cluster.

Monitoring Agent for Siebel

You can use the Siebel agent to monitor the health and performance of Siebel resourcesincluding Siebel statistics, user sessions, components, tasks, application server, SiebelGateway Name Server, process CPU and memory usage, and log event monitoring.

Python data collector

You can use the Python data collector to monitor the health and performance of Pythonresources and see diagnostics data such as request context and method trace. To enablethe capabilities of the data collector, you only need to configure the data collector afteryou download it. There is no installation process for this lightweight Python datacollector like other Cloud APM agents.

Agent enhancements

2 IBM Cloud Application Performance Management: User's Guide

Monitoring Agent for Amazon EC2The following enhancements are added to the Amazon EC2 agent:v Replace Instance ID with tag name when a tag name is availablev Allow data to be filtered and grouped based on tag name

Monitoring Agent for DB2

The following enhancements are added in the DB2 agent:v Linux on Power Little Endian (pLinux LE) is supportedv Added a script file to grant privileges to a DB2 user to view data for all the attributes

of the DB2 agent for a monitored instance

Monitoring Agent for HadoopThe following enhancements are added in the Hadoop agent:v Added support to install and configure the agent on Windows 2016 and AIX 7.2

systemsv Added support for monitoring the following Hadoop offerings: Hortonworks HDP 2.5,

Cloudera CDH 5.8, and IBM BigInsights 4.2v Added the test connection button to verify connection to the Hadoop daemons that

you specify when you configure the agentv Improved the agent configuration process to reduce the configuration time and

complexity. The configuration is simplified because the following prerequisite andconfiguration tasks are not required: Installing the plug-in on each node of the Hadoop cluster Configuring and updating the hadoop-metrics2.properties file Restarting the Hadoop daemons after configuring the hadoop-metrics2.properties

file Configuring all the DataNodes and NodeManagers in the cluster Restarting the agent when additional nodes are added to the cluster

Monitoring Agent for JBossThe following enhancements are added to the JBoss agent:v Added transaction tracking and deep dive monitoring in the Advanced Agents offeringv Added a dashboard page to monitor datasource metricsv Added support for monitoring the following JBoss offerings: WildFly 8.x/9.x/10.x,

JBoss EAP 7.x, JBoss AS 7.xv Added support for running the agent on the Windows operating system

Monitoring Agent for Linux KVMThe following enhancements are added to the dashboard of the Linux KVM agent:v Updated the Hosts group widget in the Hosts, Clusters, and Storage page to display

the Max Scheduling Memory (GB) and the Live Snapshot KPIsv Added the Storage Details page to display details about the disks and disk snapshots

in the storage poolv Add the Network Transmitted/Received Data (GB) group widget in the Host Detail

page to display historical information of the total data (in GB) that is transmitted andreceived over the network

Monitoring Agent for Linux OSThe following enhancement is added to the Linux OS agent:v Linux on Power Little Endian (pLinux LE) is supported

Monitoring Agent for Microsoft Exchange ServerThe following enhancements are added in the dashboard of the Microsoft ExchangeServer agent:

Chapter 1. What's new 3

v Added the inbound time and outbound time attributes in the Reachability data setv Added pages and group widgets to display reachability detailsv Added an eventing threshold for reachabilityv Added support to install and configure the agent on Exchange Server 2016 and

Windows Server 2016 system

Monitoring Agent for Microsoft Internet Information ServicesThe following enhancement is added to the Microsoft IIS agent :v Added support to install and configure the on the Microsoft Windows Server 2016

system

Monitoring Agent for Microsoft Active DirectoryThe following enhancements are added in the Microsoft Active Directory agent:v Added the group widgets and pages to display the details of Group Policy Object,

Netlogon, Local Security Authority, and LDAP detailsv Added the following data sets that you can view in the Attribute details tab:

Services Data Set Replication File Replication Service Moved or Deleted Org. Unit LDAP Attributes Security Accounts Manager DFS Address Book Event Log Password Setting Objects

v Added the data sets for ADFS, ADFS Proxy, and Asynchronous Thread Queuev Added the group widgets and pages to display details of ADFS and ADFS Proxyv Added support to install and configure the agent on Windows Server 2016 systems

Monitoring Agent for Microsoft .NETThe following enhancements are added in the dashboard of the Microsoft .NET agent:v Updated the MS .NET Status group widget on the Component page to display the

response times of database calls, status of .NET processes with high thread count, andJust in Time (JIT) compilation failures

v Added data sets, pages, and group widgets to show JIT compilation details, databasecall details, GC handles and pinned objects collection for a selected .NET process,thread contention rate, and thread queue length

v Added eventing thresholds for JIT failures, .NET request failures, slow commands,garbage collection, and the active threads in .NET processes

Monitoring Agent for Microsoft SQL ServerThe following enhancements are added to the dashboard of the Microsoft SQL Serveragent:v Added the Expensive Queries group widget in the Server Performance - Detail page to

view the top 10 cached query plans according to the performance statistics of theMicrosoft SQL Server

v Added support for monitoring the Microsoft SQL Server 2016v Added support to install and configure the Microsoft SQL Server agent on the

Microsoft Windows Server 2016 system


v Added the new COLL_ERRORLOG_RECYCLE_WAIT environment variable to set thetime interval (in seconds) for which the agent waits before collecting data of the MSSQL Error Event Detail attribute group

Monitoring Agent for MongoDBThe following enhancements are added to the dashboard of the MongoDB agent:v Updated the Component page to display the number of MongoDB instances and their

statusv Added pages to display details of the MMAPv1 and the WiredTiger storage enginesv Added the Input Output Information page to display cursor details and historical data

for the queued operations, active connections, data flow, and the data access of theselected host

v Added pages to display details of the locks of version 2.x and version 3.x, or laterv Added the Replication Details page to display details of the replication member, oplog,

and historical data of the replication lag and the space that is used by the oplog

Monitoring Agent for Node.jsThe following enhancements are added to the Node.js agent to leverage NodeApplication Metrics (Appmetrics):v Added new dashboard and group widgets to view garbage collection detailsv Added new dashboard and group widgets to view event loop details

Monitoring Agent for PostgreSQLThe following enhancements are added to the PostgreSQL agent:v Added support to install and configure the agent on Windows systemsv Added support for monitoring the PostgreSQL V9.6v Updated the Status Overview page so that status is not critical when the buffer hit rate

is zero

Monitoring Agent for SAP NetWeaver Java StackThe following enhancements are added to the SAP NetWeaver Java Stack agent:v Added data sets, group widgets, and pages to collect and view the transaction tracking

and diagnostics datav Added support to install and configure the agent on Windows 2016 systems

Monitoring Agent for Synthetic PlaybackThe following enhancement is added to the Synthetic Playback agent:v The Synthetic Playback agent includes a new filtering feature for synthetic transactions.

In the Synthetic Script Manager, configure blacklists and whitelists for your synthetictransactions that exclude or include requests to specified URLs and domains. Useblacklists and whitelists to filter out or include dependencies that affect the responsetimes for your application, such as third-party metrics.

Monitoring Agent for TomcatThe following enhancement is added to the Tomcat agent:v Added support to install and configure the Tomcat agent on Windows and SUSE Linux

Enterprise 12 systems

Monitoring Agent for WebSphere ApplicationsThe following enhancements are added to the WebSphere Applications agent:v Linux on Power Little Endian (pLinux LE) is supported. (Transaction tracking is not

supported on pLinux LE systems.)v Added support for IBM WebSphere Application Server traditional V9.


v Added the Memory Analysis dashboard to help you diagnose possible memory leaksby checking the heap usage information for each heap dump. The diagnostics modemust be enabled for this dashboard to contain data.

v Added support to use the Application Health Status data set to create event thresholdsfor application status monitoring. The data collection for this usage is disabled bydefault. You must modify the data collector properties file to enable it before you createevent thresholds.

v Simplified the manual configuration of data collector. For WebSphere ApplicationsServer, you only need to add some JVM arguments and variables for the applicationserver on the WebSphere administrative console. For Liberty, you only need to modifythree files for the server.

Response Time Monitoring AgentThe following enhancements are added to the Response Time Monitoring agent:v Added support for configuring user tracking for applications in the Agent

Configuration page.v Added support for configuring session tracking for applications in the Agent

Configuration page.

Cloud APM console enhancementsVarious improvements were made to the agent installation and configuration interfaces, as well asthe following console enhancements:v Technology preview: A new Custom Views tab is available for your Application Dashboard

pages. You can create a variety of views for reporting metrics from a managed resource andapply functions such as average and count. After you open a saved page, you can refresh thepage with data from a different resource, and download the page metrics as a PDF or CSV file.For more information, see Custom views on page 638.

If you do not see Custom Views in your Cloud APM subscription and you want to try out thisnew feature, please open a service request with IBM Support to enable the Custom Viewstechnology preview. Be aware that your custom dashboard pages and the historical data thatpopulates them are not saved during system maintenance.

v When you open the Cloud APM console help system, notice that it is hosted by IBMKnowledge Center. You have the

Hide table of contents tool, search and print capabilities,

and links to support information and feedback options.


http://ibm.biz/ibm_support

Before After

Agent Builder enhancementsSupport is improved for building Cloud APM summary dashboards for Agent Builder agents.You must use single-row data sets to provide data for summary dashboards. You can providesuch data sets from entire log files and from any sets of data that can be filtered to a single row.

Previous releases

For information about new features, capabilities, and coverage in previous releases, see the followingWhat's new topics:v What's new: September 2016 on page 11v What's new: April 2016

What's new: April 2016New features, capabilities, and coverage are available in this release.

IBM MarketplaceIBM Performance Management on Cloud offerings are available from IBM Marketplace. Sign upfor a free trial or subscription account. For more information, see Chapter 7, Downloading youragents and data collectors, on page 75.

New agents available

Monitoring Agent for Citrix Virtual Desktop InfrastructureYou can use the Citrix VDI agent to monitor the health, availability, and performance ofCitrix XenDesktop or XenApp resources such as sites, machines, applications, desktops,sessions, and users. This agent is in the Infrastructure Extension Pack and is available for


the following offerings: IBM Monitoring, IBM Application Performance Management, andIBM Application Performance Management Advanced.

Monitoring Agent for Microsoft Lync ServerYou can use the Microsoft Lync Server agent to monitor the health, availability, andperformance of the Microsoft Lync Server resources such as database, mediation server,synthetic transactions, instant messaging, CDR service write operations, and SIP peers.

Monitoring Agent for WebLogic

You can use the WebLogic agent to monitor the health, availability, and performance ofWebLogic server resources such as Java virtual machines (JVMs), Java messaging service(JMS), and Java Database Connectivity (JDBC).

Integration enhancements

Agent coexistenceAgent coexistence is supported. You can install IBM Performance Management agents onthe same computer where IBM Tivoli Monitoring agents are installed. However, bothagents cannot be installed in the same directory. See Cloud APM agent and TivoliMonitoring agent coexistence on page 513.

IBM Alert NotificationAlert Notification includes a mobile app that offers a subset of Alert Notificationfunctions on iOS and Android devices.

IBM integration stack monitoringYou can monitor the IBM integration stack to see transaction tracking information for the IBMMQ, IBM Integration Bus, and DataPower appliance middleware products and the services theyexpose and troubleshoot if any problems arise. See Scenario: Monitoring the IBM integrationstack on page 66.

Agent enhancements

Monitoring Agent for DB2Commands were added for granting privileges to the default user (for Windows systems)and instance owner user (for Linux and AIX systems) for viewing the data for some ofthe DB2 agent attributes.

Monitoring Agent for HadoopThe Hadoop agent is supported on Linux, Windows, and AIX operating systems.

Monitoring Agent for HMC BaseMonitoring capabilities are provided for virtual I/O and for hardware events.

Monitoring Agent for IBM Integration Bus

The library path of the latest version of IBM MQ (WebSphere MQ) can be automaticallydiscovered during agent configuration on Linux and AIX systems.

Monitoring Agent for Microsoft Cluster ServerThe Microsoft Cluster Server agent gets automatically configured after it is installed.

Monitoring Agent for Microsoft Exchange ServerSome additional services were added in the Exchange Services tab of the agentconfiguration window for determining the Exchange Server status.

Monitoring Agent for Microsoft Hyper-V ServerRemoved the agent configuration panel. The agent configuration is not required.

Monitoring Agent for SAP HANA DatabaseThe Cache Information Details group widget was added in the SAP HANA DatabaseDetails dashboard to provide information about the percentage of used memory,percentage of available memory, and hit ratio of the cache for the monitored database.


Monitoring Agent for Synthetic PlaybackThe Synthetic Playback agent includes the following features:v You can install and configure the Synthetic Playback agent to monitor the performance

and availability of private, internal-facing applications on the Application PerformanceDashboard, in addition to public, external-facing applications.

v Use the Synthetic Script Manager to generate a simple script to test the availability andperformance of your applications.

v Configure simultaneous or staggered playback of synthetic transactions at differentlocations.

v Monitor your monthly playback usage in the Synthetic Script Manager.v View HTTP metrics and availability ratios in Synthetic Playback agent reports.v View two new reports: Trend of Transactions and Trend of Subtransactions.v Organize your synthetic transactions into a resource group and apply thresholds to all

transactions in that resource group.v View synthetic transaction data in the My Transactions window in the Application

Performance Dashboard without needing to create an application that containsassociated synthetic transactions.

v Download synthetic scripts from Synthetic Script Manager.

Monitoring Agent for VMware VIThe VMware VI agent dashboard is enhanced to include the following new features:v The number of triggered alarms in the critical or warning state are also displayed on

the Component page.v A new table on the Cluster Summary page provides information about the proactive

and failure alarms. You can click the triggered entity in the table and view the detailpage of that triggered entity.

v A new table on the Cluster Detail page displays details of the ESX servers that belongto the selected cluster. You can click the ESX server and view the detail page of thatESX server.

v The Datastore table on the Cluster Detail page shows the over-commitment metric ofthe datastore.

v The Virtual Machines table on VM Detail page displays more performance metrics suchas memory size, NICs, and disks. You can click these metrics and view their detailpages.

v New widgets and pages are added to display important performance metrics of thememory, disks, and network for the selected virtual machine.

v A new table on the ESX Server Detail page displays the network performance of theserver network.

v The Datastore table on the VM Detail page and the ESX Server Detail page displays thelatency metric of the datastore.

v A new table on the Datastore Detail page displays information about the virtualmachine that is associated with the datastore. You can click the virtual machine in thetable and view the Virtual Machine Detail page.

v The title of the % Memory (History) chart on the VM detail page was changed to GuestMemory(History).

Monitoring Agent for WebSphere ApplicationsThe In-flight Requests Summary dashboard provides the capability to identify the requestinstances that are currently slow or hung. You can perform a soft cancel operation on anin-flight request by selecting the request and then clicking Cancel Thread in the In-flightRequest widget on this dashboard.


All predefined eventing thresholds were refined to provide a better user experience. Theenhancements and updates involve the condition that triggers an alert, the samplinginterval, and the severity of the threshold.

The user interface of the Monitoring Agent for WebSphere Applications is accessible tousers with physical disabilities.

The configuration process was refined based on customer feedback and technical reviewto provide a better user experience.

Monitoring Agent for WebSphere MQSome changes were made to the predefined eventing thresholds:v All predefined thresholds have a prefix of MQ_ instead of MQSeries_ as in previous

versions.v Two thresholds, MQ_Channel_Initiator_Crit and MQ_Queue_Manager_Crit, were

added to trigger critical alerts for the channel initiator server status and queuemanager status.

v The trigger condition of the MQ_Queue_Depth_High event was changed from static80% to the high depth value of the queue.

The name of the Queue not being Read - Top 5 widget was changed to Queue in Use notbeing Read - Top 5. This widget provides a list of top five queues that have messages andare connected by one or more applications to put messages on the queue, but are notbeing read by any application.

The library path of the latest version of IBM MQ (WebSphere MQ) can be automaticallydiscovered during agent configuration. You can keep the WMQLIBPATH parameter empty inthe silent response file or accept the default value when you configure the agentinteractively.

OS agentsThe OS agents contain a new functionality to monitor application log files. Thefunctionality includes the capability to configure log file monitoring based on regularexpressions.

For compatibility, the OS agent consumes the following information and formats:v Configuration information and the format file that was used by the IBM Tivoli

Monitoring 6.x Log File Agentv Configuration information and format strings that were used by the Tivoli Event

Console Log File Adapter

These format strings allow the agent to filter the log data according to patterns in theformat file and submit only the relevant data to an event consumer. The OS Agent sendsdata to the Performance Management server or through the Event Integration Facility(EIF) to any EIF receiver, such as the OMNIbus EIF probe.

Response Time Monitoring Agent

End User Transactions dashboards include user and device information, which waspreviously displayed in the Authenticated Users and Mobile Devices Users dashboards inthe Users group. User, session, and device information are sorted by location (country,state, and city) based on the IP address of the user. Use the new and updated dashboardsto understand user volumes and whether issues are isolated to specific sets of users.

Customize the locations that are applied to specific IP addresses or address ranges in theEnd User Transaction dashboards for your particular environment. Use the Geolocationtab in the Agent Configuration to customize location values.

Transaction TrackingThe Transaction Summary page includes a Service Dependencies topology, which showsthe selected resource node, such as an IBM Integration Bus, and the services that it


depends on. The Transaction Details page includes a Transaction Dependencies topologythat shows a transaction node for each component instance, and an uninstrumented nodefor each dependent service at the transaction level, for example, IBM Integration Bus andits service transactions. The Transaction Details page also highlights the users of theselected application who are experiencing the slowest response times, and the hosts withthe highest volume of transactions.

General agent enhancementsThe following general agent installation and configuration enhancements were made:v The agent installation script performs a permissions check before the installation starts.

If you do not have adequate permission, a message is displayed.v The agent status command checks the status between the agent and the Performance

Management console.v Agents that are supported on Windows systems have a GUI utility that you can use to

perform agent configuration and check the connection status.v You can use a new command to remove an agent instance without uninstalling the

agent.

Performance Management server enhancements

Performance Management user authentication is managed through a BlueID OpenID Connectprovider.

Performance Management console enhancements

v The Performance Management console appearance was updated to align with the IBM Bluemixuser interface. For example, view the differences between a summary box in the All MyApplications dashboard from V8.1.2 and now:

v A new option was added to the Advanced Configuration page so advanced users can easilyenable or disable all predefined thresholds across all system groups. See Thresholdsbackground information on page 546.

v A new option was added to the Advanced Configuration page to control the ApplicationPerformance Dashboard automatic refresh rate. For more information, see UI Integration onpage 601.

v Various improvements were made to the agent installation and configuration interfaces.v Improvements to the accessibility of the Performance Management console. For information

about the accessibility features of the user interface, see Accessibility features on page 663.

API You can use APIs to create scripts for automating the onboarding of your PerformanceManagement environment. For more information, see Exploring the APIs on page 600.

Agent Builder enhancementAgent Builder includes enhanced data set filtering. You can use filtering to create data sets thatreturn a single row based on multi-row data sets including the Availability data set. Use thisfeature to provide information in summary dashboards.

What's new: September 2016New features, capabilities, and coverage are available in this release.

New agents available


Monitoring Agent for Amazon EC2You can use the Amazon EC2 agent to monitor the health, availability, and performanceof your Amazon Elastic Compute Cloud (EC2) Instance resources. You can monitor thefollowing resources:v CPU utilizationv Elastic Block Store (EBS) utilizationv Network utilizationv Amazon Web Services (AWS) maintenance updatesv Disk performance

This agent is in the Infrastructure Extension Pack and is available for the followingofferings: IBM Monitoring, IBM Application Performance Management, and IBMApplication Performance Management Advanced.

Monitoring Agent for SAP NetWeaver Java StackYou can use the SAP NetWeaver Java Stack agent to monitor the health, availability, andperformance of your SAP NetWeaver Java Stack Cluster and Instance resources. You canuse the agent to monitor the cluster resources, such as heap dumps, JVM Instance,response time of the user sessions, transaction details, system information, and licensedetails. You can use the agent to monitor the instance resources, such as CPU utilization,disk utilization, memory utilization, database collection, garbage collection, heap dumps,failed application, web container, and session information. This agent is in the SAPExtension Pack and available if you have one of the following offerings: IBM ApplicationPerformance Management and IBM Application Performance Management Advanced.

Agent enhancements

Monitoring Agent for Citrix Virtual Desktop InfrastructureAdded the ability to retrieve Windows Event Log Events for Virtual Delivery Agent(VDA) and Desktop Delivery Controller (DDC) machines.

Monitoring Agent for Linux KVMDashboards are available for the agent to monitor the deployment of your LinuxKernel-based virtual machines. The dashboards provide the following monitoringcapabilities:v The summary dashboard shows the overall status of the hosts based on the CPU and

memory utilization of your Linux Kernel-based virtual machines environment orapplication.

v The Host Detail dashboard shows details about the selected host.v The Hosts, Clusters, and Storage dashboard shows details about the monitored virtual

machines.v The Virtual Machine Details dashboard shows details about the virtual machine that

you select on the Host Detail page.

Monitoring Agent for Linux OS

Docker V1.8.0 or later is supported. New attribute groups and widgets were added toenable the Linux OS agent to deliver docker monitoring capabilities.

Monitoring Agent for Oracle DatabaseThe Oracle Database agent dashboard includes the following new features on the InstanceDetails page:v A table that displays information about the lock contention on the selected instance.v A table that displays information about the Oracle Real Application Clusters GCS and

GES.v A table that displays details of the Automatic Storage Management (ASM) disk groups

that are attached to the selected instance.


v A view that shows detailed information per tablespace, which is visible if you clickBottom 5 Free Table Space.

v A table that displays the historical details of the foreground and background processesthat are attached to the selected instance. You can click the entity in the table and viewa detailed table of all processes for that instance.

v A table that displays the Top 5 Worst SQL queries (by run time) on the selectedinstance. You can click in the table and view a detailed table of the top 50 worst SQLqueries for that instance.

Monitoring Agent for Synthetic PlaybackThe Synthetic Playback agent includes a new security feature. You can prevent passwordsthat are stored in synthetic scripts from displaying in the Synthetic Script Manager.

Monitoring Agent for VMware VIWith the addition of the agent decoupling feature, you can view and select the agentnode and its subnodes in the same view.

When you select the VMware Virtual Infrastructure component in the Select Componentwindow, the Component Editor displays a tree structure of the agent node with all itssubnodes.v If you expand the tree and select the agent node, all subnodes are automatically

selected. You can also expand the tree and individually select the subnodes that youwant to monitor.

v If you select the agent node when the tree is collapsed, all subnodes are automaticallyexcluded.

When you select the ESX Server component in the Select Component window, along withsubnodes, stand-alone ESX Servers are also displayed in the Component Editor. With thesubnodes, you can select stand-alone ESX Servers for monitoring.

After the application is created, the APM UI dashboard displays a tree structure of theagent instance as parent and its nodes as children.


You can customize the locations that are applied to specific IP addresses or addressranges in the End User Transaction dashboards for your particular environment. Use theGeolocation tab in the Agent Configuration to customize location values.

Cloud APM console enhancements

v Various improvements were made to the agent installation and configuration interfaces.v A Dashboard Log option was added to the Actions menu to review the list of agent

dashboards that were updated since the last server restart. For more information, see All MyApplications - Application Performance Dashboard on page 605.

v The Application Performance Dashboard page for the selected application is streamlined forimproved viewing. A count of critical and warning severity events is displayed on the Eventstab title and replaces the Event Severity Summary bar chart. For applications with topologyviews enabled, the Aggregate Application Topology view has a toggle button for switching tothe Current Component Status bar chart. For more information, see Status Overview on page608.

v In earlier releases, the Application Performance Dashboard Attribute Details tab was availableonly for component instances. The Attribute Details tab is available for creating historicaltables of Response Time Monitoring agent and Synthetic Playback agent transaction instances.For visually impaired users, the ability to create historical tables provides an alternative to linecharts, which assistive technologies such as screen-reader software cannot interpret. For moreinformation, see Viewing and managing custom charts and tables on page 618.


API You can use APIs to create scripts for automating the onboarding of your PerformanceManagement environment. For more information, see Exploring the APIs on page 600.


Chapter 2. Product overview

IBM Cloud Application Performance Management is a comprehensive solution that helps you manage theperformance and availability of applications that are deployed on premises, in a public cloud, or as ahybrid combination. This solution provides you with visibility, control, and automation of yourapplications, ensuring optimal performance and efficient use of resources.

By using this solution, you manage your data center, cloud infrastructure, and workloads with cognitiveintelligence. You can reduce and prevent outages and slowdowns around the clock in a hybridapplication world as Cloud APM assists you in moving from identifying performance issues to isolatingwhere the problem is occurring and diagnosing issues before your business is impacted.

Use the key features, which vary by offering, to work with data that is collected by the Cloud APMagents. More features are available through integration with other products and components.

Architecture overviewIBM Cloud Application Performance Management uses agents and data collectors to collect data on themonitored hosts. Agents and data collectors pass the data to the Cloud APM server, which collates it intothe Cloud APM console. The Cloud APM server is hosted in the IBM cloud.

Agents and data collectors

Agents and data collectors monitor systems, subsystems, or applications and collect data. An agent or adata collector interacts with a single resource (for example, a system or application) and, in most cases, ison the same computer or virtual machine where the system or application is running. For example, theLinux OS agent collects performance indicators for the operating system on the Linux host and the

Copyright IBM Corp. 2014, 2017 15

WebSphere Applications agent monitors the performance indicators of WebSphere application servers.Also, some agents track transactions between different resources.

You can set up thresholds on key performance indicators (KPIs). If an indicator changes to go over orunder the threshold, the agent or data collector generates an alert, which the server processes. You canalso configure forwarding of events to a target such as the Netcool/OMNIbus Probe for Tivoli EIF or anSMTP server and use Alert Notification to configure email notifications for events.

Agents and data collectors are preconfigured to communicate with the Cloud APM server.

Communication between the server and agents or data collectors

The agents or data collectors on every monitored host establish HTTPS communication with the CloudAPM server, which is in the IBM cloud. The agent is the client side of the connection.

The agents or data collectors require internet connectivity to send data to the server and, if they cannotsend data directly over the internet, a forward proxy might be required. For more information aboutforward proxy, see Configuring agents to communicate through a forward proxy on page 113.

For information about the protocols or algorithms that are used for HTTPS communication, see Securecommunication on page 113.

Every 60 seconds, agents or data collectors push information to the server. Every agent or data collectorpushes all the information that is required to populate the user interface every minute. For example, anoperating system agent pushes information such as CPU and memory usage to the server every 60seconds, even if no user is viewing the information at the moment.

Data stored by the server

Every 60 seconds, agents and data collectors push resource monitoring data to the Cloud APM server.Transaction monitoring data is also sent to the server. The server stores all the values that are sent by theagents and data collectors for 8 days. Summarized transaction data is stored for longer periods.

Saved monitoring data is called historical data. The server uses historical data to display tables andgraphs that you can use to analyze the trends in your environment.

Historical reports are also available for certain agents. For more information, see Reports on page 646.

Scalability

Depending on your IBM Cloud Application Performance Management offering and the capacity of yourCloud APM server environment, you can connect up to 4000 agents.

Integration

IBM Cloud Application Performance Management integrates with other products and components whenthey are configured for communication with the Cloud APM server.

Products that can be integrated include Netcool/OMNIbus, Tivoli Monitoring, IBM OMEGAMON,Operations Analytics - Log Analysis, Operations Analytics - Predictive Insights, IBM Alert Notificationand IBM Bluemix.

Agent Builder is a component that can be used to create custom agents.


User interfaceThe Cloud APM console is the user interface for Cloud APM. This unified user interface provides a singleview across hybrid applications. You use the console to view the status of your applications and quicklyassess and fix performance and availability issues.

The dashboards in the console simplify problem identification so you can isolate bottlenecks that affectapplication performance. With simple dashboard navigation, you move from a view of application statusto code level detail. You have visibility into source code problems at the exact moment of an issue. Youcan search and diagnose problems by using integrated search analytics.

The Application Performance Dashboard navigator in the console is hierarchical, giving a status overviewof your applications, the health of their components, and the quality of the user experience. For moredetails about your monitored resource, you can click a navigator item or a link in the dashboard views.Consider, for example, that your application has a slow response time. The issue is revealed in thedashboard. Starting from your dashboard, you can follow the problem to the source by clicking links todiscover the cause: high CPU usage on a system due to an out-of-control process.

For more information about using the dashboards in the Cloud APM console, see Chapter 14, Using thedashboards, on page 605.

Offerings and add-onsIBM Cloud Application Performance Management contains two offerings and multiple add-ons. Specificadd-ons can be used with each offering.

For each offering, add-ons are available in IBM Marketplace. IBM Cloud Application PerformanceManagement, Advanced is the most comprehensive offering, the one that includes all agents, datacollectors, and dashboard pages. IBM Cloud Application Performance Management, Base is a subset of

Chapter 2. Product overview 17

https://www.ibm.com/us-en/marketplace/application-performance-management/purchase

Cloud APM, Advanced. You can replace Cloud APM, Base with Cloud APM, Advanced at any time. Thefinal installed offering after this replacement is Cloud APM, Advanced. The diagram shows whichadd-ons are available for each offering.

Offerings

IBM Cloud Application Performance Management, AdvancedThis offering is for end user experience, transaction tracking, and resource monitoring ofall your application components. You have code level visibility into your applications andthe health of your application servers. Use the diagnostics dashboards to findperformance bottlenecks in the application code and for managing your criticalapplications in production.

The offering includes the IBM Cloud Application Performance Management, Base, andcontains agents and data collectors that you use to monitor applications, transactions, andother resources that are installed in your enterprise.

With this offering, DevOps has a complete solution that provides full visibility andcontrol over your applications and infrastructure. Line of business owners can managecritical applications and end user experience in production. Application developers canview transaction details and diagnose application problems.

IBM Cloud Application Performance Management, BaseThis offering is for resource monitoring of infrastructure, application components, andcloud workloads. Resource monitoring helps you identify and address slow transactions,capacity issues, and outages.

The offering contains agents and data collectors that you use to monitor applications andother resources that are installed in your enterprise.

With this offering, IT operators can deal with slow transactions, capacity issues, andoutages.

Add-ons

Advanced Extension Pack This extension pack contains the Monitoring Agent for SAP HANA Database, the SAPNetWeaver Java Stack agent, and the Monitoring Agent for RabbitMQ. Use the SAPHANA Database agent to monitor the SAP HANA database. Use the SAP NetWeaverJava Stack agent to monitor the SAP NetWeaver Java Stack. Use the RabbitMQ agent tomonitor RabbitMQ messaging. This extension pack is available if you have the IBMCloud Application Performance Management, Advanced offering.


Base Extension PackThis extension pack contains the Monitoring Agent for Cassandra, the Monitoring Agentfor Hadoop, and the Monitoring Agent for Microsoft Office 365. Use these agents tomonitor a Cassandra database, Hadoop cluster, and Microsoft Office 365 subscriptions.This extension pack is available if you have either of the Cloud APM offerings.

Infrastructure Extension PackThis extension pack contains the Monitoring Agent for Amazon EC2 and the MonitoringAgent for Citrix Virtual Desktop Infrastructure. Use the Citrix VDI agent to monitor yourCitrix virtual desktop infrastructure. Use the Amazon EC2 agent to monitor your AmazonEC2 instances. This extension pack is available if you have either of the Cloud APMofferings.

z Systems Extension PackYou can use the z Systems Extension Pack to view monitoring data and events for yourOMEGAMON application components in the Cloud APM console. This extension pack isavailable if you have either of the Cloud APM offerings.

Operations Analytics - Predictive InsightsThis add-on is for analyzing the metric data that is collected by Cloud APM, andgenerating alarms when anomalies are detected. The add-on is available if you haveeither of the Cloud APM offerings.

Website MonitoringThis add-on is for monitoring the availability and performance of your web applicationsfrom multiple geographically distributed points of presence. This add-on does notfunction as a stand-alone offering, but is available if you have the IBM Cloud ApplicationPerformance Management, Advanced offering.

For an overview of the features in each offering, see Offering details.

To see which agents are included in an offering or add-on and the agent or data collector capabilities, seeCapabilities on page 21.

For a description of each agent or data collector and their specific information, see Descriptions onpage 24.

Offering detailsSome features are available for all offerings and others are available only for certain offerings.

Table 1 shows key features that are available for each offering at-a-glance.

Table 1. Features in each offering

FeatureCloud APM, Advanced

(For DevOps, Developers,and Line of Business)

Cloud APM, Base(For Operations)

Application resource monitoring:Languages, middleware (coverage varies by offering).

Operating system monitoring:Linux, UNIX, Windows systems

Log file monitoring:Use the OS Agents to monitor application log files.


Table 1. Features in each offering (continued)




Dashboards:

v View Tivoli Monitoring and Cloud APM KPIs in thesame dashboards

v Historical metricsv Customizable dashboards

APIs:Manage your environment by using APIs.

Role-based access control:Manage the access and privilege of your IBM CloudApplication Performance Management users.

Historical reporting:Generate reports for the performance and response timeof your applications that are broken down by transaction,device, browser, and others (coverage varies by offering).

IBM Agent Builder:Build custom agents to monitor any platform ortechnology.

Database resource monitoring:(coverage varies by offering)

Infrastructure resource monitoring:Hypervisors, storage, and network (coverage varies byoffering).

Commercial applications resource monitoring:Business and collaboration applications (coverage variesby offering).

Response time monitoring:See how your application performance is affecting yourusers.

Integration with search analytics:Find the insights to quickly isolate, diagnose, and resolveproblems.

Operations Analytics - Predictive Insights (add-on):Determine application performance anomalies before theyimpact your users.

Real end user experience monitoring:See what your users experience from your infrastructureto their device.

Transaction tracking:Track end-to-end transactions through your applicationenvironment.

v Application topology: See how all components areconnected in your application environment.

v Transaction instance topology: See the path that isfollowed through your environment for each instanceof a transaction.

Synthetic Playback:Monitor the availability of your internal websites.


Table 1. Features in each offering (continued)




Deep-dive diagnostics:

v Drill down from summary dashboards to viewcode-level, stack trace, and SQL query detail forspecific agents.

v Detect, diagnose, and kill hung or slow transactionsthat are still in progress.

Thresholds:Detect specific application behaviors and conditionsbased on actively monitored definitions.

Resource groups:Categorize managed systems in your monitoredenterprise by their purpose.

Extra features such as the following are available for all offerings through integration with other productsand components. See Integration on page 39, and for more details, see Chapter 11, Integrating withother products and components, on page 513).v Tivoli Monitoring and OMEGAMON agents: Use the Hybrid Gateway to retrieve monitoring data and

events so this information is displayed in the Cloud APM console.v Agent coexistence: Install Cloud APM agents on the same computer where Tivoli Monitoring agents

are installed.v Netcool/OMNIbus and other EIF receivers: Forward events to IBM Tivoli Netcool/OMNIbus.v Alert Notification: Receive notification when application performance exceeds thresholds.v IBM Control Desk: Automatically open tickets in Control Desk.v IBM Bluemix: Monitors Bluemix applications.

Agents and data collectorsIBM Cloud Application Performance Management agents and data collectors are available in the offeringsand add-ons.

CapabilitiesAgent and data collector capabilities vary depending on your offering. The key agent and data collectorcapabilities are resource monitoring, transaction tracking, and diagnostics. You can subscribe to any of theofferings and add-ons in IBM Cloud Application Performance Management. Specific offerings arerequired for add-ons.

Each agent or data collector monitors the resources for which the agent or the data collector is named, forexample the Monitoring Agent for Cisco UCS monitors Cisco UCS resources.

Depending on whether you are a developer, in operations, or a line-of-business owner, you use differentCloud APM capabilities. Some capabilities are common to all offerings, for example, resource monitoring.Other capabilities such as transaction tracking and deep-dive diagnostics are available only in specificofferings.v Resource monitoring capability includes response time monitoring, application resource monitoring,

and infrastructure resource monitoring.v Transaction tracking capability provides transaction instance and topology information for agents and

data collectors with this capability as noted in Table 2 on page 22.


v Diagnostics capability includes tracing and analyzing individual requests, and when necessary, methodcalls.

The agents and data collectors for the applications that you want to monitor are available for downloadfrom Products and services. The agents take minutes to install. The data collectors require no installation,and you need to only configure them after the download completes. For instructions about installing theagents, see Chapter 9, Installing your agents, on page 83.

Table 2 provides a comprehensive list of the agents and data collectors, shows which offering or add-oncontains the agent or data collector, and shows the capabilities of the agent or data collector. Whenadd-ons (such as Infrastructure Extension Pack and Website Monitoring) are noted for an agent or a datacollector, they are required.

In Table 2, indicates resource monitoring, indicates transaction tracking, and

indicatesdiagnostics.

Table 2. Agent and data collector capabilities in each offering

Agents and data collectors Cloud APM, Advanced Cloud APM, Base

Amazon EC2 agentInfrastructure Extension Pack Infrastructure Extension Pack

Cassandra agent

Base Extension Pack Base Extension Pack

Cisco UCS agent

Citrix VDI agentInfrastructure Extension Pack Infrastructure Extension Pack

Data collectors for Bluemix applications

v Bluemix Liberty data collectorv Bluemix Node.js data collectorv Bluemix Python data collectorv Bluemix Ruby data collector

DB2 agent

DataPower agent

Hadoop agentBase Extension Pack Base Extension Pack

HMC Base agent

HTTP Server agent

IBM Integration Bus agent

(REST API services are not monitoredby the IBM Integration Bus agent)

JBoss agent

Linux OS agent

Linux KVM agent

Microsoft Active Directory agent

Microsoft Cluster Server agent

Microsoft Exchange Server agent

Microsoft Hyper-V Server agent


Table 2. Agent and data collector capabilities in each offering (continued)

Agents and data collectors Cloud APM, Advanced Cloud APM, Base

Microsoft IIS agent

Microsoft Lync Server agent

Microsoft .NET agent

Microsoft Office 365 agent

Base Extension Pack Base Extension Pack

Microsoft SharePoint Server agent

Microsoft SQL Server agent

MongoDB agent

MySQL agent

NetApp Storage agent

Node.js agent

OMEGAMON agents

z Systems Extension Pack z Systems Extension Pack

Oracle Database agent

PHP agent

PostgreSQL agent

Python agent

Python data collector

RabbitMQ agent


Ruby agent

SAP agent

SAP HANA Database agentAdvanced Extension Pack

SAP NetWeaver Java Stack agent

Advanced Extension Pack

Siebel agent

Synthetic Playback agentWebsite Monitoring

Tomcat agent

UNIX OS agent

VMware VI agent

WebLogic agent

WebSphere Applications agent

WebSphere Infrastructure Manageragent

WebSphere MQ agent

Windows OS agent


DescriptionsReview the agent and data collector descriptions for a synopsis of each IBM Cloud ApplicationPerformance Management agent or data collector, and to access more information about the agents.

Each agent or data collector has a version number, which changes each time the agent or data collector isupdated. In any release, new agents and data collectors might be added, and existing agents and datacollectors might be updated. If you do not have the latest version of an agent or data collector, considerupdating it. For information about how to check the version of an agent or data collector in yourenvironment, see Agent version command.

Each agent or data collector description provides links to the following types of details about the CloudAPM agent or data collector:v Agent or data collector configuration and other information about specific agent or data collector

capabilitiesv Reference PDF that contains descriptions of the Cloud APM agent or data collector dashboards, group

widgets, thresholds, data sets, and attributes (metrics and KPIs)

For links to documentation for IBM Tivoli Monitoring V6 and V7 agents that can coexist with CloudAPM V8 agents and data collector, see Table 63 on page 514.

Data collectors for Bluemix applicationsThe data collectors for Bluemix applications provide you with the capability to monitor thefollowing types of Bluemix applications:v Bluemix Liberty applicationsv Bluemix Node.js applicationsv Bluemix Python applicationsv Bluemix Ruby applications

Both resource monitoring and deep-dive diagnostics are supported, which helps detect, isolate,and diagnose issues of your Bluemix applications. You can configure the data collector to trackthe performance of individual request and method calls, and use the information to diagnoseslow requests and take actions accordingly.v For information about configuring the data collectors, see Configuring the data collectors for

Bluemix applications on page 133.v For information about the dashboards, thresholds, and attributes, see the Bluemix monitoring

Reference.

Monitoring Agent for Amazon EC2The Amazon EC2 agent provides you with a central point of monitoring for the health,availability, and performance of your Amazon Elastic Compute Cloud (EC2) instances. The agentdisplays a comprehensive set of metrics to help you make informed decisions about your EC2environment, including CPU utilization, Elastic Block Store (EBS) utilization, network utilization,Amazon Web Services (AWS) maintenance updates, and disk performance.v For information about configuring the agent after installation, see Configuring the Amazon

EC2 agent on page 121.v For information about the dashboards, thresholds, and attributes, see the Amazon EC2 agent

Reference.

Monitoring Agent for CassandraThe Cassandra agent provides you with the capability to monitor the Cassandra cluster. You cancollect and analyze information about the nodes, keyspaces, and column families of theCassandra cluster.v For information about configuring the agent after installation, see Configuring the Cassandra

agent on page 122.


http://ibm.biz/bluemixdatacollechttp://ibm.biz/bluemixdatacollechttps://ibm.biz/agent-amazonec2https://ibm.biz/agent-amazonec2

v For information about the dashboards, thresholds, and attributes, see the Cassandra agentReference .

Monitoring Agent for Cisco UCSThe Cisco UCS agent provides you with an environment to monitor the health, network, andperformance of Cisco UCS. The Cisco UCS agent provides a comprehensive way for collectingand analyzing information that is specific to Cisco UCS and required to detect problems earlyand prevent them.v For information about configuring the agent after installation, see Configuring the Cisco UCS

agent on page 124.v For information about the dashboards, thresholds, and attributes, see the Cisco UCS agent

Reference.

Monitoring Agent for Citrix Virtual Desktop InfrastructureThe Citrix VDI agent provides you with a central point of monitoring for the health, availability,and performance of your Citrix virtual desktop infrastructure. The agent displays acomprehensive set of metrics to help you make informed decisions about your XenDesktop orXenApp resources, including sites, machines, applications, desktops, sessions, users, and more.v For information about configuring the agent after installation, see Configuring the Citrix VDI

agent on page 130.v For information about the dashboards, thresholds, and attributes, see the Citrix VDI agent

Reference.

Monitoring Agent for DataPowerThe DataPower agent provides a central point of monitoring for the DataPower Appliances inyour enterprise environment. You can identify and receive notifications about common problemswith the appliances. The agent also provides information about performance, resource, andworkload for the appliances.v For information about configuring the agent after installation, see Configuring the DataPower

agent on page 146.v For information about the dashboards, thresholds, and attributes, see the DataPower agent

Reference.v For information about monitoring DataPower appliances as part of the IBM integration stack,

see Monitoring the IBM integration stack on page 66.

Monitoring Agent for DB2The DB2 agent offers a central point of monitoring for your DB2 environment. You can monitor amultitude of servers from a single IBM Performance Management console, with each servermonitored by a DB2 agent. You can collect and analyze information in relation to applications,databases, and system resources.v For information before you upgrade to a new version of the agent, see Agents on AIX:

Stopping the agent and running slibclean before you upgrade on page 538v For information about configuring the agent after installation, see Configuring the DB2 agent

on page 157.v For information about the dashboards, thresholds, and attributes, see the DB2 agent Reference.v For information about monitoring database transactions as part of the IBM Java application

stack, see Monitoring the IBM Java application stack on page 59.

Monitoring Agent for HadoopThe Hadoop agent provides capabilities to monitor the Hadoop cluster in your organization. Youcan use the agent to collect and analyze information about the Hadoop cluster, such as status ofdata nodes and Java virtual machine, memory heap and non-heap information, and informationabout Hadoop nodes, file systems, and queues.v For information about configuring the agent after installation, see Configuring the Hadoop

agent on page 164.


http://ibm.biz/agent-cassandrahttp://ibm.biz/agent-cassandrahttps://ibm.biz/agent-ciscoucshttps://ibm.biz/agent-ciscoucshttps://ibm.biz/agent-citrixvdihttps://ibm.biz/agent-citrixvdihttp://ibm.biz/agent-datapowerhttp://ibm.biz/agent-datapowerhttp://ibm.biz/agent-db2

v For information about the dashboards, thresholds, and attributes, see the Hadoop agentReference.

Monitoring Agent for HMC BaseThe HMC Base agent provides you with the capability to monitor the Hardware ManagementConsole (HMC). The agent monitors the availability and health of the HMC resources: CPU,memory, storage, and network. The agent also reports on the HMC inventory and configurationof Power servers, CPU pools, and LPARs. The CPU utilization of the Power servers, LPARs, andpools are monitored by using HMC performance sample data.v For information about configuring the agent after installation, see Configuring the HMC Base

agent on page 170.v For information about the dashboards, thresholds, and attributes, see the HMC Base agent

Reference.

Monitoring Agent for HTTP ServerThe HTTP Server agent collects performance data about the IBM HTTP Server. For example,server information, such as the status and type of server, the number of server errors, and thenumber of successful and failed logins to the server are shown. A data collector gathers the d

IBM Performance Management on Cloud: User's Guide

Documents

Transcript of IBM Performance Management on Cloud: User's Guide