VeeamOne is alerting on CloudConnect repos for our Reseller's companies

[ilogsdon]

Hello, We encountered an interesting problem with the way VeeamOne, CloudConnect VBRs, and the VSPC interact. I'm curious if anyone else is set up the same way and has encountered this, and how they have dealt with it.

We have VeeamOne monitoring two cloudconnect vbrs. We have most of our cloudconnect companies set up as vCloud Director tenants instead of Native tenants. Because of this (not sure why) VeeamOne is unable to see any of the vCD tenant repos or alert on them. What we just found out this week is that VeeamOne can see and alert on ANY Native tenant on the CC VBRs, this includes every tenant our Resellers set up as well.

We have already filtered out all our reseller's companies from our VSPC alerting and they have set up their own alerting through their VSPC reseller portal. How can we prevent VeeamOne from alerting on their repos? The only way I've found is to manually add each repository to the Excluded Objects list of the alert rule but that's a terrible solution and requires way to much manual intervention each time our Resellers add a new company.

So, I guess I have two questions...
1. How have other people dealt with this problem and is there a recommended best-way to set this up?
2. We prefer VeeamOne over the crappy VSPC alerting engine anyway so how can we get VeeamOne to see all the vCD tenant repos as well so we can keep all our alerting in VOne?

[wishr]

Hi Isaac,

Thanks for posting.

We'll take some time to take a look at this usage scenario in detail and once done will report back with answers and recommendations.

Thanks

[Vitaliy S.]

Also, can you please clarify what is that crappy in the VSPC alerting engine? This would help us to improve it down the road.

[Vitaliy S.]

Because of this (not sure why) VeeamOne is unable to see any of the vCD tenant repos or alert on them.

Isaac, our QA team was not able to reproduce the issue you're describing, so either more details about your setup or a support case is required here.

[wishr]

Hi Isaac,

Regarding disabling the alarms for reseller's repositories, currently, the only workaround is to use exclusion rules, as you mentioned. We'll see what can be improved to make it easier in the next Veeam ONE versions.

Thanks