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

adhiraj-g · September 28, 2021, 2:23pm

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

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?

github.com/Azure/azure-rest-api-specs

Consumption API (2019-10-01) missing startDate and endDate query parameters and incorrect bool type

opened 11:05AM - 30 Nov 20 UTC

mrsheepuk

bug Consumption Service Attention

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.

MarianaD · September 29, 2021, 8:40am

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) , as stated in the issue you referenced above, some properties are missing and objects have been replaced.

system · October 27, 2021, 10:40am

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