Dynatrace dramatically improves the depth of application data accessible within Splunk. PurePath™ technology unlocks powerful insights by automatically injecting itself inside the application, with transaction level visibility into method arguments, query parameters, and even business context. Published events are pre-correlated end-to-end with a unique ID and streamed directly into Splunk. This rich data set is only available through our patented PurePath™ technology and eliminates the need to refine logging or manually correlate across service tiers. Automatically capture the business context across even your most complex applications and get visibility for every transaction down to the method level.
This new Splunk app leverages Dynatrace's unique brand of APM for visibility inside of applications and across every user interaction, tracing 100 percent of transactions in production environments with near zero overhead. In addition to performance monitoring and root cause analysis, both business transactions and user behavior can now be analyzed and correlated in real-time against any other machine data or structured business data source indexed by Splunk Enterprise.
Sample Use Cases
- User Experience Analytics: Understand who's impacted by performance or errors by analyzing real-time user sessions with external data sources like CRM and social media.
- Security & Fraud Prevention: Identify malicious behavior by combining real-time performance impacts with machine data from firewalls and security threats
- Pinpoint Root Cause: One-click access to deep application analysis and insight Getting Started
- Dynatrace Application Monitoring 5.5+ with enabled Business Transaction Export and Splunk 5 (or later) for Windows or Linux.
- The Splunk server must also have Java 6 (or later) installed.
- Maxmind and Google Maps Splunk Applications may be necessary for included "Visits on Map" dashboard
- python-lxml required for fetching Dashboard data
- Dashboard data input requires environment variables DTUSER and DTPASS to be populated with the username and password of a Dynatrace user with permission to access dashboards
Release Notes v2.2.3
- Updated Flume start script to fix Windows issue with flume.pid not being available
- Updated Dashboard script to utilize environment variables for Dynatrace username and password
Release Notes v2.2.2
- Incorrect upload, please disregard
Release Notes v2.2.1
- Changed the startup script for flume to check for an existing flume instance before starting a new one.
- Cleanup preformed on distributed package.
- Directories renamed in according with current Splunk app requirements.
Note, since the directory the application resides in has changed it is recommended that you delete the existing application directory ($SPLUNK_HOME/etc/apps/APM_dynatrace) otherwise the application will appear twice within the Splunk interface.
Release Notes v2.1
Version 2.1 changed the startup script for flume server and the data input scripts to python and removed the dependency on powershell/curl/xsltproc and bat/shell scripts
Release Notes v2.0
Version 2.0 has major changes in the OOB Dashboards which are populated with APM data from Compuware dynaTrace.
- Application at Glance : Gives you at glance view of the Applications, Visitors and Critical Transactions
- Visitors on a Map: Gives you a geographical view of your visitors, with the ability to zero on a single visit
- Key Analytic Metrics: Allows you to share analysis APM data for business analysis and effectiveness of your web/app properties
- Transaction +Activity Data and User Activity Data: Gives you a timeline view of your transactions, so you can understand at what time of the day certain transactions are heavily used or not.
The Splunk App also has a pivot data model to start with, which an be used to create models around User Activity, Visits and Transaction Health and leverage the Splunk platform for Analysis.
The Splunk App for Linux platform has a cleanup script to clean the log files once they have been ingested.
Release Notes v1.0.3
Fixed a packaging issue that may have prevented embedded Flume server from starting properly.