[Feature]: Give users the ability to have diagnostic-level verbosity for Nuget network activity #11242
Labels
Area:Logging
Area:Protocol
Client/Server protocol /code around it
Functionality:SDK
The NuGet client packages published to nuget.org
Priority:3
Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog.
Type:Feature
NuGet Product(s) Involved
NuGet.exe, MSBuild.exe, dotnet.exe
The Elevator Pitch
While doing the research that eventually led to #11027, I realized how little information I can actually get about network operations from Nuget Clients. This leads to all sorts of experimentation with packet captures, artificial environments, and frankly guesswork.
A flag, either that honors MSBuild verbosity in build tasks, environment variable, what-have-you, that turns on max verbosity for all network activity (or even errors) could significantly help customers debug through the problems they face. The above issue, for instance, helped find a very old deficiency that had been in Azure DevOps package feeds more-or-less forever.
Additional Context and Details
No response
The text was updated successfully, but these errors were encountered: