Service mapping connects business criticality to infrastructure impact. Criticality is decided at the top, on a business application or service. Changes and failures happen at the bottom, on servers, databases and network devices. Without an accurate map between them, change risk is assessed against whatever the configuration item (CI) record says about itself, and a server supporting a production service can be treated as low risk because someone recorded it as development. A current, top-down service map is what lets criticality flow down to every CI a service depends on.
Business criticality belongs on the business application and the application service, where owners can judge the impact of an outage in business terms. Environment belongs there too: production, test or development.
Change risk assessment and incident prioritisation, though, start from a CI. A change request names a server. An incident names a database. The question each process asks is "what depends on this, and how much does it matter?".
The service map answers that question. It records which CIs deliver which application service, so any process starting from a CI can look up the services above it and take the highest criticality among them.
On one estate of several million CIs, business application environments were believed to be correctly documented, with the infrastructure beneath each environment recorded.
The development environment of one business application had been mapped to infrastructure that actually hosted its production environment. A change was raised against the development environment and classed as low priority, on the reasonable basis that development was low risk.
When the infrastructure was shut down for the change, production went down with it.
It wasn't the first time. The organisation's own client invoked a get-out clause in their contract and left.
We first established what hardware was actually providing each environment, then used custom pattern extensions and top-down, pattern-based service mapping to rebuild the maps from what was really running.
Start from the business application. Record business criticality and owner on the business application. Create an application service for each environment, and set the environment explicitly on each one.
Map each environment top-down. Use an entry point specific to that environment, such as its own web address or load balancer, confirmed by the service owner. Mapping from a shared entry point merges environments.
Check for shared infrastructure. Report on infrastructure CIs that appear in application services from more than one environment. Some sharing is deliberate. Every instance should be known and documented, and the CI should be treated at the criticality of its most critical service.
Don't trust the CI's own environment field alone. Many CIs carry a field describing what they're used for. Compare it with the environment of the services they appear in, and report every disagreement.
| CI says | Service map says | Action |
|---|---|---|
| Development | Supports a production service | Treat as production immediately, then correct the record |
| Production | Supports only development services | Check the map, then correct whichever is wrong |
| Anything | In no service at all | Find its purpose before it's changed |
A map only protects you if the processes read it.
Configure change risk assessment to take the highest criticality among the services above each affected CI, overriding any lower value on the CI itself. Show the impacted services and their environments on the change record, so the approver sees production when production is at risk.
For incidents, use the same lookup to set impact, so a failed server is prioritised by the most critical service it supports.
Track key performance indicators (KPIs) that show whether the maps are doing their job: changes classed as low risk that caused production incidents, and CIs whose own environment disagrees with their services. The first should fall to zero as the second falls.
Environments are rebuilt, migrated and repurposed. A map that was right last year can be wrong now.
Re-run top-down mapping on a schedule, and whenever a change affects the hosting of an application service. Ask each service owner to certify their maps periodically, including the environment of each, and escalate unanswered certifications.
Record in the RACI (responsible, accountable, consulted, informed) that service owners are accountable for what their maps contain, and the configuration management team for how they're built.
For the difference between horizontal and top-down discovery, see our article on horizontal and vertical discovery. For the wider effect of the data model on security and performance, see our earlier service mapping article.
Our discovery and integration coverage review establishes what is missing from your estate view, where, and what it costs during an incident. For service mapping, that includes which critical services lack a current map, and where CI environment and service environment disagree. We scope it with you at an initial consultation.
For a view of the whole configuration management database (CMDB), our two-week CMDB health baseline scores which CIs are trustworthy and which are guesses, in a report you can take to your change advisory board.
Book a CMDB diagnostic call or arrange a meeting with a consultant.
On the business application and its application services. Infrastructure should take its criticality from the services it supports.
It can, though it should be deliberate and documented. Treat it at the criticality of its most critical service.
Usually because the map was built from the wrong entry point, or the environment was set by hand and never checked against what the server actually hosts.
On a regular schedule, and after any change that affects where a service is hosted.
Written by Warren O'Neill, Apex Configuration Group.
Book a free call to discuss how Apex can help you on your journey to a better CMDB