Details
-
Story
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Content Mngmt 6, Content Mngmt 7
-
8
Description
eWe need an operations run book covering the main operational aspects of the A/B/n testing back-end (service). See also these links to some background on ops run books, what it is, why it's needed and how to write one and an example/template run book.
Some main goals of the run-book are:
- Define and document a process to share knowledge and reduce dependencies on individuals
- Prevent production incidents, identify and fix problems before customers become aware
- Enable us to react quickly and efficiently to production incidents
- Clear and efficient procedure to restore service
- Safe operational procedures for standard tasks (on-/off-boarding, backup/restore, upgrade, ...)
Aspectes to cover:
- Monitoring and alerting. See https://wiki.magnolia-cms.com/display/DEVINT/ABn+Testing+monitors+and+metrics
- Cost control
- Data retention and deletion of old data
- License expiry: do we warn customers ahead of time?
- Quality of service
- Does the pipeline run regularly and without errors?
- Are page visits / conversions processed correctly and timely?
- DymamoDB record size limits
- Read / write rate
- API gateway errors / response times
- Logging: how to access, aggregate, collate, read. What to look out for
- Incident management: process, points of contact, response times
- On / off boarding customers
- Releases and deployment
- how to do new releases, deployments?
- backwards compatibility / versioning
- staging / testing
- Backup / restore
- Regular maintenance tasks
- Internal beta (for the validation part see https://jira.magnolia-cms.com/browse/ABTEST-454?focusedCommentId=263755&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-263755)
- ...?
Checklists
Acceptance criteria
Attachments
Issue Links
- relates to
-
ABTEST-409 Customer onboarding process
-
- Closed
-
- mentioned in
-
Page Loading...
- Wiki Page
-
Wiki Page Loading...