 Hi, and welcome to Observing Cloud Native Observables with the new SIG Observability, which already tells you that observability is kind of a buzzword, but there is some value to it. I'm Richard. I'm Bartek. And we are going to tell you what this is all about. SIG is a special interest group, and observability at a very fundamental level is about making complex systems rockable for humans. And that's basically what we're working on. So if you look at our charter, it's very much around fostering, reviewing, and growing the ecosystem of and around observability, identifying and reporting gaps within the CNCS project portfolio, find, establish, write down patterns and best current practices. And the current is important because things change over time. Educate and inform users about all of these without any bias, which obviously means no vendor lock-in, a truly vendor-neutral venue for all thought validation and such. And as a little bit of a test balloon, we are doing more in due diligence reports than other SIGs, where we actually walk through the whole due diligence process to take some load off of TOC. And one thing which we're really, really, really trying to is have a bias for action. Of course, usually any new endeavor is always nice and cool and shiny and everyone's to join. And we're trying very, very hard to actually push for actual bias, for actual action and for actual outcomes. Looking at our past activities, we obviously charted ourselves and self-created with the blessing of the TOC. And we did already two incubation reviews and due diligence reports for Cortex and Thanos, both of which passed and are now in incubating stage. We started gathering requirements about online analytics platforms and analytics. And we already explored some overlap with AI and ML. Of course, especially in metrics land, this is like perfect signal for machines to understand and grok. And also integrate with other projects for some knowledge transfer. Amazing. And as you might be already aware, our observability landscape in the CNCF space is already quite rich. We have kind of different levels of project stage within the CNCF. And in graduated, we have Fluendee, which is related to logging. Jagger, which is the tracing system. Prometheus, which is a first system that kind of get into the CNCF from the observability space around metric monitoring. And then we have incubated stage where we have Cortex and Thanos, which are metric systems scaling Prometheus. And those are kind of bolded here because those are where kind of moved, well, thanks to the seek observability kind of movement. And we are looking to help other projects to graduate as well and join our space. We have open tracing, which now kind of merged into open telemetry, but still is incubated project around tracing. And then in Sunbox, we have, you know, chaos mesh and litmus for a related to chaos engineering. And yeah, please join our, you know, meetings to learn more about them. We'll kind of share knowledge as well. We have open metrics, which is essentially metric format and kind of exposition, well-established format and protocol around all applications. And open telemetry at the end, which has amazing progress as you could see if you're following the Twitter or actions, you know, kind of collaborating with many, many vendors and allowing them to kind of integrating well within single, simple kind of application you can put on your infrastructure is kind of amazing. So, you know, the observability kind of space here is very rich already. You can do a lot just using those projects, but you know, that's not everything, right? We are definitely not done yet with this landscape. And there might be some observability areas that, you know, are missing from this landscape or maybe we can integrate better with, right? So, if you look at integrations or at the overlap, there is obvious overlap between the three golden signals, metrics, logs and traces in exactly this order, basically Pareto principle, that's just the ordering of the most bang for your buck versus where it's just the effort you need to put in so it usually makes sense to start with metrics, then go to logging, then go to tracing. That's just kind of the natural evolution. And if I do say so myself, one thing helped really connect the dots a bit where open metrics took the label-based metrics exposition format of Prometheus. And already back in 2015, the intention was to also have logs and events with the same label-based access mechanisms, which with Profana Loki we have, which is super nice. And as was announced, we are recording this on a Tuesday. So yesterday of my time, I don't know by heart when this is actually showing. Tracing based on exemplars. What that means is basically you only have an ID for your traces and nothing else. So you come into your traces from metrics and logs, which are relevant to you. Of course, they have high latency or there was an error or what have you. And those obviously carry label sets with rich data, which enables you to actually go to what is interesting to you. And then you just jump into the trace with the help of an idea and you don't need to have that usual needle and haystack problem of tracing. And personally, I think that exemplars are the future for traces, like absolutely 100%. And this is why even back in 2016, Open Metrics already had support for traces, which permitted through the Prometheus Cortex Thanos and also Loki ecosystem. And with Profana Temple, we now have something which actually stores traces based on exemplars. But there's more. We have continuous profiling, where you have an obvious overlap between metrics and tracing, which kind of goes in this direction, but where does it sit precisely? Should we have a new project, which can actually store those or can we make either of the other fields of our groups or solutions work for you? Then there's another thing, which I think is too often overlooked, crash dumps. You can argue that there is somewhere sitting in between tracing and logging, but having informed state about, hey, something actually aborted abnormally and this is what it's dying gas was, I think will be useful in the future to actually figure out why something specific be hit the wall. But this is just us thinking about those things. There are certainly other signals and we would love to hear about your thoughts around what else might be missing here. Because that's literally what I think is about. It is a special interest group and we highly, highly, highly recommend it and invite anyone to come to us and actually talk about what you want to see in this space. Yes, and there are actually much more we are doing right now, which is on our plate. So let's quickly go through that. We started our proper meetings, let's say a couple months ago really, so pretty early. However, we already started kind of a few directions here and there. And it's really about building this community around observability to make sure everyone can contribute in their area of expertise. So by allocating those kind of small working groups and let's say some groups that are focusing on one area, we can just scale and do much more better together. So examples of things we are doing right now, we are definitely looking forward to just start, seek observability strong and to learn more about projects and each other. That's why we are planning to have some introduction webinars. We already have some introduction things to Steve from about open telemetry. We are planning to I think host Litmus project as the first one which will introduce themselves. So we can learn about their problems, each project's problems, maybe we can have kind of collaboration there in terms of integrations and kind of user experience of really any concept of maintaining open source project even that is related to observability. So that's our plan here. And other aspect is this lacking of well integration between a good integration between, let's say infrastructure engineers and big data analytic engineers. There is not much conversion formats and API integration towards this connection. So as a first thing we started to look on how to get metrics from the projects we support like from to use Thanos Cortex and get or like open telemetry and get into Parkett file, Apache Arrow, many, many projects from Apache foundation for example, how to integrate that. So yeah, we started some QC, some cool coding but also some user requirements. So depending on your background you can help in many, many areas. Next one, which is kind of starting right now, we recently had this observability rather, which was amazing because we suddenly have more data to understand what is the interest regarding the projects and the problem space. However, obviously you cannot easily ask people you might have some biased information based on your connections and that's normal. So we are kind of starting some effort into making, maybe improving this kind of surveys and making them easier and actually make companies motivated to actually take part in those surveys to actually have meaningful data that everyone is trusting, right? So there is some work on that side. And last but not the least is introduction to observability, right? Like there are lots of questions that are people coming to our meeting and saying, okay, I don't know where to start. I just want to improve observability in my company. How do I start? And there was no good starting docs or I don't know, some index that will route you to the particular projects or materials that explain you certain problems. Like for example, how do I gather metrics? When do I switch to logs? Do I need tracing? What is distributed tracing? What is profiling? And all of those are, maybe for some people it's obvious but sometimes some direction, initial direction is very needed. So we are looking forward into creating some ways of having some maybe a good introduction page that will route to at least CNCF landscape projects. I think it's a good opportunity to also collaborate with other six to learn how they share knowledge and have some method of doing that. So if you want to help in this direction, maybe help us writing some better documentation. Maybe actually write better documentation on each of the projects and kind of route and link them together in one place. That would be super amazing and we are looking for your ideas and feedback. And last but not least, yeah, we want to help projects to graduate due to further stages. We want to make sure they are well supported, well maintained. So we are looking into proposals of getting projects higher. One particular ideas or like proposals we will be working right now is Open Metrics. We are moving, I mean, Open Metrics is moving quite fast and we are considering, you know, yeah, maybe have some review in terms of incubation graduation. So all sorts of kind of actions like that is in our scope. Next, I'm Bartek, I'm kind of tech lead here. We have Richie here who is sick chair. We have also Matt Young who is another sick chair. And this is kind of a starting point, but we have also, I mean, huge amount of amazing people who contributed already to our sick observability. They were on our meetings. They help us with the review and preparation of the charter docs. And they are part of, you know, all those smaller working groups and direction we are creating. So yeah, and so many of those and it's super nice that, you know, we can kind of build the community with those amazing people. And anytime you need help, they are super happy to just, you know, use their time in order to enrich this observability, you know, open source. It's super amazing and thank you, everyone. And yeah, you will meet all those people and all of them are friendly and amazing. So please join us just to meet people really. That's one first argument you can have. And yeah, so action item for you. How you can help, how you can join us if you want. Well, first of all, we have B-weekly meetings. You have a Google doc here. We'll share slides so you can click on that. And we focus on those meetings to be, you know, mostly introductionary, maybe some presentations, maybe some status update, but we've meant for those meeting, well, for the actual work to be done outside the meetings. We are too large group already to actually, you know, do everything in one hour. So please be prepared for that. But obviously please put stuff on agenda and add, you know, any topic that you want there. We have our repository, go there. There are like basic information there. Put an issue on the repository if you want to have some asynchronous method of doing some requests for us. We have CC Slack, we have Main Inclist, and yeah, you can help with all of those stuff. Maybe you have some feedback. Maybe you want to have, maybe you need some help as a project on observability project or maybe observability project, maybe outside of CC and CF event. You don't want to know how to start, how to integrate. Maybe you have ideas, we want them. Maybe you have just free time and you don't know what to do with that. We will definitely have some ideas how to allocate this. So please join us next. So that's it. Thank you for listening. Now is really time for any live questions you have to ask. Our talk was a bit shorter just for this purpose. If you want to take this opportunity and ask questions related to seek observability and just learn more, we're happy to take questions. Yep, looking forward to the questions. Thank you very much. Thank you.