How does the Dot Net Agent monitoring the executable and the Agent Naming work?
For Example: Perfmon agent in Windows running as a Windows service.
Release : All versions
Component : APM Agents
Engineering has provided insightful information on Dot Net Agent monitoring and naming.
introscope.agent.dotnet.monitorApplications=w3wp.exe,aspnet_wp.exe,MyPerfMon.exe
But this will be monitored like another .Net application and you don’t see perfmon related metrics that you wanted to collect based on properties listed in agent profile.
Hence this renaming and monitoring is of no use as you miss the basic perfmon metrics.
The .NET Agent document explains about configuring perfmon collector properties. The agent profile that has all perfmon collector properties and had comments above each of the property which also explains about the property.
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-apm-agents/SaaS/microsoft-net-agent/configure-the-net-agent.html
Check this above link to go through its related properties.
Coming to the two points that you had mentioned below,
How to change the .Net Perfmon windows service name
This is not linked to our product for documenting such points, and if still customer wanted to change the windows service name for some reason, they can follow windows documentation of renaming the service. I believe this may involve some registry editing.
How to change the agent name
Regarding Agent naming, this is not related to perfmon agent. For agent name, we have autonaming and naming properties and is fully documented.