Chat now with support
Chat with Support

Foglight for Microsoft DOT NET 5.9.7.5 - Release Notes

Resolved Issues and Enhancements

Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in this release.

 

Patches Issued for Previous Release

The following is a list of issues resolved in patches issued for the previous release. These issues are also fixed in this release.

Issues also Resolved in the ApplicationServers-Nexus-5_9_7_4.car Patch

Defect ID

Resolved Issue

CAC-741 High CPU usage occurs on the Agent Manager where the Nexus agent is running.
CAC-738 During the Agent Manager startup cycle, errors appear indicating that the Nexus agent cannot be started. The Nexus agent does eventually start.
CAC-737 A NullPointerException appears in the Nexus logs, sometimes causing the Nexus agent to stop data collection.

 

Issues also Resolved in the Foglight for Microsoft .NET 5.9.7.3 Patch

 

Defect ID

Resolved Issue

DN-1356 Reduce blocking on exception calls by syncing with specific locks for exception handling.

 

Issues also Resolved in Foglight for Microsoft .NET 5.9.7.1

 

Defect ID

Resolved Issue

CAC-713 Removed a rule that could cause topology churn and poor performance when deployed on Foglight Management Server Federation Master Servers.
CAC-701 Improved the performance of the Application Server Administration dashboards.
CAC-699 If the Nexus runs out of memory, the Agent Manager (FglAM) restarts automatically to correct the issue.
CAC-698 When a Nexus had many agents connected to it, the app server startup time was slower than usual.
CAC-685 Added a UUID transform in the URL transform rules to reduce the number of request types created by UUIDs in the URL.
CAC-602

Added a default URL transformation rule to decrease the number of request type topology objects on the Foglight Management Server. The rule conditions are:

  1. Request types that have request separation configured are not transformed.
  2. Static file requests (such as images) are not transformed.
  3. If there are 3 or more '/' in the URL, trim after the third '/'. For example:  /a/b/c/d/e/f.h -> /a/b/*
  4. If there are 2 '/', trim after the second '/'. For example: /a/b -> /a/*
  5. If there is only 1 '/', trim after the first '/'. For example: /a -> /*

The new default rule applies only to new installations. If you upgrade to version 5.9.6, your existing URL transformation rules are not changed.

CAC-257 Read the topic "Before You Begin the Installation Process" in the Managing Microsoft .NET Systems: Installation and Configuration Guide or help for important information about embedded Foglight Agent Manager settings before you install the cartridge.
DN-1305 Added a pre-filter to the .NET agent profiler to exclude classes of no interest and thereby reduce monitoring overhead. By default, .NET framework classes are excluded, except for the classes required for profiling.
DN-1286 Added support for Tag and Follow™ over WCF (Web Component Framework) calls.
DN-933 Added a setting to handle case insensitive IIS Request URLs.
DN-708 SQL parameters can be collected for Microsoft implemented Database methods (including SQL Server access methods), and OracleCommand methods.

Back to Top

Known Issues

Known Issues

The following is a list of issues known to exist at the time of this release.

 

Defect ID

Known Issue

CAC-275 The first time you open the Integrations tab after creating the first integration, the tab may appear empty.
Workaround: Toggle the "Show targets only" option to correct the display issue.
CAC-259 When switching the configuration on the .NET Administration dashboard, the number of agents affected is not indicated.
DN-1272 In certain instances, with new installations of version 5.9.6, a race condition may cause the full URL of requests to appear on the Request Type dashboard instead of the shortened version set by the default URL Transformation rule.
DN-1260 When .NET Counters Agents of version 5.9.4.x attempt to connect to a Foglight Management Server with Foglight for Microsoft .NET version 5.9.5 installed, a large number of errors are logged for the DotNETIISSite serviceUptime metric.
Workaround: Upgrade the Counters Agents to version 5.9.5.
DN-1131 In some cases, due to a known issue with the Agent Manager (FAM-2817), the Nexus receives the default contents of the ASP when it is restarts. Symptoms of this issue include agents failing to be enabled after a Nexus restart, such as during an upgrade.
 
Workaround: If you are using a Nexus hosted on a remote Agent Manager, restart the Agent Manager that is hosting the Nexus.

If you are using the default Nexus on the embedded Agent Manager, use the following procedure:
  1. Navigate to the Nexus Administration dashboard (Application Servers > Administration > Application Servers Administration > Nexus Administration).
  2. On the Nexus Administration dashboard, click the name of the Nexus.
  3. In the menu that opens, select Edit recording settings.
  4. Select the Advanced tab.
  5. Change one of the settings. For example, change MaxSeparationValueSize from 32 to 30.
  6. Click Save.
  7. On the Nexus Administration dashboard, click the name of the Nexus again to deactivate and then reactivate it.
DN-1128 The SQL statement view of single traces includes the comment portion of the SQL statement.
DN-1107 The version 5.9.3.x and 5.9.4 Foglight for Microsoft .NET Transaction Agents are incompatible with SharePoint. Therefore, do not attempt to use any version 5.9.3.x or 5.9.4 .NET Transaction Agent on any host that has SharePoint installed.

In version 5.9.5 and later, this issue is avoided by adding the ability to exclude application pools and shipping with a default configuration that excludes SharePoint application pools.
DN-1039 The trace for the main request of the WCF call contains the nodes for the Web Client and HTTP calls to WCF but does not contain the WCF method. The WCF method is collected separately.
DN-1023 All .NET transaction agents from the same IIS share the same agent configuration.
DN-1012 If you are using a version 5.9.2 or earlier .NET agent, some of the new functionality in this version is unavailable.
Upgrade your agents to version 5.9.3.x or later to access all of the agent management functionality.
DN-849 Due to a known issue with the Agent Manager (FAM-5006), under rare circumstances the .NET agent installers may fail to run on the monitored host and the following log message can be seen: WARN [IncomingMessage[3]-11] com.quest.dotnet.agent.DotNetAgentImpl - Data collection not starting unless deployment directory is set.
Fix: Upgrade the Agent Manager (FglAM) to version 5.7.6.3 or later.
DN-828 IIS Management Script and Tools must be installed on the monitored host for the .NET Agent to collect WMI metrics.
DN-811,
DN-786		 When capturing a trace, the ADO.NET Rollback() method for SqlTransaction may not be collected. If it is missed, the SqlTransaction::RollBack() node does not appear in the SQL call tree of the trace.
DN-738 When capturing a trace, some Remoting methods may not be collected (for example, SqlDependencyProcessDispatcher::StartWithDefault(), SqlDependencyProcessDispatcher::Stop()).

 

Back to Top

Third Party Known Issues

Third Party Known Issues

The following is a list of third party issues known to exist at the time of this release.

 

Defect ID

Known Issue

CAC-318 Some earlier versions of the JRE do not correctly detect Windows 8 or Windows Server 2012. This is an known issue with the JRE reporting "Windows NT (unknown)" in the os.name system property.
Workaround: Updating your JRE to the most recent build should correct the problem. For more information, see: http://bugs.java.com/view_bug.do?bug_id=7170169
DN-1211,
DN-1168		 If the agent is unable to read expected performance counter ".NET CLR Memory\\Process ID", the following warning is logged:
Unable to read Performance Counter ".NET CLR Memory\\Process ID\\_Global_". CLR counters will not be collected. It may be necessary to rebuild performance counters. Refer to release notes for details.
The performance counter libraries may become corrupted and may need to be rebuilt.

To rebuild the libraries:

1. On Windows Server 2003, type the following commands at an Administrator command prompt:
      cd\windows\system32
      lodctr /R

  OR

2. On later version of Windows, type the following commands at an Administrative command prompt:
      cd c:\windows\system32
      lodctr /R

    Additionally, for x64 system:
       cd c:\windows\sysWOW64
       lodctr /R

3. Resync the counters with Windows Management Instrumentation (WMI):
      WINMGMT.EXE /RESYNCPERF

4. Stop and restart the Performance Logs and Alerts service.

5. Stop and restart the WMI service.
DN-864

Applies to agent is running on the following versions, with the IIS Management Scripts and Tools module installed:

  • Windows Vista
  • Windows Server 2008
  •  Windows 7
  • Windows Server 2008 R2
Symptom: The following error message appears in the agent log:

com.quest.dotnet.agent.DotNetAgentImpl - The agent has reached the maximum number (30) of IIS WMI provider errors and will now stop collection. To enable IIS monitoring, install the IIS Management Scripts and Tools component. If it is already installed, the failure is possibly due to the IIS WMI Provider running out of memory. Please restart the Windows Management Instrumentation service.

Workaround: Install the following hotfix, to address a memory leak in the WmiPrvSe.exe process: http://support.microsoft.com/kb/2519454
DN-489 The .NET performance counters agent uses the Win32_Service WMI class for monitoring Windows services. On Windows Server 2008 R2 or Windows 7, this can cause a memory leak and generate a "No more threads can be created in the system" error message in the log.
Workaround: Apply the hotfix available from Microsoft: http://support.microsoft.com/kb/981314.

 

Back to Top

Upgrade and Compatibility

Upgrade and Compatibility

Foglight for Microsoft .NET 5.9.7.5 supports upgrades from version 5.9.x and 5.6.x.

  • Upgrades from version 5.9.2 or later are optional.
  • Upgrades from version 5.9.1 are mandatory.

For full upgrade instructions, see the Foglight Upgrade Guide 5.6.11.

 

Foglight Compatibility Requirements:

  • Foglight Management Server version 5.6.7 and later.
  • The Nexus requires Foglight Agent Manager version 5.6.7.2 or later. Version 5.6.7.3 or later is recommended.
  • The .NET agent requires Foglight Agent Manager version 5.6.2.6 or later.

Agent Compatiblity Requirements:

  • Foglight for Microsoft .NET 5.9.7.5 accepts connections from .NET agents versions 5.9.5, 5.9.4.x, 5.9.3.x, and 5.9.2. Earlier versions of the .NET agent, including 5.9.1, are not supported.

  • The .NET agent version 5.9.7.5 requires that .NET Framework 4.0 or later is installed on the monitored host.
  • Application pools monitored by the .NET agent can use either .NET v2.0 or .NET v4.0.

Compatibility with other Application Server Monitoring products:

  • Foglight for Microsoft .NET 5.9.7.5 is compatible with Foglight for Java EE Technologies version 5.9.2 and later. Do not attempt to use it alongside any earlier versions of Foglight for Java EE Technologies.
  • Foglight for Microsoft .NET 5.9.7.5 is compatible with Foglight for JMX version 5.9.3 and later. Do not attempt to use it alongside any earlier versions of Foglight for JMX.

 

Back to Top

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating