The location for the .NET Agent log files is
See Agent Log Files for a description of how the logs are organized into sets that rollover.
Log File Size
Within a set, the first file for the agent log can reach 5MB. This file never gets deleted, because it contains valuable information about the context in which the agent was started.
Each of the remaining logs in the set can reach a maximum of 5MB.
Allowing for several restarts and all possible logs that could be generated—.NET Agent, Business Transaction, and REST—the maximum number of rollover logs is five The maximum size per set is 5MB + (5 X 5MB) = 30MB.
Some log files, such as SamplingInfo and Winston are configured differently and can be 9MB in size with only two archive files.
Profiler logging is different, we log to the Profiler folder and one file per instrumented process is created. This is done by a different logging framework called Boost. Boost uses the archive files and max size, however, it also has two other limits, one to limit the number of files in the Profiler folder (defaults to 50) and the other max size (defaults to 30MB).
Controlling the .NET Agent Logging Level
You control the logging level for the .NET Agent by changing the value of the
min level parameter in the
AppDynamicsAgentLog.config file found in the .NET Agent logs directory. The log configuration is per server. The .NET Machine Agent and the .NET Agent read the same configuration file and write to the same set of output files.