409 Errors when calling nlog on Azure Storage

[Hidayath2007]

We have a web application running in a high-load environment with multiple external integrations. Recently, we've been encountering frequent 409 Conflict errors and BlockCountExceedsLimit exceptions.

A support ticket was opened with Microsoft to determine if these issues were related to infrastructure limitations, but they have since ruled that out.

We have the sets logs to roll over every hour and have not had any success. Has anyone else faced this problem and have any suggestions

FYI :
These are the nlog versions in use
NLog version="4.7.15"
NLog.Extensions.AzureBlobStorage" version="2.4.0"
NLog.Extensions.Logging" version="1. 7.5"
Our application is on Framework 4.8

[snakefoot]

If you have multiple nodes all writing to the same blob, then I guess you are able to exceed the limit of 50,000 blocks per blob. Even if you roll to a new blob every hour. If writing every 200 msec, then a single node can write 20000 blocks per hour.

Maybe assign a name/group to each node, and include that in the blob-name (or some other id like the process-id / machine-name) ?

[Hidayath2007]

If you have multiple nodes all writing to the same blob, then I guess you are able to exceed the limit of 50,000 blocks per blob. Even if you roll to a new blob every hour. If writing every 200 msec, then a single node can write 20000 blocks per hour.

Maybe assign a name/group to each node, and include that in the blob-name (or some other id like the process-id / machine-name) ?

Do you know Is there some documentation for this?

[snakefoot]

Maximum number of blocks in a block blob or append blob: 50,000 blocks

Do you know Is there some documentation for this?

https://learn.microsoft.com/en-us/azure/storage/blobs/scalability-targets

NLog ${machinename}

NLog${processid}

List of available NLog LayoutRenderers

Docs for NLog.Extensions.AzureBlobStorage