![azure storage emulator v4.3 azure storage emulator v4.3](https://blog.jongallant.com/2020/04/local-azure-storage-development-with-azurite-azuresdks-storage-explorer/017.png)
One of the ways to accomplish this is by using Azure PowerShell Cmdlets.
AZURE STORAGE EMULATOR V4.3 UPDATE
What this means is that you can now turn on diagnostics or update your diagnostics configuration without redeploying your code. While 1.0 version of diagnostics was a Plugin model, the latest version of diagnostics make use of Azure Extension model. Diagnostics now use Azure Extension model For an example, please see Step 2 on this page. With the latest changes, it is certainly possible to do so. It was not possible with diagnostics 1.0. Moreover you would want querying capability on these custom fields. To give you an example, let’s say you want to trace a particular request in your application with some custom fields. With ETW Event Source, you can define your own diagnostics data and have diagnostics engine take care of persisting that in Azure Storage for you. In version 1.0, you’re somewhat restricted with what kind of diagnostics data you can persist and the structure of that data was pretty much decided for you. This is a big improvement in the diagnostics. There was a 1.2 version of the library as well but you need not worry about it now. This is the latest version of diagnostics client library. What You Getįirst let’s talk about the new stuff you get in the latest version of diagnostics. In this post we will talk about diagnostics changes in the latest SDK.
![azure storage emulator v4.3 azure storage emulator v4.3](https://docs.microsoft.com/fr-fr/azure/storage/common/media/storage-use-azurite/azurite-vs-code-extension.png)
One of the major change that was done in this release is related to diagnostics. Recently Azure team announced the availability of SDK 2.5.