Discovery runing in Production is advisable

[ravishankerayya]

Hi All

Can somebody tell us some info or best practises running Discovery in the production.

How do we handle the duplicate CI data populated by discovery and slowing the production system and the data quality.

Is it okay to run in stage rather in production what are your thoughts?

Please share your thoughts

thanks

Ravi

[camran · Accepted solution]

There are a couple of best practices here.

Rule of thumb is ...* Never run Discovery on Prod infrastructure from your prod instance at the start.

To manage the duplicate data, you have to normalize and create a business rule to assess existing database 1) Initially class by class. 2) Once mature create the task for each new case.

1- Initially run the discovery from Dev instance to Production infrastructure. Once your CMDB is stable, directly run it from Prod instance to Prod infrastructure.

2- Define and Enforce Configuration policy, that is going to be the track for your discovery.

Policy example: What actions are required for new discovered CIs ? or Updated CIs.

Best practices are after a certain level of maturity, discovered CIs should be through Change management.

Regards

Camran

[ravishankerayya]

Thank you all for the replies.

[Fred Jean]

Hello, I feel that this a subject where ServiceNow doesn't say much either in documentation or in courses.

So I also wonder about Service Mapping configuration.

Should one configure Services in dev or production instance ? (In a situation where were ServiceNow is not yet in production and we are configuring ITOM and ITSM).

If in production we might require custom patterns for instance where it would then be recommanded to  implement and test in dev then move to production before actually being able to create the service. And also that would involve having a production platform ready with Discovery configured to get all required CIs.

So it would seem to make sense to do everything in dev first but then :

• That wouldn't be consistent with the fact that Services need to be approved by Service Owner, and so that approval would involve giving these Service Owners access to dev platform and also enable outbound email to that they can receive the notification for the approval requests.
• How do me then move the created Services in production as this data and not captured in update sets ?
  Would it means XML exports from cmdb_ci_service_discovered (or cmdb_ci_service_auto ?), sa_m2m_service_entry_point, svc_ci_assoc and what other table content would then be needed ?

How does this usually work ? What is the best practise for Service Mapping ?

Regards,