Description
Description
Hello,
Since upgrading to version 8 of dotnet-monitor, we’ve noticed that no processes are being detected when using Connect mode and the default diagnostic port.
To reproduce this issue, start an application that exposes the /tmp
folder in a volume (here named diag
):
docker run -it -v diag:/tmp -p 8080:8080 mcr.microsoft.com/dotnet/samples:aspnetapp
then start dotnet-monitor with the same (diag
) volume mounted:
docker run -it -v diag:/tmp -p 52323:52323 mcr.microsoft.com/dotnet/monitor:8 collect --urls "http://*:52323" --no-auth
When you access http://localhost:52323/processes
, it returns an empty list []
. We would expect to see some processes listed instead, like for example:
[{"pid":1,"uid":"79c27c06-eb74-4c49-bd41-93d6f4c4c93c","name":"aspnetapp","isDefault":true}]
as a dotnet-monitor in versions 6 or 7 behaved.
Regression?
To observe the change in behavior, simply update the version number to 7:
docker run -it -v diag:/tmp -p 52323:52323 mcr.microsoft.com/dotnet/monitor:7 collect --urls "http://*:52323" --no-auth
or version 6:
docker run -it -v diag:/tmp -p 52323:52323 mcr.microsoft.com/dotnet/monitor:6 --urls "http://*:52323" --no-auth
then access http://localhost:52323/processes
, you should see some processes listed.
I’ve reviewed the documentation and couldn’t find any information about changes to configuration or behavior since version 8.
Am I overlooking something?