Chain monitoring with a traffic light: one status the whole organisation gets

Most monitoring shows the technology: graphs, metrics, separate alerts per system. For an admin that is fine, but the rest of the organisation gets nothing out of it. Chain monitoring flips that around. Instead of separate parts you show the chain, and you translate that chain into a traffic light: green, amber or red. This post explains how that works and why a traffic light is the status everyone understands.

TL;DR

• Chain monitoring looks at the whole chain of systems that together deliver a service, not at separate servers.
• The traffic light principle translates technical status into a colour: green, amber or red.
• You draw your chain, connect your existing monitoring to it, and let a colour come out.
• The dashboard can be shared with no login, so everyone sees the same status.
• ITSM Radar from the ServiceChanger family will make this possible and is coming soon.

What chain monitoring is

A service that touches your users almost never rests on a single system. Take signing in: it hangs on your identity provider, on a network connection, on a database, and sometimes on an external party. If one link fails, the user notices the service does not work, even though each separate part still shows green in its own dashboard.

Chain monitoring looks at that connection. You record which systems together form a service and in what order they depend on each other. With that you see not just whether a server is running, but whether the chain as a whole does its job. That is the difference between "the database responds" and "users can sign in".

The traffic light principle

The problem with classic monitoring is not too little information, it is too much. A director or a first-line agent does not need to read a CPU graph. They want to know: does it work or not?

For that you use a traffic light. Every link and every service gets a colour:

Colour	Meaning	What you do
Green	The chain works as it should	Nothing, just watch
Amber	There is a warning or a link is struggling	Look before it turns red
Red	The service is disrupted	Act now

The strength is in the simplicity. A traffic light needs no explanation. The technology underneath can be complex, the outcome is a colour everyone gets straight away.

How you build it

You build chain monitoring with a traffic light in three steps, and you throw away nothing you already have.

1. Draw the chain. Map which systems together deliver a service and how they depend on each other. Start with one or two services that really matter, not everything at once.
2. Connect your existing tools. You probably already monitor with SCOM, Azure Monitor or something else. Keep those. You put an overlay on top that pulls in the signals, instead of rebuilding everything.
3. Translate to a colour. Per link you decide when something is green, amber or red. Those statuses roll up into the traffic light for the whole service.

So the idea is not a new monitoring tool that replaces your old one. It is a layer on top that translates the status of what you already measure into a chain and a colour.

A status with no login

A dashboard only admins can open does not solve the communication problem. During a disruption the service desk wants to know what is going on, a department head wants to know if it hits their service, and management wants an honest picture without bothering anyone.

That is why chain monitoring comes with a status you can share without a login. Anyone with the link sees the same traffic light, at the same moment. No account, no role, no briefing first. That saves a lot of phone calls during an outage, because the answer is already on the screen.

How this fits with ServiceChanger

This is the positioning of ITSM Radar, a separate product in the ServiceChanger family. Where ServiceChanger itself is about automating access and licensing, ITSM Radar is about making your IT chain visible through a traffic light. It is an overlay on your existing monitoring such as SCOM and Azure Monitor, not a replacement for it. ITSM Radar is not available yet and is coming soon.

FAQ

Does chain monitoring replace my current monitoring? No. You keep SCOM, Azure Monitor or whatever you use. The chain layer pulls the signals from those and translates them into a traffic light. Your old tools stay the source.

Why a traffic light and not just graphs? Graphs are for the admin looking for the cause. A traffic light is for everyone who only wants to know if it works. You need both, but for communication the colour wins.

Why share with no login? Because a status only works if the people who need it can reach it. During a disruption you do not want people to sign in first or call for the latest state.

Can I use ITSM Radar now? Not yet. It is a separate product in the ServiceChanger family and is coming soon.

Further reading

• Shift-left on the service desk for how to move work to the earliest point in the chain.
• Service desk strategy for the wider story on how to set up your service desk.

Next step

Want to see your IT chain in a traffic light the whole organisation understands? ITSM Radar from the ServiceChanger family will make this possible and is coming soon. Get in touch if you want an early look.