API usage issues - TOP being ignored, timeout, etc.

[OTDani]

using version azure-mgmt-consumption==9.0.0

The API .usage_details.list(
scope=f'/providers/Microsoft.Billing/billingAccounts/{billingAccountIdLong}/billingProfiles/{billingProfileId}'
,metric='amortizedcost',
top=100)

Completely ignores the top clause, also if you use it '100'.

The API also throws (429) Too many requests. Please retry after 60 seconds.
when you try to consume it.

Could you please advise on what is the correct way to use this API to get the current months all charges from Azure, to all subscriptions in our billing account / billing profile?

Is there a way to govern to get back e.g. last 3 days only?

The closest we get if we start to loop over each subscription separately - but this both seems a bad approach, as we have billing profiles and consolidated accounts - while also it is VERY slow - 6 accounts data jan 1 to 15 takes 13 minutes, and these are not even our big accounts.

Thank you in advance

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 0e8c4735-1579-58a0-f375-096d5dbdc2c4
• Version Independent ID: 30a48745-054c-2748-f326-ab3b498dc144
• Content: azure.mgmt.consumption.operations.UsageDetailsOperations class
• Content Source: docs-ref-autogen/azure-mgmt-consumption/azure.mgmt.consumption.operations.UsageDetailsOperations.yml
• GitHub Login: @lmazuel
• Microsoft Alias: lmazuel

[tjprescott]

@msyyc can you take a look?

[kazrael2119]

Hello @OTDani ，I tried to solve your problem. Here is the code. I hope it will help you

import os
import datetime

from azure.identity import DefaultAzureCredential
from azure.mgmt.consumption import ConsumptionManagementClient

credentials = DefaultAzureCredential()
subscription = os.getenv('SUBSCRIPTION_ID')

consumption_client = ConsumptionManagementClient(DefaultAzureCredential(), subscription_id=subscription)
billing_account_id = 'your billing account id'

#Get today's date and the date three days ago
current_date = datetime.datetime.now()
offset = datetime.timedelta(days=-3)
past_date = (current_date + offset).strftime('%Y-%m-%dT%H:%M:%SZ')
filter_expression = "{} and {}".format(current_date.strftime('%Y-%m-%dT%H:%M:%SZ'), past_date)

res=consumption_client.usage_details.list(
    scope=f'/providers/Microsoft.Billing/billingAccounts/{billing_account_id}/billingProfiles/{billing_account_id}'
    ,metric='amortizedcost',
    top=100,filter=filter_expression)

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ccmbpxpcrew.

Issue Details

---

using version azure-mgmt-consumption==9.0.0

The API .usage_details.list(
scope=f'/providers/Microsoft.Billing/billingAccounts/{billingAccountIdLong}/billingProfiles/{billingProfileId}'
,metric='amortizedcost',
top=100)

Completely ignores the top clause, also if you use it '100'.

The API also throws (429) Too many requests. Please retry after 60 seconds.
when you try to consume it.

Could you please advise on what is the correct way to use this API to get the current months all charges from Azure, to all subscriptions in our billing account / billing profile?

Is there a way to govern to get back e.g. last 3 days only?

The closest we get if we start to loop over each subscription separately - but this both seems a bad approach, as we have billing profiles and consolidated accounts - while also it is VERY slow - 6 accounts data jan 1 to 15 takes 13 minutes, and these are not even our big accounts.

Thank you in advance

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 0e8c4735-1579-58a0-f375-096d5dbdc2c4
• Version Independent ID: 30a48745-054c-2748-f326-ab3b498dc144
• Content: azure.mgmt.consumption.operations.UsageDetailsOperations class
• Content Source: docs-ref-autogen/azure-mgmt-consumption/azure.mgmt.consumption.operations.UsageDetailsOperations.yml
• GitHub Login: @lmazuel
• Microsoft Alias: lmazuel

Author:	OTDani
Assignees:	msyyc, kazrael2119
Labels:	question, Service Attention, Mgmt, customer-reported, needs-author-feedback, Consumption - Billing
Milestone:	-

[ghost]

Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

[OTDani]

We are waiting on @ccmbpxpcrew
Please let me know what is the information you need from me?

[BigCat20196]

Hi @OTDani, For some reason, the top parameter is indeed invalid in python sdk. @kazrael2119 provides an sample on how to use it to return only the results of the last three days. Hope it can help you.

[OTDani]

Thanks @BigCat20196 @kazrael2119 !!

1. in the @kazrael2119 code the scope is

scope=f'/providers/Microsoft.Billing/billingAccounts/{billing_account_id}/billingProfiles/{billing_account_id}'

Could you please double check this? As AFAIK it should be a billing profile id at the end, this throws an error 500.

2. Using what i think was intended, the code times out with (429) Too many requests. Please retry after 60 seconds.

scope=f'/providers/Microsoft.Billing/billingAccounts/{billingAccountIdLong}/billingProfiles/{billingProfileId}'

but it runs, but not fine for just a subscription scope:

scope=f'/subscriptions/{azu_subscription_id}/'

Returns 1 small account taking over a minute - 4474 elements - (I'm sitting on gigabit net)
It completely ignores the date filter.
Expected data from Past 3 days, actual: the API gives back data from month's start as it would without the filter 😢

3. Back to the other two issues:

• How to overcome (429) Too many requests. Please retry after 60 seconds. ?
• How to speed this up?

[msyyc]

Hi @OTDani , Python SDK is just tools to send/receive request/response. According to the context, it seems that server does not take the filter effect. Please follow https://github.com/Azure/azure-sdk-for-python/blob/main/doc/dev/debug_guide.md to provide more detailed logs. With the logs, you could see the raw request and response from server. If the request is right with filters while server still return more data, it proves that there may be problems in server and you could make issue in https://github.com/Azure/azure-rest-api-specs/issues

[ghost]

Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!