text stringlengths 0 2.02k |
|---|
**Gerhard Lazu:** Yes, Grafana. Sorry, Adam, what were you saying? |
**Adam Stacoviak:** I was saying I thought you said you were taking the day off because you had nothing to do because the internet was down, essentially. That's what I thought you were saying. |
**Jerod Santo:** Oh, no. |
**Adam Stacoviak:** I misunderstood. |
**Jerod Santo:** I wasn't doing anything anyways. |
**Gerhard Lazu:** I was just chilling. It was a gorgeous day, sunny, and it was a day off; I was sunbathing. I won't go into more details with that. \[laughs\] |
**Jerod Santo:** Well, let me say two things. First of all, thanks for springing into action and bringing this back up; 21 minutes, nothing wrong with that, compared to the BBC, those suckers, they were down for much longer... But the bummer side, let me tell you the bummer side, which - I haven't told you this before,... |
**Adam Stacoviak:** Yeah. |
**Gerhard Lazu:** I remember that, actually. I remember that, because I remember looking at the stats, and the stats were down, and I was thinking "I wanna talk to Jerod about this." So if there's one lesson to learn from this, we need to double up. So everything that we do, we need to do two of that thing. Say like mo... |
**Jerod Santo:** \[12:14\] Well, it's one of those ROI kind of conversations, and I think this is a good conversation for Ship It, like "What's worth doing?" and the fact is that in our five years of being on Fastly, this is the first incident they've had... And if it didn't happen to be right when we released a popula... |
So the question becomes "What does it take to get that redundancy? What does that redundancy cost, and what does it gain?" And in the case of stats, I'm not sure what side of the teeter-totter we actually end up on, because the way it works now as Fastly streams the logs of all of the requests to the mp3 files over to ... |
But what would it take to get Linodes doing the same thing, or changing the way we do our stats, so that we're either redundant or do it differently? I don't know the answer to that off the top of my head. |
**Adam Stacoviak:** In the case of something like Grafana though, I would put that back on them. We shouldn't have two Grafanas. I think this is probably the case for multi-cloud - wouldn't it make sense then to be let's say on GCP, Azure, or essentially multi-cloud? And maybe that's an issue with cloud at large. The c... |
**Gerhard Lazu:** Now, obviously, as you would expect, I think about this differently. |
**Jerod Santo:** \[laughs\] Please tell us. |
**Adam Stacoviak:** Please tell. |
**Gerhard Lazu:** The way I think about this is that we are in a unique position to try out all these providers. We have the know-how, and really, our integrations are fairly simple... So I know that it wouldn't take that much more to integrate Cloudflare. So how about we use Cloudflare AND Fastly? ...the two biggest C... |
Now, the pipeline that orchestrates all of that will be interesting... But this is not something that's gonna happen even like in a year. It's slowly, gradually... It's maybe a direction that we choose to go towards... And maybe we realize "You know what? Actually, in practice, Cloudflare and Fastly - it's just too com... |
**Adam Stacoviak:** \[15:58\] Yeah, that's that cost that Jerod was talking about - how much does the redundancy cost, and how much does it gain you? |
**Gerhard Lazu:** So from a CDN perspective we just basically have multiple DNS entries; you point both Fastly and Cloudflare to the same origin - or origins in this case... let's just start with the one origin. The configuration is maybe slightly different, but we don't have too many rules in Fastly. How do they map t... |
**Jerod Santo:** Yes. And I looked at Cloudflare - it was probably two years ago now - with regards to serving our mp3's, and where I ran into problems was their visibility into the logs and getting that information out paled in comparison to what Fastly provides. So we would lose a lot of fidelity in those logs, like ... |
**Adam Stacoviak:** Yeah, if they've improved their logs, then it's back on the table, let's say. |
**Jerod Santo:** Yeah. So that's maybe the long-term direction. What's some stuff that is more immediate, that you have on the hitlist? Things that we should be doing with the platform. |
**Adam Stacoviak:** I think multi-CDN makes sense to me, just for those reasons. If you've got one that goes down, then you've got another resolver. |
**Jerod Santo:** But once in five years... How often is Fastly down? |
**Gerhard Lazu:** Okay, I'm thinking about this from the perspective of the experience and sharing these things. |
**Jerod Santo:** Right. |
**Gerhard Lazu:** A few years back, we were missing this. But we don't know what they have or don't have this year, or maybe what we're missing. Maybe they don't even know what we would like for them to have. And listeners of this show, they can think "You know what - this show is really interesting, because they are u... |
**Jerod Santo:** Right. |
**Gerhard Lazu:** So in a way, we're just producing good content. That is very relevant to us, when we say "You know what - we are informed, and we have made an informed decision to not use Cloudflare because of these reasons... Which may or may not apply to you, by the way." |
**Jerod Santo:** Right. It's like there's a brand new hammer, and we grab hold of it... And everyone gathers around, we put our hand out and we strike it right on our thumb. And then everybody knows "That hammer really hurts when you strike it on your thumb. I'm glad those guys did it. I've learned something. I don't h... |
**Gerhard Lazu:** \[laughs\] I think that's a very interesting perspective, but I don't see it that way. It's an amazing analogy, but I'm not sure that it applies here... But it's great fun, that's for sure. |
**Adam Stacoviak:** Yeah. |
**Jerod Santo:** Okay, good. |
Break: \[19:16\] |
**Gerhard Lazu:** So you were asking, Jerod, what is next on our hill... One of the things I learned from the Fastly incident is that we don't have anything to manage incidents. When something is down, how do we let users know what is going on? How do we learn from it in a way that we can capture and then share amongst... |
A document is great, a Slack just to write some messages is great, but it feels very ad-hoc. So one of the things that I would really like is a way to manage these types of incidents. And guess what - there's another incident that we have right now. |
**Jerod Santo:** Right now? |
**Gerhard Lazu:** Right now, right now. |
**Jerod Santo:** Like the website's down right now? |
**Gerhard Lazu:** No. The incident - this is a small incident... |
**Jerod Santo:** Okay, good... |
**Gerhard Lazu:** No, the website is 100% up. |
**Jerod Santo:** 100% uptime, thank you. |
**Gerhard Lazu:** Yeah. So Fastly, it's your responsibility to keep it up, right? That's what it boils down to. It's someone else's problem. It's Fastly's problem. |
**Jerod Santo:** That's right. Pass the buck. |
**Gerhard Lazu:** Right. So right now, one of the DNSimple tokens that we used to renew certificates has been deleted. So it's either Adam or Jerod, because I haven't. |
**Adam Stacoviak:** It wasn't me... |
**Gerhard Lazu:** Anyways, I'm not pointing any fingers... |
**Adam Stacoviak:** I don't touch DNS. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.