April 2017 Summaries

Users can now easily check the installed version of OneAgent on a monitored host without entering edit mode or navigating through the environment's Deployment status page. To find this information, users should select "Hosts" from the navigation menu, choose the specific host they are interested in, and click on the "Properties and tags" link on the Host page, which displays the host's properties, including the OneAgent version.

The text outlines updates and enhancements for Dynatrace OneAgent, covering a range of platforms and technologies such as Java, .NET, Node.js, and mobile environments like Android and iOS. Key improvements include support for Mongo Async drivers, Redis, and Nginx Plus, as well as enhanced Docker integration with version 1.13.1, enabling better port visibility within containers. It highlights the addition of user tagging capabilities in Android and iOS through Dynatrace ADK calls, facilitating user identification across apps. Additional updates mention improved multidex instrumentation for OkHttp 3, cost control through session sampling, and refinements in the handling of OneAgent traffic during network disruptions. Security enhancements feature a Private Security Gateway that supports multi-tenant operations and improved diagnostic logging for better system analysis.

Dynatrace employs its own performance monitoring solutions internally to ensure their efficacy and address potential improvements firsthand, a practice they refer to as "drinking their own Champagne." During a visit to the engineering lab in Linz, Austria, an insightful demonstration by Stefan Gusenbauer, the Development Lead, illustrated how Dynatrace is integrated into their Continuous Test Environment to provide swift feedback on performance, scalability, and architectural regressions. By capturing detailed data from automated test executions, Dynatrace enables easy identification and analysis of problematic test runs and server-side issues, such as the architectural regression revealed through a series of asynchronous calls in the persistence layer. This approach not only verifies the functionality of Dynatrace's solutions but also enhances the efficiency of problem triage and feedback loops, ultimately benefiting both the company and its customers.

Dynatrace has released a new feature for mobile user session analysis, enhancing the ability to track and analyze user journeys across digital platforms, including mobile web and native apps, which is crucial for businesses focusing on mobile-first strategies. This tool allows businesses to examine individual user sessions, providing insights into user actions and device-related information, thereby facilitating a comprehensive view of user interactions across web and mobile channels. Users can filter sessions by specific attributes such as device type or operating system, and even focus on individual users to gain detailed insights. Additionally, the integration of session crash analysis provides a sequence of events leading to any crashes, enabling swift resolution with access to code-level details. With this addition, Dynatrace's mobile monitoring is fully integrated with its real user monitoring system, offering robust, seamless insights at standard pricing.

Dynatrace enables the automatic detection and naming of server-side services by leveraging application deployment properties, while also offering customizable service naming rules to better reflect users' service landscapes. Users can enhance and personalize service names by adding metadata or specific properties using a customizable format that includes static text and optional placeholders. These rules can be tailored to apply to specific process groups, technologies, or service types, and conditions can be added to refine applicability further. The service naming rules allow for the inclusion of properties and metadata from process and service names, and even support the use of regex for extracting portions of detected names. This functionality not only enhances naming conventions but also aids in organizing and categorizing services intuitively, while built-in rules describe default behaviors but do not allow for configuration.