Exclusion Issue Post 13.1 Upgrade

[stfconsulting]

Hello, we are having an issue where our exclusion rules were broken after the upgrade. We realized that the format on how exclusions are handled now is different. We put in the exclusions and that fixes everything. We come back 30 min later and the exclusion mask is gone and now all machines are excluded in the entire infrastructure. Is this a known isuse? Version 13.1.0.7034

[Mildur]

Hi stfconsulting,

What did our support engineer tell you in the support case? Our Support team is fully capable of providing you with an answer after they review the situation together with the log files. This is not something we can troubleshoot over the forum.

Please provide a support case ID for this issue, as requested when you click New Topic. Without a case number, the topic will eventually be deleted or closed by the moderators.

Best regards,
Fabian

[lethalmutiny]

I have the same issue. I have Case #08186817 open for this. I provided a copy of my database to the engineer on my case and they were able to replicate it. It is with R&D right now to investigate and resolve.

[david.domask]

Hi lethalmutiny, welcome to the forums.

Thanks for sharing the case number and the status, please let's wait for the conclusion to the case however before posting as noted in the forum rules.

I can see that indeed there is work from the RND side on this, but please continue with Support on the issue.

[nadeemp]

I guess the issue occurs when the rules are configured based on Object Name (rather than Infrastructure Location).

Workaround for the time being: create a Business View group based on VM name property (similar to how monitoring rules were configured in Server Settings), then create an exclusion rule based on this Business View group - Infrastructure Location.