You can monitor standalone services that run on a
supported version
of .NET Framework and use Windows Communication Foundation (WCF), .NET Remoting Framework, or both.
By default, the App Visibility agent for .NET monitors applications and services running on Internet Information Services (IIS), but if you modify the agent policy file, you can also monitor these standalone services.
To add monitoring for the standalone services
- Edit the agent policy file.
- Uncomment the
self_hosted_services.list_to_monitorparameter. - Add a Windows service name. If you want to monitor more than one standalone service, separate the service names by a comma.
Ensure that you use the service name, not the display name:- In the Windows Service console (Control Panel > Administrative Tools > Services), locate the service you want to monitor.
- Right-click and select Properties.
- Copy the service name.
Example of the standalone services for .NET Framework
# List of self hosted services to monitor, each item should be a service name (not display name).
# The values should be separated by commas in the list
self_hosted_services.list_to_monitor = service1,service2
Related topics
Modifying an App Visibility agent policy
Configuring an App Visibility agent policy to collect and monitor application information
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks
3 Comments
Mohamed Eraky
How can i get WCF Service name. if this service implemented in IIS.
Harihara Subramanian
Hi Mohamed Eraky,
Apologies for a delayed response. Our SME had to say this:
Nothing special needs to be done to monitor WCF services running in IIS. By default, the .NET agent will attempt to monitor all .NET processes running in IIS. (of course subject to the supported limitations.)
However, for WCF services running outside of IIS, we need to manually configure the .NET Agent to tell about the Windows services that it needs to monitor (in addition to the IIS) and this is what the documentation article describes.
+ Petr Vyhnak.
Harihara Subramanian
Hi Mohamed Eraky,
You got an additional response from the SME.
By default, .NET agent will try to attach the IIS worker processes if they run on a .NET code, but we can configure it to attach to some windows services in addition to the IIS by giving the list of service names as described in the documentation.
This can be useful in some scenarios, when the windows service runs on .NET in a supported scenario, like Remoting services, WCF standalone services (in version 10.5 you need to apply the fix pack), or in 11.3.01 Web API services (Web API support is introduced newly in that version)