Live Service
Live Service
Live service work is how we handle problems with the running platform: bugs,
weird data, and anything else that means the service isn’t behaving as it
should.
What this covers
These pages cover issues in the platform team’s remit:
- data pipelines
- Manage
- Check and Provide
- DevOps
They do not cover the remit of the Consumers or Design teams.
Issues typically reach us from:
- local planning authorities (LPAs) getting in touch
- someone in the team, or another team, noticing something that looks wrong
- alerts in
#planning-data-alerts
Live service or incident?
If significant parts of the service are down or returning incorrect data,
that’s an incident. Follow
Managing technical incidents
in the run book, which covers incident roles, comms and post-incident review.
Everything else follows the triage process below. The two meet at the point
where an issue is prioritised as P1 or P2 - at which point it becomes an
incident and moves to the run book.
Key pages
- Live service triage and prioritisation -
how an issue moves from being noticed to being fixed - Raising a live service ticket -
where to raise an issue and what a good ticket contains - Debugging live services
- Metrics and reporting
Related
- Managing technical incidents
- How to resolve certain issues -
run book procedures worth trying during initial investigation - Data quality analysis and investigations -
for weird data issues