feat: Add Azure Monitor input plugin

[ShiranAvidov]

Required for all PRs:

• Updated associated README.md.
• Wrote appropriate unit tests.
• Pull request title or commits are in conventional commit format

resolves #7930

[srebhan]

@ShiranAvidov thanks for the interesting PR! Beside the comments in the code, I have a more general comment_:
Please try to simplify the code (e.g. by doing the init-stuff sequentially) and try to maybe reorganize the code to multiple files e.g. for the structures or helper-functions. This would ease the review and later working with the code as the current code base is rather large compared to other plugins.

Looking forward to the next round. :-)

[ShiranAvidov]

Hi @srebhan,
I changed the code according your comments.

Happy holidays :)

[powersj]

@ShiranAvidov if you could please rebase on master and resolve the conflicts with go.mod that would help keep this PR moving.

Thanks!

[telegraf-tiger]

☺️ This pull request doesn't significantly change the Telegraf binary size (less than 1%)

📦 Looks like new artifacts were built from this PR.

Expand this list to get them here ! 🐯

Artifact URLs

DEB	RPM	TAR GZ	ZIP
amd64.deb	aarch64.rpm	darwin_amd64.tar.gz	windows_amd64.zip
arm64.deb	armel.rpm	darwin_arm64.tar.gz	windows_i386.zip
armel.deb	armv6hl.rpm	freebsd_amd64.tar.gz
armhf.deb	i386.rpm	freebsd_armv7.tar.gz
i386.deb	ppc64le.rpm	freebsd_i386.tar.gz
mips.deb	riscv64.rpm	linux_amd64.tar.gz
mipsel.deb	s390x.rpm	linux_arm64.tar.gz
ppc64el.deb	x86_64.rpm	linux_armel.tar.gz
riscv64.deb		linux_armhf.tar.gz
s390x.deb		linux_i386.tar.gz
		linux_mips.tar.gz
		linux_mipsel.tar.gz
		linux_ppc64le.tar.gz
		linux_riscv64.tar.gz
		linux_s390x.tar.gz
		static_linux_amd64.tar.gz

[srebhan]

After looking at the code, I wonder why you cannot use the Azure-SDK for go instead of directly working with the URLs. If you scroll down you find API packages for resources/resource groups as well as substriptions...

Any reason you do not use those? They even do have examples...

[ShiranAvidov]

@srebhan done.

[ZPascal]

@srebhan Are there still open points from your side? Is the PR mergeable?

[powersj]

@srebhan I think this one looks good and is ready. It does not have the sample config structure we use now, were you planning to do that in a follow up?

[ZPascal]

@srebhan Any news from your side?

[ZPascal]

@powersj Is there the possibility to rebase and merge it? We want to consume the new functionality.

[srebhan]

Looks good to me. Sorry for the late reply... Thanks for all your effort @ShiranAvidov and @ZPascal!

[srebhan]

@ZPascal can you please resolve the remaining conflict?

[powersj]

I just pushed to resolve the go.sum conflict, let's see if tests pass

[powersj]

please run go mod tidy and check in changes, you might have to use the same version of Go as the CI

Doesn't look like it, so still need you to push an update after running go mod tidy

[powersj]

@srebhan can you re-reivew, I've cleaned up linter issues, ran make tidy, and moved the sample config out

[telegraf-tiger]

Download PR build artifacts for linux_amd64.tar.gz, darwin_amd64.tar.gz, and windows_amd64.zip.
Downloads for additional architectures and packages are available below.

☺️ This pull request doesn't significantly change the Telegraf binary size (less than 1%)

📦 Click here to get additional PR build artifacts

Artifact URLs

DEB	RPM	TAR GZ	ZIP
amd64.deb	aarch64.rpm	darwin_amd64.tar.gz	windows_amd64.zip
arm64.deb	armel.rpm	darwin_arm64.tar.gz	windows_arm64.zip
armel.deb	armv6hl.rpm	freebsd_amd64.tar.gz	windows_i386.zip
armhf.deb	i386.rpm	freebsd_armv7.tar.gz
i386.deb	ppc64le.rpm	freebsd_i386.tar.gz
mips.deb	riscv64.rpm	linux_amd64.tar.gz
mipsel.deb	s390x.rpm	linux_arm64.tar.gz
ppc64el.deb	x86_64.rpm	linux_armel.tar.gz
riscv64.deb		linux_armhf.tar.gz
s390x.deb		linux_i386.tar.gz
		linux_mips.tar.gz
		linux_mipsel.tar.gz
		linux_ppc64le.tar.gz
		linux_riscv64.tar.gz
		linux_s390x.tar.gz
		static_linux_amd64.tar.gz

[srebhan]

Looks good to me. Thanks for all the work @ShiranAvidov and @powersj!

[ZPascal]

@powersj Thank you for handling the merge conflicts. Also, from side thank you, @ShiranAvidov @srebhan @powersj for the review, the feature and the invested work to deliver the functionality.