|
Skipping the 2021-08-17 call
Dear all, as most of us seem to be on vacation, we decided to skip the 2021-08-17 call. See you in September, Richard
Dear all, as most of us seem to be on vacation, we decided to skip the 2021-08-17 call. See you in September, Richard
|
By
Richard Hartmann
· #65
·
|
|
Daylight savings fun this week
Dear all, there is no non-painful way to deal with daylight savings, so just to make sure: We will have our call today at 16:00 UTC. Best, Richard
Dear all, there is no non-painful way to deal with daylight savings, so just to make sure: We will have our call today at 16:00 UTC. Best, Richard
|
By
Richard Hartmann
· #57
·
|
|
Extra meeting today
Dear all, as agreed, Amye created an extra invitation for us last week. It was copied over from the regular forthnightly one, lives in the same calendar, has the same invitations, meeting notes, Zoom
Dear all, as agreed, Amye created an extra invitation for us last week. It was copied over from the regular forthnightly one, lives in the same calendar, has the same invitations, meeting notes, Zoom
|
By
Richard Hartmann
· #54
·
|
|
PromQL compliance overview
Dear all, https://promlabs.com/blog/2020/11/26/an-update-on-promql-compatibility-across-vendors might be of wider interest within this group. Best, Richard
Dear all, https://promlabs.com/blog/2020/11/26/an-update-on-promql-compatibility-across-vendors might be of wider interest within this group. Best, Richard
|
By
Richard Hartmann
· #46
·
|
|
Due diligence document for OpenMetrics
Dear all, as agreed during the last SIG O11y call, we addressed all comments & concerns in the document, both the ones raised during the call and afterwards. Please review/clarify/update where needed.
Dear all, as agreed during the last SIG O11y call, we addressed all comments & concerns in the document, both the ones raised during the call and afterwards. Please review/clarify/update where needed.
|
By
Richard Hartmann
· #45
·
|
|
Due diligence document for OpenMetrics
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 record,
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 record,
|
By
Richard Hartmann
· #44
·
|
|
Prometheus & Observability documentation
Post it here, please. I do get FOSDEM feedback email too, but that's invisible to this list.
Post it here, please. I do get FOSDEM feedback email too, but that's invisible to this list.
|
By
Richard Hartmann
· #31
·
|
|
Skipping August meetings
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, 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
|
By
Richard Hartmann
· #29
·
|
|
Prometheus & Observability documentation
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 detai
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 detai
|
By
Richard Hartmann
· #28
·
|
|
Data analysis use case collection & collation
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 th
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 th
|
By
Richard Hartmann
· #27
·
|
|
Meeting times
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
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
|
By
Richard Hartmann
· #26
·
|
|
Recommendations for Open Source Analytic (OLAP) system / API to mine Thanos/Prometheus data.
Hijacking top email to reply across the board. As many of you will know, I have been nagging Prometheus-team about this for years, so yes, I think we should cover this. At PromCon 2017's dev summit ha
Hijacking top email to reply across the board. As many of you will know, I have been nagging Prometheus-team about this for years, so yes, I think we should cover this. At PromCon 2017's dev summit ha
|
By
Richard Hartmann
· #20
·
|
|
[SIG o11y] Third chair nomination : Steve Flanders
Dear all, as announced during yesterday's TOC call, Matt Young and I are suggesting Steve Flanders of Splunk & Open Telemetry as the third chair for our SIG. I will leave the honours of introduction t
Dear all, as announced during yesterday's TOC call, Matt Young and I are suggesting Steve Flanders of Splunk & Open Telemetry as the third chair for our SIG. I will leave the honours of introduction t
|
By
Richard Hartmann
· #11
·
|
|
[SIG o11y] Call cadence
Dear all, as announced during yesterday's TOC call, we will have our call fortnightly on every second Tuesday, 16:00 UTC, starting next week. Amye will also add it to our CNCF calendar. Best, Richard
Dear all, as announced during yesterday's TOC call, we will have our call fortnightly on every second Tuesday, 16:00 UTC, starting next week. Amye will also add it to our CNCF calendar. Best, Richard
|
By
Richard Hartmann
· #10
·
|
|
[SIG o11y] Tech lead nomination: Bartek (Bartłomiej Płotka)
Dear all, as announced during yesterday's TOC call, Matt Young and I are suggesting Bartek of Red Hat & Prometheus and Thanos as Tech Lead for our SIG. You can find Bartek's platform here: https://doc
Dear all, as announced during yesterday's TOC call, Matt Young and I are suggesting Bartek of Red Hat & Prometheus and Thanos as Tech Lead for our SIG. You can find Bartek's platform here: https://doc
|
By
Richard Hartmann
· #9
·
|
|
Meeting date
Dear all, before we start finding a meeting date, we would like to get a feeling for the room on overall meeting times. There are three different options in this privacy-preserving alternative to dood
Dear all, before we start finding a meeting date, we would like to get a feeling for the room on overall meeting times. There are three different options in this privacy-preserving alternative to dood
|
By
Richard Hartmann
· #7
·
|
|
SIG Observability has a TOC Liaison!
I think "next" is up to TOC's discretion, but "soon" sounds realistic.
I think "next" is up to TOC's discretion, but "soon" sounds realistic.
|
By
Richard Hartmann
· #6
·
|