.NET Agent for Linux Troubleshooting

This page describes general techniques when troubleshooting the .NET Agent for Linux deployment problems, and provides a few specific scenarios you may encounter with workarounds.

Agent Startup Situations

The agent startup is dependent on three basic steps:

.NET Core loads the agent using profiler settings in the environment variables.
Splunk AppDynamics agent loads the configuration and additional library.
The agent registers on the Controller using connection details found in the configuration file.

The sample startup console output on .NET Agent for Linux indicates a successful startup when going through these steps.

The following situations may occur:

Symptom	Probable root causes
No console output from Splunk AppDynamics was written to the console	Environment variables were not set correctly Agent binaries do not match the OS version
Agent complains about failing to load the configuration file	`AppDynamicsConfig.json` or `[appname].AppDynamicsConfig.json` were not found in the corresponding folders.
Agent complains about HTTP errors	Agent failed to communicate to the Controller using connection settings provided in the configuration file.

Accessing Logs While Running Docker Container in the Background

The default agent configuration redirects all agent output to the console. This is enabled for troubleshooting purposes.

If you are running the container in the background—-d for detach—it is possible to access all output using the following Docker command:

docker logs <container id>

Default Agent Log Files Location

The agent log files location is at /tmp/appd/dotnet by default.

You can change this setting to redirect all logs to the console output for a single view troubleshooting by adding the following configuration to the AppDynamicsConfig.json file as follows:

 "log": [
    {
      "outputtype": "console"
    }
  ]