we are trying to monitor an Azure environment with around 50 subscriptions in the same tenant.
If I omit the subscription id in the azure ruleset completely, we get no information about any ressource groups or vms.
If I enter a subscription ID, I get the data for that subscription. (obviously )
As it is not possible to enter multiple subscription ids in the same ruleset, i tried to create multiple rules for the same azure dummy host, but it is only possible to assign one rule per host.
Do I need to create 50 dummy hosts now to assign 50 rules with the corresponding subscription IDs correctly ?
Is there a workaround or am I making a general mistake ?
afaik so far - yes.
It makes sense to only request the first 3 things that are not subscription ID dependent only once (or maybe even on a separate dummy host) and then for each subscription ID, another dummy host with one special agent config rule.
(for future reference, in 2.2 the first 3 are the following and are by default not selected:
)
But it would be interesting @martin.hirschvogel is that “works as designed” and is there maybe a feature on the roadmap for larger customers that have a few more subscription IDs and don’t want dozens/hundreds of subscription IDs configured separately?
I think back in 2018, when this was initially developed, it was probably not considered. It is clearly a painpoint now, especially with every cloud infra getting larger with companies scaling via subscriptions.
No need to create a dummy host anymore, that is being done automatically for you.
Handling thousands of subscriptions (Azure) or accounts (AWS) is on the roadmap. In AWS, we have a good idea how this could be solved. But it requires basically a different configuration both in AWS and on Checkmk, which can be managed also via the new config concept.
With the new DCD architecture, we also likely don’t have to worry too much about too many DCD connections. But that one is currently not an easy project.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.
)
