Almost Every infrastructure decision I endorse or regret after 4 years

Re:Almost Every infrastructure decision I endorse or regret ... by mlrtime on Friday February 20, 2026 @07:46AM (#47087344)

Pagerduty: They haven't yet hit that point where PD doubles the prices for them. Or they don't have everyone on the platform, it will be their next Datadog (too expensive)

[ Parent | on HN ]

[dead]

Re:Almost Every infrastructure decision I endorse or regret ... by yowlingcat on Friday February 20, 2026 @05:42PM (#47095019)

Very clever. Our team is small enough right now for this to not be an issue, but I've ran into this issue previously and this feels like a far more practical design to avoid lockin.

[ Parent | on HN ]

Re:Almost Every infrastructure decision I endorse or regret ... by mlrtime on Saturday February 21, 2026 @07:28AM (#47100152)

100%

Anyone implementing PD paging into their company: I highly advise you add a template/interface on top of PD. This will make swapping out later much easier.

[ Parent | on HN ]

Re:Almost Every infrastructure decision I endorse or regret ... by TechIsCool on Friday February 20, 2026 @12:14PM (#47090789)

I agree, 2-3x pricing because you have more people always felt like a cash grab, similar to an SSO Tax. We also have a lot of complex Pagerduty configurations and their APIs are painful. Why do timestamps drift, templates get updated but don't show drift, and identifiers are not the same between UI and API. I regret implementing within Terraform and would rather just let teams manage their own on-call sadly.

[ Parent | on HN ]