Your completely correct.
For some background we got two teams, one managing the platform/datacenter and other team manage everything for customer applications. So in the eye of the application team they don’t care if the machine is running in DC1 or DC3, they want to monitor customer host/applications.
The platform/datacenter care more because they have to allocate resource, make network changes, security change and for example limit cross-datacenter communication.
So when application-team add more host, they add the host to the folder (with ansbile/API/etc) customerA or customerB. Then the platform/datacenter need to run recurring automation script to say:
Machine1-customerA;DC1;site1-intern
Machine2-customerA;DC1;site1-dmz
Machine1-customerB;DC2;site2-intern
Machine2-customerB;DC2;site2-dmz
If they use other name or administration is not up to date. There are unnecessary error’s.
Automation like https://github.com/wrossmann/add-to-check_mk or https://github.com/tribe29/ansible-checkmk
It would really help if we can make rule in CheckMK to say: CustomerA (regulair expression) run in DC1 site1-intern and CustomerA-DMZ (regulair expression) run in DC1 site1-DMZ and so on. So that no matter what host are added. With will run on the correct site. Not forgetting the production-env/testing-env/develement-env etc.