Update 5

2018-06-11

A new update for Dynatrace AppMon 2018 April has been released! This update contains critical fixes and improvements. Using a controlled installation , you can select which agents when to update, without migration!. Download here!

Known Issues

2018 April Update 5 contains a bug regarding Performance Warehouse authentication on SQL Server. When using Windows Authentication for SQL Server, it is advised to not install Update 5 but wait for Update 6 instead.

JLT-219069 Performance Warehouse: When the connection is configured to use SSO with Windows Authentication and a separate user is configured the Performance Warehouse cannot connect or store data anymore.

A workaround is to rollback to Update 4. Non-Windows users or users who are not using the Windows authentication are not affected.

Resolved Issues

This update contains all changes of public updates of previous versions released to this date.

7.1.5.1020 Resolved Issues

Most critical issues since the last public updates

All resolved issues

Correlation and Analysis

  • JLT-214263 - Add support for Async Webrequest response time for OneAgent paths.
  • JLT-217104 - Make Remoting data of Appmon Agents show up in Remoting dashlet
  • JLT-215382 - Unify the internal representation of .net method signature types for appmon and classic agents.
  • JLT-218087 - Show the sensorname that started a purepath in the purepath dashlet in debug mode.
  • JLT-215933 - Unify calculation of synctimes and waittimes for appmon and classic agents.

Server

  • JLT-218856 - Revert JLT-215379 to avoid interrupting direct OneAgent to Server connections
  • JLT-217563 - Sensor extensions with a higher order than custom sensor packs are not immediately applied to AppMon agent custom ruleset after sensor order change. Incomplete state remains until next ruleset cache rebuild.
  • JLT-217002 - Error during database analysis occurring due to missing query values
  • JLT-217875 - Potential NullPointerExceptions in server log during server start up.
  • JLT-216547 - Enable ExtendedRegexFinder by default
  • JLT-216180 - Infrastructure related views are slow and cause high CPU and memory usage on the server
  • JLT-215035 - Classbrowser shows duplicates for methods with primitive parameters for .NET agents when both Classic and AppMon agents have been in use in the same agent group.
  • JLT-218215 - Rare combinations of business transaction configurations and PurePath data cause business transaction analysis to fail. Affected PurePaths are ignored, dtserver may log an "UnsupportedOperationException".
  • JLT-215379 - Disabling the server setting "Allow Agent Connections to Dynatrace Server" has no effect for AppMon Agents.
  • JLT-218085 - IncidentRuleEngine doesn't react correctly to "clear session" in all cases.
  • JLT-215050 - Instrumentation rules created from information reported by the .NET AppMon agent do not work for Classic Agents when the method signature contains primitive data types.
  • JLT-218397 - Webrequest-Measures may produce incorrect matches if two or more Webrequest-Measures have the same URI or query string but different match types.
  • JLT-218395 - Hosts added during runtime trigger on default thresholds
  • JLT-217782 - Some host performance measures (e.g. Swap Used, Swap Free, ...) are missing in measure configuration dialog

Client

  • JLT-217637 - Saving table column preferences as default does not work
  • JLT-217834 - Measure configuration dialog: The list for application-based measure calculation restriction may contain duplicates.
  • JLT-209860 - Removal of business transactions used in incident rules do not cause SystemProfileIntegrityException any longer.
  • JLT-217630 - Multiple "Exception Summary" / "Database Summary" nodes below 1 instrumented method
  • JLT-217114 - The PWH configuration dialog had some quirks when enabling the SQL Server "Windows Authentication" feature

WebUI

  • JLT-215772 - User gets informed if both the tile specific session and the dashboard session (used as fallback) is not available.
  • JLT-218152 - Changes on a cloned Alert tile impact the original tile.
  • JLT-218326 - "AppMon Self-Monitoring - Measure health" shows no data for several tiles

Communication

  • JLT-217538 - The debug flags to disable JDBC normalization "optionTrimSQLStatementJava" and "debugEnableSqlNormalizationNative" only affected Classic or AppMon Agents respectively. Setting either one will now affect agents of both platforms.
  • JLT-218261 - SSO: IdP metadata files > 64 KB can not be sent from the client to the server

IIS

  • ONE-15244 - Add some logging in case of JSA injection problems for easier issue analysis.

.NET Agent

  • JLT-216897 - LoadTest Tags will be recognized correctly now.

Core

  • ONE-15390 - Crash of a monitored application may occur in case a single sub-path reaches the limit of 10.000 nodes.

Server Platform

  • JLT-216736 - Inconsistent behavior of REST API for alerts when accessing information of host incidents for users with restricted system profile permissions.
  • JLT-212136 - The timestamps logged in "AgentRegistration" messages upon connecting a new agent to the server were in non-UTC timezone(All logs are in UTC starting from 7.1 by default)

7.1.4.1022 Resolved Issues

Most critical issues since the last public updates

All resolved issues

WebUI

  • JLT-217280 - Clone button visible for web dashboards even without create dashboard permission.
  • JLT-217068 - Timeframe picker: properly set lower date limit of end date when changing start date.

Correlation and Analysis

  • JLT-213207 - Aggregate aggreagated nodes from appmon agents so the paths look more similar to paths of classic agents.
  • JLT-216345 - Ensure the transaction of a subpath is accessible after completion.
  • JLT-215131 - Remove custom external call attachments from Appmon Agents' nodes in case they have a child node.
  • JLT-217285 - Avoid failing to postprocess subpaths that only have a link node as an entry node.

Integration and Services

  • JLT-217598 - When the token is correct but disabled, the dynatrace server returns 403 instead of 401 and this wasn't handled correctly, leading to log spammin.

Collector

  • JLT-217279 - Increased the thread-count for sending keep-alive commands to agents to prevent piling up these events in case of collector->agent communication timeouts
  • JLT-217779 - Fix ensures that even 7.1.0 bootstrap agents are updated to the latest 7.1.4 version that provides bootstrapping features and fixes
  • JLT-217290 - Reduce Collector Memory Usage in high agent-count scenarios by shrinking AgentBuffer of control-channel.
  • JLT-217250 - Improved logging of connection problems in the HTTP based communication used by AppMon agent. We show more details about the root cause when the communication doesn't work as expected.

Agent

  • JLT-216268 - Workaround to a crash in a 3rd party Apache module (mod_novell_ag) when UEM is enabled.

Plugins

  • JLT-217317 - Update: Don't deliver plugins which are not in the installer

Client

  • JLT-213119 - Support Archive export from System Information dashlet gets canceled after opening a different dashboard
  • JLT-212110 - NPE when refreshing while connecting to or disconnecting from a server
  • JLT-216444 - Adapted hint text that disabling CPU time capturing only works for classic agents.
  • JLT-216326 - Improve message when users try to update when they should upgrade

Server

  • JLT-215687 - The server may hang rarely during shutdown.
  • JLT-217105 - Changing a JMX measure may deadlock the server when storing the system profile
  • JLT-217775 - Host in a custom hostgroup is getting triggered on the default hostgroup thresholds
  • JLT-215956 - The REST api does not show the instrumentation state for all agents.
  • JLT-218259 - Revert JLT-217255 (Oracle jdbc driver 12.2.0.1 introduced regression)
  • JLT-217240 - AppMon Agent is showing offline in Infrastructure overview, although agent is sending data.
  • JLT-216094 - Potential deadlock while multiple hosts connecting at once

UEM

  • JLT-217260 - Country names of 'East Timor' and/or 'Timor Leste' are now reported as 'Democratic Republic of Timor-Leste'
  • JLT-217168 - Correction of the spelling of some French regions

PWH

  • JLT-217255 - The new ojdbc8 version supports TLS v1.2 (amongst other changes)

IIS

  • ONE-15242 - Fix possible invalid pure paths when using IIS module insights.

JavaScript

  • ONE-15231 - Issue is that our angular module incorrectly uses HttpHeaders even if Headers is used. This is caused when using HttpClient in Angular 4 which can still use Headers resulting in an error. Fix is to use HttpHeaders first only if it's instrumented.

Communication

  • JLT-215042 - Connect timeout not considered for SSL connections, leading to long blocking waits when TCP packets are dropped.

Webserver Agent

  • JLT-217166 - The Webserver Agent bootstrapper does not translate the dtwsagent.ini file directive LogFilePath correctly into the options string for the AppMon Agent. The AppMon Agent then stores its log files in the directory above the intended one.

.NET Agent

  • JLT-212558 - Support WCF Singleton-Contracts

Server Platform

  • JLT-214375 - Java agent expects different sensor key for CTG sensor depending on agent platform and version.

7.1.3.1020 Resolved Issues

Most critical issues since the last public updates

All resolved issues

Server

  • JLT-173207 - Allow to update Language packs
  • JLT-210175 - JLT-210175 Error: "DuplicateBundleException has already been installed from" after update add-delete-add (no rollout) without server restarts
  • JLT-210940 - Reduce performance impact of measure export from AppMon to Dynatrace by reducing the object churn
  • JLT-211638 - The PurePaths created within the last one or two seconds before agent shutdown might be lost.
  • JLT-213401 - Frontend server incorrectly logs failed storage of measure references causing log spam. Improved logging behavior.
  • JLT-213787 - Provide more meaningful error messages in the AppMon -> Dynatrace metric export "Test Connection" button
  • JLT-214268 - Pointless "Rule X has changed" log output on server startup.
  • JLT-214914 - Prevent pointless stack traces in server log file
  • JLT-214943 - Optimized version of regular expression capture groups produced incorrect results in certain cases
  • JLT-215366 - REST Update upload fails due to finished=true while still success=false (docker containers)
  • JLT-216186 - External calls within a PurePath (e.g., an invocation of a web resource not monitored by AppMon) are not detected anymore.
  • JLT-216619 - Deleting a system profile while JMX export is enabled causes an exception in the JMX management agent.
  • JLT-216898 - External calls within a PurePath (e.g., web requests to resources which are not monitored by AppMon) are not detected for some edge cases.
  • JLT-217012 - Debug logging for host incident calculation

Plugins

  • JLT-208505 - Backend server log spam: "WARNING [MonitorMetric] Invalid default rate specified:none" during update rollout
  • JLT-212673 - SnmpMonitor Plugin broken (cannot move to OSGi "resolved" state) by update add (no rollout) without server restarts
  • JLT-217163 - A mostly unwanted version of the Generic execution plugin is shipped with updates

Client

  • JLT-212424 - Improved logging for invalid dashlet refreshes.
  • JLT-212753 - Multiple warning dialogs are shown when pasting a Sensor Group
  • JLT-213368 - Adapted wrong AppMon spellings
  • JLT-213403 - Dashlet data does not get updated when switching between global and session specific data source.
  • JLT-213404 - Fixed drilldown issue for Infrastructure Overview.
  • JLT-213423 - Multiple breadcrumb items are created after opening the System Information view from the Help-menu.
  • JLT-213424 - The remaining dashboards tab is not shown.
  • JLT-213439 - Dashboard infobar shows wrong data source information and source locked indicator.
  • JLT-213578 - When using the old cockpit as sidebar the new Dashboards Dashlet would be shown under the offline node.
  • JLT-214370 - Externalization issue for new implemented Dashlets.
  • JLT-215556 - Implemented threadding sensor settings to avoid invalid threadding sensor placements.
  • JLT-215941 - Prepend the proposed "Web UI URI" with an https:// as a more sensible default.
  • JLT-216344 - An installed language pack leads to incomplete text when switching the agent platform of individual Java or .NET agents.
  • JLT-216443 - Selecting "System Profile Data Import" Task throws a NullPointerException
  • JLT-216793 - possible NPE while searching for cross-product-PurePaths

Correlation and Analysis

  • JLT-212928 - Fix race condition when handling unresolved method references from OneAgents
  • JLT-213596 - Avoid not correlating SubPaths of OneAgents that got sent just before an agent shutdown.
  • JLT-216338 - Get rid of logspam when paths run into the 1 hour age limit.
  • JLT-216339 - A race condition when handling multiple concurrent circular reference detection/breaking attempts in conjunction with custom tagging leads to PurePaths not being removed from memory and subsequent necessity to restart server.

Java Agent

  • JLT-214837 - PurePath percentage feature is broken when using sensor "Java Web Requests"
  • JLT-216038 - Adding support for capturing HTTP headers on Mule ESB 3.8.1 and 3.9.0

Server Platform

  • JLT-214839 - Avoid unnecessary resends of appmon agent messages that can lead warnings on the server in certain corner cases (full gcs, network hickups,...)
  • JLT-215746 - Updated http communication library to avoid unnecessary message resends.

JavaScript Agent

  • JLT-215946 - custom headers field is set as an empty object in jsagent's XMLHttpRequest wrapper, potentially breaking customer code that may be expecting otherwise
  • JLT-216286 - disables sendBeacon usage when lzw encoding is enabled to prevent potential blocked beacons which are missing omitted Content-type header
  • JLT-216294 - No possibility to limit referrer length in beacon query

UEM

  • JLT-216242 - Improve logging for missing "UEM-compatible AgentResource" "Migration required"
  • JLT-216437 - Updated oneagent-uem-databases to version 1.0.12

Mainframe

  • JLT-216446 - Tagging for CICS/IMS ADK results in uncorrelated paths.

JavaScript

  • ONE-13291 - Introduces support for Angular 5

7.1.2.1034 Resolved Issues

Most critical issues since the last public updates

Mainframe

  • JLT-212861 - Purepaths were timing out, and the server was being stressed.
    • Impact: Pure paths were timing out
    • Cause: Events were being dropped, particularly EndPath events. This meant that the server never closed out the purepaths that contained the dropped events. This caused timeouts, and a backup in the server's purepath buffer/cache.
    • Solution: When the zRemoteAgent sees this situation, he will generate the missing EndPath event.

Server

  • JLT-213316 - Test Automation: error message appears when clicking on external test execution in Test Results dashlet.
    • Impact: It is not possible to view external test execution measures values and related chart with corridor.
    • Cause: Not supported negative values of external test execution measures.
    • Solution: Added support for negative values.

All resolved issues

Client

  • JLT-214256 - Creating a Database measure from the PP dashlet suggests the connection pool name as SQL statement instead of the actual query
  • JLT-215262 - Updating and restarting the client just after first connect to server can lead to loss of connection settings.
  • JLT-214532 - Incident drill down and Incident notfication emails sometimes shows empty incident overview.
  • JLT-214826 - Provide compatibility in Web Services
  • JLT-210509 - The "Save as..." dashboard menu entry would sometimes be disabled even though it should actually be enabled.
  • JLT-212243 - Mac client freezes when trying to browse JMX metrics in fullscreen mode.
  • JLT-214378 - Data Export Wizard cannot be opened in Webstart Client
  • JLT-216076 - Introduced patent section to the about dialog

PWH

  • JLT-213806 - Truncate measure name at 500 characters.
  • JLT-213247 - Wrong database in Performance Warehouse configuration dialog.
  • JLT-213784 - SQL exception when deleting a BT.
  • JLT-214238 - An internal error (value already present) stops writing dynamic measures into the performance warehouse.
  • JLT-214941 - Improved runtime of performance warehouse migration.

UEM

  • JLT-212435 - Byte allocation in serialization of session was incorrect
  • JLT-216188 - Updated the UEM Databases
  • JLT-209250 - Updated GeoTools to version 19.0
  • JLT-209881 - Unlinked web requests now contain a step number
  • JLT-215007 - fix NullPointerException
  • JLT-199969 - Added new names for Cabo Verde (Cape Verde) and St Kitts and Nevis (Saint Kitts and Nevis)

Server

  • JLT-213803 - Editing an incident downtime may cause an exception when storing system profile afterward
  • JLT-196793 - Server reports with charts will not fail completely with STIX fonts issue on RHEL anymore
  • JLT-213678 - Log levels for Plugins aren't always applied properly
  • JLT-214926 - Self-monitoring Agent raises severe incidents regarding GC overhead even though the AppMon Server is healthy
  • JLT-197200 - Server update installation: free disk space check relies on session directory, but should check server install
  • JLT-213316 - Test Automation: error message appears when clicking on external test execution in Test Results dashlet.
  • JLT-210441 - Incident "PureLytics skipped data because session was not found" is created when PureLytics still references session which was deleted by session storage cleanp (e.g. disk or storage limit reached, empty session).
  • JLT-215648 - Limit number of retained CAS UEM files to prevent slowdown of the Backend Server
  • JLT-211805 - Agentres files which are used for the controlled JS rollout should not be deleted automatically
  • JLT-214154 - Exceptions thrown in user plugin code are incorrectly reported as exceptions thrown in dtserver/collector code
  • JLT-214153 - Host-monitoring incidents cannot be deleted via System Profiles they're attributed to but only directly via "Infrastructure" System Profile.
  • JLT-215043 - Disabling optimized regex engine
  • JLT-213024 - Transaction Flow might show a webservice call as external call despite the server side being instrumented.
  • JLT-215950 - Incident rule with multiple mail actions only uses first one.
  • JLT-212642 - Encoding issue in "Open in browser" links
  • JLT-213137 - Invalid configured categorization tags are now replaced by the default configuration.
  • JLT-214061 - Infrastructure Alerts aren't suppressed by incident downtimes on custom System Profiles
  • JLT-211112 - Mitigation of IndexOutOfBoundsException and log message added.
  • JLT-212598 - Add visit anonymization rest api.
  • JLT-215267 - Server: java.lang.ArrayIndexOutOfBoundsException Fix an exception in the PurePath dashlet
  • JLT-214853 - Realtime analysis ignores matching database measure

Correlation and Analysis

  • JLT-215140 - Dropped PurePaths due to modification attempt of immutable connection-pool data.
  • JLT-213588 - Fix detection of external webservice calls
  • JLT-210589 - Correct API time calculations as well as API suppression for nested sub-paths.

JavaScript Agent

  • JLT-214848 - JSAgent incorrectly triggers onbeforeunload fakeout if elements with href attributes 'javascript:' are clicked, causing source actions to be lost.
  • JLT-215563 - In embedded IE browsers, referring to window results in an "Invalid calling object" error during the unload event, because the original copy may be destroyed if there are no references to it
  • JLT-211528 - embedded IE browser cannot invoke our setTimeout copy on destroyed window object during unload event. this fix ensures we use a copy of the window object to prevent this
  • JLT-212175 - Dojo module causes exceptions with undefined properties
  • JLT-211642 - JS agent doesn't capture sequential XHR calls from different ajax frameworks.
  • JLT-213572 - Dojo module causes exceptions on older IE browsers

Mainframe

  • JLT-216446 - Tagging for CICS/IMS ADK results in uncorrelated paths.
  • JLT-215339 - Addresses clock_gettime not found when using the dtzagentlauncher before 7.0.
  • JLT-212861 - Purepaths were timing out, and the server was being stressed.

Java

  • ONE-14202 - OneJavaAgent did not set stateCookie with block-information for affected application when a injection percentage was in place. Because of that, a configured percentage did not have the correct effect.

Collector

  • JLT-214042 - Wrong indentation in purepath nodes for JCICS API call

Integration and Services

  • JLT-213785 - The test connection button for the AppMon Metric Export feature wasn't working in certain set-ups due to the HTTP header containing a blank.
  • JLT-215436 - [AppMon Metrics Export] Fixed empty dimension keys for some AppMon BTs
  • JLT-215354 - [AppMon Metrics Export] Fixed that appmon host monitoring metrics didn't get the per-host splittings exported to dynatrace

Java Agent

  • JLT-216098 - WebSphere PMI: Improved detection of PerfMBean

In some rare cases, multiple instances of PerfMBeans are registered on multiple MBeanServers exisiting on single WebSphere instances, and only one of those PerfMBeans instances provides access to PMI data. Added checks to identify this instance.

WebUI

  • JLT-215682 - In the user action details view the name of the resources is now parsed correctly.
  • JLT-206048 - Number of orphaned web requests was not being shown
  • JLT-214815 - The WebUI can now handle large visit ids for drill downs into the visit details page.

zAgent

  • ONE-13460 - Fixed the problem of disabled IMS agents are not removed from the Agent Overview
  • ONE-13485 - If a CICS persistent mirror task is running, the CICS agent was unable to start a second path using that same task id, if the previous path in that task was corrupt. The new path is now started correctly, and the previous path ended as corrupt.

.NET Agent

  • JLT-206216 - Many log-lines show "Server cannot append header after HTTP headers have been sent" - Exceptions. Throttling the amount of those log entries.
  • JLT-204818 - Improved handling of long paths in DotNet http tagging sensor.

DB Agent

  • JLT-215475 - Database configuration dialog - argument not valid
  • JLT-213012 - Database agent validation error was reported as successfully validated connection

Session Storage

  • JLT-215151 - Handle problem during SessionStorage updates caused by preceding IO problem

Tests

  • JLT-213050 - Verify if there is any metric included before persisting test execution

Communication

  • JLT-215469 - Internal. Fixed tagging to get PPs from Frontend to Backend server automatically.

7.1.1.1005 Resolved Issues

This release contains all changes included in:

  • 7.0.18 and previous 7.0 updates.
  • 6.5.35 and previous 6.5 updates.
  • all updates released for 6.3 and all earlier versions.

This release together with its latest public update contains all changes of all public updates for versions earlier than 6.5.

Most critical issues since the last public updates

.NET Agent

  • JLT-215594 - 32 bit and 64 bit agent provide inconsistent OS properties for license check.

    • Impact: License exhausted although there are sufficient WOSIs in the license.
    • Cause: WOSIs not correctly detected due to inconsistent properties.
    • Solution: Use only consistent OS properties for license check. Agent restart is not required.
  • JLT-215483 - Different .net or IIS agent versions on one WOSI might consume multiple licenses.

    • Impact: License exhausted although there are sufficient WOSIs in the license.
    • Cause: Some properties used for license check can have different values than in previous agent versions.
    • Solution: Use only unchanged properties when different agent versions are connected. Agent restart is not required.

All resolved issues

.NET Agent

  • JLT-215594 - 32 bit and 64 bit agent provide inconsistent OS properties for license check.
  • JLT-215483 - Different .net or IIS agent versions on one WOSI might consume multiple licenses.