Discovery Implementation - Dev, UAT & Prod

[pauladams]

Hello Experts,

We are planning to implement Discovery soon and have questions regarding the MID Servers, CIs and the updatesets across Dev, UAT and Prod instances.

1) Do we need to capture all the configuration - Discovery Schedules, Probes, Sensors, Patterns etc. in update sets in Dev?

2) A MID server can only communicate with one instance. Do we need separate MID servers for Dev, UAT and Prod? Whats the best practice?

3) Do we run discovery separately from the scratch in Dev, UAT and Prod? or Do we import the data we have in Dev in UAT and then schedule the subsequent discovery?

Thanks

Pa

[Raj68]

Hi,

go through below link it will help you in your requirement:

https://community.servicenow.com/community?id=community_blog&sys_id=e41daea5dbd0dbc01dcaf3231f96197b

Discovery Best Practices :

https://community.servicenow.com/community?id=community_blog&sys_id=4efc26a5dbd0dbc01dcaf3231f96191a

NOTE: Mark correct or helpful if it helps you.

 Warm Regards,

Raj patel

[Snehal Pawar]

Hi,

You can refer the below link.

https://docs.servicenow.com/bundle/london-it-operations-management/page/product/discovery/reference/r-discovery.html

https://community.servicenow.com/community?id=community_question&sys_id=8c211be9dbdcdbc01dcaf3231f96196b

Mark it correct or helpful if it helps you.

Thanks,

Snehal.

[tim_broberg]

1. Capture cconfig in dev? You will want to capture any changes from the Out of the Box (OOB) configuration in an update set and import them up the chain to test and prod.
2. Separate mids? Yes, mids support only one instance, so separate mids for dev / test / prod.
3. Separate discovery or import CIs? Probably separate discovery unless you're manually updating CIs, but up to you.

    - Tim.