You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Operating system and version:
windows 10 and Installed the built-in IIS components
./net framework 3.5(包含./net2.0\3.0)
./net framework 4.8 advanced services
.NET extensibility 3.5\4.8
ASP.NET 3.5\4.8
I compiled the same codebase using(It only includes an operation to access Baidu using HttpClient) .NET SDK versions 6.0.136, 5.0.408, and 3.1.426 respectively, for testing purposes
1.I placed the compiled package in the specified physical path directory for the IIS website.
2.Started the application and it was accessible normally.
3.However, I added environment variables using web.config. The specific configuration is as follows:
4.After restarting IIS, the application was still accessible normally, but I found that the probe was not loaded. Are there any steps I did wrong?
5.I also tested configuring the above settings directly using system environment variables, but the probe still wasn't loaded. What could be the possible reasons?
I was hoping to see the probe being loaded, but after testing, I found that the application was functioning normally and I could access it through the port configured in IIS. However, there was no sign of the probe being loaded.
The text was updated successfully, but these errors were encountered:
The parameters for the environmentVariable node that I configured in the web.config file are mainly as follows:
ELASTIC_APM_SERVICE_NAME=dotnettest
COR_ENABLE_PROFILING=1COR_PROFILER_PATH=E:\IIS\agent\elastic_apm_profiler.dll
ELASTIC_APM_PROFILER_HOME=E:\IIS\agent
ELASTIC_APM_PROFILER_INTEGRATIONS=E:\IIS\agent\integrations.yml
ELASTIC_APM_SERVER_URL=localhost:8200
ELASTIC_OTEL_LOG_LEVEL=trace
ELASTIC_OTEL_LOG_DIRECTORY=E:\IIS\agent\logs
ELASTIC_APM_APPLICATION_PACKAGES=E:\IIS\ddd\
APM Agent version
elastic_apm_profiler_1.30.0-win-x64.zip
Environment
Operating system and version:
windows 10 and Installed the built-in IIS components
./net framework 3.5(包含./net2.0\3.0)
./net framework 4.8 advanced services
.NET extensibility 3.5\4.8
ASP.NET 3.5\4.8
I compiled the same codebase using(It only includes an operation to access Baidu using HttpClient) .NET SDK versions 6.0.136, 5.0.408, and 3.1.426 respectively, for testing purposes
dotnet build
dotnet publish -c Release -o ./publish
1.I placed the compiled package in the specified physical path directory for the IIS website.
4.After restarting IIS, the application was still accessible normally, but I found that the probe was not loaded. Are there any steps I did wrong? 5.I also tested configuring the above settings directly using system environment variables, but the probe still wasn't loaded. What could be the possible reasons?2.Started the application and it was accessible normally.
3.However, I added environment variables using web.config. The specific configuration is as follows:
I was hoping to see the probe being loaded, but after testing, I found that the application was functioning normally and I could access it through the port configured in IIS. However, there was no sign of the probe being loaded.
The text was updated successfully, but these errors were encountered: