Kusto query to get Azure Storage account details with historical data (every week how much capacity consumed))

Monalisa 60 Reputation points
2024-06-24T12:15:05.7533333+00:00

Kusto query to get Azure Storage account details with historical data (every week how much capacity consumed))

User's image

Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
3,234 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Amrinder Singh 5,155 Reputation points Microsoft Employee
    2024-06-24T13:24:11.37+00:00

    Hi Monalisa - Thanks for reaching out.

    While you can pull the basic detail w.r.t. name, subscription details, RG etc, you won't be able to get a week wise capacity breakup directly. This is because there is no weekly based metric.

    If you have configured to store transaction metrics, then you can query them to get an aggregated value or if you any kind of weekly inventory report, that might also help you calculating the weekly capacity of the account.

    Please let us know if you have any further queries. I’m happy to assist you further.    


    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.


  2. Monalisa 60 Reputation points
    2024-06-26T15:46:12.8033333+00:00

    Hi @Amrinder singh

    Our requirement to get weekly capacity report of storage account and store them in storage account and club them and send to the recipients using automation powershell

    can you please help on the same.

    We are using below query to get capacity details

    AzureMetrics | where ResourceProvider == "MICROSOFT.STORAGE"

    0 comments No comments

  3. Monalisa 60 Reputation points
    2024-06-27T07:28:23.1133333+00:00

    Hi

    can you please help on this


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.