text stringlengths 0 2.35k |
|---|
[2672.24 --> 2673.16] Do you have any ideas? |
[2673.54 --> 2677.46] We need some analytics, don't we, on the usage of it really? |
[2677.46 --> 2684.74] Then we can say, you know, no one's looked at these alerts for ages, you know, or you could put a specific time on it if you want. |
[2684.84 --> 2686.82] I don't know, I don't want to design the application now. |
[2686.94 --> 2688.16] But yeah, something like that. |
[2688.22 --> 2695.18] I mean, I like the idea that you should go back and look at them and pay attention to whether you still need them and things. |
[2695.24 --> 2703.62] This is a little bit like how in GitHub, like, or in your project management tool, if you have loads of stuff in there, most of it's just getting ignored. |
[2703.62 --> 2714.76] And in a way, it creates this also this idea that you're so far away from being done, which we of course are, but you don't, you know, it sort of reinforces that. |
[2714.90 --> 2718.88] So it is that thing of if there's just so much there, it stops being useful. |
[2719.20 --> 2725.18] I like the idea that, does it take experience though, do you think, to know what's useful, what's not? |
[2725.18 --> 2725.90] Does that? |
[2726.14 --> 2727.00] It could do. |
[2727.24 --> 2732.88] I mean, the more you see these things, you will realize where it's important, where it's useful and where not. |
[2733.18 --> 2742.88] And this is where I've seen some of the junior engineers and teams struggle, which is like, they start worrying about every single alert that comes on Slack or whichever is your preferred tool. |
[2742.98 --> 2744.36] And they're like, oh, what do I do? |
[2744.44 --> 2745.14] I've got this alert. |
[2745.26 --> 2749.30] It might be my change, but it might not be related to your change at all. |
[2749.30 --> 2758.54] So I think it's something that the team should do on a regular basis as like a team activity or something like that, where they sanity check their alerts. |
[2758.98 --> 2765.24] One way we used to do is any alert that we actually did anything with, we started putting some everything. |
[2765.68 --> 2767.00] All of our alerts used to come to Slack. |
[2767.10 --> 2769.14] So we used to start putting some emojis on it. |
[2769.26 --> 2772.68] So we know which of them were actually things that mattered. |
[2772.68 --> 2778.14] And like on a weekly basis, we were like, oh, there were 10 of these, which we did nothing with. |
[2778.54 --> 2779.72] So maybe we can get rid of it. |
[2779.88 --> 2785.18] So that like, it's very hard to get that feedback cycle on alerts I've found. |
[2785.56 --> 2788.30] Matt, you need to collect the emojis and then feed it back. |
[2788.42 --> 2790.52] Is the API going the other way on emojis? |
[2790.78 --> 2796.44] We do that for in the Grafana incident tool, but I need to tell the on-call team about that idea. |
[2796.52 --> 2797.22] That's such a good idea. |
[2797.38 --> 2798.18] That is kind of fun. |
[2798.28 --> 2802.16] You could collect that data and literally, yeah, you then, oh, hello. |
[2802.68 --> 2804.24] You're like, what does dancing penguin mean? |
[2804.56 --> 2804.86] Yeah. |
[2806.24 --> 2806.64] Yeah. |
[2806.90 --> 2807.82] It means it's cool. |
[2809.76 --> 2811.90] Who owns that idea legally? |
[2812.04 --> 2812.52] I don't know. |
[2812.98 --> 2813.62] I do. |
[2813.62 --> 2814.00] I feel like. |
[2814.32 --> 2814.42] Yeah. |
[2817.28 --> 2818.14] That's a good idea. |
[2818.26 --> 2818.66] Solved. |
[2822.34 --> 2827.02] I want to, I wanted to quickly touch on as you progress in your career, right? |
[2827.04 --> 2829.76] Often you're going to walk into new organizations, right? |
[2829.78 --> 2832.62] And you're, you're new to Lego and everything today is just reinvigorating. |
[2832.68 --> 2835.86] And for us, the thought that we had this, or that I was kind of noodling on this morning, |
[2835.86 --> 2837.90] which is all these things are true. |
[2837.90 --> 2841.34] All these methods are like, are kind of proven. |
[2841.76 --> 2846.42] And in, you know, in some ways, like it has nothing to do with the technology and everything |
[2846.42 --> 2848.30] to do with the landscape that you're walking into. |
[2848.38 --> 2851.86] And then, then you have to figure out how, how and what you introduce. |
[2851.86 --> 2857.82] And I guess I'm curious, like how much about open source tooling makes it easier to transfer |
[2857.82 --> 2858.78] into a new organization? |
[2859.48 --> 2864.72] And even just how much, like, how do you approach going into a new org, having this experience, |
[2864.72 --> 2867.84] but then also not understanding how everything fits together? |
[2867.84 --> 2868.56] Hmm. |
[2869.06 --> 2870.46] I mean, this is so relatable. |
[2871.02 --> 2872.42] I'm going through this now. |
[2872.52 --> 2872.66] Yeah. |
[2872.66 --> 2877.26] Like, given I've been in the Lego group for only three months and I care about monitoring |
[2877.26 --> 2880.42] and like in general sustainability of products quite a lot. |
[2880.42 --> 2886.70] But I've been looking at different teams doing this and thinking, okay, this team has this |
[2886.70 --> 2888.28] Grafana dashboard to do it. |
[2888.36 --> 2891.06] This other team has Neuralic and they're doing something with it. |
[2891.22 --> 2896.86] I think for me, I was lucky that I was in a team that was building monitoring tools as |
[2896.86 --> 2901.24] a service, like providing monitoring tools as a service to other teams. |
[2901.24 --> 2907.92] So for me, it was like easier to catch on to what is happening in different areas within |
[2907.92 --> 2908.64] the Lego group. |
[2908.64 --> 2915.54] But I think what I fall back to is always think about what are the core aspects of monitoring. |
[2916.00 --> 2920.42] So it's things like logging, metrics, alerting, tracing. |
[2920.76 --> 2923.20] So notifications, some of those core things. |
[2923.48 --> 2928.68] And it is looking at those aspects and thinking, how is the team solving these problems? |
[2929.28 --> 2936.08] And where the team have done, used a tool, I have often just endorsed what they've got and |
[2936.08 --> 2941.86] looked into it, but where they haven't, I have often suggested open source tools in those |
[2941.86 --> 2944.28] use cases because two reasons. |
[2944.42 --> 2946.98] One, it's easy to get started and get going with it. |
[2947.08 --> 2951.28] You don't need any licensing and all of those kinds of challenges that come with a proprietary |
[2951.28 --> 2951.76] tool. |
[2951.76 --> 2958.18] And on the other side, there's a lot of community that can help you getting started with the |
[2958.18 --> 2958.76] tool as well. |
[2958.76 --> 2965.34] So I think those are reasons why I would prefer, like when suggesting to teams, I would prefer |
[2965.34 --> 2968.16] open source technologies when it comes to this space. |
[2968.16 --> 2975.36] I mean, as an example, when I was doing some experimentation for my own personal project, I could have gone |
[2975.36 --> 2978.84] with one of the tools that was already available in the organization when I was working. |
[2979.00 --> 2983.76] But then I was like, I mean, if I left this organization, I can't take that tool with me. |
[2984.14 --> 2987.64] So it's better to have it on more open source tools. |
[2987.92 --> 2991.84] I mean, in that case, I used, I think it was Graphite and Grafana that I used in that case. |
[2991.84 --> 2998.58] But it is that while there is transferable skills within the organization, like as an |
[2998.58 --> 3006.06] example, the Lego technology, I think we have around 200 or 250 odd teams in it. |
[3006.70 --> 3013.82] And if these people within the teams have to move between each other, speaking the common |
[3013.82 --> 3015.26] language is quite important. |
[3015.68 --> 3020.64] And having that community outside of the Lego group who can help us with this is quite |
[3020.64 --> 3021.08] important. |
[3021.08 --> 3025.74] And I feel like that is where the power of using open source technologies comes from. |
[3026.10 --> 3030.34] And I mean, I have come from an organization where we were a very big advocate of open source |
[3030.34 --> 3030.84] technology. |
[3031.08 --> 3035.96] So I probably would be singing the song of let's go all in on open source. |
[3037.84 --> 3040.76] So I'm interested then what's next? |
[3041.02 --> 3044.90] What's coming up and how do you keep your finger on the pulse of what's going on? |
[3044.90 --> 3051.94] I often think about like less about tools and more about the capabilities that we really |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.