Add service alerting using PagerDuty
Configure PagerDuty for your microservice by setting up users, schedules, escalation policies and alerts in the alert-config repository.
Create a platform readiness assessment (PRA) page
Create and maintain a PRA in Confluence so your microservice can pass the Change Approval Board (CAB) and go live with confidence.
All new microservices must pass a Change Approval Board (CAB) before they receive Production traffic.
A PRA is a quality check that confirms your service:
- follows MDTP best practices and opinions
- won’t disrupt existing services or platform infrastructure
Why your PRA is important
Create your PRA as you start building the microservice and make sure the team knows the criteria.
- Increase the chance of a smooth peer review
- Avoid costly rework
- Prevent launch delays caused by a failed CAB
Create your PRA
- Use the Confluence PRA template.
- Add the microservice name to the page title field.
- Select Publish.
Your PRA is stored in the PRA Confluence space and should be updated as development progresses.
Next steps
- Speak to a centre tech lead about the PRA requirements.
- Engage the Customer Insights Platform (CIP) team to align audit events with HMRC standards.
- Add all PRA work to your backlog and prioritise it for completion before peer review and launch.
- Deploy to Production early and throughout development.
- Develop and test the service, updating the PRA as you go.
- Complete a self-assessment.
- Get a peer review from a tech lead in another team.
- Pass a CAB.
Need support?
Ask in #team-platdocs on Slack.
Got feedback?
We’re always improving our documentation. Share your feedback with the team channel above.
Add service alerting using PagerDuty
Configure PagerDuty for your microservice by setting up users, schedules, escalation policies and alerts in the alert-config repository.
Create a platform readiness assessment (PRA) page
Create and maintain a PRA in Confluence so your microservice can pass the Change Approval Board (CAB) and go live with confidence.
All new microservices must pass a Change Approval Board (CAB) before they receive Production traffic.
A PRA is a quality check that confirms your service:
- follows MDTP best practices and opinions
- won’t disrupt existing services or platform infrastructure
Why your PRA is important
Create your PRA as you start building the microservice and make sure the team knows the criteria.
- Increase the chance of a smooth peer review
- Avoid costly rework
- Prevent launch delays caused by a failed CAB
Create your PRA
- Use the Confluence PRA template.
- Add the microservice name to the page title field.
- Select Publish.
Your PRA is stored in the PRA Confluence space and should be updated as development progresses.
Next steps
- Speak to a centre tech lead about the PRA requirements.
- Engage the Customer Insights Platform (CIP) team to align audit events with HMRC standards.
- Add all PRA work to your backlog and prioritise it for completion before peer review and launch.
- Deploy to Production early and throughout development.
- Develop and test the service, updating the PRA as you go.
- Complete a self-assessment.
- Get a peer review from a tech lead in another team.
- Pass a CAB.
Need support?
Ask in #team-platdocs on Slack.
Got feedback?
We’re always improving our documentation. Share your feedback with the team channel above.
Add service alerting using PagerDuty
Configure PagerDuty for your microservice by setting up users, schedules, escalation policies and alerts in the alert-config repository.
Create a platform readiness assessment (PRA) page
Create and maintain a PRA in Confluence so your microservice can pass the Change Approval Board (CAB) and go live with confidence.
All new microservices must pass a Change Approval Board (CAB) before they receive Production traffic.
A PRA is a quality check that confirms your service:
- follows MDTP best practices and opinions
- won’t disrupt existing services or platform infrastructure
Why your PRA is important
Create your PRA as you start building the microservice and make sure the team knows the criteria.
- Increase the chance of a smooth peer review
- Avoid costly rework
- Prevent launch delays caused by a failed CAB
Create your PRA
- Use the Confluence PRA template.
- Add the microservice name to the page title field.
- Select Publish.
Your PRA is stored in the PRA Confluence space and should be updated as development progresses.
Next steps
- Speak to a centre tech lead about the PRA requirements.
- Engage the Customer Insights Platform (CIP) team to align audit events with HMRC standards.
- Add all PRA work to your backlog and prioritise it for completion before peer review and launch.
- Deploy to Production early and throughout development.
- Develop and test the service, updating the PRA as you go.
- Complete a self-assessment.
- Get a peer review from a tech lead in another team.
- Pass a CAB.
Need support?
Ask in #team-platdocs on Slack.
Got feedback?
We’re always improving our documentation. Share your feedback with the team channel above.