Request for a flag/option to store dumps/traces at default location

[vedantm11]

Background and Motivation

We will be using dotnet-monitor to take dumps/traces for many of our dotnet applications, the current setup we are using is we have dotnet-monitor as a sidecar container running with all the application containers, communicating through the IPC socket on a shared volume mount in a pod.

While some of the applications we have normal dump sizes, for some of our applications, the dump size can span from 20GB to over 50 GB. In such cases it is not favourable for us to get the dump as a HTTP response or even have the file moved to the egressProvider location set.

We have observed in some cases the dump gets created fine at the temporary location set by the application/dotnet-monitor, but it gets corrupted during the move operation. We don't want the dump file to get corrupted during the move operation and would rather pick it up from the default location.

Also the dotnet monitor has a 250 MiB memory limit, which also makes it favorable to store the file where it is.

Proposed Feature

We observed dump files getting corrupted while the move operation from the default to the egressProvider location. We want either a new request argument or flag for egressProvider which would just store the file at the default location, no move operation happens on the generated dump file.

Usage Examples

This would help us use the already generated dump files for the application instead of having the risk of getting them corrupted during the move operation. For now we have setup an egress provider for storing the files at our desired location.

[github-actions]

Welcome to dotnet-monitor!

Thanks for creating your first issue; let us know what you think of dotnet-monitor by filling out our survey.