DX Application Performance Management

  • 1.  .NET agent use of the -DagentManager argument

    Posted 10-26-2017 02:50 PM

    Howdy Community,

     

    So we are installing 10.5.2.24 and this time around we are installing more and more MS .NET agents.  During the installation of the agent using the exe, a service wrapper is created using the answers from the installer prompts.  There seems to be no way to inject custom agent parameters into the mix, like a custom IntroscopeAgent.profile or inject the -DagentManager.

     

    So, I have to instruct the system admins either how to edit the IntroscopeAgent.profile and restart the service, or provide then an environment specific IntroscopeAgent.profile.  It would be much better if I could customize the IntroscopeAgent.profile to use the -DagentManager= JVM argument and comment out the agentManager from the config than have to instruct the system admins how to do stuff.

     

    Is there any way that we can inject JVM parameters or a custom IntroscopeAgent.profile into the installer to be included in the service wrapper?

     

    Thank you,

     

    Billy



  • 2.  Re: .NET agent use of the -DagentManager argument

    Broadcom Employee
    Posted 10-26-2017 03:49 PM

    Dear Team:

     

    If you are an APM Admin/Customer or CA partner, can you please first to provide any suggestions to help Billy?

     

    Thanks,

    Matt



  • 3.  Re: .NET agent use of the -DagentManager argument

    Broadcom Employee
    Posted 10-26-2017 05:58 PM

    Hi Billy,

    The service wrapper is only for the PerfMonCollectorAgent. Is that the issue?



  • 4.  Re: .NET agent use of the -DagentManager argument

    Posted 10-27-2017 07:39 AM

    Haruhiko,

     

    It is the installer and the lack of fine control over the settings, like custom JVM arguments for the agent.

     

    The Windows service for the .NET agent has the command line of:

    "C:\Program Files\CA APM\Introscope 10.5.2.24\wily\bin\PerfMonCollectorAgent.exe"

     

    Which is far different than what I am used to.  With the enterprise managers, you can go into the IntroscopeEnterpriseManager.lax and muck with the JVM arguments or even the IntroscopeEnterpriseManager.profile.  Then with the epagent, you can create a simple EMCtrl.sh or use an older version since the 10.5.2 version has the "Tanuki Software" wrapper which really limits how to manage the IntroscopeAgent.properties file.

     

    So with the use of the "PerfMonCollectorAgent.exe" is there a way to inject something like the -DagentManager= for the Java or epagent?

     

    The main goal here is to only have one "IntroscopeAgent.profile" that will not have the 'agentManager.url.1=" within it and set that value via a environment variable.



  • 5.  Re: .NET agent use of the -DagentManager argument
    Best Answer

    Broadcom Employee
    Posted 10-27-2017 11:51 AM

    Hi Billy,

    The service is strictly for the PerfMon agent, as I stated previously. IIS applications are started via internal processes within IIS and the use of environment variables:

    • com.wily.introscope.agentProfile=<Agent_Home>\IntroscopeAgent.profile
    • Cor_Enable_Profiling=0x1
    • COR_PROFILER={5F048FC6-251C-4684-8CCA-76047B02AC98}

    All IIS applications share the same configurations. The only way to get around this is to go the old route to instrument via web.config for each application. You can get a feel for how that looks by looking at the same provided with the agent called Sample.exe.config in your agent directory.