Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[receiver/azuremonitorreceiver] feat: multi subscriptions support and automatic discovery #36612

Open
celian-garcia opened this issue Dec 2, 2024 · 1 comment · May be fixed by #36467
Open
Labels
enhancement New feature or request needs triage New item requiring triage receiver/azuremonitor

Comments

@celian-garcia
Copy link

Component(s)

receiver/azuremonitor

Is your feature request related to a problem? Please describe.

When a tenant contains multiple subscriptions, if a new one is created you have to create a new receiver.

Describe the solution you'd like

I want to be able to say "take all the subscriptions of the tenant"

Describe alternatives you've considered

Maintaining a config but too painful.

Additional context

For an additional context, I'd like to create a new PR after that to revive the topic of the batch api usage. #29593

The idea is that if you have many subscription with many resources, you can be rate limited by Azure with the current get of Resource metrics. Using the batch API, you don't have anymore the problems of rate limitation. We're using already it from a fork in Amadeus for 1 year and it's promising.

@celian-garcia celian-garcia added enhancement New feature or request needs triage New item requiring triage labels Dec 2, 2024
Copy link
Contributor

github-actions bot commented Dec 2, 2024

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs triage New item requiring triage receiver/azuremonitor
Projects
None yet
1 participant