.NET CLR v2 & V4 - No reporting

[Richard Briceno]

Hi team,

 

I currently have a .Net agent installed on a server that has CLR v2 and CLR v4. The sites to monitor are with .Net Framework v4. In the introscope, only the perfmoncollector is being displayed. According to the literature, to monitor both CLR the following line must be activated: com.wily.introscope.nativeprofiler.monitor.inprocsxs.multiple.clrs = v2, v4 It has already been done, and even so it is not showing the desired sites.

 

Considerations:

 

- The application servers are in a network segment different from the MOM.

- Telnet and ping tests have already been carried out, and all Ok

- This is displayed: * SuperDomain * | SRVWEB2 | .NET Process | PerfMonCollectorAgent.exe | PerfMon | .NET CLR Exceptions

- The antivirus is inactivated, to adjust the profile. And the IIS was restarted, and even then it did not work.

 

What other tests can be done?

 

Thanks,

Richard

[Wan Fei Chee]

Hi Richard,

 

Per the CA APM Documentation, here's the detailed description of the "com.wily.introscope.nativeprofiler.monitor.inprocsxs.multiple.clrs" properties:

 

com.wily.introscope.nativeprofiler.monitor.inprocsxs.multiple.clrs

Controls how the agent handles monitoring for multiple versions of the Common Language Runtime. By default, the agent only monitors one version of the .NET Framework based on the version of the CLR loaded first. Use this property to modify the default behavior and specify whether to monitor .NET Framework 4 components.

Property settings
The valid values are:

• None -- Specifies that you want to use the default behavior and select the version of the .NET Framework to monitor based on the CLR loaded first.
• V4 -- Specifies that you want to monitor only .NET Framework 4 components. Alternatively, you can specify the CLR version number, for example, v4.0.3031

•  

Default

None.
This value indicates that only one version of the .NET Framework is monitored. The application loaded first determines which version of the .NET Framework is monitored.

Example

com.wily.introscope.nativeprofiler.monitor.inprocsxs.multiple.clrs=v4

Notes

The application must be restarted before changes to this property take effect.

 

In your case, as you only want to monitor v4, can you please try defining only v4 for this property, restart the application and see if it helps?

 

Thanks,

Aryne

[Richard Briceno]

Hi Aryne,

 

Thanks,

Richard

[Lynn Williams]

Hi Richard,
If Aryne's suggestion does not help here is some other information.

The fact that you see PerfMonCollectorAgent.exe metrics means there is no network problem between Windows Server running the agent and the APM cluster.

As of the APM 9.7 agent .Net v2 is actually no longer supported, but your .NET v4 apps should be getting monitored.
By default all App Pools for the IIS process w3wp.exe will be monitored

 

If you download & run Process Explorer (Process Explorer - Windows Sysinternals | Microsoft Docs ) and use "Find Handle" for string "wily.Agent" do you see the wily.Agent.dll in the GAC for both processes PerfMonCollectorAgent.exe & w3wp.exe? e.g.

 

In the wily\logs directory are there any nativeprofiler*, AutoProbe*, IntroscopeAgent* files apart from the ones for PerfMonCollectorAgent_exe?

 

Running the executable AGENT_HOME\wily\wilypermissions.exe from a command prompt started with Run as Administrator may help: e.g.
C:\Program Files\CA APM\Introscope\wily>wilypermissions.exe "C:\Program Files\CA APM\Introscope\wily"

 

If you still have a problem is it possible to restart the Windows Server as that is sometimes needed to complete the installation?

 

Hope that helps

 

Regards,

 

Lynn

[Richard Briceno]

Hi Lynn,

I did what you told me, but I had to restart the windows server. And sopresa worked the recommendations given.

Thank you very much, Richard

[Norris Graves]

Hi @Richard_Mendoza   

 

Please follow the recommendation above and let us know if it was helpful for you and we have provided you a correct response.

 

Norris