Click the Start a free trial link to start a 30-day SaaS trial of our product and join our community as a trial customer. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
I am trying to profiler .NET Core application in linux environment.
Here, I have installed and configured .NET core agent in my Centos.
I given the environmental variable in service file as follows,
Then restarted the app service and apache server.
To check appdynamics profiler installation by running the following command,
lsof -p 2268 | grep -i appd
dotnet 2268 root mem REG 253,0 6443304 69595618 /opt/appdynamics/dotnet/libappdprofiler_glibc.so
dotnet 2268 root mem REG 253,0 6776 69595628 /opt/appdynamics/dotnet/libappdprofiler.so
<2268> is my dotnet process id and confirmed profiler loaded successfully.
My question is...
We have given only one profiler path which is libappdprofiler.so, then How this file "libappdprofiler_glibc" is loading? What is the use of this file?
Thanks in advance.
I found this information. Please let me know if it helps.
Regarding the "libappdprofiler_glibc.so" and "libappdprofiler_musl.so" libraries, all platforms use the "libappdprofiler.so" as the profiler which deploys "libappdprofiler_musl.so" if the platform is Alpine and "libappdprofiler_glibc.so" for all other Linux platforms. The pseudo profiler in the 21.5+ version detects the platform and then uses the correct profiler to deploy using either "libappdprofiler_glibc.so" or "libappdprofiler_musl.so".
While in the version before 21.5, the "libappdprofiler.so" was the actual profiler and there were 2 different agents for Alpine and other Linux platforms.
Ryan, Cisco AppDynamics Community Manager
Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Check out Observabiity in Action
new deep dive videos weekly in the Knowledge Base.