configuration file tracking belong to certain application on some Linux hosts

[Jae Young]

Hi Expert,

Question regarding the Configuration File tracking on horizontal Discovery:

I am looking for a way of setting up configuration file tracking on each different group of Linux host respectively (per its main service base)

for example, 
Linux server farm A is for mail service
Linux server farm B is for http service
Linux server farm C is for rsyslog

I'd like to setup configuration file tracking of main service on linux hosts only at farm A,     http service on linux hosts only at farm B......etc

The intent is to avoid unnecessary load across all Linux host by tracking the conf file of the main service for each hosts

I'm wondering if this could be technically feasible 

[Rahul Priyadars]

Hi Jaye

Hope you have explored the docs. File tracking is possible using CMDB class - cmdb_ci_config_file_tracked

https://docs.servicenow.com/bundle/quebec-it-operations-management/page/product/discovery/concept/tracked-config-files.html

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1002122

Regards

RP

[Dustin D]

We are trying to implement the same solution.

Following the documentation, we've created a new CI Class (child of Server CI Class), discovery pattern, and CI classification. We also defined the configuration files we want to track in the "Tracked Files" tab in the discovery pattern. When we launch discovery the CI is successfully classified as our new CI class, however it never attempts to discover the tracked configuration file.

We already have configuration file tracking working with an out of the box class (Linux Server). What are we doing wrong here?