Reliability of Windows Azure Storage Logging -


we in process of creating piece of software backup storage account (blobs & tables, no queues) , while researching how came across possibility storage logging. use feature smart incremental backups after initial full backup. in introductory post feature here following caveat mentioned:

during normal operation requests logged; important note logging provided on best effort basis. means not guarantee every message logged due fact log data buffered in memory @ storage front-ends before being written out, , if role restarted buffer of logs lost.

as backup solution behavior makes features unusable, can't miss file. wonder if has changed in meantime microsoft has built number of features on top of blob function triggers , new azure event grid.

my question whether behavior has changed in meantime or logs still on best effort basis , should stick our 'scanning' strategy?

the behavior azure storage logs still same. case, might better off using eventgrid notification blob storage: https://azure.microsoft.com/en-us/blog/introducing-azure-event-grid-an-event-service-for-modern-applications/


Comments

Popular posts from this blog

Is there a better way to structure post methods in Class Based Views -

performance - Why is XCHG reg, reg a 3 micro-op instruction on modern Intel architectures? -

jquery - Responsive Navbar with Sub Navbar -