Dear all, for today's SIG O11y DD on OM (abbrevations!), please see https://docs.google.com/document/d/1BN6ABvfbAMhJthH6xNOY5Lmls3jeE3kFbMgF04BzEKE Ideally read it before the meeting. For the

Hi, Hope you are all well! 1. To avoid timing confusion, let's agree on one time finally (: There were some wintertime clock changes in EU, all went upside down. I assumed we align to the public CNCF

Ooh, thanks for that. I just joined and am catching up. Very observable 🤭

> Factual correction: 😱 Kind Regards, Bartek Płotka (@bwplotka)

Yeah, great. Thanks.-- This is my life,but world of us~~

Factual correction: https://www.youtube.com/playlist?list=PLj6h78yzYM2PJkFrpP6IT52KkdBvcvS_9 We should _resume_ recording ;) Cheers, Michael -- Product Developer Advocate, AWS container

We can consider recording those, yes (: So far we did not. Kind Regards, Bartek Płotka (@bwplotka)

Hi Do we have recordings for the meeting? It is too late for me to join. -- This is my life,but world of us~~

Hi SIG Observability! Hope at least some of us had some relaxing time this summer - I am personally still looking for some PTO time 🌴🌴🌴 (: Just a short reminder: We are back with the SIG

Thanks for this feedback! <arthursens2005@...> wrote: I agree that ML needs more nuance. I have better mental pictures to transport my caveats now and those would hopefully enable

Thanks Arthur - those questions are an amazing indication for us what sections of our potential SIG 101 doc should be extended (: > One topic that is still unclear to me is: When should I need

Hello Richard and everyone, Maybe some of you recognize me from GitHub, some may not, but for context to everyone.. I'm a recently graduated student with not much experience around the whole

Post it here, please. I do get FOSDEM feedback email too, but that's invisible to this list.

Hi Richard, Regarding Observability 101 content: I noticed the recording page has a feedback link. Should I send feedback there, or post it here? Thank you, Amin

Dear all, as we were only nine people during the call, as PTO time is coming, and as we don't have any pressing action items, we decided to skip both August meetings. Best, Richard

Dear all, during our call I mentioned that Prometheus will be overhauling our complete documentation, see https://docs.google.com/document/d/1yuaPKLDvhJNXMF1ubsOOm5kE2_6dvCxHowBQIDs0KdU/edit for

Dear all, as per yesterday's call, we will start collecting use cases for data analysis scenarios. Please use https://docs.google.com/document/d/1yfbBG8MBllLRCXVNMp2fgRJm5TiCooO9NSD2CfOQ4ck/edit as

Dear all, as agreed during the last meeting, we will start future calls s.t., i.e. on time. While I understand the struggle of juggling endless meetings all too well, we end at 50m to allow people to

Hi. A short reminder to check the DD before tomorrow's meeting as the plan is to review it together, similar to the Cortex document. Doc: