Staleness metric not available for Application class and child classes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2022 12:09 PM
We have our Health Inclusion Rules set on the base Configuration Item class (cmdb_ci). We can see that all 5 inclusion rules are on most child classes as well. However, for a class like Application and it's child classes, we don't see the staleness rule inherited from the base cmdb_ci class.
We want to be able to track staleness on child classes of the Application class like IBM Webpshere, IBM Websphere MQ, Database Instance, MSFT SQL Instance, etc.
Is there a setting or property that determines which health metrics can be used for a class?
I've added a couple screenshots for what we are seeing.
- Labels:
-
Data Health Tools

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2022 03:00 AM
Hi,
Just check in your condition builder if you have used Class 'is a' application. If you use just 'is' then it will pick only application class.
Regards,
Vivek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2024 04:14 AM
Is the issue already been fix with the staleness metric in application class?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2024 08:51 PM
@Glenn11 This is not a bug, probably some misconfiguration. if you are facing the issue I would cross check there is no staleness rule defined already on that class by going to cmdb_health_config table directly.