23 lines
1.0 KiB
Markdown
23 lines
1.0 KiB
Markdown
2024-08-14
|
|
|
|
#logos #vercel #bigcommerce #celigo #replatform #oncall #alerting
|
|
|
|
|
|
With the replatform work, we have several new systems for which the [[Business Solutions Group]] on-call rotation will need to eventually be responsible.
|
|
|
|
## New Systems with Alerting Needs
|
|
Alerting should probably happen for:
|
|
1. The new.logos.com site hosted by Vercel
|
|
2. Celigo data flows when integration fails
|
|
3. BigCommerce order and payment processing failures
|
|
|
|
## Ideas
|
|
Nate suggested a couple of things I agree with.
|
|
### Only low-priority at first
|
|
Only low-priority alerting at first for all replatforming things. Justification: the initial rollout will be pretty minimal and won't serve a lot of customers or orders. It shouldn't alert anyone off-hours to fix anything.
|
|
### Separate on-call rotation at first
|
|
Have a separate on-call rotation for only replatforming things at first. They can:
|
|
1. Refine alerting before we turn on any high-priority alerts
|
|
2. Train the rest of the rotation before we merge the two rotations on replatform things
|
|
|