Skip to end of metadata
Go to start of metadata

February 16th, 2010

We are proud to present dynaTrace 3.2.

This upgrade provides new features and key improvements to scalability, performance and stability.

We recommend to upgrade dynaTrace Agents, dynaTrace Collectors and dynaTrace Servers to 3.2. Please see the Migration Guide and Deployment Guide for dynaTrace 3.2 for detailed instructions.

Highlights of dynaTrace 3.2

dynaTrace 3.2 also includes

Additional Information

Download dynaTrace 3.2

(lightbulb) 50+ new features and improvements

100% Traceability in Production under Load

Large applications covered with single dynaTrace Server

Production systems are typically under high load and managing their performance is critical to the success of every business. As modern applications - i.e. based on services, cloud computing but also classical and clustered multi-tier architectures - become increasingly complex, maintaining the environment becomes a real challenge. This release is capable of providing 100% traceability even for large applications with a single dynaTrace Server and thus, enabling you to focus on what matters most: your application.

Following the Deployment Guide for dynaTrace 3.2 is instrumental in reaching the maximum performance gain, e.g. running on sufficient hardware, having the recommended deployment and knowing the expected peak load of your applications in production.

Extended real-time visibility into production systems

The dynaTrace Server now supports up to 32 GB of memory which means 4x more transactions of your production applications always at your fingertips, in real-time.

Monitoring Services Integration

[

The performance of a service or website is critical to its success. To ensure service levels are met and downtimes are detected immediately even with no user load (e.g. during night), synthetic transactions are executed by virtual users 24x7 at regular intervals. Performance metrics based on these synthetic transactions deliver repeatable results which are suitable for predictable alerting and trending. dynaTrace is capable of separating real from virtual users in your production system and of producing reports which focus on the performance of each of these transactions separately. This means that the backend performance of the "buy"-click can be correlated to monitoring services providers like keynote or gomez.

Report creation and automated distribution

[

The Reporting Plugin, which was available on the Community Portal, already made dynaTrace Report automation and distribution easy. Thanks to your feedback, we've been able to further improve it and it now ships out-of-the-box with the product. The plugin is capable of creating reports based on a schedule (e.g. every day/week) and sends the report in any format via email and/or stores it on a shared folder. Furthermore, email reports embed images now inline so they can be viewed conveniently in your favorite email client.

New Features

dynaTrace is now capable of following transactions across thread boundaries of .NET applications. This is a long awaited catch-up to dynaTrace's Java capabilities which is instrumental to diagnosing and monitoring heterogeneous applications including both Java/.NET tiers.

dynaTrace's architecture has been designed for high-load, 24x7 production environments. To get most out of your dynaTrace deployment - also during peaks - this release comes with two new Dashboards that help you with sizing and fine-tuning all dynaTrace components.

The following questions can be answered:

  • Is my dynaTrace deployment working as expected?
  • Is more or less memory required for my dynaTrace Collectors or Servers?
  • Is the load distributed equally across my dynaTrace Collectors?
  • Should I add another dynaTrace Collector or Server?

It is now possible to create Dashboards and Reports which fully integrate with tagged requests coming from monitoring service providers like keynoteor gomez. Define Business Transaction Mappings based on arbitrary header fields to correlate specific virtual users with specific user actions (e.g. click on a button or performing a use case) and monitor/diagnose them to spot performance improvements.

Key Improvements

  • The Welcome Dashboard was opened automatically every time the dynaTrace Client connected to a dynaTrace Server. It is now opened only once when you connect to a dynaTrace Server for the first time.
  • The "Save Dashboards" dialog which pops up when closing the dynaTrace Client has been improved. If no Dashboard should be saved, instead of deselecting all changed Dashboards and clicking "Save" you now can simply click "Skip" and the dynaTrace Client exits.
  • When changing the Dashboard's data source to point to a different Session, the dropdown is now sorted alphabetically which makes it easier to pick the Session you are looking for.
  • Measures used for Business Transactions' evaluation criterion are now created as non-dynamic Measures per default. Feedback from the field showed that this is the typical usage scenario and it avoids unnecessary computational load on the dynaTrace Server.
  • Business Transaction Mappings now support groupings based on multiple captured arguments of the same method. If, for instance, a single method's parameter is used to define the user's country and city, a Business Transaction Mapping can show CPU times for each city grouped by country.
  • Measures resulting from Business Transaction Mappings now show up in a separate Metric Group called "Business Transaction Results".
  • The defaults for units and aggregations have been revised when adding Measures to Charts (e.g. Kilobytes instead of Bytes for remoting). This saves many clicks and time while creating Dashboards used for monitoring which rely on Charts heavily.
  • An Incident is thrown on the dynaTrace Server when a dynaTrace Agent matches multiple Agent Mappings. This help to avoid configuration issues, e.g. after copying a System Profile.
  • Our experience from the field showed that 512 MB of heap for the dynaTrace Collector is not enough for the typical deployment with 20+ Systems under Diagnosis per dynaTrace Collector. The default setting has been raised to 1024 MB which ensures that most deployments work smoothly out-of-the-box.
  • In previous releases, only relative paths could be configured to hold Sessions, temporary files and log files; they had to be located inside the directory the dynaTrace Server was installed. Albeit this could be worked around, it is now easier by specifying absolute paths/directories.
  • Support for Microsoft SQL Server and the dynaTrace Repository has been extended; the dynaTrace Repository now works with deployments where multiple SQL Server instances are running.
  • The dynaTrace Server's REST interface has been extended and is now capable of automating the reanalysis of a dynaTrace Session. It is typically required when dynaTrace is used for continuous integration because Business Transactions require the Session to be reanalyzed once.

Edition Updates

Licensing of .NET Systems under Diagnosis has been simplified. A bigger Microsoft Server Edition supersedes a smaller one, for example if you have dynaTrace licenses for Microsoft Server Datacenter Edition but connect .NET SUDs from Microsoft Server Enterprise or Standard Edition, they are accepted.

TrueSight Application Visibility: It is now possible to directly access a dynaTrace Session while it is being recorded. Recording a dynaTrace Session with a 10 minute interval as a workaround is not required anymore. Please note that continuous session recording plus rotation is still highly recommended. This ensures that sessions are small and maintainable, especially in production scenarios.

Resolved Issues

  • Connecting to the dynaTrace Server took several minutes with thousands of offline dynaTrace Sessions available on the dynaTrace Client. With this release, the dynaTrace Sessions are read in the background and the connection is established immediately.
  • After copy&pasting a Sensor Group, the associated API Breakdown Measure was missing (e.g. in API breakdowns) and had to be created manually.
  • Measures were created from scratch after renaming a Monitor. The new Measures had to be re-added to Charts, Business Transaction Mappings, etc. This is not necessary anymore.
  • Adding the Business Transaction Dashlet from the Cockpit to a new Dashboard misleadingly added it to the currently opened Dashboard.
  • Calling server.getName() on an Incident in the Plugin SDK always returned "dynaTrace Server" instead of the configured server name.

Resolved Issues specific to .NET:

Known Problems

While our team is striving to provide a world-class customer experience, it is not always in our hands to resolve all issues e.g. due to third party constraints or known bugs in other technologies. This section provides a heads-up on common problems you might run into. Check out the Knowledge Base for workarounds and many hints.

Additional Information

Software and Hardware Requirements

dynaTrace Agent

  • Windows 32/64, Linux 32/64, Solaris SPARC 32/64, Solaris x86/x64, AIX 32/64 Power 5 Architecture, z/OS 31/64, z/Linux 31/64, Linux IA64, HP-UX PARISC, HP-UX IA64
  • Sun JVM, IBM JVM, JRockit JVM, HP JVM
  • 10MB disk space

dynaTrace Server

  • Windows 2000/XP/2003 Server/2008 Server/Vista, Linux, AIX, Solaris SPARC, Solaris x86/64
    • Windows and Linux installers/packages contain a private 32bit/64bit JRE
    • AIX requires IBM JDK 1.6 SR2+
    • Solaris SPARC and Solaris x86/64 require J2SE 6.0
  • 1GB disk space, 4GB memory

See the Deployment Guide for dynaTrace 3.2 for more specific hardware recommendations.

dynaTrace Collector

  • Windows 2000/XP/2003 Server/2008 Server/Vista, Linux, Solaris SPARC, Solaris x86/64, AIX Power 5, z/OS, z/Linux, HP-UX
  • Sun JVM 1.6+, IBM JVM 1.6 SR2+, HP JVM 1.6+
  • 1GB disk space, 128MB memory

See the Deployment Guide for dynaTrace 3.2 for more specific hardware recommendations.

dynaTrace Client

  • Windows 2000/XP/2003 Server/2008 Server/Vista, SUSE/RedHat Linux with GTK
  • 100MB disk space
  • 1GB memory

See the Deployment Guide for dynaTrace 3.2 for more specific hardware recommendations.

dynaTrace Repository

  • Relational database of choice
    • embedded database (default: Apache Derby)
    • Oracle 10g/11g
    • Microsoft SQL Server 2000/2005/2008
    • IBM DB2 Version 9
    • PostgreSQL 8

To determine the disk space requirements for the dynaTrace Repository upfront you can should calculate 15GB per 1000 persistent measures (of all System Profiles within the dynaTrace Repository).

You can find more details in https://community.dynatrace.com/community/display/DOCDT32/Deployment+Guide+for+dynaTrace+3.2#DeploymentGuidefordynaTrace3.2-RDBMS.

Supported Java Virtual Machines

 

Windows
x86/x64
32 bit

Windows
x64
64 bit*

Linux
x86/x64
32 bit

Linux
x64
64 bit

Linux
IA64
64 bit

Solaris 8+ SPARC
32/64
32 bit

Solaris 8+ SPARC
64
64 bit

Solaris 10
x86/x64
32 bit

Solaris 10
x64
64 bit

AIX 5.2+
P32/P64
32 bit

AIX 5.2+
P64
64 bit

HP-UX
IA64
32 bit

HP-UX
IA64
64 bit

HP-UX
PA-RISC2.0
32 bit

HP-UX
PA-RISC2.0
64 bit

z/Linux
z31/z64
31 bit

z/Linux
z64
64 bit

z/OS
z31/z64
31 bit

z/OS
z64
64 bit

Sun JVM 6.0

(tick)

(tick)

(tick)

(tick)

n.a.

(tick)

(tick)

(tick)

(tick)

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

Sun JVM 5.0

(tick)

(tick)

(tick)

(tick)

n.a.

(tick)

(tick)

(tick)

(tick)

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

Sun JVM 1.4.2

(tick)

n.a.

(tick)

n.a.

(tick)

(tick)

(tick)

(tick)

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

IBM JVM 6.0

n.a.

n.a.

(tick)

(tick)

n.a.

n.a.

n.a.

n.a.

n.a.

(tick)

(tick)

n.a.

n.a.

n.a.

n.a.

(tick)

(tick)

(tick)

(tick)

IBM JVM 5.0

(tick)

(tick)

(tick)

(tick)

n.a.

n.a.

n.a.

n.a.

n.a.

(tick)

(tick)

n.a.

n.a.

n.a.

n.a.

(tick)

(tick)

(tick)

(tick)

IBM JVM 1.4.2

(tick)

(tick)

(tick)

(tick)

n.a.

n.a.

n.a.

n.a.

n.a.

(tick)

(tick)

n.a.

n.a.

n.a.

n.a.

(tick)

(tick)

(tick)

(tick)

Oracle JRockit 6.0

(tick)

(tick)

(tick)

(tick)

(tick)

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

Oracle JRockit 5.0

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

Oracle JRockit 1.4.2

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

HP JVM 6.0

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

(tick)

(tick)

(tick)

(tick)

n.a.

n.a.

n.a.

n.a.

HP JVM 5.0

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

(tick)

(tick)

(tick)

(tick)

n.a.

n.a.

n.a.

n.a.

HP JVM 1.4.2

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

n.a.

(tick)

(tick)

(tick)

(tick)

n.a.

n.a.

n.a.

n.a.

n.a. = not applicable
*Itanium is not supported

Supported .NET Platforms*

 

Windows
x86/x64
32 bit

Windows
x64
64 bit

.NET 1.1

(tick)

n.a.

.NET 2.0

(tick)

(tick)

.NET 3.0

(tick)

(tick)

.NET 3.5

(tick)

(tick)

n.a. = not applicable
*Itanium is not supported

Supported Application Environments

Application Servers

ESBs and SOA

Runtimes

DBs

Operating Systems(Platforms)

C IBM WebSphere 5.1/6/6.1/7
C Oracle WebLogic 8.1(SP3/SP4/SP5/SP6)/
C Oracle WebLogic 9/9.1/9.2/10/11g
C Oracle Application Server 9i, 10g   
C JBoss 3/4/5
C Apache Tomcat 5/6
C Borland Enterprise Server 6.5
C Borland Application Server 6.7
C Sun Java Web Server 6.1
C Sun Java Application Server 8.2/9/9.1
C Microsoft IIS/ASP.NET 6/7
C Microsoft SharePoint
S MS COM+ Component Services for .NET
S Adobe LiveCycle
S SpringSource dm Server
S Fujitsu Interstage 9
S SAP NetWeaver 2004/2007
S ATG Dynamo 6.3.0
S CoreMedia
S ServletExec 4.1
S JRun 4
S ColdFusion 6.1/7
S Proprietary Java/.NET Servers

C Oracle Service Bus
C Fuse ESB
S Oracle SOA Suite

Sun JVM
IBM JVM 
Oracle JRockit JVM
BEA/Oracle RT 2.0
HP JVM
Microsoft .NET CLR

C IBM DB2 8/9
C Oracle DB 9i/10g/11g
C MS SQL Server 2000/ 2003/2005/2008
C PostgreSQL
C Java DB
C Generic JDBC drivers and
ADO.NET data providers
(e.g. ODP.NET)

C MS Windows XP/
2000/ 2003 Server/
2008 Server/
Windows Vista
C Suse Linux 8+
C RedHat Linux 4+
C AIX 5.2+
C Solaris SPARC 8+
C Solaris 10+ x86/x64
C IBM z/OS 390
C z/Linux SLES 8 SP4
C HP-UX PA-RISC2.0
C HP-UX IA64
C Linux IA64

Web Service Stacks

Remoting

Messaging

Frameworks

C IBM WebSphere 5.1/6/6.1/7
C Oracle WebLogic 8.1/9/9.1/9.2/10/11g
C .NET WebServices
C AXIS 1.4
C AXIS2 1.3
C Hessian 2.1/3/3.1/3.2
C Oracle WebServices
C JAX WebServices
C Codehaus XFire 1.2
C Apache HttpClient 1
S Apache CXF 2.2
S SAP Netweaver
S WebMethods Glue

C RMI / IIOP
C RMI / JRMP
C RMI / T3
C .NET Remoting
C ORMI
C JBoss Remoting
C WCF
C HTTP Remoting
C XML-RPC.NET

C JMS
C IBM WebSphere MQ 5.1/6/6.1
C Apache Active MQ 4/4.1
C Microsoft MQ 3.0
S TIBCO Rendezvous

C Hibernate
C Struts 1.x/2.x(to be tested) 
C AWT/Swing/RCP/WPF/WinForms
S Spring
S BlazeDS
S Oracle Coherence 
C Applets
others

Support level: C = certified, S = supported, L = limited support

Please see the Known Systems section of the Community Portal for details.

Supported Browsers for Web Start

Browser

Version

Microsoft Internet Explorer

6+

Mozilla Firefox

3+

Edition Feature Comparison

 

Development

Test Center
Standard

Test Center

Production

Transaction Tracing (PurePath Technology)

 

 

 

 

Continuous (Always On/24x7) Tracing of All Individual Transactions

(tick)

(tick)

(tick)

(tick)

Tracing at Code-level Capturing Contextual Data

(tick)

(warning)

(tick)

(tick)

Tracing Across Multiple Tiers/Servers

(tick)

(tick)

(tick)

(tick)

Tracing Across heterogeneous Technologies

(tick)

(tick)

(tick)

(tick)

Tracing with Low Overhead & Small Footprint

(tick)

(tick)

(tick)

(tick)

 

 

 

 

 

Diagnostics (Java/.NET Deep-Dive)

 

 

 

 

Session Capturing

1h/100MB

RAM limit

RAM limit

RAM limit

Real-time diagnosis

(tick)

(tick)

(tick)

(tick)

Offline diagnosis

(tick)

(tick)

(tick)

(tick)

Web/Web Services Sensors

(tick)

(tick)

(tick)

(tick)

Tagged Web/Web Services request tracing

(tick)

(tick)

(tick)

(tick)

Tracing across Java thread boundaries (Thread/Executor Tagging Sensors)

(tick)

(tick)

(tick)

(tick)

Database Sensors (JDBC, ADO.NET)

(tick)

(tick)

(tick)

(tick)

Exception/Logging Sensors and Analyzers

(tick)

(tick)

(tick)

(tick)

Remoting Tagging and Performance Sensors (RMI, T3, WCF, WS, HTTP, ...)

(tick)

(tick)

(tick)

(tick)

Core Messaging Tagging and Performance Sensors (MSMQ, JMS)

(tick)

(tick)

(tick)

(tick)

Advanced Messaging (Tibco Rendezvous, Custom Entry Points, ...)

(tick)

(error)

(tick)

(tick)

Basic Memory Diagnostics (Full Memory Dumps, Suspension Diag)

(tick)

Add-on

(tick)

(tick)

Advanced Memory Diagnostics (Selective Memory Dumps)

(tick)

(error)

(tick)

(tick)

Component Sensors (EJBs, .NET Serviced Components)

(tick)

(tick)

(tick)

(tick)

Thread/Synchronization Sensors

(tick)

(error)

(tick)

(tick)

Directory/JNDI Sensors and Analyzers

(tick)

(error)

(tick)

(tick)

Custom Sensors and Custom KSPs

(tick)

(error)

(tick)

(tick)

Diffing/Regression Reports (sessions/views/automated)

(tick)

(error)

(tick)

(tick)

UML sequence diagrams

(tick)

(tick)

(tick)

(tick)

 

 

 

 

 

Monitoring

 

 

 

 

System Monitoring (Agent: PMI, JMX, Perfmon, JVM, CLR)

(tick)

(tick)

(tick)

(tick)

System Monitoring (Collector: OSGI-Plugin)

LAN

embedded

(tick)

(tick)

Pluggable Synthetic End-user Monitors, Actions/Notifications (scheduled)

(tick)

(tick)

(tick)

(tick)

Alerting on Incidents

(tick)

(tick)

(tick)

(tick)

Percentiles

(tick)

(tick)

(tick)

(tick)

Long Term Performance Charts

(tick)

(warning)

(tick)

(tick)

Business Transaction Mapping

(tick)

(error)

(tick)

(tick)

Application Dependency Mapping

(tick)

(error)

(tick)

(tick)

Enterprise Management System Integration and Automation

(tick)

(warning)

(tick)

(tick)

 

 

 

 

 

Development/Testing

 

 

 

 

Source-Code Viewing (Decompilers)

(tick)

(tick)

(tick)

(tick)

CodeLink IDE Integration

(tick)

(tick)

(tick)

(tick)

Build Systems Integration

(tick)

(error)

(tick)

(error)

Load Testing Integration

25VU

(tick)

(tick)

(tick)

 

 

 

 

 

Lifecycle / Dashboards

 

 

 

 

Customizable Dashboards

(tick)

(tick)

(tick)

(tick)

Reporting of dashboards

(tick)

(tick)

(tick)

(tick)

Dashboard Sharing

(tick)

(error)

(tick)

(tick)

 

 

 

 

 

Automation

 

 

 

 

Automation/Integration interfaces (Web-Services/Rest/JMX)

(tick)

integration only

(tick)

(tick)

Scheduled Memory Dumps

(tick)

(tick)
(Add-on)

(tick)

(tick)

 

 

 

 

 

Deployment

 

 

 

 

Remote Agents

(tick)

(tick)

(tick)

(tick)

Low Overhead

(tick)

(tick)

(tick)

(tick)

No Source-Code Required (Byte-code/IL-Code Instrumentation)

(tick)

(tick)

(tick)

(tick)

Auto Discovery of Application Components

(tick)

(tick)

(tick)

(tick)

Diagnose Remotely (Server access via WAN (through Client))

(tick)

(tick)

(tick)

(tick)

Collectors (Instrumentation)

LAN

embedded

(tick)

(tick)

Central Agent Deployment and Configuration

(tick)

(tick)

(tick)

(tick)

Cluster & Virtualization Support

(tick)

(tick)

(tick)

(tick)

Hot Sensor Configuration and Placement

(tick)

(tick)

(tick)

(tick)

Visual Class Browser and Sensor Placement Wizard

(tick)

(error)

(tick)

(tick)

Auto Sensor Placement Wizard

(tick)

(error)

(tick)

(tick)

Active system profiles

unl.

1

unl.

unl.

Multiple Sensor Configurations (per SysProfile)

unl.

1

unl.

unl.

Recovery& Watchdog (24x7 Support)

(tick)

(error)

(tick)

(tick)

WAN Support with Encryption/Compression (agent/collector/server/client)

(warning)

(warning)

(tick)

(tick)

Data-Protection/Scrambling/Omission

(error)

(error)

(tick)

(tick)

Authentication

(tick)

(error)

(tick)

(tick)

Roles and permission

license

1

unl.

unl.

User Groups and LDAP integration

(tick)

(error)

(tick)

(tick)

Repository (Embedded)

(tick)

(error)

(tick)

(tick)

Repository External (SQL,DB2,Orcl)

(tick)

(error)

(tick)

(tick)

Web-enabled Rich client (Webstart)

(tick)

(error)

(tick)

(tick)

Workstation Client with embedded dynaTrace Server and 2 Agents

(tick)

(error)

(error)

(error)

Free dynaTrace Viewer

(tick)

(tick)

(tick)

(tick)

 

 

 

 

 

Technologies

 

 

 

 

Java Capturing

(tick)

(tick)

(tick)

(tick)

.NET Capturing

(tick)

(tick)

(tick)

(tick)

Heterogenuous Applications

(tick)

(tick)

(tick)

(tick)

Unicode Support

(tick)

(tick)

(tick)

(tick)

 

 

 

 

 

Platforms

 

 

 

 

Agents/Collectors for Distributed Computing Environments

(tick)

(tick)
(Agents)

(tick)

(tick)

Agents/Collectors for Java on Mainframe (zOS/zLinux)

(tick)

(error)

(tick)

(tick)

Server for Windows, Linux, Solaris, AIX

(tick)

(tick)

(tick)

(tick)

Client for Windows, Linux, Mac OSX (experimental)

(tick)

(tick)

(tick)

(tick)

Legend
(tick) supported
(warning) partially supported
(error) not supported

  1. Anonymous (login to see details)

    Do I get the 3.5x MPS speedup automatically ore are there any hardware requirements associated with it?

    1. Anonymous (login to see details)

      Thanks for the comment -> updated.