I want to update the missing attributes information in CMDB for Application services

Bhaskar Palle1
Tera Contributor

Hi Team,

 

I have some missing attributes in CMDB for application Services. Key fields are not updated (Empty) i want to get them updated by Service Owners, what is the best approach to get the updated in CMDB.

 

Thanks

Bhaskar

1 ACCEPTED SOLUTION

CMDB Whisperer
Mega Sage
Mega Sage

The prescribed method for this is to use CMDB Health dashboard.  Basically this involves:

  1. Identifying the fields you are interested in as Recommended Fields for the specific class you are in need of.
  2. Enable the CMDB Completeness job to run on a nightly basis. 
  3. You can drill to the completeness dashboard to show the specific CIs (by class) that are marked as missing Recommended Fields.
  4. If desired, you can also have this automatically create Tasks that are automatically assigned to the data owner for the CI.  Since you can only configure this setting globally, not per class, the recommended standard would be to assign the tasks to the Managed by Group or Managed by (user) field, since that is, by definition, the data owner of the CI.
  5. Be careful with auto task creation.  It will create individual tasks for each CI!  That's a lot of tasks for users to manage, and generally doesn't provide a great user experience.  You may need to tweak this feature or avoid it entirely for that reason.  My recommendation would be to start without tasks first, or at the very least start by assigning it to the configuration managers so end users don't end up overwhelmed.  Then reassign them to the data owners judiciously.
  6. Start small with recommended fields, just one or two of your most critical fields for each class, then add more once you have had success closing the completeness gap. 
  7. Use health inclusion rules to make sure you are measuring only the CIs you can manage, or else this can get overwhelming really fast.  Each health result will be for a single CI and will have ALL of the recommended fields that are missing.  Thus if you define too many recommended fields you increase your chances of getting a hit, driving down your overall completeness metric, and making it much more difficult to see measurable results of your remediation!

The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.

View solution in original post

1 REPLY 1

CMDB Whisperer
Mega Sage
Mega Sage

The prescribed method for this is to use CMDB Health dashboard.  Basically this involves:

  1. Identifying the fields you are interested in as Recommended Fields for the specific class you are in need of.
  2. Enable the CMDB Completeness job to run on a nightly basis. 
  3. You can drill to the completeness dashboard to show the specific CIs (by class) that are marked as missing Recommended Fields.
  4. If desired, you can also have this automatically create Tasks that are automatically assigned to the data owner for the CI.  Since you can only configure this setting globally, not per class, the recommended standard would be to assign the tasks to the Managed by Group or Managed by (user) field, since that is, by definition, the data owner of the CI.
  5. Be careful with auto task creation.  It will create individual tasks for each CI!  That's a lot of tasks for users to manage, and generally doesn't provide a great user experience.  You may need to tweak this feature or avoid it entirely for that reason.  My recommendation would be to start without tasks first, or at the very least start by assigning it to the configuration managers so end users don't end up overwhelmed.  Then reassign them to the data owners judiciously.
  6. Start small with recommended fields, just one or two of your most critical fields for each class, then add more once you have had success closing the completeness gap. 
  7. Use health inclusion rules to make sure you are measuring only the CIs you can manage, or else this can get overwhelming really fast.  Each health result will be for a single CI and will have ALL of the recommended fields that are missing.  Thus if you define too many recommended fields you increase your chances of getting a hit, driving down your overall completeness metric, and making it much more difficult to see measurable results of your remediation!

The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.