PSM MONITORING

AND
TROUBLESHOOTING
COURSE INTRODUCTION
1. Your trainer: Johan Lang

2. Training layout
– Presentation (~4 hours)
– Practice session (~4 hours)

3. Presentation modules
– PSM fundamentals
– PSM navigation and functionality
– PSM techniques

4. Delivery notes

2
PSM FUNDAMENTALS

Johan Lang
Principal Support Engineer

April 2018
AGENDA
1. Introduction

2. Concepts

3. Terminology

4
 • Introduce PSM and its main components

OBJECTIVES • Describe the concepts of PurePaths and Business

Transactions

• Cover PSM terminology

5
1 INTRODUCTION

6
INTRODUCTION

• What is the PTC System Monitor (PSM)?

– Aid monitoring and forensic diagnosis
– Captures code execution paths and SQL data
– Provides live application health status
– Based on dynaTrace

• How it functions
– Separate server-client system that monitors Windchill
– Stays up even when the monitored product are down
– “Flight data recorder”
– Performance warehouse stores subsets of collected data
– Web accessible dashboards for remote monitoring
– Store and export incident data
– Customizable for specific requirements and custom code sources

7
CAPABILITIES

20+ Dashboards Alerts on KPIs Reports

Key host and application Warning and Severe Validate SLAs
metrics notifications Resource and response time
trend analysis

User Tracking Instrumentation of core areas Collaborate with PTC TS

100+ Business Transactions Code level diagnostic data Integration with System
Configuration Collector

8
COMPONENTS

• Agent • Collector • Server

– Injected into – Receives data from – Receives data
monitored process Agents packets from the
– Gathers data and – Packages the data Collectors
sends to Collector and sends it to Server – Processes and stores
– Lightweight, small – Multiple Collectors the data
footprint can connect to single • Session data stored
– Each agent has a Server on disk space
unique name – Number of collectors • Subscribed
depends on number measures stored in
Performance
of locations Warehouse
– Serves client web
requests

9
COMPONENTS

• Client • Performance • Other add-ons

– User portal to the PSM Warehouse – User Experience
server – Database where Monitor
– View / navigate data metrics / – Oracle/SQL Server
– Configure PSM server measurements are monitoring
– Two variants: stored – …
• Thin – Production database
• Full (Thick) recommended
• Oracle
• SQL Server

10
COMPONENTS

11
2 CONCEPTS

12
PUREPATH

• Complete, multi-dimensional
stack trace

• Spans multiple components

• Includes:
– Method calls
– Method execution measures

13
PUREPATH

• Some advantages • Some disadvantages

– Complete path through all – SQL statements can appear
components earlier/later than actual call
– Includes API signature and metrics – No line numbers
– Lack of DB fetch visibility

14
BUSINESS TRANSACTIONS

15
BUSINESS TRANSACTION

Search

16
BUSINESS TRANSACTION
Hawaii Florida Australia

Search

17
BUSINESS TRANSACTION
Hawaii Florida Australia

Response time and

execution count of
search transactions
Search
split by destination

Response Time

5s

4s

3s Response Time Hawaii

10:13 10:14 10:15 10:16 10:17
6s
Hawaii Florida Australia
5s
Search Result Count
4s
800
600 3s

400 2s
200 10:13 10:14 10:15 10:16 10:17
0 Min Avg Max
10:13 10:14 10:15 10:16 10:17

Hawaii Florida Australia

18
BUSINESS TRANSACTIONS
• Definition:
– Logical grouping of PurePaths
– Can be used as a basis for Incidents
– Can filter out PurePaths based on criteria
– Can be used as chart measures

- Each product has a number of key Out-of-the-Box Business Transactions

19
BUSINESS TRANSACTIONS
Transaction monitoring

20
 Fast Time to Value
BUSINESS TRANSACTION
Transaction visualization and analysis

Every transaction
linked to
underlying
Infrastructure

Detailed
analysis on
root cause

21
3 TERMINOLOGY

22
TERMINOLOGY

• Monitors / tasks • Incident • Measure

– Executes on remote – Triggers actions – Monitors aspect of
machine based on criteria application
– Executes on – Criteria based on – Single, numeric data
scheduled basis Measures / Business point
– Monitor stores Transactions
resulting data in – Actions include:
Measures • Pop-up in client
– Tasks executes action • Send e-mail
but does not capture • Thread dump
measure • Heap dump
• Session dump
• Script execution

23
TERMINOLOGY

• Sensor • Sensor Pack

– Entry point to start tracking – Collection of Sensor and Sensor
– Pattern matching API call Groups
– Organized into Sensor Groups
– Place – enable pattern

24
TERMINOLOGY

• Agent Group
– Couples Sensor placement
and configuration with
agent mapping
– Mapping matches agent
name -> apply settings

25
SYSTEM PROFILE

• The profile contains all definitions for Sensors, Incidents, Measure definitions and
thresholds

• Different Profiles can be set up

• Different Agents can map to a single profile

• Agent Groups differentiate between several Processes running on the monitored

Server
– Ensure unique Agent instance names!

26
SYSTEM PROFILE

27
QUESTIONS?

28