text stringlengths 0 1.8k |
|---|
**Adam Stacoviak:** Oh, boy... |
**Jerod Santo:** Wow. |
**Adam Stacoviak:** I'm gonna read the transcript. |
**Gerhard Lazu:** As a listener, if you want this to make a bit more sense, then read the transcript, if you want, as Adam is doing; or maybe listen to that, I think it'll make a lot of sense. So a big portion of episode 10 we discussed about incidents, about having issues, and how do we share the learning within the t... |
**Adam Stacoviak:** Oh, yes... |
**Jerod Santo:** Yes. |
**Adam Stacoviak:** I recall that. We were trying to track that down, yeah. |
**Gerhard Lazu:** It was actually me. |
**Jerod Santo:** I had a feeling... \[laughs\] |
**Gerhard Lazu:** Yeah, it was definitely me. |
**Adam Stacoviak:** Well, I know it wasn't me... \[laughter\] |
**Gerhard Lazu:** I did it. |
**Jerod Santo:** Why? How? Tell us. |
**Gerhard Lazu:** So when I've set up the new DNSimple token for cert manager and for external DNS, even though I created a new one, I was still using the old value. So there was a new token, but the value which I was using in the new infrastructure was the value from the previous token, from the old token. |
**Jerod Santo:** It was the old one. |
**Gerhard Lazu:** So when I deleted the old token, because that's what it was in DNSimple, that just stopped working. So things broke. |
**Jerod Santo:** \[04:12\] I see. |
**Gerhard Lazu:** But it gets a bit more interesting than that. Apparently, there's two sets of tokens. There's one token which you get by user settings and the user access token, and those are the ones that we were looking at the last time, trying to figure out why is this token missing, where is the token. But there'... |
The more important thing was "How do we track this? How do we capture this so that in the future when this happens we know where to look?" We looked at a few incident management platforms, we discussed both FireHydrant and Incident.io; we even did a write-up. I say "we", it's a royal we. We did a write-up to compare th... |
When we discussed in episode ten, FireHydrant was actually fronted by Fastly... Because the issue which we were trying to mitigate against was Fastly, it would have been a bad decision to choose a system that has Fastly in front when there's a Fastly issue, because you can't get to the system. So Incident doesn't use F... |
**Jerod Santo:** Is this the one that comes into Slack and starts a new channel in Slack, and then you can update it there? |
**Gerhard Lazu:** Yes. |
**Jerod Santo:** Okay. So I remember that much... I don't remember anything else about it, honestly. |
**Gerhard Lazu:** Okay. |
**Jerod Santo:** How about you? You might have way more context than I do. |
**Adam Stacoviak:** I remember the emails about it, in addition to the incident in Slack, of course... There were some emails about TLS expiring, and issues, and stuff like that. |
**Gerhard Lazu:** Yeah, we had those. Yes, they were useful, but not useful from the perspective of "What is the problem? What goes into debugging the problem, and so on and so forth?" So there is the Incidents Slack channel, which by the way, is public to everyone... So if anyone wants to go in our Slack, open up Inci... |
The reason why I'm asking this is because having run it and having captured this information, how useful is that? Just glancing at it - does it look useful? Is it something that you see going back to, referring to? That's what I'm wondering. |
**Jerod Santo:** So you just heard how bad my memory is... |
**Gerhard Lazu:** Mm-hm. That's why you write things down. |
**Jerod Santo:** Right. So in the case of somebody saying "Haven't we had this problem before?" Or "Distant memory of TLS errors...", and I would say "Yeah, we have, but I don't remember anything about it." |
**Adam Stacoviak:** Yes. |
**Jerod Santo:** When was that? We're talking about July, we're now in September, so a couple months... It's just come and gone. Now, I think you've fixed it, Gerhard, so you probably remember it better than I do... I just kind of watched it happen. |
So the ability to go back to it, which I now have scrolled back to it; it was July 12th. It just happened to be my birthday when this happened... |
**Gerhard Lazu:** Happy birthday! \[laughs\] |
**Jerod Santo:** Oh, thank you. Awfully belated there... |
**Gerhard Lazu:** I'm pretty sure I said Happy Birthday back then, but now that you mentioned it... |
**Jerod Santo:** Now that you know how bad my memory is, you can just retcon that for me... I'm seeing some details here about it, and if I could click through somehow to Incident.io from the Slack incident, then I'm sure there'll be even more information. But in this particular channel, or maybe -- oh, here we go. I'v... |
**Gerhard Lazu:** \[08:14\] Yeah. |
**Jerod Santo:** And that's about what I would use it for. |
**Adam Stacoviak:** Yeah. I like the fact that there's a grand channel, an Incidents channel where you can go and see all the incidents. And I like the fact that it's public. So if you're listening to this, you're in Slack already, then just hop in that channel and you can just pay attention to what we're doing... Just... |
**Gerhard Lazu:** That was one of the things which were top of my mind back then. Not only that, but I tried it, and now we're improving our understanding of this new thing that is in our Stack. What do we like about it, what don't we like about it? Stuff like that. How well does it work? Or at least we know where to p... |
So I mentioned that we had four incidents since. But the second one - that was an interesting one... This is something that Jerod was trying to investigate, and actually, he even fixed it. |
**Jerod Santo:** I did. |
**Gerhard Lazu:** That was the PR\#378. Do you wanna tell us a little bit about that, the story behind it? |
**Jerod Santo:** Yeah. |
**Adam Stacoviak:** Testing Jerod's memory again. Here we go. |
**Jerod Santo:** I'm now opening the incident to my memory... It was like a failure for the application to boot in production, or something... Oh, it's coming back to me. So this leads into Oban a little bit, doesn't it? |
**Gerhard Lazu:** Yes, yes. Parker Selbert. Thank you, Parker; that was a great improvement, by the way. We really appreciate it. And I even captured this in a comment, in PR\#378, how much we appreciate you contributing this, and testing how reliable our system is. And in some ways, it failed in an unexpected way... B... |
**Adam Stacoviak:** Well, I'm just looking down the Incidents channel now, and 1) I like the fact that we're describing it as memory, which I think is interesting... You know, some would say that incidents tend to be big things, not small things; I guess they're just incidents, that they can make them more grand than t... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.