|Release Date||Release Name|
|January 15th, 2020||Get Dynatrace NAM 2019 SP3|
|October 3rd, 2019||Dynatrace NAM 2019 SP2|
|July 15th, 2019||Dynatrace NAM 2019 SP1|
|May 31st, 2019||Dynatrace NAM 2019 GA|
|May 17th, 2019||Dynatrace NAM 2019 Release Candidate|
|March 29th, 2019||Dynatrace NAM 2019 Beta Refresh|
|February 4th, 2019||Dynatrace NAM 2019 Beta|
To be authorized by the NAM Console, all users must have access to both the NAM Server public URL and NAM Console public URL. See Upgrade considerations.
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.
- Business hour definitions are used to control when alarms per given application or software service should be triggered and when not.
- 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.
- 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. You can also review and edit user and group access rights to reports, including quick preview if report can be accessed in the domain access permissions mode. Report explorer is currently in the beta stage but we will bring it to its full potential in upcoming service packs, effectively replacing Manage reports and Export/import screens.
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 userrights can access the DMI REST API with the assurance that Data Access Permissions are properly applied to their calls.
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.
- You can now import and export alert configuration using NAM Console.
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
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.
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.
- NAM does not support and does not plan to support the EDT protocol. The last supported by NAM version of Citrix is version 7.18 with EDT protocol disabled. Note that, starting with Citrix 7.16, the Enlightened Data Transport (EDT) is set to "preferred" by default.
Synthetic Classic (i.e., Gomez Synthetic) data is no longer imported, processed, reported, or alerted upon in NAM 2019. Please follow the process of upgrading this use case to a more powerful Dynatrace Synthetic.
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. We encourage to upgrade AppMon to Dynatrace RUM which offers more powerful alternative to this use case.
When you upgrade to NAM 2019, all AppMon/UEM and Synthetic Classic (Gomez) data is permanently removed, including database tables. If this applies to you, be sure to back up all of your data before continuing with the upgrade. Follow the Backing up AppMon/UEM and Synthetic Classic (Gomez) data instructions to render historical data in your Dynatrace NAM reports using CSV-data views introduced in NAM 2019.
Application Health Status (AHS) report is no longer rendered. It is deprecated in favor of the Health Dashboard.
The Dynatrace Mobile App will no longer connect to NAM 2019. Since NAM 2018 usability of NAM reports on mobile devices has been improved and alerts can be delivered to Slack with mobile applications for major platforms.
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. Use Data Export API or DMI Public REST API and new CSV data views to enable SNMP third-party metrics in reports with historical data.
The NAM Console will no longer manage DC RUM ADS servers. Use cases offered previously by ADS are addressed with Advanced Diagnostics On-Demand extension to NAM Server since NAM 2018.
The Twitter section type in NAM reports is now deprecated.
EndaceProbe is no longer supported.
As already announced, the end of support is planned for the following decodes:
As of September 30, 2019:
- The Tuxedo Jolt decode will no longer be supported as we shift this use case to a more powerful Dynatrace alternative, which covers Tuxedo Jolt as Java-based interface,
- The VoIP decode will no longer be supported. You may of course continue to use the decode beyond this date, without official support.
As of September 30, 2020:
We will end support for the IIOP decode as we shift this use case to a more powerful Dynatrace alternative, which covers IIOP protocols, most commonly driven by underlying Java-based applications.
As of September 30, 2020, we will end support for TCAM (a part of the Citrix monitoring decode) shifting system monitoring use cases to a more powerful Dynatrace alternative. The remaining feature of client name mapping to network connections behind Citrix server is rarely used these days in favor of NAM decodes providing user name recognition, as well as RUM agent used to monitor browser users on Citrix servers.
Upgrading and getting started with this release
See upgrade paths, compare it against your inventory, and download all required installation packages at their latest service pack release.
Information about changes the upgrade will bring to your deployment.
Information designed for customers who have their Dynatrace products at releases that support a direct upgrade to current release.
To achieve optimal and reliable performance from your NAM software, ensure that your system meets the specifications of platforms and cards described in Hardware Recommendations.