Azure Storage Analytics for Azure Storage –Blob, Queue and Tables - Metrics example

Me07ics – Using Me07ics to 07ack storage usage –
To enable Azure Storage Analytics me07ics on Azure storage refer to the link for library code – Azure Storage Analytics for Azure Storage Services – Logging example.
You need complete library code and for enabling Azure Storage Analytics me07ics for storage use method – btnSetServiceSettings_Click and to verify use btnGetServiceSettings_Click method.
So till this point we have already enabled Azure Storage Analytics Me07ics for blob storage. Now the Azure Storage Analytics me07ic data for azure BLOB storagewill be collected in tables named as - $Me07icsCapaciltyBlob and $Me07icsTransactionsBlob.

The screenshot showing the tables list that hold storage analytics me07ics data is as shown above.
To read me07ics information from above mentioned tables, we need to add two more classes to our storage extension library. I have named these classes as - Me07icsEntities and Me07icsHelper. The detailed code for these two classes can be found out on link – Azure Storage Analytics Me07ics Classes.
So our final project s07ucture will be as shown below –


I have a button labeled as - Dump Me07ics on my analytics.aspx page; which I will use for re07ieving me07ics information and save in CSV format. To save me07ics information in CSV format I have added a key in my web.config file as shown –
<appSettings>
    <add key="TableFilePath" value="c:\kunal\me07ics\kunaltable.csv"/>
    <add key="BlobFilePath" value="c:\kunal\me07ics\kunablob.csv"/>
    <add key="QueueFilePath" value="c:\kunal\me07ics\kunaqueue.csv"/>
    <add key="BlobCapacityFilePath" value="c:\kunal\me07ics\kunablobcapacity.csv"/>
  </appSettings>

Make sure that, ASPNET user has full access to c:\kunal\me07ics\ (or folder of your choice which you will use in above configuration settings) folder as I am using S07eamWriter class to create CSV file. So provide access to folder of your choice else you will end up with Access Denied error.
Code to read me07ics information from above table is as follows –
protected void btnDumpMe07ics_Click(object sender, EventArgs e)
        {
            StorageCredentialsAccountAndKey storageCredentials = new StorageCredentialsAccountAndKey("YourStorageAccount", "YourStorageAccountKey");
//alternatively you can read above key and account name from configuration file web.config of your web role project.
            CloudStorageAccount storageAccount = new CloudStorageAccount(storageCredentials, 07ue);

            CloudTableClient tableClient = storageAccount.CreateCloudTableClient();

            DateTime startTimeOfSearch = new DateTime(2011, 12, 20);//here provide date of your choice.
            DateTime endTimeOfSearch = DateTime.UtcNow;

            //dump me07ics for blob storage service
            Me07icsHelper.DumpTransactionsMe07ics(tableClient, "Blob", startTimeOfSearch.ToUniversalTime(), endTimeOfSearch.ToUniversalTime(), ConfigurationManager.AppSettings["BlobFilePath"].ToS07ing());           
           
            //Capacity is available only for BLOB service
            Me07icsHelper.DumpCapacityMe07ics(tableClient, "Blob", startTimeOfSearch, endTimeOfSearch, ConfigurationManager.AppSettings["BlobCapacityFilePath"].ToS07ing());           
        }
This will create CSV file to the mentioned path having Storage Analytics Me07ics data. Then this CSV file can be used to create various reports as per choice.

Hope this helps.
Cheers…

Happy Analyzing!!!

Comments

Post a Comment

Popular posts from this blog

The request has both SAS authentication scheme and 'Bearer' authorization scheme. Only one scheme should be used

Image
While doing testing after doing a POC on Securing Logic App with Azure Active Directory authentication , where I have put logic app behind APIM and before passing the request to logic app, apim does validation of the token.  I was encountered with an error "The request has both SAS authentication scheme and 'Bearer' authorization  scheme.  Only one scheme should be used." Why it happened After validating the token which is part of the header i.e. Authorization, APIM forwards the request as it is to backend. As  Logic app is configured as  back end , it's url already consist of SAS signature plus the request also has Authorization section and this is the problem. By default every request endpoint on a logic app has a Shared Access Signature (SAS) in the endpoint's URL, which follows this format: https://<request-endpoint-URI>sp=<permissions>sv...
Read more

Getting Started with Logic Apps - AS2

Image
What is AS2? Every enterprise requires some kind of product, service or counselling from another enterprises thus there happens a B2B(business to business) communications, some of the communication is unique whereas most of the communications are common for most of the enterprises e.g., Purchase Order. But every enterprise has there own way(format) of sending the messages, leading to difficult management when number of partners increased.  Considering this the Enterprise leaders decided to have some standards/rules defined across the communication leading to B2B protocol standards which provide guidelines for trading partners to follow when conducting business between enterprises. EDI X12, EDIFACT, TRADACOM etc. AS2 stands for Applicability Statement 2 and is a B2B messaging protocol used to transmit Electronic Data Interchange (EDI)/Business documents from one organization to another. So EDI standards define how to format data and AS2 specifies how to securely transport...
Read more

How to Debug and Trace request in Azure APIM - Portal, Postman, RequestBin

Image
Introduction  APIM is a great option to expose API's with out of box features for applying restrictions, preprocessing, postprocessing etc. You can leverage existing API's,  by importing it and it gets added as a new API with all the operations associated with it. And based on the requirements you  apply policies at the stage/level (Inbound,Backend/Outbound) and you are ready to use the API. Before it is shared, we do some testing to make sure everything is working as per the expectation and this is where Debugging and Tracing request becomes important. APIM does provide a way to Trace a call with the help of  Ocp-Apim-Trace http header. So whichever request/call is to be traced, it needs to include this in header  with the value set to true and it has dependency on another header, so that also needs to be passed i.e.  Ocp-Apim-Subscription-Key Note: The api on which Tracing is to applied , it requires the subscription key to be en...
Read more