ITOM deep-dive · LessonBy Sneha I, ServiceNow Trainer, 8 yrs · Published · ServiceNow · all levels
Service Mapping approaches
Map application services accurately with tag based, traffic based and pattern based approaches.
Quick answer
Map application services accurately with tag based, traffic based and pattern based approaches.
Key takeaways
- Top down, tag based and traffic based each suit different estates
- Cloud tags carry the ownership data mapping needs
- Validate maps with application owners before publishing
- Unmaintained maps become misleading quickly
Three approaches
Top down mapping starts from an entry point and follows connections using patterns. Tag based mapping groups cloud resources by tag into an application service. Traffic based mapping infers relationships from observed connections, which is useful where patterns do not cover a technology.
Choosing per estate
Cloud native estates map well with tags because the tags already carry ownership. Traditional data centre estates rely on entry points and patterns. Most organisations end up using two of the three.
Keeping maps trustworthy
A wrong map is worse than no map.
- Review new maps with the application owner before publishing
- Re run mapping after major releases, topology changes
- Watch for CIs added by traffic that are not really part of the service
- Publish only the services you will maintain
Practice challenge
+0 XPStreak ×0
Question 1 of 2
Which approach suits a cloud estate with good tagging?
Frequently asked questions
Does Service Mapping need Discovery?
They are complementary. Discovery finds and populates CIs, Service Mapping builds the service topology on top.
How often should maps refresh?
On a schedule plus after significant change. Static maps drift within weeks in active estates.