Earlier this year, we shipped a number of changes to make it faster to calculate who's on call.
We cut our CPU usage by 50% with some simple changes, but struggled to make a meaningful difference until we gave it to Opus 4.6 🧵 (1/7)
@jonas Factoring in culture and controls, it doesn’t seem that wild to me.
Obvs this is great twitter fodder as stated, but I can imagine an eng org as mature as intercom isn’t going to blindly set the target without some back pressure/constraint around reliability etc.
Got it (and sorry for the delay here). This is totally a gap on behalf, but one that we'll be closing in the not-too-distant future. Two key developments we're thinking about:
- Heartbeat monitoring / pingdom-esque checks so you can automatically display uptime, latency, etc.
- Additional status page checks, so you can automatically show the status of services/companies you depend on.
Will keep you posted!
@ouraring please can you fix some basics of activity detection? You know my location, and suggesting “Downhill skiing” as an activity when I was riding a bike in sunny California seems like such a miss for an otherwise epic product.
Writing a post-mortem shouldn’t require a memory test.
Our new post-mortem editor puts incident context and built-in AI right where you’re writing, so the story comes together without the tab shuffle.
See what other features we've added: https://t.co/K9RzduCeKv