text
stringlengths
0
2.35k
[3051.94 --> 3053.30] need within an organization.
[3054.16 --> 3059.14] And like it could be anything from like, what do we need in terms of system infrastructure
[3059.14 --> 3060.00] side of things?
[3060.00 --> 3063.56] Or like the topic for today, more around observability.
[3063.56 --> 3070.30] So around observability, like I often think the capabilities that we need are logging metrics.
[3070.30 --> 3076.40] And like an organization can invest in having multiple tools for the same thing.
[3076.56 --> 3079.94] Or it could be one tool that does all of it.
[3080.06 --> 3082.60] It depends on the kind of organization you are.
[3082.60 --> 3091.42] So I have often leaned towards like what's happening in like the DevOps communities or like in the
[3091.42 --> 3098.56] monitoring communities to actually get insights from them saying, oh, there's I think two years
[3098.56 --> 3103.50] ago was when I was introduced to Loki, which is the logging tool.
[3103.68 --> 3110.58] And I got super excited about this mainly because we were using another logging tool within the
[3110.58 --> 3112.50] organization, which was super expensive.
[3112.60 --> 3118.74] And like, do we use this super expensive tool, which has some belts and visits, which we don't
[3118.74 --> 3119.12] use?
[3119.22 --> 3120.92] Or can we go with something like Loki?
[3121.42 --> 3127.28] And it is finding out capabilities that you care about and looking at what is happening in
[3127.28 --> 3129.48] that particular market and stuff.
[3129.74 --> 3136.34] Within the monitoring space, logging, I think my preference within logging would be like if
[3136.34 --> 3142.36] you are in the AWS land, then something like AWS CloudWatch or like Loki, Splunk.
[3142.36 --> 3146.66] These are a couple of tools that I have used in the logging space.
[3146.82 --> 3149.70] You can use the same kind of tools for metrics as well.
[3150.04 --> 3156.92] But there are better tools for metrics like Pometheus is really good or Graphite, which again, like I have
[3156.92 --> 3159.74] spent quite a lot of my career in Graphite.
[3159.74 --> 3164.76] So I probably have a preference in this space and see what innovation is happening in the
[3164.76 --> 3165.70] Graphite space.
[3165.88 --> 3170.44] But yeah, Pometheus is probably another one which is really good in the time series database
[3170.44 --> 3171.52] side of things.
[3172.02 --> 3175.36] And then it's also to do with like your metrics aggregation.
[3175.44 --> 3179.60] So you have all of these different metrics and logs and everything that you're collecting,
[3179.60 --> 3181.78] but how do you visualize them together?
[3181.78 --> 3186.76] So you need something around the visualization layer, which is where like Grafana or like
[3186.76 --> 3189.66] Kibana, one of these kinds of tools would come in handy and stuff.
[3190.14 --> 3194.20] And finally, I think it's the whole, you're doing all of this because you want to alert
[3194.20 --> 3194.48] things.
[3194.64 --> 3196.72] So what do we have in the alerting space?
[3196.80 --> 3200.22] Thinking about like, do I use like Slack notifications?
[3200.22 --> 3204.92] Do I use email notifications, SMSs, page of duty, whatever.
[3205.52 --> 3210.46] And it's just making sure you understand the capabilities of what you're trying to solve
[3210.46 --> 3213.24] and finding core products in each of those areas.
[3213.34 --> 3216.92] And it could be the same product that solves everything or it could be different products.
[3217.12 --> 3223.08] And yeah, I tend to lean towards communities and conferences to actually figure out what is
[3223.08 --> 3225.14] hot in the market and in places.
[3225.98 --> 3226.10] Yeah.
[3226.10 --> 3230.52] And what I really like about this is like, that's all kind of like through the lens of
[3230.52 --> 3233.50] release the way that you think about it as like, what are the problems that you're trying to solve
[3233.50 --> 3235.22] for the, for the customer?
[3235.36 --> 3235.50] Right.
[3235.52 --> 3237.12] And then what is the value that you're trying to provide?
[3237.16 --> 3241.88] So even at that point, like all of these could become sort of like, it's not interchangeable,
[3241.88 --> 3244.58] but you can solve the problem in 400 different ways.
[3244.66 --> 3244.96] Right.
[3245.04 --> 3248.52] And, and I just really liked that you start with, it feels like you start with that approach
[3248.52 --> 3250.34] to say like, what do you actually need to do?
[3250.64 --> 3251.80] What do you need to protect?
[3252.28 --> 3254.12] And then figure out how to do it.
[3254.30 --> 3255.48] And I like that.
[3255.48 --> 3259.66] That feels like the most transferable skill between company to company.
[3259.90 --> 3260.02] Yeah.
[3260.14 --> 3265.22] And also like within teams, when there are so many different teams and every team's autonomous
[3265.22 --> 3270.20] to use their own tools and stuff, then like, I think you need the core principles to be
[3270.20 --> 3272.94] the same irrespective of what tools they're using.
[3272.94 --> 3278.94] And that's where I find having the capabilities and the principle layer set, right, would help
[3278.94 --> 3282.70] teams figure out what is the best tool for their use cases and stuff.
[3282.70 --> 3283.94] Well, that's amazing.
[3284.12 --> 3286.16] Loads of great practical advice there.
[3286.24 --> 3289.80] And you yourself have spoken at conferences on this subject as well.
[3289.94 --> 3293.78] I noticed that people can, we'll put, put one in the show notes for people interested,
[3294.14 --> 3296.58] but you can also Google or use any search engine.
[3296.68 --> 3297.78] Other search engines are available.
[3298.50 --> 3304.16] You can duck, duck, go and find just for your name and you'll, yeah.
[3304.16 --> 3304.94] Nayana Shetty.
[3305.44 --> 3308.20] Well, unfortunately that is the time.
[3308.38 --> 3310.60] That's all the time we have, I'm afraid.
[3311.16 --> 3312.32] Thank you so much.
[3312.94 --> 3314.24] Matt Toback was here, weren't you, Matt?
[3314.64 --> 3315.32] I was.
[3315.36 --> 3318.54] Is there anything that you want to say to your future self just before we go?
[3319.06 --> 3320.12] Oh, I love that.
[3320.12 --> 3325.00] I think it is, you don't have to solve all problems today.
[3325.18 --> 3329.32] There are things that you can leave for the future to solve.
[3330.32 --> 3333.12] That is what I would say to my future self.
[3334.94 --> 3339.14] It'd be more useful if we could send messages to our past selves though, because we could
[3339.14 --> 3341.44] like tell them what the stocks are going to do in that.
[3341.66 --> 3344.18] No, because we, we know what happens, right?
[3344.32 --> 3345.42] The space-time continuum.
[3346.18 --> 3347.02] It's just not good.
[3347.16 --> 3348.02] Biff gets it, doesn't he?
[3348.30 --> 3349.04] Biff, he does.
[3350.12 --> 3350.56] Okay.
[3351.70 --> 3352.40] We won't do it then.
[3353.12 --> 3354.22] We won't do it then, Matt.
[3354.38 --> 3355.40] You've, yeah.
[3356.08 --> 3356.44] Okay.
[3356.96 --> 3358.40] Well, yes.
[3358.40 --> 3359.20] Thank you so much.
[3360.26 --> 3361.14] I've enjoyed it.
[3361.24 --> 3364.60] I mean, this is a topic that I enjoy speaking in general.
[3364.84 --> 3365.28] So yeah.
[3365.60 --> 3368.50] Are you speaking at any other conferences coming up or will you?