Hi @marloii ,
Service Graph Connectors (SGCs), Discovery, and other integrations are used to ingest Configuration Item (CI) data into the CMDB. While these tools are effective for populating infrastructure data, Service Mapping provides additional value by establishing a service-centric view of the infrastructure and its dependencies.
1. Service Graph Connectors (SGCs)
Service Graph Connectors integrate with third-party systems to bring CI data into the CMDB.
Examples:
- Microsoft Intune → imports managed devices such as laptops and mobile devices.
- Cisco Meraki → imports network devices like switches and access points.
- Azure / AWS connectors → import cloud resources such as VMs, load balancers, and storage.
In this case, the external system already knows the assets, and ServiceNow simply synchronizes that information into the CMDB.
2. Horizontal Discovery
Discovery scans the network using IP ranges and credentials to identify infrastructure components.
Examples:
- Discover Windows/Linux servers
- Discover network devices such as routers and firewalls
- Discover databases and middleware
- Identify installed software on servers
This helps build the infrastructure layer of the CMDB.
3. Application Dependency Mapping (ADM)
ADM is part of Horizontal Discovery and identifies relationships between applications by analyzing network traffic.
Example:
If a web server communicates with:
- an application server
- which connects to a database server
Discovery can detect these connections through network ports and traffic patterns.
However, ADM maps dependencies based on traffic, not necessarily based on business services.
What Service Mapping Adds
1. Service-Centric Mapping
Service Mapping identifies all infrastructure and application components that support a specific business service and stores this relationship in the CMDB.
Example:
Online Banking Service
Service Mapping may map:
Online Banking Service
→ Web Server
→ Application Server
→ Database Server
→ Load Balancer
→ Storage
→ Network Components
This creates a service topology showing how everything works together to deliver the service.
2. Agentless Discovery
Service Mapping is agentless, meaning:
- No additional software needs to be installed on target servers.
- It uses credentials and patterns to discover application components.
Example:
Service Mapping can detect:
- Apache / IIS web servers
- Tomcat / WebLogic application servers
- Oracle / MySQL databases
3. Configuration-Based Mapping
Unlike ADM, Service Mapping does not rely only on network traffic (netstat).
Instead, it:
- Uses application patterns
- Reads configuration files
- Identifies processes and ports
Example:
Instead of simply detecting traffic between servers, it can determine:
Service
→ Tomcat application
→ specific database instance
→ messaging queue
4. Dependency Visualization
Service Mapping automatically creates service maps showing how all components interact.
Example use cases:
- Incident Impact Analysis
If a database fails, the service map shows which services are impacted. - Change Risk Analysis
Before making a change to a server, teams can see which services depend on it.
Relationship Between Discovery and Service Mapping
Discovery acts as the foundation for Service Mapping.
Discovery:
- Finds infrastructure CIs
Service Mapping:
- Builds service-level relationships on top of those discovered CIs
Both capabilities are part of ServiceNow ITOM Visibility.
Why Service Mapping Is Valuable
Service Mapping helps organizations:
- Quickly identify which services are affected when a CI fails
- Perform better root cause analysis
- Reduce the risk of outages during changes
- Improve service visibility for operations teams
Example:
If a database server goes down, Service Mapping immediately shows that it affects:
- Customer Portal
- Payment Processing Service
- Reporting Application
Without Service Mapping, teams may only see that a server is down, but not which business services are impacted.
Please Accept the solution if you understood the concept.
