How frequently are service maps updated (service mapping)?

[shank1]

Hello, I see below points in the servicenow official documentation for Service Mapping:

"

Always Accurate and Up to Date:

Once Service Mapping maps a service, it intelligently searches IT infrastructure, applications, and PaaS services for changes that affect the way services are delivered. When Service Mapping detects a change, it updates the related service maps in real time.

Service Mapping also maintains a complete history of service topology that allows users to see changes made to a service between any two points in time.

"

I have 2 questions here:

1. How frequently are the maps updated? 

(What I understand is that, only when the respective discovery schedules run the CI's are updated in the maps or when you run the discovery on the map, it gets updated).

Assuming that based on the discovery schedules, the maps are updated at 1 PM.

Suppose at 2 PM a server is down. So this wont be reflecting on the map right automatically right?

2. Where can I see the complete history of service topology to see the changes made till now.

Thanks !

[Ashish Nahar · Accepted solution]

For the first question : 

After Service Mapping discovers CIs belonging to your application service for the first time, it then runs discovery on CIs again to find changes and updates. You can define how often Service Mapping runs the discovery process for different configuration items (CIs) and updates information about them.

If a server is down at 2am and discovery is running during that period, it will not be able to discover. But your map is more used by event management to show that server is down and based on the impact to the service, it will show up in the color defined.

https://docs.servicenow.com/bundle/madrid-it-operations-management/page/product/service-mapping/task...

For 2nd Question : 

https://docs.servicenow.com/bundle/madrid-it-operations-management/page/product/service-mapping/task...

Details about changes to an application service and to its CIs is stored in the CMDB. Typically, these changes reflect adding or removing CIs from an application service, upgrading or updating CIs, or modifying CI configuration files. The system gathers this data by querying CMDB tables and then creating the change history view. In deployments where Service Mapping is activated, the type of change information Service Mapping queries depends on discovery patterns that Service Mapping uses to discover CIs.

Changes to configuration files are associated with CIs to which these files belong. Maps show configuration file changes as changes to related CIs.

Please mark helpful or correct based on the advise provided

[Chris Ellis]

Looks like I am a year late to the party, however, I would like some further clarification. Let's assume we run ZERO Discovery (ad-hoc, schedules, etc.) during the day. Using shanks example above, if a device goes down at 2pm in the afternoon, will Service Mapping be able to "detect" it and remove that device from the associated service maps as well as detect when the device is back online? If so, how often does that detection take place?

[shank1]

Chris, have a look into this for your requirement

[Ian Mildon]

If the maps are marked as Operational, then Discovery will run and update them daily