User and training guides and related documentation from Parametric Technology Corporation and its subsidiary companies (collectively "PTC") are

Transcription

1 PTC System Monitor Installation and Usage Guide PTC System Monitor 2.0 July 17, 2012

2 Copyright 2012 Parametric Technology Corporation and/or Its Subsidiary Companies. All Rights Reserved. User and training guides and related documentation from Parametric Technology Corporation and its subsidiary companies (collectively "PTC") are subject to the copyright laws of the United States and other countries and are provided under a license agreement that restricts copying, disclosure, and use of such documentation. PTC hereby grants to the licensed software user the right to make copies in printed form of this documentation if provided on software media, but only for internal/personal use and in accordance with the license agreement under which the applicable software is licensed. Any copy made shall include the PTC copyright notice and any other proprietary notice provided by PTC. Training materials may not be copied without the express written consent of PTC. This documentation may not be disclosed, transferred, modified, or reduced to any form, including electronic media, or transmitted or made publicly available by any means without the prior written consent of PTC and no authorization is granted to make copies for such purposes. Information described herein is furnished for general information only, is subject to change without notice, and should not be construed as a warranty or commitment by PTC. PTC assumes no responsibility or liability for any errors or inaccuracies that may appear in this document. The software described in this document is provided under written license agreement, contains valuable trade secrets and proprietary information, and is protected by the copyright laws of the United States and other countries. It may not be copied or distributed in any form or medium, disclosed to third parties, or used in any manner not provided for in the software licenses agreement except with written prior approval from PTC. UNAUTHORIZED USE OF SOFTWARE OR ITS DOCUMENTATION CAN RESULT IN CIVIL DAMAGES AND CRIMINAL PROSECUTION. PTC regards software piracy as the crime it is, and we view offenders accordingly. We do not tolerate the piracy of PTC software products, and we pursue (both civilly and criminally) those who do so using all legal means available, including public and private surveillance resources. As part of these efforts, PTC uses data monitoring and scouring technologies to obtain and transmit data on users of illegal copies of our software. This data collection is not performed on users of legally licensed software from PTC and its authorized distributors. If you are using an illegal copy of our software and do not consent to the collection and transmission of such data (including to the United States), cease using the illegal version, and contact PTC to obtain a legally licensed copy. Important Copyright, Trademark, Patent, and Licensing Information: See the About Box, or copyright notice, of your PTC software. UNITED STATES GOVERNMENT RESTRICTED RIGHTS LEGEND This document and the software described herein are Commercial Computer Documentation and Software, pursuant to FAR (a)-(b) (OCT 95) or DFARS (a) and (a) (JUN 95), and are provided to the US Government under a limited commercial license only. For procurements predating the above clauses, use, duplication, or disclosure by the Government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software Clause at DFARS (OCT 88) or Commercial Computer Software-Restricted Rights at FAR (c)(1)-(2) (JUN 87), as applicable Parametric Technology Corporation, 140 Kendrick Street, Needham, MA USA

3 Contents About This Guide...5 Introducing the PTC System Monitor...7 PTC System Monitor Details...8 Working with PTC Technical Support...14 License Information...20 Accessing Online Documentation...21 Planning a PTC System Monitor Deployment...23 Single Host Configuration...24 Desktop Virtualized Installation...25 Production and Test Configurations...26 dynatrace Server and Collector Installation Guidelines...26 Verifying a Deployment...28 Backup and Recovery Strategies...29 Installing and Configuring the PTC System Monitor...31 PTC System Monitor Installation and Initial Configuration Overview...32 Downloading the Media Content for PTC System Monitor...36 Installing Using the GUI...37 Installing Using the Command Line...45 Starting and Stopping dynatrace Components...50 Installing PTC FastPacks...53 Setting up Monitoring for Multiple Integrity Applications...56 Setting Initial Configuration Options...57 Uninstalling the PTC System Monitor...65 Using PTC System Monitor Client...73 PTC System Monitor Client Overview...74 Client Startup...76 Start Center...79 Basic Client Navigation...80 FastPack Considerations Backing Up Current Configuration...83 Dashlets and Dashboards...84 Search for Information...85 Filters...86 Configure Monitoring for Your System...87 Monitoring Integrity Accessing Dashboards that Provide Monitoring Information Using Integrity Server Dashboards Using Incidents to Locate Issues Using Business Transactions to Locate Issues

4 Limiting the Overhead of the PTC System Monitor Using Self-Monitoring and Other Incidents to Check PTC System Monitor Performance Glossary of dynatrace Terms PTC System Monitor Installation and Usage Guide

5 About This Guide This guide documents the installation and use of the PTC System Monitor. It contains the following chapters: Introducing the PTC System Monitor on page 7 Planning a PTC System Monitor Deployment on page 23 Installing and Configuring the PTC System Monitor on page 31 Using PTC System Monitor Client on page 73 Monitoring Integrity on page 107 Glossary of dynatrace Terms on page 143 This guide is intended for system administrators who are installing the PTC System Monitor and setting up their Integrity environment to work with the PTC System Monitor. The PTC System Monitor is powered by the dynatrace Production Edition. To take advantage of the functionality in the PTC System Monitor, you must have: General system administration and networking knowledge General Integrity knowledge 5

6 Technical Support Contact PTC-Integrity Support through the PTC website ( support/index.htm), or by phone, , or fax if you encounter problems using this product or the product documentation. You must have a Service Contract Number (SCN) before you can receive technical support. If you do not have an SCN, contact the PTC Maintenance Department using the instructions found in the PTC Customer Service Guide or on the PTC Technical Support page. For additional information about the support policy for the PTC System Monitor, see Working with PTC Technical Support on page 14. Documentation for Integrity Products You can access Integritydocumentation using the following resources: The PTC System Monitor documentation is contained in this document. Additional documentation is available from the dynatrace Client. You can access the dynatrace documentation from the client by pressing F1 or clicking any help icon. Documentation for other Integrity products is available on the Integrity Customer Community, accessible through the PTC website ( com/support/index.htm). 6 PTC System Monitor Installation and Usage Guide

7 1 Introducing the PTC System Monitor PTC System Monitor Details...8 Working with PTC Technical Support...14 License Information...20 Accessing Online Documentation...21 This chapter describes the dynatrace product that is the underlying software in the PTC System Monitor. It also provides technical support information and license information. 7

8 PTC System Monitor Details The PTC System Monitor is a separate, independent, application performance monitoring system that is powered by the Production Edition of dynatrace. PTC has tailored the dynatrace Production Edition to meet the needs for monitoring Integrity. The PTC System Monitor provides useful dashboards and instrumentation that allows monitoring while maintaining critical performance requirements. dynatrace Components The following dynatrace components are installed with the PTC System Monitor: dynatrace Description Component Server Provides real-time analysis, root-cause analysis, collaboration, reporting, web access, alerting services, central management, and dynatrace documentation. Includes an embedded collector and repository that can be used for exploratory purposes. Standalone Collector Collects the information coming from agents, including PurePath and monitoring information. For descriptions of common dynatrace terms including PurePath, see Glossary of dynatrace Terms on page 143. Agents Allows Java Virtual Machine processes to be monitored. The agents are lightweight shared libraries that are loaded by the JVMs that execute Integrity server processes. Client Provides the user interface for monitoring your Integrity environment and troubleshooting issues. This client is available as installed version and also available remotely using Java Web Start technology. The following components are not installed by default with the PTC System Monitor: dynatrace Analysis Server The dynatrace Memory Analysis Server can provide deep memory analysis services of large memory dumps. Although mentioned in the dynatrace documentation, it is not currently included in the installation package that PTC provides. It can be optionally installed if needed. 8 PTC System Monitor Installation and Usage Guide

9 dynatrace Local Client The local client is a Java-based application that is installed on machines from which monitoring activities are performed. Although mentioned in the dynatrace documentation, it is not currently included in the installation package that PTC provides. It can be optionally installed if needed. Additional Components In addition to the installed dynatrace components, you must set up a production database (either SQL Server or Oracle) as the data repository to use with the dynatrace Server to monitor production or test data. Use the embedded repository only for non-production system environments. In the dynatrace documentation, the repository is known as the Performance Warehouse. You should also consider using an LDAP directory to provide authenticated access to the monitoring capabilities exposed by the PTC System Monitor. To establish users who have authenticated access to monitoring capabilities, you can manually define users through the client or you can connect to an existing LDAP directory. LDAP setup details are described later in this guide. Using dynatrace Components Installation of the PTC System Monitor includes injecting dynatrace Agents in the Java Virtual Machines that execute Integrity components. Think of these agents as modules that allow instrumentation of Integrity through the placement of sensors on specific classes and methods. Sensors are comprised of small bits of injected byte-code that sit at component boundaries and capture contextual information, such as response time data, CPU usage, method arguments, SQL statements, exceptions, and memory allocation. Each agent passes the collected information to a dynatrace Collector, which subsequently communicates with a dynatrace Server where the data is reassembled and analyzed. Introducing the PTC System Monitor 9

10 When working with a fully instrumented environment, there are many agents and a lot of data being transmitted. The dynatrace Collectors exist to efficiently handle this voluminous data, as shown in the following diagram: The collectors manage all of the data sent by agents and pass that data on to the dynatrace Server, where some of the data is distilled into PurePaths. For example, a PurePath can contain the information collected from an individual request as it 10 PTC System Monitor Installation and Usage Guide

11 travels through your Integrity environment. The following diagram shows a sample PurePath. The agents pass the information captured by sensors to a collector, and then the collector passes that data to the server: PTC provides sensors and sensor groups specific to Integrity and eventually to many components in Integrity. By accessing the sensor data from the dynatrace Server using the Webstart Client, you can see monitoring and performance related information almost instantaneously. dynatrace Production Edition Technical Details The dynatrace Production Edition provides advanced application performance management tools for rapidly identifying and diagnosing problems in applications, reducing mean time to repair. With dynatrace Production Edition, companies can now manage the performance of their mission critical applications in a 24x7 environment, capture critical diagnostics information all the time, provide exact root-cause analysis and resolve Java/.NET issues in minutes instead of days. The dynatrace always-on PurePath transaction tracing technology makes this all possible by enabling you to manage business transactions end-to-end and map application dependencies to quickly understand issue priorities. Performance diagnostics down to code-level enables rapid diagnosis of the root cause of issues. Additionally, PurePath information can be shared with all stakeholders to quickly reach consensus on issues and resolutions. Introducing the PTC System Monitor 11

12 The Production Edition provides: PurePath technology allows you to diagnose root-cause in minutes Tracing of individual transactions Real-time business-level to code-level visibility End-to-end across globally distributed tiers Low overhead, small footprint on target servers Share reports with all key stakeholders Measure application performance on all levels Extend dynatrace with open source plugins Automatically document and isolate problems Rapidly diagnose and resolve problems Rapidly deploy in your datacenter Key Production Edition features include: Deep-dive diagnostics in production Always-on 24x7 code-level transaction tracing at low 3-5% overhead Business transaction management with application and system monitoring Application discovery and dependency mapping with UML modeling Dashboards for monitoring, including business, operations, test, and development Global transaction tracing, diagnostics, and monitoring Real-time alerting and automated problem documentation Interactive real-time and offline code-level problem reports SOA, virtualization, and cluster support 12 PTC System Monitor Installation and Usage Guide

13 Other Editions Available from dynatrace In addition to the Product Edition (included in the PTC System Monitor), the following editions can be purchased from dynatrace: Test Center Edition dynatrace Test Center Edition integrates with major commercial and open source load testing solutions (such as LoadRunner, SilkPerformer and Visual Studio Team System) to eliminate manual problem reproduction and cut lost productivity time. With this edition, developers and test professionals can eliminate the multiple days it often takes to find, document, reproduce, diagnose and resolve performance issues. Using the PurePath transaction tracing technology, dynatrace provides in-depth code-level visibility into the performance of each individual transaction of all virtual users in large load tests of highly distributed applications. With dynatrace, developers and test professionals can now automate and accelerate the process of documenting, diagnosing, and resolving performance issues in Java/.NET applications, allowing more time to be spent on strategic development and test activities. Development Team Edition dynatrace Development Edition enables development teams to validate the dynamic behavior of software architectures, to proactively tune application performance, and to detect performance regression issues during continuous integration. This edition enables developers to identify and resolve issues before they reach test and production where the cost of resolving problems can be as much as 100x more expensive. The dynatrace PurePath transaction tracing and run-time modeling technology makes this possible with tracing transaction executions at code-level across distributed tiers and integrations with build systems such as Ant, Maven, NAnt, MSBuild. Its tight integration with leading IDEs further accelerates final problem resolution. For additional information about these editions, contact dynatrace directly. Introducing the PTC System Monitor 13

14 Working with PTC Technical Support PTC-Integrity Technical Support provides the first line of support for all issues related to the PTC System Monitor, which uses dynatrace Production Edition components. Contact PTC-Integrity Technical Support through the PTC website ( or by phone, , or fax if you encounter problems using this product or the product documentation. There is an understanding that the PTC System Monitor has a rich set of features and capabilities that allow you to tailor the out-of-the-box configuration in terms of Dashboards, Sensors, Business Transactions and instrumentation to better meet your individual needs. Therefore, PTC recommends that you contact PTC-Integrity Technical Support before customizing the PTC System Monitor due to the potential consequences that it may have on the overall performance of the instrumented Integrity system. In the circumstances where you experience issues with the PTC System Monitor or it is determined that there is an adverse impact on the Integrity application due to the current PTC System Monitor configuration, PTC-Integrity Technical Support reserves the right to request that you revert back to the base PTC System Monitor configuration as provided by PTC to isolate the root cause of the issue. Reverting back to the base PTC System Monitor configuration is accomplished by reinstalling the PTC FastPack that was used when you installed the PTC System Monitor. To save your current configuration before re-installing the PTC FastPack, you can rename the profile. Also back up any dashboard files. To understand a specific issue, PTC-Integrity Technical Support usually requires supporting data. Depending on the issue, you could be asked to provide one or more of the following: The export of an entire session of existing data This method collects all data for a given time frame. Depending on how long the time frame is, this export could become a very large data file. Usually, the time frame specified should be the four hours around the time of interest. For export details, see Exporting an Entire Session on page 15. The export of a specific PurePath When the issue has been linked to be a specific action, the exporting the related PurePath provides a small export file for analysis. A possible problem with this approach is that it does not provide data related to other transactions. For export details, see Exporting a Specific PurePath on page 17. The export of a session based on an incident This method collects a finite set of data around the time of the incident. However, the data may not show the root cause of the incident. For export details, see Exporting a Session Based on an Incident on page PTC System Monitor Installation and Usage Guide

15 The export of additional diagnostic information, such as CPU samples, memory dumps, or thread dumps You could be asked to start CPU sampling, create a memory snapshot, or create a thread dump. After you have completed the requested activity, you can then export the details. For details, see Creating and Exporting Runtime Diagnostic Information on page 19. Relevant Integrity system configuration information You can use the Integrity Support Package that is available from Administration Client Server Diagnostics Collect Support Package to collect and send Integrity files to PTC Technical Support. PTC System Monitor system information If there is a problem with one or more of the dynatrace components, you may be asked to provide the system information for the PTC System Monitor. For details on how to provide the information, see Saving PTC System Monitor Information on page 20. The following sections provide details on how to gather PTC System Monitor data that can then be sent to PTC-Integrity Technical Support. Exporting an Entire Session Right-click the profile in use and select Session Storage Export Session. For example, right-click your system profile and select Export Session as shown in the following: Introducing the PTC System Monitor 15

16 Export files use the.dts extension. In the Export Session window, include the path for a DTS file that will be created, the time frame to use for the export, and select PurePaths and time series to get both exact measures and averages of the maximum and minimum values: Click Export to create the export file. Note Do not check the Remove confidential strings from Session option, since this will remove all SQL. 16 PTC System Monitor Installation and Usage Guide

17 Exporting a Specific PurePath Navigate to the PurePath of interest. For example from the Cockpits tab, doubleclick PurePaths that is nested under the Diagnose Performance node in your system profile. Then locate the PurePath, right-click, and select Export: Export files use the.dts extension. In the Export Session window, include the path for a DTS file that will be created and select PurePaths to get exact measures: Click Export to create the export file. Exporting a Session Based on an Incident Navigate to the PurePath of interest. Then right-click the PurePath and select Export Incident Session: Introducing the PTC System Monitor 17

18 Export files use the.dts extension. In the Export Session window, the time frame to use for the export is selected. Include the path for a DTS file that will be created, and select PurePaths and time series to get both exact measures and averages of the maximum and minimum values. For example: Click Export to create the export file. 18 PTC System Monitor Installation and Usage Guide

19 Creating and Exporting Runtime Diagnostic Information Creating and exporting the requested information can be done from the Cockpits tab. Navigate to the Diagnose Runtime node under the system profile you are using and then expand the node. For example: The following activities could be requested: From the CPU Sampling node, you can create and export CPU samples that can help to find CPU hotspots. Caution Using CPU Sampling can result in a large CPU overhead on the Integrity Server. From the Threads node, you can create and export thread dumps that can help to diagnose performance bottlenecks. From the Total Memory node, you can create and export memory snapshots that can help in identifying leaks or trends. Caution Using Total Memory may cause the Integrity Server to pause for a couple of minutes before continuing. Note The Selective Memory activity is not applicable and should not be requested. To create an export of any runtime diagnostic results snapshot, right-click the row containing the snapshot and select Export Sample or Export Dump. Introducing the PTC System Monitor 19

20 Saving PTC System Monitor Information The information about your PTC System Monitor is stored on the dynatrace Server. To create a ZIP file containing configuration, dashboard, license, profile, and session files: 1. Under Cockpits, double-click Status Overview System Information. 2. Expand the server node to see Support Information in the right panel: 3. To save a support archive ZIP file, right-click Support Information and select Package Files. 4. Navigate to a local directory where you want to save the file, enter a file name, and click Save. License Information The license to use the PTC System Monitor is a dynatrace group license that is assigned to PTC; it is not a specific license assigned to your company. The PTC System Monitor license is included in the PTC FastPack that you install into the installed client. You do not import a specific license from the Configure License panel. Instructions on installing PTC FastPacks are included in the installation and configuration chapter, later in this guide. 20 PTC System Monitor Installation and Usage Guide

21 Accessing Online Documentation Online help is available from the Webstart Client. This help consists of dynatrace documentation that is posted on the dynatrace web site, which requires Internet access. In a future release of the PTC System Monitor, the documentation will not require Internet access. You can access the dynatrace documentation from the client by pressing F1 or clicking any help icon. Additionally, you can access the online dynatrace documentation directly from the dynatrace web site. Be aware that this is general purpose documentation provided by dynatrace. Information about the PTC implementation of dynatrace, the PTC System Monitor, is contained in this guide. Introducing the PTC System Monitor 21

22

23 2 Planning a PTC System Monitor Deployment Single Host Configuration...24 Desktop Virtualized Installation...25 Production and Test Configurations...26 dynatrace Server and Collector Installation Guidelines...26 Verifying a Deployment...28 Backup and Recovery Strategies...29 The PTC System Monitor can be installed and configured to meet a site's needs. In production and test environments, PTC strongly recommends using a standalone system monitoring configuration. A standalone configuration is strongly recommended because using a standalone configuration decouples the monitoring infrastructure from the server being monitored. If the server being monitored goes down, monitoring and all the benefits of monitoring (such as incident notification) will still be available and of use. In some cases where the reporting is not deemed a critical feature, installing the PTC System Monitor on the same system as the Integrity software is appropriate provided that enough CPU, memory and disk space is available to operate the PTC System Monitor. The following sections show examples of recommended configurations that can be considered and installation guidelines for the dynatrace Server and Collector. 23

24 Single Host Configuration A single host configuration is appropriate if you are interested in monitoring a single server installation or if you are a first time user of the PTC System Monitoring software who wants to investigate its usage with the least amount of configuration required. The following diagram shows the monitoring and Integrity software on a single host: In this configuration, the system monitoring software is installed on the same host as an Integrity installation. At a minimum, the dynatrace Server and Agent installations are required. For non-production systems, you can use the embedded collector in the system monitoring server and use the embedded data repository. Note For a production system, you must install and configure a standalone collector and the server must store its repository data in an Oracle or Microsoft SQL Server database. 24 PTC System Monitor Installation and Usage Guide

25 Desktop Virtualized Installation In cases where the system monitoring solution is being installed in a desktop virtual configuration (primary usage would be with VMware Workstation only, not with the enterprise level VMware ESX or Microsoft Hyper-V configurations), consider installing the PTC System Monitor on the host machine and install the agents into the virtual machine. The following diagram shows the monitoring software accessing agents on one virtual machine: This configuration is particularly advantageous if you have a limited amount of memory in virtual machines but can accommodate the use of the PTC System Monitor on the host machine. It also allows you to install one PTC System Monitor and then configure it to monitor numerous different virtual machine configurations (a unique system profile for each virtual machine is strongly recommended). Planning a PTC System Monitor Deployment 25

26 Production and Test Configurations For production and test environments, PTC recommends that you install the dynatrace Server and Collector on a separate machine. The following diagram shows a typical Integrity and dynatrace deployment where there is one dynatrace Server and one dynatrace Collector on a separate system: Use of a separate system provides the ability to monitor, measure, and alert administrators of both application and infrastructure related issues. This type of configuration is required in cases where you are using Integrity clustered application servers. This environment treats the system monitor as a neutral party. For a production or processing-intensive environment, you must use a standalone collector configuration and use an Oracle or SQL Server repository to store the collected data. dynatrace Server and Collector Installation Guidelines To plan your dynatrace component installation, you must be aware of the memory, disk space, and other requirements for the components. 26 PTC System Monitor Installation and Usage Guide

27 General installation guidelines for the dynatrace Server are: 64-bit system (requirement). Total memory recommended: 4 to 6 GB (as set in the dynatrace client; see Setting Server Memory Settings on page 61). Disk space The server stores data in two locations: Stored sessions, which are usually stored on the dynatrace Server. Consider allocating at least 40 GB for session storage. Repository (relational database), which can optionally be installed on a host that is different from the host where the dynatrace Server is installed. Typically, allow 20 GB of disk space for the data files and transaction logs generated yearly from a medium-sized Integrity environment. General installation guidelines for the dynatrace Collector are: 64-bit system (requirement). Install each collector within the same local area network (LAN) as its agents and with no firewall between each collector and its agents. Agent load can be balanced by using multiple collectors if network or host resources require. In production and test environments, use a dedicated collector that you install separately instead of using the collector embedded in the dynatrace Server. For the required setting change, see Disabling the Embedded Collector on page 63. Planning a PTC System Monitor Deployment 27

28 Verifying a Deployment There are several system performance metrics that should be used to verify a deployment. The measures explained here are put together in specialized dynatrace self-monitoring dashboards that you should use to verify your deployment. To access the dashboards: 1. Open the Start Center. To open the Start Center, click the Open Start Center icon located above Cockpits near the top of the dynatrace Client window. 2. From the large tabs shown on the left side of the Start Center window, click Monitoring. Links to the health dashboards are displayed in the right panel under Deployment Health. 3. Click the dynatrace Server Health link to display the dynatrace selfmonitoring data for the dynatrace Server. 4. Click the dynatrace Collector Health link to display the dynatrace Collector sizing health. From these dashboards, you can verify that your dynatrace components are installed and functioning correctly. Specifically, check the following metrics: Skipped Events (per Interval) This field should be 0, otherwise you will receive incomplete PurePaths. If this happens, check the MPS metric, the send queue buffer size of your collectors, and the Bytes Received per Interval metric. MPS (Measures per Second) 28 PTC System Monitor Installation and Usage Guide

29 You can compare the values on agent/collector and server level with an estimate that can be calculated using the DeploymentGuide.xlsx spreadsheet that is available from the Deployment Guide topic in the local server documentation. You can access this topic from the Start Center. Click the Deployment Guide link: If the values are much higher than expected, either the instrumentation rules should be justified or the transaction load was underestimated. You can use the Completed PurePaths per Interval or the PurePath Length measures to investigate this further. Bytes Received per Interval Compare these values on the collector level with the physical bandwidth available to ensure that there will not be a bottleneck. Send Buffer Queue Used/Committed Size Check if the used size is consistently smaller than the committed size. Skipped events occur when the used buffer reaches the committed size. Sometimes the solution is as simple as increasing the Send Queue Buffer Size. PurePath Buffer Duration Check this value to see how far back you can retroactively analyze PurePaths. This value reflects the difference between the start time of the oldest PurePath and the end time of the latest PurePath in memory. Therefore it increases after the server starts and stabilizes after the server's buffers are filled. Backup and Recovery Strategies Develop backup and recovery strategies for the two major data containers. Planning a PTC System Monitor Deployment 29

30 dynatrace Server You should backup the following directories and files, where <dynatrace_home> is the installation directory for the PTC System Monitor: <dynatrace_home>/server/conf/dashboards <dynatrace_home>/server/conf/dtlicense.key <dynatrace_home>/server/conf/dtstorage.dat <dynatrace_home>/server/conf/plugins <dynatrace_home>/server/conf/profiles <dynatrace_home>/server/conf/sensors <dynatrace_home>/server/conf/server.config.xml <dynatrace_home>/server/conf/user.permissions.xml <dynatrace_home>/server/sessions <dynatrace_home>/*.ini Performance Warehouse Your database administrator should develop a backup strategy for your Performance Warehouse that fits your needs. 30 PTC System Monitor Installation and Usage Guide

31 3 Installing and Configuring the PTC System Monitor PTC System Monitor Installation and Initial Configuration Overview...32 Downloading the Media Content for PTC System Monitor...36 Installing Using the GUI...37 Installing Using the Command Line...45 Starting and Stopping dynatrace Components...50 Installing PTC FastPacks...53 Setting up Monitoring for Multiple Integrity Applications...56 Setting Initial Configuration Options...57 Uninstalling the PTC System Monitor...65 This chapter contains details about installing and completing the initial configuration required to use the PTC System Monitor. 31

32 PTC System Monitor Installation and Initial Configuration Overview As part of the planning process, you have decided where to install the PTC System Monitor components. If you have not completed the planning process, see Planning a PTC System Monitor Deployment on page 23. Use the installation sections in this chapter to complete the installation. Then continue with the required configuration steps described in the configuration sections in this chapter. PTC System Monitor Requirements Your system must meet the following requirements for installing and using PTC System Monitor components: Installing the dynatrace Server and Collector components requires administrator privileges on the system. On Windows, you must run the installation command using Run as administrator command prompt option regardless of what the installer user permissions are. When installing dynatrace Agents on UNIX and Linux platforms, the user performing the installation must have write permission to the Integrity directory where PTC System Monitor artifacts are stored. The directory file path is <install_dir>/opt/psm, where <install_dir> is the directory where Integrity is installed. The systems where the dynatrace Server and Collector components are installed must be 64-bit systems. dynatrace Agents can be installed on either 32-bit or 64-bit systems. 32 PTC System Monitor Installation and Usage Guide

33 Java Requirements To run the installer for the PTC System Monitor, you must have Java 5 or Java 6 in your path. Additionally, your system must meet the following Java requirement to run PTC System Monitor components: PTC System Monitor requires that Java 6 or higher is installed and that JAVA_HOME is correctly set. There is an issue with Java 6 update 26 on Windows. The native file selector dialog fails. This affects using Webstart Clients. PTC recommends that you use Java 6 with update 27 or later. Installing and Configuring the PTC System Monitor 33

34 Installation Terminology Understanding the following terms is helpful when completing the installation and viewing log entries: Bind Address A bind address that is specified in the context of a listening server process identifies an address on a host computer where the installation is taking place. This address is used by the component being installed when listening for incoming communication from another component. A bind address normally consists of an IP address and a port. The IP address and port are specified separately when installing from a windows interface and together when installing from the command line. The IP address portion of the bind address can be specified as: Bind Address Value Description Indicates that all IP addresses on all network interfaces available on the host computer will be used for the required communication. valid IP address Indicates that communication only occurs on the specified IP address. specific host name Indicates that communication only occurs on the IP address to which the specified host name resolves. When using the command line installer, the <inet4_address> value specified for the bind_address argument and similar arguments used to specify listener information must include both address and port. The format for these argument values is: <address>:<port_number> Home Home is used in conjunction with the dynatrace Server, dynatrace Collector, and Integrity components. In each case, home refers to the full directory path where the component will be installed or is installed. PSM PSM stands for PTC System Monitor. You may see this term used in arguments or log messages. 34 PTC System Monitor Installation and Usage Guide

35 Installation and Configuration Steps Complete the following general steps to install and configure the PTC System Monitor: 1. Download the media content. See Downloading the Media Content for PTC System Monitor on page Install the dynatrace Server and a standalone dynatrace Collector. Although the dynatrace Server has an embedded collector, PTC recommends that you disable the embedded collector and install at least one standalone collector when monitoring Integrity production or test systems. 3. Optionally install additional standalone dynatrace Collectors. You can install multiple collectors to set up load balancing when you expect a lot of traffic between agents and collectors. A collector installation is validated using a connection to the running server. Therefore, ensure that you dynatrace server is running when you install a collector. 4. Use the PTC System Monitor installer to install the dynatrace agents on Integrity. Note Ensure that the dynatrace Collector that agents will communicate with is started before installing the agents. Ensure that a plugin directory containing IntegrityAgent.jar exists in the same directory as the core installer (PSMInstaller.jar). See Specifying Arguments for Installing dynatrace Agents on page 49. After the agent installation steps have been completed successfully, restart the Integrity server. 5. Ensure that all components are started and can communicate. See Starting and Stopping dynatrace Components on page Use the dynatrace Client to install PTC FastPacks. See Installing PTC FastPacks on page 53. If you are going to monitor multiple Integrity applications, see Setting up Monitoring for Multiple Integrity Applications on page Complete initial configuration steps as defined in Setting Initial Configuration Options on page 57. After the initial PTC System Monitor installation and setup, there may be updates to PTC FastPacks, the PTC license, and dynatrace components that are available and ready to install. For FastPack and license installation details, see Installing PTC FastPacks on page 53. Installing and Configuring the PTC System Monitor 35

36 Downloading the Media Content for PTC System Monitor You can download the file containing the media content from the Integrity Customer Community, accessible through the PTC website ( community). Extract the content of the ZIP file to a local drive. The download file contains the installer, the Integrity Agent plugin, and the client installers. Note A FastPack is required to configure dynatrace to monitor Integrity. This FastPack also includes the license required to use dynatrace. Please contact Integrity Customer Support to acquire the FastPack. 36 PTC System Monitor Installation and Usage Guide

37 Installing Using the GUI The PTC System Monitor installer can be run in GUI mode by either doubleclicking on PSMInstaller.jar in Windows or by running java -jar PSMInstaller.jar without any arguments from a command line. 1. Once the GUI is launched, you must accept the Customer Agreement and click Next to continue. 2. Select Install PTC System Monitor 2.0 and click Next. Installing and Configuring the PTC System Monitor 37

38 3. Select the components that you wish to install from the displayed list and click Next. 38 PTC System Monitor Installation and Usage Guide

39 4. If you are installing the dynatrace Server, you will be presented with the following screen where you can specify the arguments for its installation: The default IP addresses are set to for the bind arguments. This value indicates that the can use any IP address defined for the host when listening for incoming data. Collector Listener Bind Address: This is where the dynatrace Server listens for agents. HTTP Bind Addresses: This is where dynatrace listens for web service connections and is where the dynatrace Server s home page is housed (default: 8020-http and 8021-https). PTC System Monitor Administrative Credentials: The administrator s user name cannot be changed. Enter the password you want associated with the administrator s user name. When starting the dynatrace client during the configuration steps described later in this chapter, use the user name and password defined here. Fill in the appropriate values and click Next. 5. If you are installing the dynatrace collector, you will be presented with the following screen where you can specify the arguments for its installation: Installing and Configuring the PTC System Monitor 39

40 The default IP addresses are set to for the bind arguments. This value indicates that the can use any IP address defined for the host when listening for incoming data. Bind Address/Port: This is where the dynatrace collector listens for agents. Server Information: This is the dynatrace Server host and port. Fill in the appropriate values and click Next. 6. If you are installing the dynatrace Agent, you will be presented with the following screen: 40 PTC System Monitor Installation and Usage Guide

41 When installing dynatrace Agents on an Integrity server, select Integrity Server from the list of products. Note Depending on the agent plugins that you have in place, this list may have more than one type of application server listed. If no products are listed, please double check that you have a plugin directory in the same location as PSMInstaller.jar, and that the directory contains at least one plugin (for example, IntegrityAgent.jar). Select an application server and click Next. 7. The following screen appears where you can specify which collector the agent connects to: Installing and Configuring the PTC System Monitor 41

42 Collector Setting: The host and port of an existing collector to which this agent will connect. Fill in the appropriate values and click Next. 8. Finally, provide the path to the Integrity Server where you want to install the agent: 42 PTC System Monitor Installation and Usage Guide

43 Click Next. 9. After specifying all of the arguments for the components that you are installing, you will be presented with a summary screen. Installing and Configuring the PTC System Monitor 43

44 Click Install to install with these settings. Installation Results When the installation completes, you are presented with the results. If there are errors, you can view the details in the installation logs which are written to you temporary directory. For example, on Windows, your temporary directory would be: <User_Profile>\AppData\Local\Temp. Note The Integrity server must be restarted to instrument a newly installed agent. 44 PTC System Monitor Installation and Usage Guide

45 Installing Using the Command Line As part of the PTC System Monitor installation process, you will install dynatrace Agents into your Integrity codebase. Therefore, be sure to back up your Integrity environment before installing the PTC System Monitor. To run the PTC System Monitor installer using the command line: 1. Open a command prompt window on the system where you want to install the dynatrace components. On a Windows platform, you must run the installer as the Administrator. Tip For example on Windows 7, right-click the Command Prompt option and select Run as administrator: 2. Navigate to the directory containing the PSMInstaller.jar file. Note If you are installing the Integrity Agent, this directory must also include a plugin directory which contains the Integrity Agent plugin ( IntegrityAgent.jar). 3. Enter the java jar PSMInstaller.jar command with all arguments necessary to install the dynatrace components. Entering the following command displays the syntax for all arguments: java -jar PSMInstaller.jar --help The top-level arguments are described in the following table: Argument Description --version Returns the version of the installer. --help Displays the syntax for all arguments. --install server Installs the dynatrace Server. --install collector Installs a standalone dynatrace Collector. --install agent Installs dynatrace Agents. The following sections provide details about the arguments associated with installing each component. Installing and Configuring the PTC System Monitor 45

46 Specifying Components to Install When planning your implementation of the PTC System Monitor, you determined where the components need to be installed. Run the PTC System Monitor installer on each system, specifying only those component arguments for the components that you want installed on that system. The arguments that identify the components start with --install. To monitor production and test Integrity systems, PTC recommends installing the dynatrace Server and standalone dynatrace Collectors on systems that are separate from your Integrity system. In this scenario, you would need to run the installer at least two times: once to install the dynatrace Server and dynatrace Collector on a separate system, and once to install the dynatrace Agents on the Integrity system. If your Integrity environment includes remote files servers, you normally would install a dynatrace Collector on a system that is on the same LAN as each remote file server and install dynatrace Agents on each remote file server. Installing all dynatrace components on a Integrity system is a quick installation for previewing the PTC system Monitor functionality. PTC does not recommend this configuration for monitoring a production or test Integrity environment. For more information about where components need to be installed, see Planning a PTC System Monitor Deployment on page PTC System Monitor Installation and Usage Guide

47 Specifying Arguments for Installing the dynatrace Server The following arguments can be specified when installing the dynatrace Server: --install server installation_dir=<dt_home> bind_address=<inet4_address> disable_http disable_https https_bind_address=<inet4_address> http_bind_address=<inet4_address> admin_password=<password> The default IP addresses are set to for these arguments. This value indicates that the server can use any IP address defined for the host when listening for incoming data. <inet4_address> values include the IP address and the port number, separated by a colon (:). For additional information about bind addresses, see PTC System Monitor Installation and Initial Configuration Overview on page 32. By default, the HTTP Server and HTTPS Server are enabled. To disable the HTTP Server, include the disable_http argument; to disable the HTTPS Server, include the disable_https argument. The admin user name cannot be changed. Enter the password you want associated with the admin user name using the admin_password=<password> argument. When starting the dynatrace client during the configuration steps described later in this chapter, use the user name and password defined here. Installing and Configuring the PTC System Monitor 47

48 Specifying Arguments for Installing a dynatrace Collector The following arguments can be specified when installing a standalone dynatrace Collector: --install collector installation_dir=<dt_home> bind_address=<inet4_address> psm_server=<inet4_address> If you choose to install both the dynatrace Server and dynatrace Collector on the same Windows system, they must be installed in the same directory. In this case, the installation_dir argument for the collector is ignored. The default IP address used by the collector to listen for agent data is set to This value indicates that the collector can use any IP address defined for the host when listening for incoming data. <inet4_address> values include the IP address and the port number, separated by a colon (:). For additional information about bind addresses, see PTC System Monitor Installation and Initial Configuration Overview on page 32. When you install the dynatrace Collector at the same time as the dynatrace Server, the server information that is required by the collector does not need to be specified in the psm_server argument. If you are installing a standalone collector, you must enter the server IP address and port that were entered in the server installation bind_address argument in the psm_server argument. 48 PTC System Monitor Installation and Usage Guide

49 Specifying Arguments for Installing dynatrace Agents The following arguments can be specified when installing dynatrace Agents: --install agent component=windchill installation_dir=<wt_home> component=tomcat installation_dir=<tomcat_home> component=windchillds installation_dir=<wt_home> component=integrity installation_dir=<integrity_home> psm_collector=<psm_collector> When installing dynatrace Agents on an Integrity server, specify the component=integrity argument. For the psm_collector argument, include the hostname or IP address of the collector and the port number that you want the agents using to communicate with collector. The format of this value is <address>:<port_number>. The dynatrace Agent installation includes both 32-bit and 64-bit libraries. The library used is determined by your Integrity settings. Installation Results When the installation completes, the window updates to display the results of the installation. For example: PSM is successfully installed at: D:\PTCSystemMonitor If there are errors, you can view the details from your temporary directory. For example, on Windows the log file is stored in your Temp directory: <User_Profile>\AppData\Local\Temp. The Integrity server must be restarted for the agent to start working. Installing and Configuring the PTC System Monitor 49

50 Starting and Stopping dynatrace Components The following sections describe how to start and stop a dynatrace Server and its associated dynatrace Collectors, and how to start the Webstart Client. dynatrace components communicate over a set of ports that are established during the installation of the components. The port numbers are configurable. Firewalls on either the collector host or server host must allow connections through the established ports. The following table lists the default ports that are used for the communication: Host Communication Default Port Collector Listens for agents Server Listens for browser connections to web 8020 services page. Server Listens for browser connections to web 8021 services page (SSL). Server Listens for collectors Server Listens for collectors (SSL) Server Listens for Java client connections Server Listens for Java client connections (SSL) Server and Collector Startup After the installation, the components are in the following states based on platform: Windows Two services are created and available to manage in the Windows Services Management Console. The dynatrace Server service is started automatically. The dynatrace Collector must be started prior to any successful agent connections. Additionally, set the collector to start automatically. UNIX and Linux Both the dynatrace Server and the dynatrace Collector are started and are ready for successful agent connections. Ensure that the dynatrace Collector that agents will communicate with is started before installing the agents. 50 PTC System Monitor Installation and Usage Guide

51 Note PTC recommends that you configure the host operating system to automatically start the dynatrace Server and all dynatrace Collectors when the machine is restarted. If the port used by the collector when listening for data is 9998, then the collector must start before the sever. By default, port 9999 is used; using port 9999 means that the startup order is not important. The following list provides information about managing dynatrace components based on platform: Windows Use Windows Services to start, stop, and configure for automatic startup. Startup links for the processes can also be found in the Start menu under dynatrace. UNIX and Linux The dtcmd command line utility is automatically included when you install the dynatrace components on UNIX and Linux platforms and can be used to restart the components: To start the server, enter the following dtcmd command from a command prompt: dtcmd -startup -spawn To start collectors, first enter following command to get the names of collectors: dtcmd -listcollectors Then enter the following command to start a specific collector, where <name> is one of the names returned from the previous command: dtcmd -startup -spawn -collector <name> On Linux, you can avoid using a terminal window by running the processes in the background. Use the following to spawn background processes: dynatrace Server:./dtserver -bg dynatrace Collector:./dtcollector -bg Installing and Configuring the PTC System Monitor 51

52 Webstart Client Startup Open the dynatrace Home page to start the PTC System Monitor Webstart Client by entering the server name and the client port in a browser using either HTTP or HTTPS. For example: Use the server name for <host> and the port number specified for the HTTP or HTTPS server during the installation. When the default port numbers were used during installation, either of the following can be entered: For additional details on starting and using the PTC System Monitor Webstart Client, see Using PTC System Monitor Client on page 73. Server and Collector Shutdown The following list provides information about shutting down dynatrace components based on platform: Windows Use Windows Services to stop dynatrace components. Stop links for the services can also be found in the Start menu under dynatrace. UNIX and Linux The dtcmd command line utility is automatically included when you install the dynatrace components on UNIX and Linux platforms and can be used to shut down the components: To shut down the server, enter the following dtcmd command from a command prompt: dtcmd -shutdown To shut down collectors, first enter following command to get the names of collectors: dtcmd -listcollectors Then enter the following command to shut down a specific collector, where <name> is one of the names returned from the previous command: dtcmd -shutdown -collector <name> 52 PTC System Monitor Installation and Usage Guide

53 Installing PTC FastPacks To facilitate updates to the PTC System Monitor, PTC provides PTC FastPacks. In most cases, the content is generated as a dynatrace Plugin file with the.dtp file extension. Files with this extension can be installed into the PTC System Monitor using the dynatrace Webstart Client. The following sections provide information on what is in each artifact and details on installing DTP files. FastPack Content FastPacks are a container for the entire Integrity implementation for dynatrace. When you first download the PTC System Monitor software, you will get PTC Integrity FastPack.dtp, which contains: dynatrace license IntegritySystem Profile business transactions measures/thresholds incidents sensors tasks/monitors Multiple dynatrace dashboards for Integrity Plugins Each PTC FastPack includes the PTC license for the PTC System Monitor; the PTC System Monitor uses the license from the last PTC FastPack that has been installed. Preserving Existing System Profiles, Dashboards, and Plugins Installing a FastPack overwrites existing system profiles, dashboards, and plugins that have the same names as those being installed. If you are installing updated PTC FastPacks and want to keep a copy of your existing system profiles and dashboards available, you can rename the profiles and dashboards before installing the updated FastPacks. For example, you can rename any dashboard by opening the dashboard, clicking F2, and typing a new name and description. Installing and Configuring the PTC System Monitor 53

54 Additionally before installing an updated FastPack, back up existing profile files, dashboard files, plugin files that have names beginning with com.ptc, and any custom plugin files you may have created that are on your dynatrace Server. These files are located in directories nested under the dynatrace Server installation directory <dynatrace_home>: <dynatrace_home>/server/conf/profiles <dynatrace_home>/server/conf/dashboards <dynatrace_home>/server/conf/plugins 54 PTC System Monitor Installation and Usage Guide

55 Installing Plugin Steps Install a DTP file by starting the dynatrace Webstart Client (if it is not already started) and navigating to: Settings dynatrace Server Plugins On the Plugins panel, click Install Plugin and navigate to the DTP file that you want to install. Then click Open. Note If you are using Java 6 update 26, there is a bug that produces an error when installing a plugin from a Webstart client. The work around is to use Java update 27 or later. You are prompted to confirm that you want to install the selected file. Click Ok to continue. Note If you are installing a file containing a license, it may take a short time for the license to be read. License information is available from the Settings dynatrace Server License window. If the license was not read, you can restart the dynatrace Server to ensure that the license is read. As a result of a FastPack installation, the Integrity system profile is available from the dynatrace client Cockpits navigator. If it is disabled, enable it. For example, System Profiles right-click PTC Integrity Server <default> and select Enable under System Profiles System Profile. All dashboard and profile names must be unique. You can install multiple FastPacks to have multiple profiles available in the same client. However, if you install a FastPack that has a profile with the same profile name as an existing profile, the existing profile is overwritten. The same is true for dashboards; installing a FastPack that has a dashboard with the same dashboard name as an existing dashboard overwrites the existing dashboard. Upgrading PTC FastPacks If you wish to keep your existing data, but upgrade to the new profile, you have two options: 1. Manually apply the list of changes in the new profile to your existing profile. Read the list of changes in the readme for the FastPack and manually apply them to your existing profile. 2. Upgrade to the new profile and manually apply any customizations again to the new profile. Installing and Configuring the PTC System Monitor 55

56 Disconnect from the performance warehouse and continuous session recording. Rename your existing profile to *_OLD and install the new one from the FastPack. Rename the new profile to the original profile name (if applicable). Setting up Monitoring for Multiple Integrity Applications To use the PTC System Monitor to monitor multiple Integrity applications that have the same release version, you must modify the agent names that are initially set in the agent mapping rules to make them unique in the monitoring tool and applications. By default all servers are mapped to the Production agent mapping under the default PTC Integrity Server system profile. If you would like to map a server to another agent group, we recommend copying the existing agent group so the sensor configurations remain. Then adjust the mappings. By default all agents that have Integrity_ prefix in their name are mapped to the Production group. You can establish a different prefix for mapping to the new agent group or you can hard code each server mapping. If you require the ability to define different thresholds per server you must copy the PTC Integrity Server system profile and map the new agent to that profile. You cannot define different incident thresholds at the agent group level. Note The advantages of keeping a single profile are: Less overhead when upgrading. Dashboards do not need to be copied/edited (they are tied to the profile). Use the following steps to install profiles and then update agent names in the installed system profiles: 1. If not already installed, install the FastPack containing the system profile you want to use as the starting point for monitoring multiple Integrity applications. For installation instructions, see the FastPack installation section in Installing and Configuring the PTC System Monitor on page Edit the system profile by double-clicking the profile name from Cockpits. 56 PTC System Monitor Installation and Usage Guide

57 3. Display the agent names that are used in agent mapping by expanding each agent group and selecting Agent Mapping Agent Mapping. For example: 4. Change the prefix used for each agent in the group. The following screen shot shows the default Integrity prefix: 5. To save changes, click Ok. 6. After you have updated all agent names in each agent group, rename the system profile to uniquely identify it. For example, include the host name in the profile name. 7. Repeat steps 1 through 6 to create a unique system profile for each additional Integrity application you want to monitor. For changes to take effect, restart Integrity if it was already running. Setting Initial Configuration Options Before you can use the PTC System Monitor, you must set a few configuration options using the PTC System Monitor Webstart Client. For information on starting the Webstart Client, see Client Startup on page 76. Setting Up a Data Repository You must set up a production database as the repository to use with the dynatrace Server to monitor production or test data. In dynatrace documentation, the repository is also known as the Performance Warehouse. You can set a repository using either SQL Server or Oracle. Installing and Configuring the PTC System Monitor 57

58 Setting Up an SQL Server Repository To set up an SQL Server repository: 1. Create the user in SQL Server Management Studio. To create the user in SQL Server Management Studio, right-click Logins and select New Login. 2. Create the database in SQL Server Management Studio. To create the database in SQL Server Management Studio, right-click Databases and select New Database. Set Owner to the user created previously. 3. From Settings dynatrace Server Performance Warehouse, add the connection information to the dynatrace Server on the Connection Details tab. Click Connect to automatically create the required tables and indexes: Clicking Connect connects to the default instance. UTF16 is only needed if an extended character set is needed for the names of measures. Setting Up an Oracle Repository To set up an Oracle repository: 1. Create the user using Oracle Enterprise Manager as follows. The database tables can be in the same instance as Integrity or a separate database. 58 PTC System Monitor Installation and Usage Guide

59 Select Server/Users and create a user similar to the Integrity database user: 2. From Settings dynatrace Server Performance Warehouse, add the connection information to the dynatrace Server on the Connection Details tab. Click Connect to automatically create the required tables and indexes: Clicking Connect connects to the default instance. UTF16 is only needed if an extended character set is needed for the names of measures. Installing and Configuring the PTC System Monitor 59

60 Configuring the Performance Warehouse The size estimate for your Performance Warehouse is dependent on how many measures you capture and how high the resolution is for stored data. To keep the Performance Warehouse size in reasonable boundaries, dynatrace uses an automated data aging algorithm that aggregates measures in 3 steps from a very high live resolution of 10 seconds down to 1 minute, 1 hour, and 1 day stored in the Performance Warehouse. Note PurePath data is not stored in the Performance Warehouse. To view server settings for the Performance Warehouse, click Settings dynatrace Server. From the Manage dynatrace Servers window, click Performance Warehouse. From the tabs on the dynatrace Performance Warehouse table, you can view and change warehouse details, associated system profiles, and storage settings. The following table shows the recommended settings for the durations of this resolutions and the disk space necessary to store 1000 measures: Resolution Interval Duration Used Space in Million Rows Disk Size Estimation high 1 minute 2 weeks ~ 20 million rows ~ 2 GB mid 1 hour 2 months 1.4 million rows ~ 0.5 GB measures million rows percentiles low 1 day 1 year 0.37 million rows million rows percentiles ~ 0.2 GB If you stick to the recommended durations for the three resolutions, you can roughly calculate using the total space of 2 GB needed per 1000 measures. Talk to your database administrator about the growth rate of these tables to figure out the actual disk space needed. To estimate the number of measures to store in the Performance Warehouse, consider the following major contributors: Component Number of Typical Subscribed Measures Measures Agent 200 JVM Metrics, PurePath Metrics Self- Monitoring 1000 Performance Counters, PMI Values,... For a deployment with 20 Agents, the measure calculation is: *200 = 5000 measures 60 PTC System Monitor Installation and Usage Guide

61 Tip The best way to obtain the number of measures is to do a test run with your system profile and use the DeploymentGuide.xlsx spreadsheet that is available from the Deployment Guide topic in the local server documentation. You can access this topic from the Webstart Client. Select Help Online Help and then click the Deployment Guide link. Instead of estimating, using the spreadsheet will give you the real number. Setting Server Memory Settings PTC recommends that you access Settings dynatrace Server Settings to configure the following: On the Server Settings tab, set Total Memory under Server Memory Settings for the dynatrace Server by adjusting the slide bar. PTC recommends using a minimum of 4096 MB (4 GB) and adjusting that number upward based on the type of environment: Small production 4 GB Medium production 6 to 8 GB Large production 12 to 16 GB Also, ensure that the Enable Self-Monitoring checkbox on Server Settings is selected to monitor the dynatrace Collectors and Server. Installing and Configuring the PTC System Monitor 61

62 The following shows the slide bar set at 4160: 62 PTC System Monitor Installation and Usage Guide

63 Disabling the Embedded Collector To disable the embedded collector in the server, PTC recommends that you access Settings dynatrace Server Services to configure the following: From the General tab, deselect the Agent Service checkbox to allow the standalone collector to operate: If you cannot make changes on this tab, you may see the following at the bottom of the panel: If you see this message, you must import a PTC FastPack with a valid license. For import instructions, see the FastPack installation section in Installing and Configuring the PTC System Monitor on page 31. Reviewing Server Storage Settings PTC recommends that you access Settings dynatrace Server Storage to review and modify the storage settings for the dynatrace Server. Out of the box: 10 GB is allocated for storing sessions in the Storage Quota field. Once the allocated storage capacity has been used, the dynatrace Server deletes the oldest unlocked session to free up space. If all sessions are locked and disk space cannot be freed, session recording stops. From Storage Settings, you can view how much disk space is currently used and change the quota value. PTC recommends initially setting this value to 40 GB or more to ensure that your recent sessions are always available. As you use the PC System Monitor, you can periodically check to see how much disk space is being used and adjust the value as needed. The stored sessions directory named is nested under the dynatrace Server installation directory. Installing and Configuring the PTC System Monitor 63

64 Verify that the disk space available in the listed directory is larger than the value of the Storage Quota or change the directory to one that does have enough storage capacity. The server has continuous transaction storage disabled. Enabling this option transparently persists data from the live session to disk. As a result, PurePaths are accessible for a longer time period and are not lost after a server restart. PTC recommends that you select the Enable continuous transaction storage checkbox to enable this option. Setting Mail Server Settings PTC recommends that you access Settings dynatrace Server Services to configure the following: Select the tab to configure SMTP server and enter administrator alerts address. Managing User Access to dynatrace Client For the initial access to the dynatrace Client, use the admin credentials set during installation. To manage user access to the dynatrace Client, PTC recommends: Enabling other users to access the dynatrace Client and keeping the admin user credentials secure. Creating a policy to change user passwords on a regular basis. The initial password for the admin user is set during the PTC System Monitor dynatrace Server installation. Enabling Others to Access the dynatrace Client To enable others to use the dynatrace Client, access Settings dynatrace Server Users. From the Users panel, you can configure any users or groups for access using the Accounts, Groups, and Roles tabs. If you choose to use LDAP to control access to the dynatrace Client, you can set up the required configuration through the LDAP tab on the Users panel. For help in configuring the client to use LDAP, see the help that is available from the Users panel. Note Although you can use the LDAP service used with Integrity, PTC recommends that you limit access by establishing a separate Base DN for dynatrace users instead of using the established Integrity users Base DN. When you configure the client to use LDAP, you must manage users through the LDAP software. 64 PTC System Monitor Installation and Usage Guide

65 Changing User Passwords There are two ways to change passwords: You can change passwords for the users set up through the Settings dynatrace Server Users Accounts tab by editing the user's row in the table displayed in the tab. You can change your password as follows: 1. Locate the server link at the bottom of the window, identified by the icon. 2. Right-click the link and select Change Password: 3. Enter the old password once and the new password twice. When passwords have been entered correctly, the Ok button activates allowing you to click Ok to complete the password change. When other users are logged in using their credentials, they can also change their passwords by right-clicking the server link in the same manner described in these steps. Uninstalling the PTC System Monitor This chapter contains details about uninstalling the components that PTC provides that make up the PTC System Monitor: dynatrace Server dynatrace Collectors dynatrace Agents Installing and Configuring the PTC System Monitor 65

66 Before installing a new version of the PTC System Monitor, you must uninstall the current version. Note Before uninstalling, stop the dynatrace Server and all dynatrace Collectors. Then uninstall dynatrace Agents first. After the agents have been uninstalled, uninstall the dynatrace Server and all dynatrace Collectors. Additionally, if you have downloaded a Webstart Client, you can remove the client. Uninstalling dynatrace Agents Using the GUI The PTC System Monitor installer can be run in GUI mode by either doubleclicking on PSMInstaller.jar in Windows or by running java -jar PSMInstaller.jar without any arguments from the command line. 1. Once the GUI is launched, you must accept the Customer Agreement and click Next to continue. 2. Select Uninstall PTC System Monitor and click Next. 66 PTC System Monitor Installation and Usage Guide

67 3. You will be presented with the following screen: Installing and Configuring the PTC System Monitor 67

68 When uninstalling dynatrace Agents from an Integrity server, select Integrity Server from the list of products. Note Depending on the agent plugins that you have in place, this list may have more than one type of application server listed. If no products are listed, please double check that you have a plugin directory in the same location as PSMInstaller.jar, and that the directory contains at least one plugin (for example, IntegrityAgent.jar). Click Next. 4. Finally, provide the path to the Integrity server where the agent is installed and click Next. 5. You will be presented with a summary screen. Click Uninstall to uninstall with these settings. 68 PTC System Monitor Installation and Usage Guide

69 Note The Integrity server must be restarted to completely remove the agent. Uninstalling dynatrace Agents Using the Command Line You can uninstall dynatrace Agents using the command line version of the PTC System Monitor installer: 1. Shut down the application from which the agents will be uninstalled. 2. Open a command prompt window on the system where you want to uninstall the dynatrace Agents. On a Windows platform, you must run the installer as the Administrator. Tip For example on Windows 7, right-click the Command Prompt option and select Run as administrator: Installing and Configuring the PTC System Monitor 69

70 3. Navigate to the directory containing the PSMInstaller.jar file. 4. Enter the java jar PSMInstaller.jar command with all arguments necessary to uninstall the dynatrace Agents. Include the top-level --uninstall agent argument and the appropriate set of additional arguments and values on the command. The following arguments can be specified when uninstalling dynatrace Agents: --install agent component=windchill installation_dir=<wt_home> component=tomcat installation_dir=<tomcat_home> component=windchillds installation_dir=<wt_home> component=integrity installation_dir=<integrity_home> psm_collector=<psm_collector> When uninstalling dynatrace Agents on an Integrity server, specify the component=integrity argument. Uninstalling dynatrace Agents from Integrity This example command assumes that dynatrace Agents have been installed on Integrity, where: The Integrity installation directory is D:\ptc\Integrity. The host name for the dynatrace Collector is dthost123 and the collector uses port Shut down Integrity before entering the command. When uninstalling agents from Integrity, enter a command on one line that is similar to the following: java -jar PSMInstaller.jar --uninstall agent component=integrity installation_dir=d:\ptc\integrity Note Ensure that a plugin directory containing IntegrityAgent.jar exists in the same directory as the core installer (PSMInstaller.jar). Uninstalling the dynatrace Server and dynatrace Collectors Before installing a new version of the PTC System Monitor, you must uninstall the current version. Uninstall dynatrace Agents first. Then, uninstall the dynatrace Server and Collectors. 70 PTC System Monitor Installation and Usage Guide

71 Note Before uninstalling the dynatrace Sever and dynatrace Collectors, back up your current server files as described in Backup and Recovery Strategies on page 29. Complete the following steps to uninstall the dynatrace Sever and dynatrace Collectors: 1. Shutdown the dynatrace Sever and dynatrace Collectors. See Server and Collector Shutdown on page Remove the components: On Windows systems, use the Windows Uninstall program option to remove the dynatrace Software components, including Webstart Clients. After components have been uninstalled, reboot your system. On UNIX and Linux systems, delete the installation directory. For example, from the command line, navigate to the installation directory and enter the rm -r <dir> command to remove the directory. 3. After completing steps 1 and 2, check to see that all installation files have been removed. Delete any remaining files. Removing the Webstart Client After you download the Webstart Client, it remains on your computer until you remove it. Complete the following steps to remove the client: 1. Open a command prompt and enter: javaws -viewer Installing and Configuring the PTC System Monitor 71

72 The current set of Java applications is displayed in the Java Cache Viewer window. For example: 2. Select the Webstart Client you want to remove and click the remove icon. 72 PTC System Monitor Installation and Usage Guide

73 4 Using PTC System Monitor Client PTC System Monitor Client Overview...74 Client Startup...76 Start Center...79 Basic Client Navigation...80 FastPack Considerations Backing Up Current Configuration...83 Dashlets and Dashboards...84 Search for Information...85 Filters...86 Configure Monitoring for Your System...87 This chapter contains details on using the PTC System Monitor client. 73

74 PTC System Monitor Client Overview The Java client for Windows and Linux platforms has many features. System administrators and IT professionals are its intended users. It can be run interactively as an active monitoring and diagnostic tool. There is also a HTTP interface (called the Webstart Client) available from the server Services page (as described later in this chapter). Note The HTML-based access has most of the functionality that is in the full Java client. It is intended for reporting and viewing dashboards by users or managers, and also for administrative monitoring using mobile devices that do not support a full Java client. The Webstart Client can also be executed in kiosk mode, during which it will automatically rotate through dashboards in order to display monitoring metrics in a public venue. Administrators will need to familiarize themselves with the basic operations of the Java client, including the following: how to backup dashboards and system profiles how to navigate, open and close dashboards how dashlets work within existing and new dashboards when to save changes to dashboards how to search for information how to apply filters and time frames to information how to adjust settings for a specific system (including thresholds, dashboards, and incidents) when to save changes to a system profile or configuration how to recover default dashboards and system profiles 74 PTC System Monitor Installation and Usage Guide

75 Requirements for Webstart Clients Your system must meet the following requirements for downloading and using PTC System Monitor Webstart Client: A 32 bit JRE from Java 6 or higher that contains a Java Web Start Launcher is installed and that JAVA_HOME is correctly set. Note There is an issue with Java 6 update 26 on Windows. The native file selector dialog fails. This issue affects Webstart Clients. PTC recommends that you use Java 6 with update 27 or later. Windows or Linux operating system. Browser that has JavaScript enabled. The client.jnlp file launched from browser is used to execute the Webstart Client. Java Webstart applications are launched by JAVA_HOME/bin/javaws. If the application to *.jnlp file extension mapping does not exist, you can create it. For example, from the Java Control Panel, select the Advanced tab. Then expand the JNLP File/MIME Association node and select Prompt User. The following shows the Windows Java Control Panel with Prompt User selected: Using PTC System Monitor Client 75

76 Click OK to save your changes and close the window. From Linux, you can launch the Java Control Panel using the following command: <Java_Home>\jre\bin\./ControlPanel The control panel displayed on Linux is similar to the Windows control panel. When opening client.jnlp file after setting Prompt User, you may be prompted to select how to open the file. The options are to open the file either with the default settings or by choosing the JRE location (javaws,). Select javaws, as shown in the following Linux window: Client Startup You can open the dynatrace Home page to start the PTC System Monitor Webstart Client by entering the server name and the client port in a browser using either HTTP or HTTPS. For example: Use the server name for <host> and the port number specified for the HTTP or HTTPS server during the installation. When the default port numbers were used during installation, either of the following can be entered: PTC System Monitor Installation and Usage Guide

77 The Home page opens displaying the following three options: Click Launch dynatrace Client to download and start the PTC System Monitor Webstart Client. Tip Launch dynatrace Client link launches the client.jnlp file to open the Webstart Client. If you have trouble opening the client, see Requirements for Webstart Clients on page 75. When the client has been downloaded, the Log In window opens. Enter the admin user name and the password that was enter during the dynatrace Server installation. Tip The Start Center window also opens by default when the client is started. For information about this window, see Start Center on page 79. Client Startup in Kiosk Mode The Webstart Client Kiosk mode allows you to run live dashboards, such as business or activity metrics. Using PTC System Monitor Client 77

78 To start the Webstart Client in kiosk mode, enter the dynatrace Home page as before. Select the Automate & Manage option. Next, select Client in Kiosk Mode to download and start Webstart Client in kiosk mode. 78 PTC System Monitor Installation and Usage Guide

79 When the client has been downloaded, the Log In window opens. Enter the admin user name and the password entered during the dynatrace Server installation. Start Center The Start Center window opens by default when the client is started. Note To turn this default action off, deselect the checkbox for Show on startup at the lower left of the window. When you first start the client, the license has not been imported. The Start Center window opens displaying the following link: Note Because the PTC license for using dynatrace is a group license, it is not managed using License setup. Instead, close the Start Center window and then import the license along with other PTC artifacts. For import instructions, see the instructions in Installing and Configuring the PTC System Monitor on page 31. The Start Center window has a series of tabs to administrative settings, monitoring, and diagnostic areas. After the initial installation and configuration is complete, a system profile for Integrity should already be selected in the upper right menu, as seen in the following screen shot. The Integrity system profiles are uniquely named by including a date code in the format of yyyymmddhhmmss after the Integrity system designator. The system profile displayed in Start Center window also identifies the host of the dynatrace Server at the end of the profile name. In this example, the date code is for May 23, 2012 at 4:52:09 PM and the host name is bl-pd4. (For more information on installation and configuration, see Installing and Configuring the PTC System Monitor on page 31.) The Administration tab displays indicators for each of the main settings that should be configured when the installation and deployment is complete. The Monitoring tab has the only accessible options for the self-monitoring dashboards: For details on using self monitoring, see Verifying a Deployment on page 28. Using PTC System Monitor Client 79

80 The other tabs besides Monitoring are not usually required for using the PTC System Monitor. The system is preconfigured with the Integrity software architecture and APIs; therefore, you will perform most of the administrative monitoring and diagnostics using the regular client user interface. For more information, see Monitoring Integrity on page 107. Basic Client Navigation The Java Webstart client has the following main features: The Cockpits tab The display area for dashlets and dashboards The status line for the currently selected dashlet The menu bar located at the top of the window Context menus are available within most areas of the client window by rightclicking. Hovering the mouse pointer for several seconds can also be used in some areas to trigger overlay windows containing detailed or underlying information. The following sections describe each area of the client. 80 PTC System Monitor Installation and Usage Guide

81 Cockpits Tab Located on the left side of the window is the Cockpits tab, which is a navigational dashlet: The Cockpits tab is a navigational dashlet that is used to access further dashlets organized under Status Overview, System Profiles, and Session Storage. There are expandable nodes within each branch of the navigation tree. Using PTC System Monitor Client 81

82 Dashlet and Dashboard Display Area Located to the right of the Cockpits tab is the display area where all other dashlets and all dashboards are displayed: In this example, the Integrity Overview dashboard is displayed. Dashlets can be displayed within new dashboards or with preconfigured properties within a saved dashboard. Dashlets show data in the form of charts and tables, and can have embedded buttons to trigger further commands or filtering. Note For more information on the functionality of dashlets and dashboards, see Dashlets and Dashboards on page 84. Status Line Located above the Cockpits tab is the status line: 82 PTC System Monitor Installation and Usage Guide

83 The status line identifies the currently selected dashlet or dashboard using the following format: <name>shows<profile> s data<time_frame_filter> where: <name> is the name of the dashlet or dashboard. In the example, the name is Integrity Overview <profile> is the name of the profile where the dashlet or dashboard resides. In the example, the profile name is PTC Integrity Server. <time_frame_filter> indicates the time frame and any applied filter that is being used to display the data. In the example, the data is from last 1 hour. You can adjust the data source, time frame, and filter by selecting items within the status line, or you can make adjustments using a context menu for the dashlet itself. Menu Bar Located at the top of the client window is the menu bar: Within the menu bar, there are menus, a group of quick-select icons for dashboards, searches, and filters, and a listing of the currently open dashboards. FastPack Considerations Backing Up Current Configuration Any time a new FastPack is applied to the server, it will overwrite any dashboard or system profile that has the same name as one contained in the FastPack. For this reason, prior to applying a FastPack, PTC recommends that you backup your configuration and rename any dashboard or system profile that has been customized but still has the default name. Using PTC System Monitor Client 83

84 For how to back up your current server files, see Backup and Recovery Strategies on page 29. Dashlets and Dashboards Dashlets A dashlet is an object used for navigation (Cockpits), diagnostics (Threads, Hotspots), or displaying of data in the Java client. Most dashlets are displayed in the form of a chart or table (or combination of both). Some dashlets such as Threads have embedded buttons to trigger an action or open further dashlets. Most dashlets are portable and can be embedded into dashboards. There are a number of context menu options and hover menu options available for most dashlets. The most commonly used context menu options include Dashlet Properties, Drill Down, Toggle Header, Configure Measures (tables), and Configure Series (charts). Hover menu options include Timeframe, Chart Resolution, Chart Type, Split Chart Mode, and Toggle Measure Table visibility. Dashlets can be expanded (maximized) and deflated to original size by doubleclicking on the header (when it is visible). Dashboards Dashboards can be created by opening a dashlet. You can open dashboards from the set of saved dashboards on the server or in a client s local storage. A saved dashboard is a preconfigured set of dashlets. The dashboard and each dashlet within it can be configured with values for the source (system profile), time frame and various filters. The size and location of each dashlet is also set within the dashboard. A dashboard can be intended for monitoring, diagnostic analysis, and reporting. Saved dashboards can be locked by the administrator or creator so that no new dashlets will be created within them (see context menu Properties for Protection and other options). In addition, user groups are configured with either Read-Write or Read-only access control for individual dashboards. Note As indicated, more than one dashboard can be opened at the same time within each client. Be aware that each open dashboard creates some amount of processing load on the server. If the amount of time required to update the dashboard or to perform other operations on the client is increasing, check to make sure that you do not have a large number of open dashboards, or a large number of running clients. 84 PTC System Monitor Installation and Usage Guide

85 Save Changes Dialog If a saved dashboard is modified by changing the properties, time frame, resolution, source, filter, size, display mode, or position of any dashlet, a Save Changes? dialog opens when the dashboard is closed (assuming you have Read/ Write permission). The same dialog opens whenever any new dashboard has been created by opening a new dashlet. Search for Information There are two main methods to search and find information with PTC System Monitor which are described in this section. Find Almost all of the tabular dashlets and system profile Edit lists are enabled with the Find function. Select any item with the table or list, and then click CTRL-F to run the Find/Search filter. For example, in the User Activity Breakdown table: To the right of the Find field, there are options to match case and switch between the search and filter mode. Using PTC System Monitor Client 85

86 Filters In addition to searching through large tables using Find, you can apply various filters to narrow down the amount of information displayed in any dashlet. The timeframe and source filters are commonly applied to all dashlets. Additional filters can be accessed from the Properties dialog or by selecting Edit Filter in the context menu for a dashlet: Integrity can be deployed in complex configurations with multiple sites, hosts and agent groups for load balancing, high availability, and performance of WAN clients. There can be multiple monitored systems for production, testing, training and development. Integrity has many different transactions, solution options and can be customized as well. Filters can be configured for Agents, Agent Groups, Hosts, APIs, Web Requests, PurePaths, Business Transactions, Incidents and Threads in order to better diagnose performance and scalability issues. 86 PTC System Monitor Installation and Usage Guide

87 One example of the use of filters can be seen on the Integrity Overview dashboard. The status indicators for each agent group use an agent group filter so that only incidents specific to that indicator are recorded. Here is the dashlet-specific filter for the Integrity_KB indicator, shown through the dashlet Properties page: Configure Monitoring for Your System The following sections show methods to modify PTC System Monitor settings in accordance with the requirements of a specific system, level of activity, and preferences of the administrators. Dashboard Modifications Note Before modifying a dashboard, PTC recommends creating a backup copy first. For how to back up your current server files, see Backup and Recovery Strategies on page 29. Using PTC System Monitor Client 87

88 Adding and Removing Dashlets To remove a dashlet from any dashboard, right-click on the dashlet header and select Close. This action cannot be undone. For example, if you do not need to monitor three servers, you can remove one of the server status indicators from the Integrity Overview dashboard: 88 PTC System Monitor Installation and Usage Guide

89 After closing, space is freed up on the dashboard: To avoid overwriting the customizations to this out-of-the-box dashboard, PTC recommends using Save As and giving the dashboard a new name instead of using Save. Using PTC System Monitor Client 89

90 To add a dashlet, first turn off protection for the dashboard in general dashboard properties by clearing the check mark from Add Cockpit Dashlets and Drill Down to new Dashboard. For example: When protection is off, you can select the dashboard context menu Add Dashlet or go to the Dashlets tab next to Cockpits. Double-click on a dashlet, set properties as needed, and it will be added to the dashboard on the right side. Drag or move the 90 PTC System Monitor Installation and Usage Guide

91 dashlet around the screen until the desired placement is achieved (this may take several tries and adjustments to other dashlets as well). When the new dashlet is placed, be sure to turn protection back on. System Profile Modifications There are various threshold and business transaction modifications that can be made to the default Integrity system profile for use with production or test systems. Before making any modifications, back up your current system profile. For how to back up your current server files, see Backup and Recovery Strategies on page 29. Business Transactions The set of business transactions provided by PTC are not configured by default to have their results measures stored in the Performance Warehouse. Customers who want to do long-term reporting on specific transactions will want to configure them to be stored. To configure the storage settings of a business transaction: 1. Double-click the Business Transaction node within the Cockpits tab. A list of business transactions appears in the Business Transaction View panel to the right. 2. Right-click on a transaction and select Edit Business Transaction to open the Business Transaction Editor window. 3. Clear the suppress storage of results in Performance Warehouse checkbox to store business transaction results. Note The checkbox may not be visible when you open the Business Transaction Editor window. If you do not see it, use the scroll bar to scroll toward the bottom of the window. Be aware that this configuration will increase the amount of storage required for data files over time. For more information, see Configuring the Performance Warehouse on page 60. Incidents The incidents configured within each system profile will highlight when specific problems occur, or when the thresholds of certain measures are exceeded. The amount of notification to the administrators is configurable. Incident thresholds and additional actions such as Thread Dumps, CPU Sampling, Memory Dumps and Activate Configuration (with additional sensors) can also be configured. The thresholds, actions and notifications are preconfigured by PTC, but can be modified as needed. Using PTC System Monitor Client 91

92 To configure an incident, double-click on the PTC Integrity Server profile, select Incidents and edit the incident that you want to configure. 92 PTC System Monitor Installation and Usage Guide

93 The Conditions tab displays the measures that are defined for the incident. Select a measure and click Edit. The thresholds can be adjusted and saved. If any incident uses the measure as part of its evaluation criteria, it will be adjusted as well. Using PTC System Monitor Client 93

94 The Actions tab displays the actions that are defined for the incident: 94 PTC System Monitor Installation and Usage Guide

95 When Smart Alerting is checked, the defined action is triggered just once, if multiple incidents occur, until the raised incident is confirmed by a user. Select and edit an action rule or add a new action: Using PTC System Monitor Client 95

96 Configuring Monitors You can configure monitors to gather performance analysis information from the host machine (where Integrity is installed), and from a backing Oracle database (if used). 96 PTC System Monitor Installation and Usage Guide

97 1. From the dynatrace client Cockpit navigator, expand System Profiles. 2. Right click on PTC Integrity Server <Default> and select Edit System profiles... In the dialog that appears select Monitors on the left side. Using PTC System Monitor Client 97

98 3. Select the monitor you want to configure and click the Edit button. 4. Complete the following configuration steps: On the Monitor tab: Complete the settings. See Windows Monitor Settings on page 98, UNIX Monitor Settings on page 100, Oracle Monitor Settings on page 100, and SQL Server Monitor Settings on page 101. Delete the existing host and add a new one. See Adding Monitor Hosts on page 103. On the Schedule tab, set the interval at which dynatrace will query for data. See Setting Monitor Schedules on page 104. Run the monitor. See Running Monitors on page 105. Windows Monitor Settings dynatrace hooks into the Windows Performance Monitor (included in all newer versions of Windows) to collect performance data. You must provide dynatrace with a Windows user with the proper permissions. For a Windows 2003/2008 host, the user needs to be a member of the Performance Monitor Users group; for a Windows XP host, the user needs to be an Administrator. From the System Profile Monitors window, edit the Default Windows Performance Monitor and complete the information on the Monitor tab based on the screen shot below: 98 PTC System Monitor Installation and Usage Guide

99 Using PTC System Monitor Client 99

100 UNIX Monitor Settings From the System Profile Monitors window, edit the Default Unix Performance Monitor and complete the information on the Monitor tab based on the screen shot below: Oracle Monitor Settings If you have an Oracle database backing Integrity, you can set up an Oracle monitor. 100 PTC System Monitor Installation and Usage Guide

101 From the System Profile Monitors window, edit the RepositoryDB and complete the information on the Monitor tab based on the screen shot below: SQL Server Monitor Settings If you have a SQL Server database backing Integrity, you can set up a SQL Server monitor. Using PTC System Monitor Client 101

102 From the System Profile Monitors window, edit the RepositoryDB and complete the information on the Monitor tab based on the screen shot below: 102 PTC System Monitor Installation and Usage Guide

103 Adding Monitor Hosts On the Monitor tab of the monitor you are configuring, delete the existing host, and add a new one. When you add a new host, select vm-dyna. Using PTC System Monitor Client 103

104 Setting Monitor Schedules On the Schedule tab of the monitor you are configuring, change the run interval to every minute. 104 PTC System Monitor Installation and Usage Guide

105 Running Monitors After saving your monitor configuration, select the monitor in the System Profile Monitors window and click the Run Now button. If everything is configured properly, the circles should turn green: Using PTC System Monitor Client 105

106

107 5 Monitoring Integrity Accessing Dashboards that Provide Monitoring Information Using Integrity Server Dashboards Using Incidents to Locate Issues Using Business Transactions to Locate Issues Limiting the Overhead of the PTC System Monitor Using Self-Monitoring and Other Incidents to Check PTC System Monitor Performance This chapter contains details on how to monitor Integrity systems using the PTC System Monitor. The contents of the chapter assumes that the PTC System Monitor has been installed and configured as describe in earlier chapters. 107

108 Accessing Dashboards that Provide Monitoring Information From the PTC System Monitor Webstart Client Dashboard menu, you can open the dashboards included in the PTC FastPack that has been installed. PTC provides a number of dashboards that can be useful when monitoring Integrity. You can select the following dashboards from the Open Dashboard window. Integrity Overview Integrity Server Integrity Host Integrity Usage Source Usage Integrity License Usage Oracle Database Dashboard MS SQL Server Dashboard For additional details about these dashboards, see Using Integrity Server Dashboards on page PTC System Monitor Installation and Usage Guide

109 Using Integrity Server Dashboards For descriptions of how to use Integrity dashboards and dashboard components, see the following sections. Integrity Overview Dashboard The Integrity Overview dashboard is the central dashboard for all Integrity Servers associated with the system profile. This dashboard is intended to be the starting point for linking to dashboards for specific servers. The following screen shot shows a sample Integrity Overview dashboard : This dashboard displays status indicators for each Integrity Server. The status of a server is based on an aggregate of the status of a set of incident rules. For more information on status indicators, see Status Indicators on page 120. To see the list of incidents and their states for a server, hover over the status indicator. Monitoring Integrity 109

110 For additional information about incidents, see Using Incidents to Locate Issues on page PTC System Monitor Installation and Usage Guide

111 To display a dashboard for a specific server, right click on an agent and select Show in Dashboard, then select the dashboard that you want to display for that server. Note The dashboard links need to be manually added using the configure option. The selected dashboard is displayed, with the results filtered based on the specific server. Note You must select the server name in the Agent dashlet to show the results in another dashboard. Right clicking on the status indicator and selecting Show in Dashboard does not work correctly. This is a known issue that has been submitted to dynatrace. Monitoring Integrity 111

112 Integrity Server Dashboard The Integrity Server dashboard displays important Integrity server information such as memory and CPU usage. The following screenshot shows a sample Integrity Server dashboard: This dashboard contains the following charts: Integrity Server Related Incidents: All the incidents that are directly related to the Integrity Server s stability. Integrity Memory Usage: The memory usage details of the Integrity Server. This does not include other processes on the host server machine. Integrity CPU Usage: The CPU usage of the Integrity Server. dynatrace Overhead: An estimated CPU overhead that dynatrace is imposing on the Integrity process. Integrity Thread Count: The number of threads that the Integrity Server has open. A summary of all errors, incidents, and database queries are also listed at the bottom. 112 PTC System Monitor Installation and Usage Guide

113 The Errors tab lists the errors that are thrown by Integrity. For example: The Database tab lists slow queries that could possibly be optimized, listed in descending order. This tab also shows how much the database connection pool is used for this server and how much the database connection contributes to the overall response time for a transaction. For example: Monitoring Integrity 113

114 Integrity Host Dashboard The Integrity Host Dashboard displays important host server data such as overall memory and CPU usage. All data is captured from the Windows, UNIX, Oracle or SQL Server Monitor, which you set up when configuring monitoring for your system. See Configuring Monitors on page 96. The following screen shot shows a sample Integrity Host dashboard. This dashboard contains the following charts: Host Related Incidents: All the incidents that are directly related to the physical host server stability. Host Memory Usage: The total memory usage on the host server, including the Integrity process. Host CPU Usage: The total memory usage on the host server, including the Integrity process. Host Disk I/O: Amount of reads and writes per second on the host server disk. Host Network I/O: Amount of bytes transmitted and received per second on a designated network interface. 114 PTC System Monitor Installation and Usage Guide

115 Integrity Usage Dashboard The Integrity Usage dashboard displays important usage information relating to workflow and document operations such as the time for creating or editing an item The following screenshot shows a sample Integrity Usage dashboard. This dashboard contains the following: Run Query Times: Lists the transaction time for all run queries for all users. Item Create/Edit Times: Lists the transaction time for all item create/edit operations for all users. Item Open Times: Lists the transaction time for all open/view item operations for all users. Document Open Times: Lists the transaction time for all open/view document operations for all users. Monitoring Integrity 115

116 Source Usage Dashboard The Source Usage dashboard displays important usage information relating to configuration management operations such as the time for checkpointing a project or submitting a change package. The following screenshot shows a sample Source Usage dashboard. 116 PTC System Monitor Installation and Usage Guide

117 Integrity License Usage Dashboard The Integrity License Usage dashboard displays all IM/SI float/seat license usage. All data is captured from the PTC Integrity Monitor which needs to be configured. The following screenshot shows a sample Integrity License Usage dashboard. Monitoring Integrity 117

118 Oracle Database Dashboard The Oracle Database dashboard displays important Oracle metrics such as cache hit ratios, system waits, and concurrent sessions. These metrics give a picture of the overall database performance. All data is captured from the Oracle Monitor, which you set up when configuring monitoring for your system. See Configuring Monitors on page 96. The following screen shot shows a sample Oracle dashboard. 118 PTC System Monitor Installation and Usage Guide

119 MS SQL Server Dashboard The MS SQL Server dashboard displays important SQL metrics such as buffer page read/writes, transactions, and access full scans. These metrics give a picture of the overall database performance. All data is captured from the SQL Monitor, which you set up when configuring monitoring for your system. See Configuring Monitors on page 96. The following screen shot shows a sample MS SQL Server dashboard. Monitoring Integrity 119

120 Status Indicators There are two types of status indicators: Server status indicators Incident status indicators Server status indicators display on the Integrity Overview dashboard. Each indicator tracks a set of incidents that determine the status of the server during the time frame set for the dashboard. Note The status indicators are only useful after you have connected the PTC System Monitor to Integrity and have configured it property. They do not indicate that there is a problem with your connection or configuration. The value of the server status indicators is based on the following: When there are no threshold violations in the incidents for the server, the health indicator is green and contains a check mark. When there is at least one threshold violation that is severe in the incidents for the server, the status indicator turns red and contains an X. When there is at least one threshold violation that is a warning and no threshold violations that are severe in the incidents for the component, the status indicator turns yellow and contains an exclamation mark. Incident status indicators display all dashboards other than the Integrity Overview dashboard. Incident status indicators display the status for each incident. 120 PTC System Monitor Installation and Usage Guide

121 The value of the incident status indicators is based on the following: When there are no threshold violations for the incident, the health indicator is green and contains a check mark. When there is at least one threshold violation that is severe for the incidents for the server, the status indicator turns red and contains an X. When there is at least one threshold violation that is a warning and no threshold violations that are severe for the incident, the status indicator turns yellow and contains an exclamation mark. Understanding Status Indicators Each indicator has two parts: The top 3/4 of the indicator shows the current status. The bottom 1/4 of the indicator shows the status from the time period listed in the link displayed near the top of the window. For example, the following screen shot shows a time period of the last hour: The following status indicator shows the current status as severe and the status from the last time period also as severe: If this indicator displays for a server, you can drill down into the incidents that and when you have determined that the incident has been addressed, you can change the upper status indicator back to green by confirming the incident where the threshold is severe. For more information on confirming incidents, see Using Monitoring Integrity 121

122 Incidents to Locate Issues on page 128. Then the top status indicator changes to green while the bottom indicator remains red until the time period in which the incident occurred has passed: Note If you are running the server with a failover configuration and the primary server fails, an incident is triggered. The secondary server then stars up with a different agent name. To clear the status icon for the primary server, you must delete the incident. For more information on confirming incidents, see Using Incidents to Locate Issues on page 128. Note When configuring the server status icon on the Integrity Overview dashboard you should set the Host filter to both the primary and secondary servers. For more information on filters, see Filters on page 86 Adding a Status Indicator To add a status indicator, do the following: 1. Right click on an existing server status icon and select Copy. 2. Right click and select Paste in the same dashboard. 3. Move the new status icon to the desired location. 4. Right click on the icon and select Dashlet Properties 5. Give it an appropriate name. 6. Select the Source tab and then edit the Filter. 7. Select the Hosts tab and change the filter to the appropriate host. Closing a Status Indicator If you do not need all the status indicators on the dashboard, you can close the indicator. This action removes the indicator from the dashboard. For example, if you only need to monitor two servers, but you have three indicators, you can close the Server 3 status indicator. Note You cannot undo the actions described in this topic; before closing indicators be sure to back up the dashboard. Use Dashboard Save As or the dashboard rightclick Save As option to save the existing dashboard with a new name before proceeding. 122 PTC System Monitor Installation and Usage Guide

123 To close a status indicator, right-click the indicator header (such as Server 3) 3 and select Close from the menu options that are displayed. Clicking Close removes the indicator from the indicators that are displayed. Then, saving the dashboard saves all of the changes that you have made to the dashboard. Drilling Down into PurePaths You can find out the underlying transaction information for a chart or incident by drilling down into PurePaths. For example, if you drill down for a chart, you will see the PurePaths that are used in the chart measures; if you drill down for an incident, you will see the PurePaths that triggered the incident. If an incident is directly triggered by a certain transaction or operation, when you drill down you will see the exact PurePath that caused the problem. If an incident is a more general problem, for example, High Memory Usage, you will see all PurePaths captured on the server for the problematic time frame. To drill down into PurePaths, right-click on the chart or on the status indicator for the Incident, and select Drilldown > PurePaths. Monitoring Integrity 123

124 PurePaths provide details of a transaction from start to finish, including method calls, return/argument values, and method execution/suspension times. A PurePath can capture data across multiple agents. 124 PTC System Monitor Installation and Usage Guide

125 You can drill down into PurePaths for a specific time frame in a chart by doing the following: 1. Left-click on the chart and drag to select an area of the chart. 2. Right-click in the selected area and select Drilldown > PurePaths. Out-ofof-the-box Threshold Values The following table describes the events and corresponding threshold values that are set in the out-of-the-box PTC System Monitor dashboards: Incident/Measure Warning Severe Unit Evaluation High CPU Usage for Host Server Host CPU Usage % Average over 1 minute High Memory Usage for Host Server Host Memory Usage % In a 5 minute window the average must hit the Monitoring Integrity 125

126 Incident/Measure Warning Severe Unit Evaluation threshold twice High DB Connection Count DB Connection Count Number Average over 1 minute Low Free Disk Space on Host Logical Disk Free Percentage %. Average over 1 minute Slow Create Item/Edit Item-New 3. 5 Seconds Maximum over 1 minute Item-Edit 3 5 Seconds. Maximum over 1 minute Slow Document Open Document Open Seconds Maximum over 1 minute Slow Document Operation Document Baseline 3 5 Seconds Maximum over 1 minute Document Branch Seconds Maximum over 1 minute Document Copy Seconds Maximum over 1 minute Document Move 3 5 Seconds Maximum over 1 minute Slow Item Trigger Run Trigger (Rule Based) Seconds Maximum over 1 minute Slow Project Checkpoint Source-Project Hours Maximum Checkpoint over PTC System Monitor Installation and Usage Guide

127 Incident/Measure Warning Severe Unit Evaluation minute Slow Chart/Report Run Chart Seconds Maximum over 1 minute Run Report Seconds Maximum over 1 minute Slow Query Run Query Seconds Maximum over 1 minute Slow Item Open Item-Open 3 5 Seconds Maximum over 1 minute Slow Login Server-Login 5 10 Seconds Maximum over 1 minute Slow Submit CP Source-Submit CP Seconds Maximum over 1 minute Monitoring Integrity 127

128 Using Incidents to Locate Issues To see the incident details for any of the status indicators that are on the System Health dashboards, right-click the status indicator and select Drill Down Incidents: The Incidents dashlet displays a view of the Incidents dashboard. From this view, you can see the Incident dashboard that not only includes incidents that have occurred, but also all incidents that could occur. The Incidents dashboard is also available from the Cockpits tab. From this view, incidents are grouped by profile (which includes the dynatrace Self-Monitoring profile). 128 PTC System Monitor Installation and Usage Guide

129 The default display for an Incidents dashlet could be confusing at first because it lists both the incidents that have been triggered and the ones that are just configured, but which have not occurred. The sorting done is by profile: You can use the Structure Mode option that is available from the right-click menu to do some additional sorting. The default sort is Group by System Profile/Incident Rule: Change the Structure Mode to a different Group by setting to see a better picture of the current incidents. Monitoring Integrity 129

130 For example, change to Group by State: Notice that the Incident Rules are not listed anymore. Now change to Group by Severity: Aside from the display, there is another behavioral rule to be aware. When you Confirm an incident, it is grayed out in the display but not removed unless you Delete it. For example, two of the four warning level incidents below have been confirmed: If you do not want to delete incidents, you can use the Structure Mode Group by Progress to segregate the Confirmed incidents. For example: 130 PTC System Monitor Installation and Usage Guide

131 Using Business Transactions to Locate Issues In dynatrace, defining a business transaction allows the categorization of PurePaths so that similar user-system interactions can be gauged and compared against each other. Business transactions are defined by using filters (such as method signatures and URIs) to categorize PurePaths as being a certain type of interaction. The business transactions can then be used to capture and evaluate the results of the interactions so that all such interactions can be compared with each other and provide visibility into the overall usage of the system. Business transactions can be used as a basis for incidents and as chart measure. PTC provides an out-of-the-box set of business transactions to capture important transactions between users and Integrity. For example, if a user claims that a certain query is slow, the administrator can use the Run Query business transaction to find exactly which part of the transaction is taking the most time. As a second example, if one user from a particular office claims that all of his or her transactions seem slow, use the All Operations by User business transaction to group and compare the response times between users in the same or different offices. Viewing Business Transactions All actions performed on the monitored server that match a defined business transaction are displayed within the Business Transaction View. Monitoring Integrity 131

132 For quick access, all business transactions are available through the Cockpits tab: By double-clicking the Business Transactions node, all business transactions that have executed in the time frame that is in effect are shown in the right panel Business Transaction View. For example: By opening the Business Transactions node, all business transactions that have been imported from the PTC FastPack are shown nested below Business Transactions. By editing a business transaction, you can choose to store results in the Performance Warehouse for reporting if needed. Changing Business Transaction Thresholds To view all warning and severe thresholds of business transactions, edit the system profile you are interested in by right-clicking the profile from the Cockpits tab and selecting Edit System Profile. Then select Business Transactions from the System 132 PTC System Monitor Installation and Usage Guide

133 Profile window. The list of business transactions displayed on the right include columns for the results calculated, the filters used, and warning and severe thresholds. To change a threshold, edit the transaction by double-clicking it or by selecting the row and clicking Edit. PTC Business Transaction Descriptions PTC provides a set of key out-of-the-box business transactions to capture important transactions between users and Integrity Monitoring Integrity 133

134 All out-of-the-box business transactions provide the following transaction information, grouped by user: minimum transaction time maximum transaction time average transaction time transaction failure rate. For example, the Item-New business transaction enables you to see who created items, how many items they created, and the transaction times and failure rates. 134 PTC System Monitor Installation and Usage Guide

135 Limiting the Overhead of the PTC System Monitor There might be cases in which the various bits of information that the PTC System Monitor is capturing causes an unacceptable amount of overhead on your system. In these cases, it might be necessary to analyze the information that is not useful to understand the information that can be ignored and not captured. For example, you can: Reduce the extent to which error and exception information is captured. Reduce the extent to which SQL statements are captured. Note By default, bind variables are captured. Capturing bind variables could cause a slowdown in performance. If you need to improve performance, you can turn bind variables off in the JDBC Sensor properties (that are described later in the topic). By default, stacktraces are captured. Capturing stacktraces could cause a slowdown in performance. If you need to improve performance, you can turn stacktraces off in the JDBC Sensor properties (that are described later in the topic). Reduce the PurePath percentage that is captured. By default, 100% of PurePaths is captured. Note The Integrity system profile contains some debugging system profile configurations that are disabled by default. These should be left disabled in order to minimum your overhead. Monitoring Integrity 135

136 Reducing Exceptions If you have determined that some Integrity exceptions that are captured by the PTC System Monitor are not meaningful, and you want to configure the PTC System Monitor to not capture the error information, you can edit a system profile to filter out the exceptions. Each agent group within each system profile that you have maintains a separate set of exceptions. Note PTC filters out a set of exceptions by adding them to the set of exclusions in each system profile that is provided. Add to the set of out-of-the-box exceptions; do not remove from the set. Complete the following steps to add exceptions to the existing set of exceptions that are filtered out for each agent group: 1. Double-click the system profile from Cockpits to open the System Profile Preferences window. 2. From each agent group in a system profile, click Sensor Configuration to open the Sensor Pack list. 3. In the Exceptions Sensor Pack row, click the Properties link. For example: 136 PTC System Monitor Installation and Usage Guide

137 4. On the Configure Sensor Properties window, click Create: Monitoring Integrity 137

138 5. In the Configuration Properties table, enter the exception class name and message text. For each, set the appropriate Match selection. For example: 6. To add more exceptions, repeat steps 4 and 5. When all exceptions have been added, click Ok to save your additions. After all agent groups have been modified, perform either a restart or Hot Sensor Placement to propagate the changes to the agents. 138 PTC System Monitor Installation and Usage Guide

139 Reducing Maximum Captured SQL Statement Length If you have determined that the current maximum length that is set can be shortened, you can edit a system profile to change the maximum that is set by default in the JDBC sensor. Each agent group within each system profile that you have maintains a separate maximum value. Note Shortening the maximum value can cause some SQL statements that were being are captured in full to be truncated. Complete the following steps to change the maximum length of captured SQL statements for each agent group: 1. Double-click the system profile from Cockpits to open the System Profile Preferences window. 2. From the each agent group in a system profile, click Sensor Configuration to open the Sensor Pack list. 3. In the JDBC Sensor Pack row, click the Properties link. For example: 4. On the Configure Sensor Properties window, modify the value in the Max. SQL Command capture length field. 5. Click Ok to save your changes. After all agent groups have been modified, perform either a restart or Hot Sensor Placement to propagate the changes to the agents. Monitoring Integrity 139