Egress Providers
We could only use one way to egress diagnostic artifacts from dotnet monitor and that is via the HTTP response stream in previous previews and this works well for over-reliable connections but this becomes increasingly challenging for less reliable connections and very large artifacts.
You can configure dotnet monitor to egress artifacts to other destinations in preview4: the local file system and Azure Blob Storage. It is also possible if you want to specify the multiple egress providers via configuration as shown in the example below:
Example
{
"Egress": {
"Providers": {
"sampleBlobStorageEgressProvider": {
"accountUri": "https://contoso.blob.core.windows.net",
"containerName": "dotnet-monitor",
"type": "azureBlobStorage",
"blobPrefix": "artifacts",
"accountKeyName": "MonitorBlobAccountKey"
}
},
"Properties": {
"MonitorBlobAccountKey": "accountKey"
}
}
}
Once it is configured, then at the time of triggering the artifact collection via an HTTP request, you can specify that which egress provider will use. With the above configuration, now you can make the request like the following:
GET /dump/?egressProvider=sampleBlobStorageEgressProvider HTTP/1.1
Look at the egress configuration documentation for more detailed instructions on configuring egress providers.