DX Application Performance Management

Hi Team ,

I need to know about the monitoring of applications running as windows service.

How can we do monitoring of the .net & java application which are running as a windows service ?

Regards,

Amit

Hi Amit,

To monitor applications that run as a Windows service, there should be no special requirements on top of normal agent profile configuration or property additions i.e.

• For .NET applications, after the .NET agent is installed on the server it will automatically monitor any .NET Framework applications according to what is configured into the agent profile for monitored IIS App Pools and application executables (subject to support of Framework version)
• For Java applications the required JVM properties for the agent needed to be added to the appropriate configuration file/script used to run the Application Server from the service.

For further details please see:

NET Agent - CA Application Performance Management - 10.5 - CA Technologies Documentation 

Java Agent - CA Application Performance Management - 10.5 - CA Technologies Documentation 

Hope that helps. Please let us know if you have more specific questions.

Regards,

Lynn

Hi Lynn ,

Thanks a lot for you response. But some of the .Net application are not hosted in IIS.

Regard 

amit

Hi Amit,

Yes that is configurable in the .NET agent profile where specific application .exe files can be added to the property introscope.agent.dotnet.monitorApplications which already has default values including w3wp.exe for IIS.

Customize .NET Instrumentation - CA Application Performance Management - 10.5 - CA Technologies Documentation 

Regards,

Lynn

It's likely you're probably going to have to monitor the EXE and not use the IIS option as Lynn was describing.

The .NET agent comes with a sample EXE config/manifest file that shows you how you can modify your Windows Service EXE to start up the .NET agent so it can be monitored.

Hi Team ,

Thanks for your quick response. 

I have done following changes and restarted the services but still agent is not coming up 

Regards 

Amit 

Try it without the path, just the name of the executable as it appears in Task Manager.

If my first reply about the monitored apps doesn't work, try following my suggestion about modifying the EXE manifest.

Hello Amit,

About the introscope.agent.dotnet.monitorApplications property, you need to use the process name, this can be obtained from the task manager

Also, you need to set the permissions using the wilypermission.exe for standalone .NET apps.

I documented all these steps in this KB

How to instrument a Standalone .NETApp 

However, if the problem persists:

1. Make sure you are using the correct .NET agent installer package. Use 64bit installer in case you are planning to monitor .NET 64bit machine and you need to monitor 32 and 64 bit applications

2. Try commenting the property the property this to force the agent to instrument all .NET apps.

#introscope.agent.dotnet.monitorApplications

Check if you can monitor for example IIS

3) If CLR is v4, set introscope.nativeprofiler.clrv4.transparency.checks.disabled=true

4) It could be the case that the main method of the application has been instrumented however it is not the entry point to the application, set introscope.nativeprofiler.generic.agent.trigger.enabled=true

5) Look at the Windows Event viewer for Application log Error messages. The .NET Agent GUID is {5F048FC6-251C-4684-8CCA-76047B02AC98}. If you see an error message similar to: “Failed to CoCreate profiler” “The profiler was loaded successfully. Profiler CLSID: '{D6E0BA92-3BC3-45ff-B9CC-B4B5AB7190BC}

then that indicates that there is another CLR profiler preventing the .NET Agent from probing the .NET process.

6) Check that the .NET agent has been installed correctly

-Verify that the correct version of wily.Agent.dll has been registered in the GAC (c:\windows\assembly).

-Verify that the below environment variables exist:
Cor_Enable_Profiling=0x1
COR_PROFILER={5F048FC6-251C-4684-8CCA-76047B02AC98}
com.wily.introscope.agentprofile=<install_dir>\wily\IntroscopeAgent.profile

7) Make sure the agent is pointing to the right EM

8) Verify that the .NET agent is attached to the .NET process using “tasklist /m”, “wily.Agent.dll" and “wily.NativeProfiler.dll" should be attached to the process

Otherwise, Enable DEBUG logging in the logging.config.xml and open a support case

I hope this helps,

Regards,

Sergio

Hi Amit:

   Was Sergio's response helpful? Are there any additional questions after reading this?

Thanks

Hal German

Hi Team ,

Sorry for my delayed response. Now it is working fine. Thanks a lot for all your assistance.

Best Regards

Amit Singh Bisht