text stringlengths 0 1.8k |
|---|
**Gerhard Lazu:** And it makes us think about things in a different way. So if you try something out, why are you trying something out? Well, we have a certain problem to address, and it may be a fun one, but we will learn. So it's this curiosity, this building curiosity. How does Incident.io work? How does FireHydrant... |
\[40:08\] Some are hard, some are dead simple, and sometimes you may even be surprised and say "You know what - I would not have guessed that this platform is so much better, so why are we complicating things using this other thing?" But you don't know until you try it. And you can't be trying these things all the time... |
**Adam Stacoviak:** This reminds me of Sesame Street. Have either of you watched Sesame Street? |
**Gerhard Lazu:** Not that I remember... |
**Jerod Santo:** No. |
**Adam Stacoviak:** Of course. Everybody knows Sesame Street. But my son is a year and a half old, so he watches Sesame Street... But something that Hailee Steinfeld sings on the show is "I wonder... What if... Let's try..." That's kind of what we're doing here, "I wonder how this would work out if we did this. What if... |
**Gerhard Lazu:** I think that's how all great ideas start. The majority of the ideas may fail, but how are you going to find the truly remarkable ideas that work well in practice? Because on paper everything is amazing, everything is new, everything is shiny. How well does it work in practice? And that's where we come... |
**Adam Stacoviak:** It's all about gleaning, really. We're doing some of this stuff, and the entire solution, the way we do it may not be pertinent to the listener in every single case, but it's about gleaning what makes sense for your case. The classic "It depends" comes into play. |
**Gerhard Lazu:** Oh, yes... |
**Adam Stacoviak:** This makes sense to do, in some cases. Does it work for me? It depends. Maybe. Maybe not. |
**Break**: \[42:02\] |
**Gerhard Lazu:** So I would like us to talk about the specifics, three areas of improvements for the changelog.com setup. Not for the whole year 2022, but just like over the next couple of months. Top of my list is the incident management, so have some sort of incident management... But that seems like a on-the-side s... |
The next thing is I would like to integrate Fastly logging. This is the origin, the backend logging with Grafana Cloud. The reason why I think we need to have that is to understand how our origin, in this case Linode (LKE) where changelog.com runs - how does the origin behave from a Fastly perspective, from a CDN persp... |
\[43:57\] So what I mean by that is like when a request hits Fastly, that request has to be proxied to a node balancer running in Linode, and that has to be proxied to Ingress NGINX running in Kubernetes, and that has to be proxied to eventually our instance of Changelog. How does that work? How does that interaction w... |
**Jerod Santo:** How hard is that to set up? |
**Gerhard Lazu:** Not too hard. The only problematic area is that Fastly doesn't support sending logs directly to Grafana Cloud. So I looked into this a couple of months ago, and the problem is around authenticating the HTTPS origin where the logs will be sent... Because it needs to push logs, HTTP requests. So how do ... |
So we need to set up - and again, this is in the support you get with Fastly, what they recommend is you need to set up a proxy... Imagine you have NGINX, it receives those requests which are the Fastly logs (it will be HTTPS), and then it proxies them to Grafana Cloud. So that would work. |
**Jerod Santo:** Where would we put our proxy? |
**Gerhard Lazu:** Well, we would use the Ingress NGINX on Kubernetes, the one that serves all the traffic, all the Changelog traffic. |
**Jerod Santo:** Well, couldn't we DDOS ourselves then? |
**Gerhard Lazu:** We could, if Fastly sends a large amount of logs... Yes, we could. Now, would we set another-- |
**Jerod Santo:** This is not a DDOS if it's ourselves. It's just a regular DOS. |
**Gerhard Lazu:** Right. \[laughs\] |
**Jerod Santo:** It's not gonna be distributed, it's just us. \[laughs\] |
**Gerhard Lazu:** Well, it will come from all Fastly endpoints, I imagine... |
**Jerod Santo:** That's true, it could come from lots of different Fastly points of presence... |
**Gerhard Lazu:** Yeah. We could run it elsewhere, I suppose, but I like things being self-contained. I like things being declared in a single place. So to me, it makes most sense to use the same setup. I mean, it is in a way a Fastly limitation, and actually specifically Fastly and Grafana Cloud, the lack of integrati... |
**Jerod Santo:** Right. |
**Gerhard Lazu:** But speaking of that, I know that Honeycomb supports Fastly logging directly... And one of the examples that Honeycomb has is the RubyGems.org traffic, which is also proxied by Fastly. So in their "Try Honeycomb out" you can play with the dataset which is the RubyGems.org traffic. So I know that that ... |
**Jerod Santo:** Just a place to start, yeah. |
**Gerhard Lazu:** Yeah. But then we're using Grafana Cloud for everything else, so... |
**Jerod Santo:** Right. |
**Gerhard Lazu:** ...that's an interesting moment... Like, do we start moving stuff across to Honeycomb, or do we have two systems? |
**Jerod Santo:** Right. That's like a little break in the dam, like a little water just starts to pour out... And it's not a big deal right now, on Grafana Cloud, right? Like, "Well, I've got just this little thing over here on Honeycomb..." |
**Gerhard Lazu:** 99%, yeah. |
**Jerod Santo:** It turns out pretty nice over there... And then it starts to crack a little bit, and more water starts to... And all of a sudden it just bursts, and Grafana loses a customer. That stuff happens. So we could also parallelize this, and we could simultaneously try to get Fastly and Grafana sitting in a tr... |
**Gerhard Lazu:** Yeah, that would be great. That is actually a request from us. |
**Jerod Santo:** And that would probably be in the benefit of both Fastly and Grafana. That would be in both entities -- to their benefit. So maybe it's already in the works, who knows. |
**Adam Stacoviak:** I would guess that it is. |
**Gerhard Lazu:** Well, I would like to know, because then we could be not doing a bunch of work... |
**Jerod Santo:** Then we could procrastinate till it's there... |
**Adam Stacoviak:** Exactly, yeah. |
**Gerhard Lazu:** But it's stuff like this, right? |
**Adam Stacoviak:** \[47:54\] Well, let's put an email feeler out. We've got some people we can talk to to know for sure... And then if it is in the works, and it's maybe on the back-burner, we can put some fire under the burner, because we need it, too. |
**Gerhard Lazu:** Well, then we've hit another interesting thing, in that I really wanna try Honeycomb out. I've signed up, and I wanna start sending some events their way and just start using Honeycomb to see what insights we can derive from the things that we do. |
One of the things that I really wanna track with Honeycomb - and I wasn't expecting to discuss this, but it seems to be related, so why not... I wanna visualize how long it takes from git push to deploy. Because there are many things that happen in that pipeline, and from the past episodes, this is really important. Th... |
So we don't really know, first of all -- I mean, in my head I know what they are, all the steps, but you and Jerod don't know. What does the git push have to go through before it goes out into prod, and what are all the things that may go wrong? And then which is the area or which is the step which takes the longest am... |
Charity Majors - I don't know which episode, but she will be on the show very soon. 15 minutes or bust. That's what it means. Your code is either in production in 15 minutes, or you're bust. |
**Jerod Santo:** There was an unpopular opinion shared on Go Time. I can't remember who shared it, but he said if it's longer than 10 minutes, you're bust. |
**Gerhard Lazu:** There you go. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.