AppD Archive

Unsure of how to configure standalone .net processes

CommunityUser
Splunk Employee
Splunk Employee

I have several windows services that I am trying to instrument, but cant seem to figure out how to. I have read the available documentation, but still not clear. All 13 windows services use the same .exe file, which I have defined in the config file. In the AppD UI, I all see a Machine Agent Tier(which isnt the name i want for the tier anyway), but nothing is being instrumented.

Here's what the config file looks like - what am i missing? How do I name the tier(in the UI) as SIKOMS Windows Service?

<?xml version="1.0" encoding="utf-8"?>
<appdynamics-agent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <controller host="xxx" port="xxx" ssl="true" enable_tls12="true">
    <application name="SIKOMS" />
    <account name="xxx" password="xxx" />
    <proxy host="xxx="xxx" />
  </controller>
  <machine-agent />
  <app-agents>
    <IIS>
      <applications>
        <application path="/" site="Default Web Site">
          <tier name="" />
        </application>
      </applications>
    </IIS>
    <standalone-applications>
      <standalone-application executable="D:\sikoms\applications\SIKWindowsServices\SIKWindowsServices.exe" command-line="-x">
        <tier name="SIKOMS Windows Service" />
      </standalone-application>
    </standalone-applications>
  </app-agents>
</appdynamics-agent>

Any help would be greatly appreciated.

0 Karma

Luis_Sánchez
Explorer

Hi,

The sintax is right, you need to take care of the command-line attribute:

<standalone-application executable="D:\sikoms\applications\SIKWindowsServices\SIKWindowsServices.exe" command-line="-x">

You need to provide de attribute to distinguish between different services provided by the same application executable, in the same path. If your services are in different paths, do not include command-line.

 

As the docs says, run the following from an elevated rights cmd.exe:

tasklist /m "mscor*"

Verify your services are in the list. If not, they aren't .NET services, so they couldn't be instrumented.

Then take a look at the command line of the service (using services.msc) and complete the entry in config.xml. Restart the AppDyn Coordinator service and the service to be instrumented. Wait 1, 2 minutes to the controller to get updated, your new tier is created and visible on the GUI.

An example of multiple services in one tier, with different paths:

		<standalone-applications>
			<standalone-application executable="E:\SNET\ACME\Programs\TEF\IFR\ACMETIFR.exe">
				<tier name="OPS-TIFR"/>
			</standalone-application>
			<standalone-application executable="E:\SNET\ACME\Programs\TEF\IFR2\ACMETIFR.exe">
				<tier name="OPS-TIFR"/>
			</standalone-application>
			<standalone-application executable="E:\SNET\ACME\Programs\TEF\IFR3\ACMETIFR.exe">
				<tier name="OPS-TIFR"/>
			</standalone-application>
			<standalone-application executable="E:\SNET\ACME\Programs\TEF\IFR4\ACMETIFR.exe">
				<tier name="OPS-TIFR"/>
			</standalone-application>
		</standalone-applications>

Your last resort is looking at the agent log, it will tell you what's going on inside it.

Hope it helps, regards,

Luis

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...