Dynatrace NAM 2019 Beta Release Notes

Release Date Release Name
May 17th, 2019 Dynatrace NAM 2019 Release Candidate
March 29th, 2019 Dynatrace NAM 2019 Beta Refresh
February 4th, 2019 Dynatrace NAM 2019 Beta

Participate in NAM 2019 Beta!

Would you like to have an early taste of what we have cooked up for 2019? We would love to hear your feedback and improve some of the new features. Get in touch with us to enroll in the Beta program. You’ll be able to communicate directly with our Product Management and Development teams that will guide you through the program.

Sign up for Beta!

Benefits

  • Get your hands on the latest innovations before anybody else.
  • Provide direct feedback to product management and engineering.
  • Drive innovation by suggesting changes and adaptations.

What's new in NAM 2019 Release Candidate

Set business hours per application or software service

Now you can set business hours per application or software service.

  • Use a third-party calendar application to upload one or more business hours calendars for your applications or software services, and then assign your applications or software services to one of the uploaded calendars.
  • The same calendars also provide visual cues on relevant time-series reports so you can see at a glance which events occurred during business hours for the application or software service being charted.

Report explorer

Manage reports and report users from a single dashboard through the new Report explorer, where you can analyze report performance, user report priorities, report links, favorites, and home pages.

Configure reporting-only NAM Server through the NAM Console

Starting with NAM 2019, you can use the NAM Console to put a NAM Server in reporting-only mode.

In this mode, the NAM Server does not receive and process data from NAM Probes. Instead, you point the reporting-only NAM Server to one or more other NAM Servers (which are not in reporting only mode). The other NAM Servers receive and process NAM Probe data. The reporting-only NAM Server receives DMI data from the other NAM Servers and then renders and serves reports based on the DMI data from the other NAM Servers.

API for site management

Alert management

You can now import and export alert configuration using NAM Console.

Other enhancements

We've improved the loss rate calculation.

Enhancing the power and flexibility of DMI

  • Easily duplicate (clone) existing DMI drilldown links, buttons, report tabs and links, and rich table entries to save you work and speed creation of new report definitions.
  • Share a link to a report’s current state, simplifying collaboration.
  • Smart time range auto-pinning temporarily prevents reports from updating the time range when linking between or within the same report; this is particularly helpful when using one-minute monitoring intervals.
  • A new PDF export engine improves report fidelity, more closely mirroring the original DMI report.
  • The NAM Server now supports CSV-driven data views. You can upload custom CSV files to generate reports. This will simplify custom analyses; examples include defining arbitrary application groupings and creating side-by-side historical snapshot comparisons.
  • Improved priority management for custom DMI report generation. Lightweight reports are given priority over reports demanding heavy – and lengthy – processing. Users can also be assigned report generation priorities (through the new Reporting user - high load user role) to ensure their reports – even the heavy ones – take precedence. Users without that role are bumped to the end of the report processing queue if they put a high load on report generation, and users with lightweight reporting demands go first.
  • Smart report reload on new data: DMI detects when you are interacting with a report or NAM menu and, if new data becomes available, it pauses report reload to prevent reload in the middle of your interaction.
  • Manage reports and report users from a single dashboard through the new Report explorer, where you can analyze report performance, user report priorities, report links, favorites, and home pages.

Create alerts with a click from the report

Now you can create an alert directly from a DMI report with a single drilldown click.

More flexible Dynatrace integration

We’ve enhanced the application mapping for integration with the Dynatrace. You can now choose to use NAM business unit names instead of the default server name, or to disable the automatic creation of applications in Dynatrace. For more information, see Unifying NAM and Dynatrace.

Configuration REST API

We’ve implemented a configuration REST API, initially supporting the configuration of software services, alerts, and sites to simplify and automate these tasks. For adding new services similar to existing services, the API supports exporting, modifying, importing, and validation of existing service and alert configuration.

Each API Token is now generated per user to reflect user roles and localizations when making API calls. This makes it possible for users with low or focused administrative rights to still access selected APIs (for example, the ability to manage alerts without gaining access to other APIs). Users with regular Reporting user rights can access the DMI REST API with the assurance that Data Access Permissions are properly applied to their calls.

NAM Console SSL certificate management

We've simplified the SSL certificate management process for the NAM Console. For more information, see How to configure SSL for NAM Console 2019.

New user role

A Reporting user - high load can run reports that put a high workload on the reporting system. For more information, see User roles and groups.

Other improvements

  • We have improved Admin console usability.
  • Calculations for baselines and trends have been improved.
  • You can now export and import alerts.

Security enhancements

We’ve implemented a new communication protocol for the NAM reporting cluster, improving security while removing dependencies on third-party libraries.

Data analysis

  • We’ve improved the performance of NAM analysis modules to deliver improved scalability and better resource utilization on high-performance machines.
  • TLS 1.3 signaling (similar information as for TLS 1.2 non-decrypted handshake reporting, though protocol differences mean certain volumetric measurements may differ).
  • SNMPv3 support
  • DTLS support
  • Monitoring DNS service running at the same UDP port and TCP port with one software service definition
  • Exclude services from auto-discovery algorithm

Currency updates

  • NAM has transitioned from Oracle JRE to OpenJDK 11. Oracle is ending commercial public updates for JRE.
  • SSL reporting now supports TLS 1.3 handshakes. Reports will be similar to existing reporting for TLS 1.2.
  • The NAM NetFlow Collector adds support for SNMPv3 for collecting interface statistics.
  • Communication within NAM Reporting cluster uses a new, more robust and secure implementation of the cluster communication protocol, no longer dependent on third-party libraries such as Hazelcast.
  • NAM Server SQL database can be automatically compressed, saving space occupied by NAM data.
  • The SAP decode now includes basic SAProuter support.

Limited support

  • Citrix support is limited to version 17 or earlier. NAM doesn't support and is not planned to support the EDT protocol, the default option in Citrix 2018.

Features no longer supported

  • Synthetic Classic (i.e., Gomez Synthetic) data is no longer imported, processed, reported, or alerted upon in NAM 2019.
  • Integration with AppMon PurePaths and UEM data is no longer available. PurePaths are no longer detected by the NAM Probe and identified in the NAM report. UEM data is no longer processed, reported, or alerted upon.
  • When you upgrade to NAM 2019, all AppMon/UEM and Synthetic Classic (Gomez) data is permanently removed, including database tables and processing data. If this applies to you, be sure to back up all of your data before continuing with the upgrade. For information, see Backing up AppMon/UEM and Synthetic Classic (Gomez) data.
  • Application Health Status (AHS) reports are no longer rendered. They are deprecated in favor of the Health Dashboard.
  • The Dynatrace Mobile App will no longer connect to NAM 2019.
  • Network link data SNMP third-party metrics are not available in trends. This feature is now deprecated and expected to be removed in the future.
  • The NAM Console will no longer manage DC RUM ADS servers.
  • The Twitter section type in NAM reports is now deprecated.
  • EndaceProbe is no longer supported.

What we would like to test

The highlights provide insight into new capabilities in NAM 2019. We encourage you to try them out, using NAM as you normally do, but with attention to enhancements of interest. We're here to help define test scenarios if you like. Gain an understanding of pertinent new features, see how they will help you with your performance monitoring requirements, and help us ensure a successful NAM 2019 launch.

We also look forward to your feedback on:

Alerts from reports

  • Choose a tile or table that displays a yellow or red status and click to create an alert. Verify that an alert is generated next time the condition occurs.

Reporting

  • If you are using 1-minute monitoring intervals, navigate through typical workflows to verify that the contents are not refreshed each minute as you investigate a problem. Is the timeframe you are viewing clear to you?
  • Test report prioritization by allowing multiple users to run reports simultaneously; be sure to include a report that is processing-heavy. Do short reports still run quickly? Experiment with users assigned the new Reporting user - high load user role to verify that their reports run with priority.
  • Share links to reports with others on your team. Is the report state maintained for a sufficient period of time?
  • If you create your own DMI reports, try editing an existing report to add or duplicate drilldown links, buttons, report tabs and links, and rich table entries.
  • Choose some frequently-used reports to test the PDF export; verify the resulting report formatting.
  • Please provide feedback on the user interface and capabilities of the new Report explorer.

Configuration automation

  • If you're interested in automating NAM configuration tasks, get in touch with us and share your expectations and inquiries. The Dynatrace NAM Product Management will be happy to give you a short presentation on NAM Configuration REST API and guide you in its application.

Upgrade

  • Provide feedback on the cluster upgrade process as well as on any perceived changes in processing speed.

Performance

  • Provide feedback on perceived performance improvements.

TLS 1.3

  • Using TLS 1.3 traffic, provide feedback on the TLS handshaking reports.

NetFlow Collector and SNMPv3

  • If you have SNMPv3 and are using the NAM NetFlow Collector, please test that this works in your environment.

Prerequisites

  • You can allocate time and resources for NAM testing.
  • You have a minimum of one Server, one Console, and one Probe that can be used for beta testing. See Supported OS and SQL versions
    • one system with RHEL for NAM probe installation
    • one system with Windows for NAM Server and NAM Console installation
  • You can direct meaningful traffic to the test environment.
  • You will be able to work with us via email, Zoom, Skype, or WebEx.

Known Issues

Applies to : NAM 2019 release candidate

Solution : To be fixed in NAM 2019 GA

Licensing

You are automatically granted a license for Beta releases. When you sign up for Beta testing, you will receive a Beta license and a link to obtain the Beta release software.