|
Re: Recommendations for Open Source Analytic (OLAP) system / API to mine Thanos/Prometheus data.
Hey Richi,
With respect to using R with Prometheus data, both Spark and Presto have the ability to write R programs against. Spark is much more mature in this space however. SparkR can run R functions
Hey Richi,
With respect to using R with Prometheus data, both Spark and Presto have the ability to write R programs against. Spark is much more mature in this space however. SparkR can run R functions
|
By
Rob Skillington
·
#21
·
|
|
Re: Recommendations for Open Source Analytic (OLAP) system / API to mine Thanos/Prometheus data.
On Wed, Jun 3, 2020 at 3:38 PM Rob Skillington <rob@...> wrote:
Just my two cents though, maybe at first it could be folded into SIG-Observability and later broken out perhaps.
The IETF, the RIPE,
On Wed, Jun 3, 2020 at 3:38 PM Rob Skillington <rob@...> wrote:
Just my two cents though, maybe at first it could be folded into SIG-Observability and later broken out perhaps.
The IETF, the RIPE,
|
By
RichiH Hartmann
·
#22
·
|
|
Re: Recommendations for Open Source Analytic (OLAP) system / API to mine Thanos/Prometheus data.
BTW, Looks like Dan also suggests Analytics is in scope of our SIGs currently: https://github.com/cncf/landscape/issues/1632#issuecomment-638763810 (:
Kind Regards,
Bartek
BTW, Looks like Dan also suggests Analytics is in scope of our SIGs currently: https://github.com/cncf/landscape/issues/1632#issuecomment-638763810 (:
Kind Regards,
Bartek
|
By
Bartłomiej Płotka
·
#23
·
|
|
Re: Recommendations for Open Source Analytic (OLAP) system / API to mine Thanos/Prometheus data.
> Thanks for those examples, a recommendation of using those would be amazing as well. What I will say might be controversial, but the goal of this initiative is NOT to steal projects or compete with
> Thanks for those examples, a recommendation of using those would be amazing as well. What I will say might be controversial, but the goal of this initiative is NOT to steal projects or compete with
|
By
Ricardo Aravena
·
#24
·
|
|
Re: [Action Required] Thanos to Incubation Due Diligence Ask For Review
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:
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:
|
By
Bartłomiej Płotka
·
#25
·
|
|
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
·
|
|
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
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
|
By
Richard Hartmann
·
#27
·
|
|
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
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
|
By
Richard Hartmann
·
#28
·
|
|
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
·
|
|
Re: Prometheus & Observability documentation
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
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
|
By
Amin Amos
·
#30
·
|
|
Re: 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
·
|
|
Re: Prometheus & Observability documentation
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
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
|
By
Arthur Silva Sens
·
#32
·
|
|
Re: Prometheus & Observability documentation
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
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
|
By
Bartłomiej Płotka
·
#33
·
|
|
Re: Prometheus & Observability documentation
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 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
|
By
RichiH Hartmann
·
#34
·
|
|
Hello after Summer: We are back with the SIG Observability Meetings!
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
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
|
By
Bartłomiej Płotka
·
#35
·
|
|
Re: Hello after Summer: We are back with the SIG Observability Meetings!
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
Do we have recordings for the meeting?
It is too late for me to join.
--
This is my life,but world of us~~
|
By
Michael Wang <xdragon007@...>
·
#36
·
|
|
Re: Hello after Summer: We are back with the SIG Observability Meetings!
We can consider recording those, yes (:
So far we did not.
Kind Regards,
Bartek Płotka (@bwplotka)
We can consider recording those, yes (:
So far we did not.
Kind Regards,
Bartek Płotka (@bwplotka)
|
By
Bartłomiej Płotka
·
#37
·
|
|
Re: Hello after Summer: We are back with the SIG Observability Meetings!
Factual correction:
https://www.youtube.com/playlist?list=PLj6h78yzYM2PJkFrpP6IT52KkdBvcvS_9
We should _resume_ recording ;)
Cheers,
Michael
--
Product Developer Advocate, AWS container
Factual correction:
https://www.youtube.com/playlist?list=PLj6h78yzYM2PJkFrpP6IT52KkdBvcvS_9
We should _resume_ recording ;)
Cheers,
Michael
--
Product Developer Advocate, AWS container
|
By
Hausenblas, Michael
·
#38
·
|
|
Re: Hello after Summer: We are back with the SIG Observability Meetings!
Yeah, great. Thanks.--
This is my life,but world of us~~
Yeah, great. Thanks.--
This is my life,but world of us~~
|
By
Michael Wang <xdragon007@...>
·
#39
·
|
|
Re: Hello after Summer: We are back with the SIG Observability Meetings!
> Factual correction:
😱
Kind Regards,
Bartek Płotka (@bwplotka)
> Factual correction:
😱
Kind Regards,
Bartek Płotka (@bwplotka)
|
By
Bartłomiej Płotka
·
#40
·
|