Case 02 / 03 · Current programme

Observability migration

Accountable for completion of an organisation-wide observability migration funded at approximately £2m+, including cross-team dependencies, readiness and practical go/no-go decisions.

London Stock Exchange Group2026–present

Reported outcomeIn flight

legacy monitoring migration

My role

Technical Program Manager and Delivery Lead, accountable for completion and practical go/no-go decisions. Platform specialists own technical design and implementation.

Result / state

The programme is active. Delivery reporting covers accepted routes, open evidence, owner decisions, risks and exceptions.

Operating context

Events, metrics and active log alarms need separate acceptance because each stream has different operational, evidence and cost conditions.

Case record / four parts

How the work moved

01 / Situation

Legacy monitoring paths are moving to a new routing model.

Applications have different event, metric and log-alarm needs, so one blanket migration rule would create gaps and unnecessary cost.

02 / Decision

Give each telemetry stream its own acceptance path.

Events, metrics and log alarms are assessed against their operational use, owner, evidence and destination.

03 / Change

Run the programme from one owned register.

Product owners, platform engineers and application teams work through route decisions, blockers, exceptions and acceptance evidence.

04 / Current state

Report completed decisions and open evidence separately.

The programme remains in flight. This case describes the current delivery controls; final migration results will follow completion.

Public delivery model

Events, metrics and log alarms each need their own acceptance path.

This public model omits internal topology, client identities, staffing and detailed financial information.

Stream 01

Events

Test alert lifecycle and downstream incident behaviour before changing the production source.

Independent acceptance

Stream 02

Metrics

Approve metrics onboarding where an operational use case and cost impact are known.

Evidence required

Stream 03

Log alarms

Identify active alarms, rebuild their equivalents and validate them before legacy retirement.

Parallel proof

Evidence and responsibility

Supported by the evidence

An organisation-wide observability migration funded at approximately £2m+.
Accountability for completion and practical go/no-go decisions.
Cross-team dependencies converted into owners, milestones, risk reviews and closure decisions.

My responsibility

Programme delivery, dependency closure, readiness reviews and practical go/no-go decisions.
Aligning product owners, application leads, architects, observability engineers and external vendors.

Scope boundary

Platform specialists own observability architecture and engineering implementation.
Final programme outcomes will be reported after the active migration is complete.

Source status / Current programme evidence · public detail intentionally bounded · 2026