Discovery marks VMware vCenter CIs that no longer exist as stale, which takes precedence over the CMDB Health staleness rule defined for the CI. These CIs health results source is set by the instance to Cloud Discovery.

geet
Tera Guru

‎07-20-2022 11:03 AM

Hi,

Can someone please explain the meaning behind this message.

Please find attachment to understand the question.

 

 

 

Preview file
69 KB
0 Helpfuls
  • 1,154 Views
1 REPLY 1

Fabian Kunzke
Kilo Sage
Kilo Sage

‎07-26-2022 01:00 AM

Hey,

This info message is a bit confusing. Let me split it up in 2 meanings:

1) Generally speaking your VMWare integration will mark CIs as stale, if they do not longer exist within VMWare VCenter. This is the same as if the CMDB Health would mark it as stale.

2) The CMDB Health staleness rule will mark anything as stale after the defined time.

These are the two rules which could lead to something being marked as stale. However, if VMWare finds something to be stale, it will overrule the CMDB Health staleness. If VMWare finds something to not be stale it will overrule the CMDB Health staleness as well.

This message "just" says: Hey, just remember, if you are using VMWare, CIs from VMWare may get marked stale no matter what you configure here.

Regards

Fabian