-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux Kudu not accessible when .NET agent presents. #616
Comments
A fix was added for no longer instrumenting the Kudu process in .NET agent version 8.26, although this was before the .NET 5 release.
|
This is how the profiler is currently detecting Kudu
$: /opt/Kudu/Kudu.Services.Web .
I suspect Microsoft changed how they invoke Kudu which made our detection no longer works. |
Quick fix for this here:
|
Description
When installing the latest agent on an app specifically targeting .NET 5 on linux azure, Kudu is no longer accessible. When removing the agent, kudu works again. It appears that Kudu was instrumented by the agent and it is unclear why the agent broke Kudu.
This only happens in linux azure. It didn't happen on Windows azure, because the profiler was hardcoded to not instrument the .Net Framework version of Kudu.
This is how the profiler is currently detecting Kudu so that it can ignore Kudu.
newrelic-dotnet-agent/src/Agent/NewRelic/Profiler/Configuration/Configuration.h
Line 171 in 2ba99ea
$: /opt/Kudu/Kudu.Services.Web
.I suspect Microsoft changed how they invoke Kudu which made our detection no longer works.
A fix would be updating the profiler to detect the kudu process in linux and don't do anything.
We may consider a feature where we could specify name of apps that the agent should not instrument.
Expected Behavior
Kudu shouldn't break.
The text was updated successfully, but these errors were encountered: