Azure billing metricset - update consumption API's

[narph]

What does this PR do?

In progress

Why is it important?

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

• Closes Outdated API version in the Metricbeat Azure module Billing set #20758

[elasticmachine]

Pinging @elastic/integrations (Team:Integrations)

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 249 min 23 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

[mergify]

This pull request does not have a backport label. Could you fix it @narph? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[ChrsMark]

Hey @narph ! What's the status on this? Also, you will need a "rebase" after the merge of #28228.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b update-azure-billing upstream/update-azure-billing
git merge upstream/master
git push upstream update-azure-billing

[ChrsMark]

lgtm, feel free to merge if CI is happy :)

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b update-azure-billing upstream/update-azure-billing
git merge upstream/master
git push upstream update-azure-billing

[ChrsMark]

/test

[ChrsMark]

@narph is there anything missing here? Could we move this forward so as to unblock the dependant ones?

[narph]

/test

[narph]

@narph is there anything missing here? Could we move this forward so as to unblock the dependant ones?

I am running the build again, although the broken build seems to not be due to my changes, the reason is still inconclusive, reaching out to robots team

[adhiraj-g]

Hi @narph and @ChrsMark ,
By when would v7.16.0 be available for use with updated consumption API features?
Is there any ETA for the same?

[adhiraj-g]

Hi @narph and @ChrsMark ,

I am using metricbeat version 7.16.2. Still its showing that the billing api is not supported. Are we using API-version: 2019-10-01 in this version?

2022-01-05T07:02:52.470-0500 ERROR module/wrapper.go:259 Error fetching data for metricset azure.billing: error retrieving usage information: Retrieving usage details failed in client: consumption.UsageDetailsClient#List: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="400" Message="Subscription scope usage is not supported for current api version. Please use api version after 2019-10-01

I tried tesing on Azure to confirm whether the subscription type i'm using is supported with the consumption API. It worked fine there.

Please help