text stringlengths 0 1.8k |
|---|
[4804.24 --> 4805.00] New hole. |
[4805.20 --> 4805.84] New fiber. |
[4806.58 --> 4807.22] New equipment. |
[4808.56 --> 4808.96] Yeah. |
[4809.06 --> 4811.12] At least you're getting to use that WAN fill over though. |
[4811.50 --> 4812.16] I do actually. |
[4812.16 --> 4812.88] On your unify system, which is awesome. |
[4812.88 --> 4813.00] I do. |
[4813.00 --> 4813.02] I do. |
[4813.38 --> 4813.76] Yeah. |
[4813.88 --> 4816.78] Not load balancing yet, but I'm working towards it. |
[4816.78 --> 4817.78] I'm sure you'll be... |
[4817.78 --> 4817.92] Yeah. |
[4820.16 --> 4820.72] All right. |
[4820.72 --> 4822.20] We got to reel this in. |
[4822.26 --> 4823.50] What's the summary here, Gerhard? |
[4823.58 --> 4825.22] What's the takeaway from this? |
[4825.30 --> 4828.14] The summary is that now I have two WAN connections. |
[4831.78 --> 4833.04] You've already said that part. |
[4833.12 --> 4833.82] What's the takeaway? |
[4834.58 --> 4835.88] What's the takeaway here? |
[4835.94 --> 4836.88] You need two of each. |
[4837.96 --> 4839.48] Two of everything. |
[4841.92 --> 4842.98] Except your wife. |
[4843.06 --> 4844.22] You only want one of us. |
[4844.24 --> 4844.82] There you go. |
[4844.82 --> 4845.64] That's such a joke. |
[4845.80 --> 4849.42] So I think we should do Gitpod and Codefaces. |
[4851.90 --> 4852.66] Of course. |
[4853.24 --> 4854.18] Yeah, because you never know. |
[4854.68 --> 4856.36] Kubernetes, Edfly, I hope. |
[4856.94 --> 4857.48] And Renda. |
[4859.26 --> 4860.16] That's how we roll. |
[4860.56 --> 4863.22] Well, I can't agree with the N+. |
[4863.22 --> 4864.38] I mean, that is smart. |
[4864.56 --> 4866.86] I mean, you can never have enough. |
[4867.04 --> 4869.40] Well, that was actually coined best in the movie Contact. |
[4869.70 --> 4870.34] Anybody remember that? |
[4871.00 --> 4872.38] Well, I'd build one when you could build two. |
[4872.38 --> 4874.20] I think I've had enough fun. |
[4874.20 --> 4875.46] I mean, I'm laughing. |
[4875.58 --> 4876.12] You might play. |
[4877.86 --> 4878.96] Yeah, I'll be right back. |
[4883.08 --> 4883.56] I'm hiding. |
[4883.62 --> 4885.78] I'll be r |
[4885.78 --> 4886.42] byb GH in the audience. |
[4886.50 --> 4887.02] What's going on? |
[4887.16 --> 4887.24] Yeah. |
[4887.34 --> 4888.80] I'll be right back. |
[4888.90 --> 4889.18] Bye. |
• Discussing the second Kaizen series, 2.5 months after episode 10 |
• Reviewing an incident involving DNSimple tokens and Cert Manager |
• Using Incident.io for incident management and tracking |
• Integrating Incident.io with Slack for easier access to past incidents |
• Sharing knowledge and distributing incident information between team members |
• Discussion of incident management and how the team uses an incident platform |
• Explanation of how /inc command creates an incident in Slack |
• Story about Oban, a background job processing library for Elixir, and its integration with the codebase |
• Review of PR#378, which improved the use of Oban and reduced dependencies |
• Discussion of the importance of testing system reliability and documentation of incidents |
• Deployment process insufficiency led to a pod being put into service even though it was unhealthy |
• The unhealthy pod caused the origin server to return 503 responses, resulting in a degraded experience for some users |
• The incident affected only logged-in users who tried to access certain endpoints or pages |
• The company took steps to improve redirects at the edge and reduce health check frequency after the incident |
• The team implemented HTTPS everywhere and removed www redirects in favor of apex domain redirects |
• Technical difficulties with www redirects |
• Fastly configuration issues causing Safari redirect problems |
• Testing in production and scripting requests to hit endpoints |
• DNSimple findings and experimentation gone wrong |
• Debugging as a detective who is also the murderer ( referencing a quote by Filipe Fortes) |
• Discussion of extra domains used for testing |
• Ping Pong domain reference to Erlang and infrastructure management |
• Gerhard Lazu discusses his connection to Switzerland and the domain "lazu.ch" |
• The discussion shifts to ClickOps and the importance of version control and GitOps for Fastly configuration |
• Gerhard shares his experience with experimenting with Fastly and finding it difficult due to its ClickOps nature |
• The conversation turns to recent incidents on Upbound Cloud, including Linode networking issues and LKE unavailability |
• Gerhard discusses the reliability of backups and restores during networking issues, particularly with CockroachDB and Fly PostgreSQL |
• Discussing network downtime and reliability |
• Using Fly to run multiple instances of an app in different regions |
• Limitations of local storage (block storage) vs S3-compatible APIs |
• Planning for multi-region deployments |
• Switching from Arc to Waffle for file uploads |
• Errors in Sentry related to Erlang 24 upgrade |
• Discussion of Erlang version upgrades and potential improvements |
• Twitter Auth issues and consideration to remove or fix feature |
• Ecto.Query.CastError errors, specifically related to podcast unsubscription route |
• Analysis of error data in Getsentry and discussion of its features |
• Proposal for handling robot-generated unsubscribe requests |
• The team is having trouble receiving emails for new issues with Sentry |
• Ownership rules in Sentry may be a solution to automatically assign new issues to the right people |
• Weekday vs weekend error patterns are being discussed, with an interesting anomaly of high errors on weekends instead of weekdays |
• Plans for episode 30, including exploring alternatives to their current infrastructure setup (Fly.io and Elixir) |
• Integrating Honeycomb is mentioned as a priority, with Jerod Santo suggesting testing its integration and reporting back |
• NGINX performance metrics discussed, including 90th and 95th percentile times |
• Long tail requests taking over a minute to service |
• Importance of reliability and robustness in software, particularly for Changelog app |
• Goal of continuous improvement (Kaizen) for infrastructure and business progress |
• Upcoming T-shirt design featuring Japanese characters representing Kaizen |
**Gerhard Lazu:** This is the second Kaizen, second series of improvements. 2,5 months later, 10 episodes later, here we are. I listened to the last episode yesterday (our first kaizen episode, episode 10), so I am picking up the discussion exactly where we left off... How about that? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.