# Does Azure metricbeat module use Consumption API version 2019-10-01

**URL:** <https://discuss.elastic.co/t/does-azure-metricbeat-module-use-consumption-api-version-2019-10-01/285371>\
**Category:** Beats\
**Tags:** beats-module, metricbeat\
**Created:** [September 28, 2021, 2:23pm UTC](https://discuss.elastic.co/t/does-azure-metricbeat-module-use-consumption-api-version-2019-10-01/285371 "2021-09-28T14:23:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![adhiraj-g](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adhiraj-g/32/88997_2.png) [@adhiraj-g](https://discuss.elastic.co/u/adhiraj-g)\
**Post date:** [September 28, 2021, 2:23pm UTC](https://discuss.elastic.co/t/does-azure-metricbeat-module-use-consumption-api-version-2019-10-01/285371/1 "2021-09-28T14:23:05Z")

</div>

Hi @MarianaD / @Kaiyan_Sheng

You had mentioned regarding raising an issue for Azure SDK with 2019-10-01 consumption API version.

This was the link shared: [Provide 2019-10-01 version of consumption APIs · Issue #12452 · Azure/azure-sdk-for-go · GitHub](https://github.com/Azure/azure-sdk-for-go/issues/12452)

Based on the comments, there is another link stating that its done. So, will we be able to fetch out billing details for pay as you go subscriptions now?

> <https://github.com/Azure/azure-rest-api-specs/issues/11849>
>
> The consumption API definition has a couple of problems in the 2019-10-01 versio…n:
> 
> \* The query parameters startDate and endDate are missing for \`UsageDetails\_List\` - for non-Enterprise Agreement subscriptions (e.g. PAYG or MCA) these allow filtering by date, adding \`properties/usageStart\` and \`properties/usageEnd\` to $filter has no effect. Manually specifying these parameters on the URL has the desired effect.
> 
> \* The returned results from the API for the LegacyUsageDetailProperties and ModernUsageDetailProperties uses the string value "1" in the field \`IsAzureCreditEligible\`, which is defined in the spec as a boolean. At least in the Go Azure SDK, the string value "1" is not parseable as a boolean, so the parse fails.

Hope to hear back from you soon.

---

<div class="post-metadata">

**Author:** ![MarianaD](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marianad/32/42687_2.png) [@MarianaD](https://discuss.elastic.co/u/MarianaD)\
**Post date:** [September 29, 2021, 8:40am UTC](https://discuss.elastic.co/t/does-azure-metricbeat-module-use-consumption-api-version-2019-10-01/285371/2 "2021-09-29T08:40:44Z")

</div>

we are currently working on adapting the metricset to the new changes in the 2019-10-01 version of the API, you can follow [Azure billing metricset - update consumption API's by narph · Pull Request #28028 · elastic/beats (github.com)](https://github.com/elastic/beats/pull/28028) , as stated in the issue you referenced above, some properties are missing and objects have been replaced.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 27, 2021, 10:40am UTC](https://discuss.elastic.co/t/does-azure-metricbeat-module-use-consumption-api-version-2019-10-01/285371/3 "2021-10-27T10:40:54Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.