Scribd
Upload
160 views

DynaTrace Analysis Overview

This document provides an overview of DynaTrace analysis including: 1. It describes the key components of the DynaTrace architecture including the server, collector, client, agent, warehouse, and analysis server. 2. It explains how DynaTrace collects metrics through pure paths, entry points, and various sensor types including auto sensors and custom sensors. 3. It outlines the main entities that can be assessed through DynaTrace including transactions, response time hotspots, purepath information, database usage, server timelines, JVM monitoring, memory analysis, and thread analysis.

Uploaded by

Sreenivasulu Reddy Sanam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
160 views

DynaTrace Analysis Overview

This document provides an overview of DynaTrace analysis including: 1. It describes the key components of the DynaTrace architecture including the server, collector, client, agent, warehouse, and analysis server. 2. It explains how DynaTrace collects metrics through pure paths, entry points, and various sensor types including auto sensors and custom sensors. 3. It outlines the main entities that can be assessed through DynaTrace including transactions, response time hotspots, purepath information, database usage, server timelines, JVM monitoring, memory analysis, and thread analysis.

Uploaded by

Sreenivasulu Reddy Sanam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

Intro to DynaTrace Analysis

- June 2015

By: Ashraf and Poorna


Agenda

• Architecture
• Metrics Collection
• Assessment Entities
• Dashboards
• Questions
DynaTrace Architecture

DynaTrace Components
• dynaTrace Server • Performance Warehouse
• dynaTrace Collector • Smart Sensor
• dynaTrace Client • dynaTrace Analysis Server
• dynaTrace Agent • Offline Session Analysis
dynaTrace Metrics Collection

 PurePath
 Entry Point
 Sensors
 Auto Sensor
 Custom Sensor
 Business Transaction
 Tire Management
 Save Session
 Offline Analysis
DynaTrace Terminologies

PurePaths:
• PurePath is the technology that provides data to the dynaTrace system.
• It is a trace through a system of applications (Web Browsers, Web Server, Java, .NET, Native) that
contains timing information as well as context information such as executed SQL statements.
• A PurePath represents a single end-to-end transaction within a monitored application.

Entry Points:
• An Entry Point is the starting point of a new PurePath.
• It is defined by a placed and active sensor with the appropriate configuration.

Sensors:
• A Sensor is a small piece of code that is injected into the
monitored applications at certain points to extract the relevant
data.
• The dynaTrace installation includes a set of built-in Knowledge
Sensor Packs for a wide set of application servers and
frameworks, which are maintained by dynaTrace, and can be
activated/deactivated.
DynaTrace Terminologies
Types of Sensors Packs:
– Java Exception Sensor – JMS Tagging Sensor
– Java Logging Sensor – WebSphere MQ Sensor
– Java Web Requests Sensor – WebSphere MQ Tagging Sensor
– Java Web Service Sensor – WebSphere MQ Mapping Sensor
– Servlet Sensor – Web Server Sensor
– JDBC Sensor – Cassandra Sensor
– JNDI Sensor – Hadoop Sensor
– JMS Sensor – ASP.NET Sensor

Auto Sensors:
• dynaTrace provides additional information on PurePaths without the need to do specific
configuration.
• Auto Sensors automatically retrieve additional call hierarchy information and place this information
on the respective PurePaths.
• This information includes class and method names, parameter and return types, and access
modifiers, code-level CPU/IO/Sync/Wait hotspots, transactional execution data etc.

Custom Sensors:
• These are user-defined sensors which acts as an Entry Point when configuration is changed to Active
and Start PurePaths.
dynaTrace Analysis

1. Transaction Flow
2. Response Time Hot Spots
3. PurePath Information
• PurePath Tree
• PurePath Contributors

• Time Consuming Methods

4. PurePath Information of 1 Transaction


• Drill Down Information
• Transaction Flow
• Sequence Diagram
5. Database Usage
6. Server Timeline (dynaLabs)
7. JVM Monitoring by Charting (Heap Usage, JVM - CPU Usage, GC Usage)

8. Memory Analysis
• Memory Leak analysis, duplicate string analysis, Http Session analysis, Root Path Analysis

9. Thread Analysis
• Stack flow of thread, state statistics, CPU hotspot

10. Host Monitoring (Total CPU Usage, Total Network Bytes Sent/Received)
Assessment

 Total - 23557 transactions were reported in DT during the test time frame.
 Total Average Response time is 0.214s
 Among them 671 transactions were having response time more than 1s
 The majority of the time (almost 56%) is spent at  JVM level and DB
contributing to 20% of the total transaction time.
 JVM Heap Memory increases as the test progress.
 Though the used heap size is less than 1Gb (MAX heap size - 1GB) the
overall process memory increased to 1.48GB triggering potential native
memory leak.
 CPU load average was less than 18%.
 Thread count increases until 315.
 Total GC time at any given time was less than 1.6s.
 Total GC utilization was less than 5%.
 Lots of Errors and Exceptions were found.
Dashboard - 1
Dashboard - 2
Dashboard - 3
Questions

• Reference

You might also like