Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi,
I have created Service Mapping for 2 Applications. I have created an Incident for 1 critical server is down.
I am able to see that the Incident is reflecting in the dependency maps. What I don't understand is how an Application owner get to know that the Server issue will impact his application or for a Critical Server or a Network issue might impact lot of applications. How an Application owner get to know now from this Service Mapping that his Application will also get impacted. Is there anything that I need to configure.
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hey @JagadishwarB
What you're seeing is actually the expected behavior of Service Mapping.
Service Mapping's primary purpose is to discover application dependencies and perform impact analysis. It helps answer questions such as:
Which business applications depend on this server?
Which databases, load balancers, or network devices support this application?
If a CI fails, which business services are impacted?
When you created an Incident for the critical server, Service Mapping correctly identified the relationship and displayed the Incident on the dependency map. However, Service Mapping does not automatically notify the Application Owner that their application is impacted.
Think of it this way:
Business Application (Online Banking)
│
Application Service
│
Application Server
│
Database Server
│
Network Device
If the Application Server goes down:
- An Incident is created against the server CI.
- The dependency map highlights the failed server.
- Service Mapping can trace the relationship and determine that the Online Banking application is impacted.
- However, the Application Owner will not automatically receive an email, Teams message, or notification unless additional functionality has been configured.
This is because Service Mapping is responsible for impact visualization, not stakeholder communication.
How do Application Owners normally get notified?
In most customer implementations, Service Mapping is combined with other ITOM/ITSM capabilities.
1. Flow Designer or Notifications
A Flow Designer flow or Notification can be configured to:
Trigger when an Incident is created for a critical CI.
Traverse the CMDB relationships to identify the impacted Business/Application Service.
Read the Service Owner, Business Owner, or Application Owner from the service record.
Automatically send an email, Microsoft Teams message, or Slack notification.
The flow would look something like:
Incident Created
↓
Get CI
↓
Identify impacted Business/Application Service
↓
Retrieve Service Owner
↓
Send Notification
Without this automation, no notification is sent automatically.
2. Event Management + Service Mapping
This is probably the most common ITOM implementation.
Monitoring Tool
↓
Event
↓
Alert
↓
Affected CI
↓
Service Mapping
↓
Impacted Business Services
↓
Notifications / Service Health
Instead of waiting for someone to manually identify the impact, Event Management uses the service map to determine which services are affected and can notify the appropriate owners.
3. Service Health Dashboard
Many organizations use Service Health along with Service Mapping.
When a critical infrastructure component fails:
The Business/Application Service health changes from Healthy to Degraded or Critical.
Application Owners can immediately see that their service is impacted.
Operations teams can identify all affected services from a single dashboard.
This provides visibility even if email notifications are not configured.
4. Major Incident Management
For P1/P2 incidents, Service Mapping becomes even more valuable.
Because Service Mapping already knows the dependencies, ServiceNow can determine:
Which Business Services are impacted.
Which Application Owners should be informed.
Which Support Groups are responsible.
Which business stakeholders should receive communications.
Many organizations automate these notifications as part of their Major Incident process.
Is there anything that needs to be configured?
Yes, if your expectation is that the Application Owner should automatically know that their application is impacted, additional configuration is required.
Typically, you would configure:
Service Owner or Application Owner on the Business/Application Service.
Flow Designer or Notifications to notify those owners.
Event Management (if using alerts instead of incidents).
Service Health dashboards for real-time visibility.
Major Incident workflows for enterprise-wide communication.
************************************************************************************************************************************
If this response helps, please mark it as Accept as Solution and Helpful.
Doing so helps others in the community and encourages me to keep contributing.
Regards
Vaishali Singh
Servicenow Developer
Linkedin - https://www.linkedin.com/in/vaishali-singh-2273361bb
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
8 hours ago
I mean to say that Application owner can view the service mapping and there itself if he can view there is an issue with the App Server or Database. It becomes Red wherever the issue is on the Service mapping itself. Not by email. Is there any workspace where Application owner comes to know about this?
