Update 11

2018-08-29

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! The installation of updates containing critical fixes can prevent monitored application impact or monitoring data loss and therefore is strongly recommended for all users. Download here!

Resolved Issues

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

7.1.11.1011 Resolved Issues

Most critical issues since the last public updates

All resolved issues

Client

  • JLT-222795 - Client dropdowns would not open on certain multi-monitor setups on Linux.
  • JLT-222867 - For some incident actions the start/end trigger behavior is not modifiable.
  • JLT-222635 - Hover popups in Transaction Flow can not be expanded on some linux systems.
  • JLT-222866 - Sorting by column "Status" in Agent Overview does not work.
  • JLT-222757 - Possible NPE when closing Client Settings.

Server

  • JLT-223083 - Created an optimized data structure to reduce cpu overhead when iterating discarded sub paths
  • JLT-221445 - Exported Sessions didn't include host metrics
  • JLT-222597 - [Dynatrace Integration] prevent logspam when appmon server has connectivity issues with dynatrace cluster.
  • JLT-222468 - Added debug logs for path completion checks / agent distribution for correlation engine
  • JLT-221747 - Testability improvement.
  • JLT-221819 - Use individual correlation queue saturation to monitor correlation engine health
  • JLT-224039 - Still used agent resources may be deleted erroneously which leads to a FileNotFoundException (No agent resource bundle for version ... found)
  • JLT-221635 - Added debug logging for distributed purepath search
  • JLT-222508 - Still used agent resources may be deleted erroneously which leads to a FileNotFoundException (No agent resource bundle for version ... found)
  • JLT-223147 - Server side report of License Overview doesn't work due to unresolved dependencies.

Correlation and Analysis

  • JLT-222280 - Only check for linkable sub-paths as long as guaranteed link times have not expired, thereby reducing CPU pressure as well as access to link buffer (synchronization point). This results in increased throughput as well as reduce memory pressure by earlier completing PurePaths in some cases.
  • JLT-221818 - Introduce individual correlation queue saturation measures for improved health monitoring, more effective correlation engine problem analysis.
  • JLT-223036 - Solve a potential visibility problem while discarding of purepaths in the correlation engine.

PWH

  • JLT-216205 - Prevent second appmon server with identical id from connecting to same performance warehouse.
  • JLT-223148 - Improvement of synchronization between backend and frontend server in case of renaming a system profile. The agent source (agent name and host) cache on front end server will be cleared in this case and repopulated.
  • JLT-208510 - Synchronization of SourceGroupHandler optimized to avoid race conditions. The SourceGroupHandler maps the agent name and agent host to numeric ids in Performance Warehouse.

JavaScript Agent

  • JLT-204603 - Error "Can't execute code from a freed script" occurs when the UEM JavaScript Agent's Perceived Render Time plugin is enabled, and IFRAME's are dynamically removed from the web page.

7.1.10.1011 Resolved Issues

Most critical issues since the last public updates

PHP Agent

  • JLT-221694 - After the upgrade from 6.5 to 7.1 an apache segmentation fault occur.
    • Impact: Causes the PHP agent not to crash
    • Cause: "configure" pointer set to invalid value.
    • Solution: Transform invalid "-1" pointer value to NULL.

All resolved issues

Server

  • JLT-215542 - ConcurrentModificationException in MeasureSubscription
  • JLT-222781 - SSO: Log incoming authentication and logout responses if the log level is set to "FINE"
  • JLT-222254 - Wrong labels for chart axis in report of License Overview dashlet.
  • JLT-218941 - Prohibit importing of system profiles of newer server versions
  • JLT-222475 - Confirming multiple incidents may modify end date of already closed incidents.
  • JLT-222306 - Remaining agent hours value too high in report of License Overview dashlet.

Integration and Services

  • JLT-221867 - Empty splitting names were provided by dynatrace integration under some rare circumstances.

Correlation and Analysis

  • JLT-212939 - Increase responsiveness of memory manager by treating memory management commands with high priority.
  • JLT-220252 - Reduce memory/CPU pressure by blocking transaction IDs when transactions run into the timeout or when they exceed the node limit or max nesting level.

.NET Agent

  • JLT-221884 - Prevent WCF Sensor from throwing exceptions from its Extension

Collector

  • JLT-222038 - added collector flags to allow for disabling support for http/ssl tunnelling on the agent listen port
  • JLT-222372 - Throttle java.security.cert.CertificateExpiredException log messages

Server Platform

  • JLT-221857 - Bootstrap logs are not included in Support Archive when agent sends an extended name, but bootstrap agent uses the simple configured name in the log file name.

Common

  • ONE-14855 - Update onagent-configuration

Communication

  • JLT-217338 - Fixed a rare NPE in communication module

PHP Agent

  • JLT-221694 - The direct reason is that "configure" pointer is set "-1" what makes the offset address to be outside the segment.

WebUI

  • JLT-220725 - Cyrillic letters are displayed in incorrect font.
  • JLT-207130 - "Other" series for pie charts shows "count" as unit (example "4.45count").

Dashboard

  • JLT-222225 - Agent Overview dashlet setting to show offline agents is ignored in server-side reports.

7.1.9.1013 Resolved Issues

Most critical issues since the last public updates

All resolved issues

Sensors

  • JLT-220604 - Enable Netty sensor for AppMon agents.
  • JLT-214126 - Erroneous quotes in log messages can cause IllegalArgumentException.

WebUI

  • JLT-220275 - When using the traffic light chart with focus on the last value and a custom timeframe (with start- and end-date) a message "No Threshold defined" was shown, allthoug there were some defined.

Server

  • JLT-221440 - SSO SAMLResponse message from IdP is rejected and login fails because InResponseTo attribute is missing
  • JLT-220150 - NumberFormatException when mapping OneAgent to AppMon version
  • JLT-221746 - Prevent log spam: "Got invalid value '-1.0' for measurement reference ..."
  • JLT-220782 - Unnecessary warnings when creating AppMon agent ruleset in case sensors irrelevant for the ruleset are activated in the system profile.
  • JLT-218298 - Legacy OneAgent version cannot be mapped to an AppMon version
  • JLT-219223 - CPU Samples for .net processes are missing thread names when using the AppMon agent
  • JLT-221796 - Added logs for on-demand analyzers runs executed on backend server.
  • JLT-221783 - Include sso.config.xml and idp.xml files in support archive (server configuration)

UEM

  • JLT-220493 - Turned off unnecessary UEM config validation for AppMon agent to improve performance.
  • JLT-218167 - Web Requests occurring before a loading action were getting incorrectly linked to that loading action.
  • JLT-221082 - NullPointerException could lead to dropped user actions.

Correlation and Analysis

  • JLT-221461 - Backend-Server: Circular sub-path references linked solely with dynaTrace links cause NullPointerExceptions resulting in performance problems.
  • JLT-221495 - Fix for empty on-demand-analysis result and showing result limit of -1 reached when the actual result limit of the analysis is reached
  • JLT-220880 - Adapted internal assertion (no effect for production)

Java Agent

  • JLT-221105 - Handle weird agent option strings more gracefully when converting classic agent options to AppMon agent options.
  • JLT-221054 - RMI tagging sensor caused connection timeout on WebLogic 12.2.1.0.0
  • JLT-220394 - Bootstrapping for the java agent on z/OS 2.3.

PWH

  • JLT-220248 - Prevent performance warehouse incidents for spurious disconnects.
  • JLT-215623 - Improve logging in SourceGroupHandler.
  • JLT-213242 - Invalid measure prevents data storage in the PWH

.NET Agent

  • JLT-221447 - DotNet RabbitMQ HandleBasicDeliver API discovery run for implementations derived from DefaultBasicConsumer not needed any more.

MessageBroker Agent

  • JLT-220885 - Addresses clock_gettime not found in the ibm integration bus agent.

Client

  • JLT-221308 - In case of communication problems while configuring SSO null pointer exceptions might be thrown
  • JLT-221508 - Disabled switch collector button in agent overview when AppMon agents are selected.

Collector

  • JLT-194059 - Improve collector log in case an agent does not match a system profile.

7.1.8.1012 Resolved Issues

Most critical issues since the last public updates

All resolved issues

Correlation and Analysis

  • JLT-219814 - Do not link a subpath to a another subpath if the resulting graph would exceed the maximum allowed nodecount.
  • JLT-217568 - DrillDown to PurePaths from Incidents doesn't work
  • JLT-220198 - Avoid NPE that happens very occasionally on timed out nodes and add some logging.
  • JLT-219918 - Improve logging of protocol errors of classic agents.
  • JLT-218094 - Prevent log spam when sub-paths cannot be force-completed.
  • JLT-220534 - Fix not regarding debugflag 'com.dynatrace.diagnostics.enableCrossSystemProfileSplit' when linking user actions with serverside purepaths.

PWH

  • JLT-220448 - Correct handling of a corner case of deleting measurements (JLT-216191) and removing one measure at the same time.
  • JLT-216191 - On erasure of data for measures the server internal cache will be cleared more selective. This avoids loss of data due to the performance impact caused by the re-population of the cache.
  • JLT-218045 - Add log output when jdbc driver throws exception with empty message and log stack (with debug flag)
  • JLT-208988 - Optimized handling of server cache inconsistency to minimize performance impact by refilling the cache.
  • JLT-220369 - Correct handling of a corner case of deleting measurements (JLT-216191) and removing the measure at the same time.
  • JLT-220463 - Avoid too intensive logging during incident cleanup.
  • JLT-219794 - Measurements are not stored in Performance Warehouse because of DataIntegrityException.
  • JLT-206797 - Removal of unused dynamic measures from server cache optimized. This minimizes the performance impact for refilling the cache.

Collector

  • JLT-220320 - Fix an instrumentation problem when using older agent versions. leading to WCF-tagging to not work any more
  • JLT-218252 - Incomplete locking during sensor pack synchronization between server and collector leads to corrupt instrumentation rulesets and therefore uninstrumented agents when repeated synchronization is triggered in short intervals.

Agent

  • JLT-217262 - Use the AppMon (instead of the classic) agent for NGINX processes by default

Server

  • JLT-215993 - To avoid ConcurrentModificationExceptions a ConcurrentHashMap will be used in Selfmonitoring
  • JLT-218973 - Tier aggregation threshold for Transaction Flow can not be changed on the server.
  • JLT-220232 - null values of LDAP attributes lead to NoSuchElementException and potentially blocked LDAP group updates for configured users
  • JLT-220347 - Host Overview dashboard shows 'Insufficient Permissions' although there is a permission

Server Platform

  • JLT-213684 - BlackDuck scan revealed vulnerabilities in jackson library: update to version 2.9.6
  • JLT-218359 - System profile names with trailing spaces or special characters are accepted by the REST interface, leading to exceptions when trying to load the profiles later.

Client

  • JLT-220251 - Processes of other hosts are shown in the process list of the host overview.
  • JLT-220635 - Renamed Security Gateway to ActiveGate
  • JLT-220656 - In case of communication problems with the frontend server the SSO certificate import fails with a null pointer exception
  • JLT-219291 - NPE in agent browser when no agent is selected
  • JLT-214765 - Prevent UnsupportedOperationException while editing dashboard configuration

Session Storage

  • JLT-219292 - Fix error when using TopX Duration filter with unlimited record limit in PurePath Dashlet

UEM

  • JLT-220446 - Small change to wrap log message in debug flag and include in stats counter

WebUI

  • JLT-220407 - Special characters were double escaped in session drop-down.
  • JLT-220518 - Fix mixed up aggregations in "Frontend server health" Web Dashboard

DB Agent

  • JLT-218702 - Amazon Aurora with MySQL 5.7 is not supported. Implemented a proper validation message stating this.

Mainframe

  • JLT-219716 - ZRemoteAgent mishandles IMS address spaces when having multiple IMS Control regions with the same SMF ID in the same LPAR

7.1.7.1010 Resolved Issues

Most critical issues since the last public updates

zAgent

  • ONE-15553 - Fix an issue with the ZRemoteAgent timing out a transaction prematurely
    • Impact: Missing or broken purepaths
    • Cause: The ZRemoteAgent in some instances may timeout a transaction prematurely causing sequence errors resulting in missing or broken purepaths
    • Solution: Use proper parameter when checking transaction timeout

All resolved issues

Tests

  • JLT-189683 - Integration test failure: "Expression was not true: Failed to change and store system profile"

Server

  • JLT-219595 - Renaming a system profile under some conditions leads to PureLytics inconsistencies and AnalysisCacheHandlerExceptions in the FrontendServer log files
  • JLT-215557 - Java Executor sensor and Thread start sensor could be configured into an inconsistent state.
  • JLT-218776 - Slight improvement in incident logging
  • JLT-217885 - Unable to remove an update because Server erroneously claims that the JavaScript agent of the update is in use
  • JLT-219104 - Storing dashboard failed. Improved robustness of request handling for storing dashboards (PurePathDataModelConfig).
  • JLT-219136 - An AssertionError is thrown when a OneAgent connects (only if the JVM runs with the -ea option)
  • JLT-218720 - Updated tomcat-jdbc and tomcat-juli libraries from 8.0.25 to 9.0.8 to prevent security scan alerts.
  • JLT-218243 - Added null-checks for session metadata fetching for support archives
  • JLT-218918 - AppMon agent custom ruleset is rebuilt with incomplete state after sensor order change if sensor installation notifications arrive too late.
  • JLT-218872 - Custom host measures don't populating data
  • JLT-219320 - Sensor extension migration for .NET thread tagging sensor not executed if the extension has been touched with public update 6.
  • JLT-209003 - Database Dashlet reported pool usages of > 100% in some scenarios
  • JLT-216327 - AppMon agent is not configured to capture argument names for the Java Web Services sensor.
  • JLT-214261 - Java Executor Tagging sensor placing and extensions have no effect for AppMon agents, which only consider the Thread Start Tagging sensor placement for the threading sensor configuration.
  • JLT-215825 - No longer regard names of method arguments to unify behavior of Appmon and Classic Agents.
  • JLT-217278 - Instrumentation difference between .NET Classic Agent and AppMon Agent for thread tagging sensor: missing rule for ThreadHelper.ThreadStart in AppMon Agent ruleset
  • JLT-219013 - NPE when AppMon agent connects
  • JLT-218436 - PureLytics runs into an endless loop when bulking to much data for analysis.
  • JLT-214234 - Changing the number of BT result measures may cause IndexOutOfBoundsExceptions

Correlation and Analysis

  • JLT-218389 - Transaction Flow shows wrong execution time for Observed Tier when it is not the last node in the subpath.
  • JLT-219787 - Avoid a NPE in subpath postprocessing and add some logging in case it would have happened.
  • JLT-215627 - Reduce memory footprint of nodes sent by Appmon agents and improve performance of subpath completion check.
  • JLT-218189 - Do not create classic agent sub-paths, if their creation is blocked due to high memory pressure.
  • JLT-218486 - Only reset custom external call flag on sub-path nodes of complete paths, thereby preventing exception.
  • JLT-217676 - Align correlation engine behavior for aggregated nodes from AppMon agents with the behavior of Classic agents by no longer creating several nodes per transferred aggregate node, if the node has several aggregate attachments.
  • JLT-218088 - No longer create empty root paths for 'execution path not instrumented' sub-paths; that's normal and created unnecessary noise.

JavaScript

  • ONE-15728 - jQuery 'synchronous' ajax actions close too early due to not wrapping their callback functions
  • ONE-15570 - VisuallyComplete time for load actions was incorrect in case of async injection or under slow network conditions
  • ONE-15554 - There is a conflict between zone.js and MutationObserver, where our frequent usage of it happens to cause an infinite loop, freezing the browser. The fix is a code workaround for it where we simply initialize the object once rather than for every XHR action.
  • ONE-15577 - The javascript agent broke the page when a new version of webpackjsonp and the angular module was used

Client

  • JLT-218709 - Importing a user defined certificate from a PKCS #12 file returns a "too many keys" error
  • JLT-217331 - System profile nodes in Incidents view are expanded by default
  • JLT-219146 - The Client freezes when selecting a time-frame offset for the right axis of the dual axis chart.
  • JLT-215934 - Generic .NET types are wrongly displayed for method arguments in the class browser.
  • JLT-219290 - SSO service provider certificate configuration can throw a null pointer exception if the communication with the frontend server times out
  • JLT-215534 - Deadlock might occur on rare conditions when closing all dashboards.
  • JLT-217628 - Changed Java/.Net Logging sensor aggregation checkbox to be visible without debug mode, added AppMon Agent requirement elaboration to the label + adjusted hint text for that checkbox element

Collector

  • JLT-219670 - Add log throttling in case a api can't be found for a specific agent.
  • JLT-218750 - sun4v as value of property 'os.arch' is not mapped to the Scalable Processor Architecture (SPARC)
  • JLT-218745 - Instrumentation may take long time if many agents connect at the same time which may lead to timeouts.
  • JLT-217595 - A NullPointerException is thrown if an agent connects that is running on an unsupported platform

WebUI

  • JLT-218697 - XSS vulnerability of Text and measures tile.
  • JLT-217103 - Allow the user to display "0" instead of "-" if no data is available in the Text and measures tile.

zAgent

  • ONE-15553 - Fix an issue with the ZRemoteAgent timing out a transaction prematurely

PWH

  • JLT-218254 - Repo Config Dialog: User field stays disabled when switching from win-auth SQL Server to different DBMS system
  • JLT-218950 - Upgrade ojdbc driver to support TLS 1.2

Common

  • ONE-14995 - Update OneAgent to Sprint 143

Session Storage

  • JLT-216359 - For GDPR compliance the user can enable time based session deletion.
  • JLT-219099 - Graceful handling of null values and null keys in web request attachment session parameters to be able to analyze and store PurePaths where such keys/values occur.

Agent

  • JLT-219026 - AgentConfiguration upgrade to 2.17.2 to support Agent 143.

Mainframe

  • JLT-218766 - zRemoteAgent crash during reconnect cycle if IMS subagents are present

Instrumentation

  • JLT-215647 - Introduced option to allow for more relaxed instrumentation. Enabling this is not without risks.

7.1.6.1012 Resolved Issues

Most critical issues since the last public updates

Server

  • JLT-219069 - Regression introduced with 7.1.5: When selecting "Windows Authentication" in the pwh configuration dialog, entering a username and password wasn't possible anymore.
    • Impact: Connecting to a SQL Server using ntmlv2 and not using the appmon windows user isn't possible.
    • Cause: Entering a user other than the windows service user isn't possible in the GUI.
    • Solution: Enabled user and password entry again.

All resolved issues

Server

  • JLT-219069 - Regression introduced with 7.1.5: When selecting "Windows Authentication" in the pwh configuration dialog, entering a username and password wasn't possible anymore.

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.