Logbot (Aug 06 2025 at 20:22): Logbot (Aug 06 2025 at 20:22):We're LIVE at the historic Oriental Theater in Denver, CO with Nora Jones. Nora is the founder of Jeli.io, recently acquired by PagerDuty and she's been shaping the way we think about reliability, incident response, and human-centered engineering for years.
We get into the real story behind the deal. Not just the headline, but what it’s like selling your company, what it takes to actually integrate a product into a larger platform, how customers responded, what changed for her team, and why her new role at PagerDuty is basically everything she was building Jeli for. :link: https://changelog.fm/653
| Ch | Start | Title | Runs |
|---|---|---|---|
| 01 | 00:00 | This week, LIVE on The Changelog | 01:09 |
| 02 | 01:10 | Sponsor: Auth0 | 01:29 |
| 03 | 02:45 | Start the LIVE show! | 01:33 |
| 04 | 04:18 | The Jeli.io journey and acquisition | 02:17 |
| 05 | 06:35 | How did you feel about the acquisition process? | 01:38 |
| 06 | 08:13 | How do you balance your desire for an exit with the needs of the industry you serve? | 01:16 |
| 07 | 09:29 | Does Jeli as a platform still exist today in PagerDuty? | 02:51 |
| 08 | 12:20 | Response from PagerDuty customers when they got access to Jeli? | 05:17 |
| 09 | 17:37 | How do you juggle managing pricing, product, and growth? | 02:50 |
| 10 | 20:28 | How are you thinking about AI at PagerDuty? | 02:39 |
| 11 | 23:07 | Sponsor: CodeRabbit | 02:43 |
| 12 | 25:50 | Let's talk about "novel incidents"? | 01:21 |
| 13 | 27:11 | How does PagerDuty think about AI agents in incidents? | 02:11 |
| 14 | 29:22 | Are you talking with users? Any examples of novel incidents? | 01:15 |
| 15 | 30:37 | Any "favorite" incidents that stand out? | 01:56 |
| 16 | 32:32 | Tell us more about your team at PagerDuty? | 03:48 |
| 17 | 36:20 | How is growth at PagerDuty different than growth at Jeli? | 02:24 |
| 18 | 38:44 | How does AI impact your product roadmap? | 04:04 |
| 19 | 42:49 | Will an increase in AI reduce the overall subject matter expertise? | 03:14 |
| 20 | 46:02 | Do you use any tools that provide insights into your team's expertise? | 03:56 |
| 21 | 49:58 | Sponsor: Depot | 02:14 |
| 22 | 52:12 | What's exciting? What's interesting? | 02:37 |
| 23 | 54:49 | What's coming up next at Pager Duty? | 01:51 |
| 24 | 56:40 | Q&A Session | 00:31 |
| 25 | 57:11 | Nabeel - What was the reaction to the acquisition from the team at Jeli? | 02:33 |
| 26 | 59:44 | James - How does PagerDuty think about helping organizations with incidents? | 02:48 |
| 27 | 1:02:32 | Kendell - Do you see yourself starting a new company anytime soon? | 01:25 |
| 28 | 1:03:58 | Jesse - How did you get your first enterprise customer at Jeli? | 01:52 |
| 29 | 1:05:50 | Matt - How does PagerDuty think about facilitating communication and knowledge transfer within its customer's organizations? | 04:05 |
| 30 | 1:09:54 | Jim - How did you learn reliability engineering? | 02:33 |
| 31 | 1:12:28 | Buy Nora's book on Chaos Engineering | 00:12 |
| 32 | 1:12:40 | Closing thoughts and stuff | 02:45 |
Adam Stacoviak (Aug 06 2025 at 20:23):There is an EPIC treat for ++ members
Tim Uckun (Aug 14 2025 at 05:26):Here is a product idea for Nora.
Build an agent that's hosted at the customer's premises. Once an incident occurs the agent downloads all the available information including logs and traces and whatnot and is tasked to create a test which would replicate the incident. It runs in a container with a blank database or some sample staging data and keeps writing tests until the same error comes up. Of course it could also be a kube env with supporting services and such too.
Last updated: Aug 18 2025 at 01:38 UTC