serilog-sinks-azureblobstorage
serilog-sinks-azureblobstorage copied to clipboard
A Serilog sink that writes events to Azure Blob Storage
I have migrated our project to latest package dependencies for various things and removed some deprecated Microsoft packages etc. and then found our app no longer deployed within the Function...
Currently we develop a azure function app with .net 6 framework & AzureFunctionsVersion v4 which includes of service bus package Microsoft.Azure.WebJobs.Extensions.ServiceBus (v 5.7), when i try to implement serilog sinks...
Config that worked with 2.x: ``` "WriteTo:AzureBlobStorage": { "Name": "AzureBlobStorage", "Args": { "accountName": "examplestorage", "sharedAccessSignature": "exampleSas", "writeInBatches": true, "period": "00:00:04", "batchPostingLimit": 1000, "storageContainerName": "exampleContainer", "storageFileName": "example.txt" } } ``` After...
I've set up the write to blob storage with the code below. ``` .WriteTo.AzureBlobStorage(configuration.GetSection("AzureAd").Get().BlobContainer, outputTemplate: "[{Timestamp:HH:mm:ss} {Level:u3}] {Message:lj} {Exception} {NewLine}", ``` This produces the following error: Error CS0121 The call...
Hi, I'm trying to use an Account SAS for a blob container, but it doesn't seem to work, any help would be appreciated. I've tried what feels like everything, but...
Can you add an example of using a Managed Identity to access the blob and/or pulling the connection string from a Key Vault. Storing the account key in plain text...
Are there any considerations when using the package with appservice WebJob? I'm using .net core 2.2. In Program.cs: ``` var host = new HostBuilder() .UseConsoleLifetime() .... .UseSerilog((hostingContext, loggerConfiguration) => {...
If I put the connection string in appsettings.json like this it works. ` "Serilog": { "WriteTo": [ {"Name": "AzureBlobStorage", "Args": {"connectionString": "", "storageContainerName": "", "storageFileName": ""}} ] } ` But...
This activates warnings if the code is not compatible to AOT. There are no active warnings to fix for now. Information: https://learn.microsoft.com/en-us/dotnet/core/deploying/native-aot