Hah, I knew it would be a good idea to check with Björn :D Thanks Björn,
that's a great write-up!
Yes, that also convinced me about not allowing the dot as a normal
character for now. Lots of good arguments, but number 3 actually resonates
the most with me - why allow two different separator
sn't collide with
our existing strings, so you could just write something like:
m"some.metric.name.with.dots"{foo="bar"}
I'm not sure if I like that much more though
However, this is all irrelevant if we choose to accept dot anyway :)
>
As long as people stick to OTel
tax nicer for the vast
>> majority of people who need a change.
>>
>> Bryan
>>
>> On 24 May 2024, at 10:00, Julius Volz wrote:
>>
>>
>> Hi,
>>
>> While others are figuring out how to add UTF-8 support and other OTel
>> compatib
Hi,
While others are figuring out how to add UTF-8 support and other OTel
compatibility functionality to Prometheus, my brain has been trying to
figure out what all of this will mean for the normal Prometheus user, how
we should explain this new optionality in Prometheus, and what we should
No, that expression would give you the number of seconds since the start of
the last scrape of a target (or recording rule evaluation), relative to the
query evaluation timestamp.
For example, if you had a scrape interval of 15s, that value would move
somewhere roughly between 0s - 15s. See:
Since that's a metric that is standardized across our client libraries, we
should keep the existing name IMO. I'm also not sure if the naming doc is
that clear on whether a timestamp necessarily has to be named "timestamp"
vs. just "time". We also use just "time" in other places as well, like
Ah it's not public, but it currently contains four members (Matthias
Rampke, Julien Pivotto, Ben Kochie, Suraj Nath).
On Tue, Jul 18, 2023 at 1:06 AM Daniel Swarbrick
wrote:
> Should that URL be accessible to anybody? I get 404...
>
> On Wednesday, May 31, 2023 at 2:24:22 PM UTC+2 Ben Kochie
mail to prometheus-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-developers/CAMV%3D_gYviO9Ad%3DJXrHKHdZzMDgnu545rTEtPi_hnALvyWzaxAA%40mail.gmail.com
> <https://groups.google.com/d/msgid/prometheus-developers/C
discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-developers/MW4PR04MB7170F604B4C4803FD408B80EA520A%40MW4PR04MB7170.namprd04.prod.outlook.com
> <https://groups.google.com/d/msgid/prometheus-developers/MW4PR04MB7170F604B4C4803FD408B80EA520A%40MW4PR04MB7170.namprd04.prod.outlo
Woohoo, welcome! :)
On Mon, Apr 3, 2023 at 3:36 PM Jesus Vazquez wrote:
> Hello!!
>
> Thank you for the invitation to join the team!
>
> I believe I met some of you at PromCon 2022 and the dev summit on the day
> after, looking forward to working with you and sharing more time together.
>
> As
Same!
On Tue, Dec 20, 2022 at 4:15 PM Bjoern Rabenstein
wrote:
> On 13.12.22 11:19, Julien Pivotto wrote:
> >
> > In this sense, I think we should ask for an exception to the GB with the
> > following arguments:
>
> Silence means consent, right?
>
> But just in case you are wondering if anyone
then others and so I'm more willing to make trade-offs to fix that.
> I do expect us to run in production with HEAD & soft limit patches (as we
> already do) since doing so without it requires too much firefighting, so
> I'm happy to share more experience of that later.
> On Monday, 28
My reaction is similar to that of Ben and Julien: if metrics within a
target go partially missing, all kinds of expectations around aggregations,
histograms, and other metric correlations are off in ways that you wouldn't
expect in a normal Prometheus setup. Everyone expects full scrape failures,
Woot, welcome, Kemal!
On Thu, Nov 17, 2022 at 11:26 AM Matthias Loibl (MetalMatze) <
metalmatze...@gmail.com> wrote:
> Dear Prometheans,
>
> The Prometheus team is growing: I am happy to announce that Kemal
> Akkoyun is joining our team!
>
> Kemal has been active as a maintainer in
Woot, welcome Bryan!!
On Fri, Oct 7, 2022 at 10:44 AM Julien Pivotto
wrote:
> Dear Prometheans,
>
> The Prometheus team is growing: I am happy to announce that Bryan
> Boreham is joining our team!
>
> Bryan has done a lot of work in the past year to improve the
> performances of the Prometheus
ot; flag
> addition
> > too David if you like, also happy to wait too until that's available if
> > that's preferential.
> >
> >
> > On Wednesday, October 5, 2022 at 5:55:58 AM UTC-4 Julius Volz wrote:
> >
> > > The versioning aspect is a good point, I
s well, so
> it is shipped to everyone, and has a known version.
>
> On 05 Oct 11:22, Julius Volz wrote:
> > I do feel that formatting entire rule files would be in scope for
> promtool,
> > but more specialized formatting and manipulations of individual PromQL
> > que
I do feel that formatting entire rule files would be in scope for promtool,
but more specialized formatting and manipulations of individual PromQL
queries (while cool) should likely live in a separate tool. I see the scope
of promtool to be mostly a tool to interact with both the Prometheus
Great to hear, sounds good to me!
On Fri, Jul 8, 2022 at 12:26 PM Julien Pivotto
wrote:
> On 19 Jun 14:39, Julius Volz wrote:
> > That's actually an interesting idea. Disclaimer: I'm not neutral because
> > I'm a mini-investor in Dagger (just for fun). But the idea that the
That's actually an interesting idea. Disclaimer: I'm not neutral because
I'm a mini-investor in Dagger (just for fun). But the idea that the CI
pipeline would really run locally (or anywhere) exactly as it would run on
the final cloud CI provider is a nice one. I'd also leave that up to Julien
to
What does CLO mean? I couldn't find the definition of that acronym anywhere.
Yeah, an ADOPTERS.md file can't hurt. We could add a few seed entries and
then just post it on Twitter and let everyone add themselves.
On Wed, Mar 2, 2022 at 8:06 PM Julien Pivotto
wrote:
> Hello,
>
> CNCF is
NO (just think the pain will be large for such a rename)
On Thu, Jan 20, 2022 at 3:41 PM Julien Pivotto
wrote:
> Dear Prometheans,
>
> As per our governance, I'd like to cast a vote to rename the Blackbox
> Exporter to Prober.
> This vote is based on the following thread:
>
>
sion on the web visit
> https://groups.google.com/d/msgid/prometheus-developers/38fbf8a5-4079-47f1-9d6f-b30cefd17d6dn%40googlegroups.com
> <https://groups.google.com/d/msgid/prometheus-developers/38fbf8a5-4079-47f1-9d6f-b30cefd17d6dn%40googlegroups.com?utm_medium=email_source=footer>
&g
Hi Arthur,
Others can provide more input about Agent-mode specifics and the most
likely changes in that realm, but definitely it's still considered an
experimental feature (being hidden behind an experimental feature
flag --enable-feature=agent). The beta release was more of a 2.32 beta to
get
Hi Prometheans,
Please welcome Matthias Loibl as a new member to the Prometheus team!
Matthias has been a friend of the Prometheus project for a long time and
has helped out with a lot of community work (meetups, evangelism,
contributor office hours, best practices around SLOs, and more).
Hi Prometheans,
Please welcome Augustin Husson as a new member to the Prometheus team!
Augustin has built a lot of the underlying new PromQL editor language
support so far and is now also helping to maintain the React UI in
Prometheus.
Cheers,
Julius
--
You received this message because you
Hi Prometheans,
Please welcome Max Inden back as a member to the Prometheus team! Max had
previously been on the team, but left to explore other things in life.
However, he is now returning with one of his goals being to maintain an
official Prometheus Rust client library that he built in the
Hi,
As Björn pointed out somewhere, our roadmap page at
https://prometheus.io/docs/introduction/roadmap/ is pretty outdated. I'd
encourage everyone who is working on great new roadmap items (sparse
histograms are an obvious candidate, but maybe something else as well?) to
incorporate them there
Yes on both counts as well from me :)
On Mon, Nov 1, 2021 at 10:06 PM Julien Pivotto
wrote:
> 1 yes
> 2 yes
>
> On Friday, October 29, 2021 at 12:54:39 PM UTC+2 husson@gmail.com
> wrote:
>
>> Hello Prometheans,
>>
>> As you may know, one month ago we moved the code living in
>>
his discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-developers/02c1b689-b836-4e2f-a5e8-0cbc9463400en%40googlegroups.com
> <https://groups.google.com/d/msgid/prometheus-developers/02c1b689-b836-4e2f-a5e8-0cbc9463400en%40googlegroups.com?utm_medium=email_source=foo
>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Prometheus Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to prometheus-devel...
/d/msgid/prometheus-developers/f365ad0c-75b0-4bad-a75d-3980f0f61669n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
--
Julius Volz
PromLabs - promlabs.com
--
You received this message because you are subscribed to the Google Groups
"Prometheus Developers" group.
that this is fine unless someone objects.
Regards,
Julius
--
Julius Volz
PromLabs - promlabs.com
--
You received this message because you are subscribed to the Google Groups
"Prometheus Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
some people actually build Prometheus from the tags and
>>>> adding extra tags could break quite a few workloads. I do not think
>>>> that building tags is a xkcd 1172 case https://xkcd.com/1172/
>>>>
>>>> Additionally, there has been interests in t
ups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-developers/CAOJizGebmGjD3%2Bde%3Dzb3dGUSSoprV0zk3JdobpAmpQ%2BhFD7uiQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/prometheus-developers/CAOJizGebmGjD3%2Bde%3Dzb3dGUSSoprV0zk3Jdo
The proposal makes sense to me!
On Wed, Jun 23, 2021 at 4:50 PM Julien Pivotto
wrote:
> Hi all,
>
>
> https://docs.google.com/document/d/1VwqXi2TOb5KXaZY6Iio7411x64pJao3GusX8MqYsJ2g/edit?usp=sharing
>
> Here is a design doc about adding additional HTTP parameters to the
> /probe endpoint.
>
>
y team would be happy to write it and contribute, but only if people think
> it's useful (and it's not already being worked on by others).
>
>
>
> On Thu, Apr 15, 2021 at 4:58 AM Julius Volz wrote:
>
>> Great, PromLabs is donating its PromQL compliance tester to this e
:
> Yeah I’m fine with either - but would probably prefer a single big repo.
> Are your PromQl tests golang unit tests by any chance?
>
> On Tue, 13 Apr 2021 at 20:36, Julius Volz wrote:
>
>> I'm fine with the main org too. Then there's just the question of whether
>> we
so less
> keen on a dedicated prometheus-compatibility org... but could be convinced.
>
> Cheers
>
> Tom
>
> On Tue, Apr 13, 2021 at 1:48 PM Richard Hartmann <
> richih.mailingl...@gmail.com> wrote:
>
>> On Tue, Apr 13, 2021 at 2:16 PM Julius Volz
>> wr
Great! I think as we start taking compatibility more seriously, we could
even create a home for remote_write / PromQL / ... compatibility tests in
either the main Prometheus org, or in a dedicated "Prometheus Compatibility
Project" org?
On Tue, Apr 13, 2021 at 2:12 PM Tom Wilkie wrote:
> Hello
YES
On Thu, Mar 25, 2021 at 11:07 PM Julien Pivotto
wrote:
> Hereby I am calling a vote to allow the expansion on environment
> variables in the prometheus configuration file.
> Because it can be seen as an override of a previous vote[1], I am calling a
> new vote for this specific part.
>
>
her week... Big +1 from
> me. Mind adding a line for /storage/remote too?
>
> Thanks
>
> Tom
>
> On Mon, Mar 1, 2021 at 8:05 PM Julius Volz wrote:
>
>> Heya all,
>>
>> Julien often helpfully pings me on PRs that touch the React UI, but it
>> would
Heya all,
Julien often helpfully pings me on PRs that touch the React UI, but it
would be much nicer if I could somehow get auto-notified by GitHub
specifically of those that touch anything under /web/ui/. Others might feel
the same about their areas of purview.
GitHub has a CODEOWNERS file
+1 for distroless.
On Mon, Feb 1, 2021 at 3:03 PM Bjoern Rabenstein wrote:
> On 31.01.21 17:32, Ben Kochie wrote:
> > Another option is we could fully build our own busybox binary, with the
> > necessary fixes.
> >
> > I'm somewhat in favor of going distroless. With a large number of users
> >
That's great to hear :) Thank you for all the Debian packaging efforts!
On Sun, Jan 31, 2021 at 9:23 PM Martina Ferrari wrote:
> On 30/01/2021 21:55, Julius Volz wrote:
> > I had to look up what "BSP" means :) For anyone else curious, although I
> > realize I'm late: ht
etheus-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-developers/9362ad7d-edcc-10bb-9929-98069190da3b%40tina.pm
> .
>
--
Julius Volz
PromLabs - promlabs.com
--
You received this message because y
(I mean /a, /b, etc. of course, not a, b, ...)
On Sat, Jan 30, 2021 at 10:49 PM Julius Volz
wrote:
> On Fri, Jan 29, 2021 at 3:50 PM Vitaly Shupak
> wrote:
>
>> This is possible to do using relabel_configs:
>>
>> scrape_configs:
>> - job_
ometheus Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to prometheus-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-developers/c604b921-828a-
s/CAHJKeLrqLd5BYVZKvrW-A7MW%3DZksB9qP4Lk%3Dt2BLK-CcVok%2BrA%40mail.gmail.com
> <https://groups.google.com/d/msgid/prometheus-developers/CAHJKeLrqLd5BYVZKvrW-A7MW%3DZksB9qP4Lk%3Dt2BLK-CcVok%2BrA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
--
Julius Volz
PromLabs - promlabs.com
-
Yeah, since we also have oss-fuzz now, it's fine to remove fuzzit IMO.
On Tue, Dec 8, 2020 at 6:03 PM Brian Brazil <
brian.bra...@robustperception.io> wrote:
> On Tue, 8 Dec 2020 at 16:04, Julien Pivotto
> wrote:
>
>> Hi all,
>>
>> I'd like to remove fuzzit from Prometheus/prometheus.
>>
>> The
ser, admin, and
developer, because those roles often overlap in the Prometheus use case. If
you have opinions on that, do let us know!
Regards,
Julius
On Tue, Nov 17, 2020 at 1:23 PM 'Evelyn Pereira Souza' via Prometheus
Developers wrote:
> On 12.11.20 15:28, Julius Volz wrote:
> > Yes we sta
On Wed, Nov 11, 2020 at 4:14 PM 'Evelyn Pereira Souza' via Prometheus
Developers wrote:
> On 04.11.20 20:08, Julius Volz wrote:
> > It's hard to put an ETA on it currently. We are interested, but still
> > evaluating who will do this, and when. Let me try and get back to you
and get back to you in a
couple of days or so.
Regards,
Julius
On Wed, Nov 4, 2020 at 7:54 PM Evelyn Pereira Souza
wrote:
> On 04.11.20 15:57, Julius Volz wrote:
> > Hi Evelyn,
>
> Hi Julius
>
> > We discussed exactly this a couple of weeks ago with the CNCF, and
heus Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to prometheus-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-developers/598b9b4e-8
On Sat, Oct 31, 2020 at 10:44 PM Julien Pivotto
wrote:
> On 31 Oct 22:26, Julius Volz wrote:
> > Hi Tobi,
> >
> > I just had another brief exchange with Alex privately a few days ago. As
> > far as I understand it, his team will come up with a design idea in t
ecision making. All results of different iterations of course we can share
>> in the chat or via email.
>>
>> We very like Prometheus and what does it mean for the dev/devops
>> community so it deserves the great design, that we can help you create!
>>
>> On Wednesday, O
speedup
was big. Hopefully this will actually work better with Gatsby :)
> On Wed, Oct 14, 2020 at 6:26 PM Julius Volz wrote:
>
>> On Wed, Oct 14, 2020 at 6:20 PM Julien Pivotto <
>> roidelapl...@prometheus.io> wrote:
>>
>>> I am 1000% for this, but it
On Wed, Oct 14, 2020 at 6:20 PM Julien Pivotto
wrote:
> I am 1000% for this, but it gatsby a replacement for nanoc?
>
Yes. It's a JS/TS-based static site builder that would completely replace
nanoc if we determine that the compilation speed is ok.
--
You received this message because you are
Hi Prometheans,
I just came off a chat and call with Alex (CC-ed) from Pixel Point (
https://pixelpoint.io/). They are a web design agency that likes to
contribute back to OSS projects that they love and use, so Alex offered us
a redesign of the https://prometheus.io/ website for free (complete
On Thu, Aug 27, 2020 at 4:37 PM Bjoern Rabenstein
wrote:
> On 26.08.20 12:07, Julius Volz wrote:
> > For a start, I filled out dummy answers (without submitting) to get to
> see all
> > the subsequent pages of the application form. You can see all the
> questi
On Wed, Aug 26, 2020 at 10:16 AM Johannes Ziemke wrote:
> Hi everyone,
>
> as mentioned in chat yesterday, Docker will limit the number of layers a
> user can pull within 6 hours:
>
>
> https://www.docker.com/blog/scaling-docker-to-serve-millions-more-developers-network-egress
>
> This will
Nice.
Note that I pointed this out to the WakaTime owner (friend of mine), so
it's linked off of https://wakatime.com/community now :)
On Sat, Aug 22, 2020 at 11:18 PM Jacob Colvin
wrote:
> Hello Prometheus Developers,
>
> I recently created my first exporter in Go, wakatime_exporter, which
>
t;> at
>> > least the initial onboarding is automated as well.
>> >
>> > [1] - https://www.gitpod.io/blog/prebuilds/
>> >
>> > On Thu, 13 Aug 2020 at 22:50, Julien Pivotto <
>> roidelapl...@prometheus.io>
>> > w
s/latest/querying/api/#finding-series-by-label-matchers
There is an open issue to allow providing matcher constraints for the
labels metadata API as well:
https://github.com/prometheus/prometheus/issues/6178
> tirsdag den 2. april 2019 kl. 10.03.11 UTC+2 skrev bai...@gmail.com:
>
>
The logo link is broken in the deploy preview. Did you mean:
"./prometheus_logo_grey.svg" -> "/prometheus_logo_grey.svg"
On Sat, Aug 15, 2020 at 11:54 PM Julien Pivotto
wrote:
>
> Hi,
>
> Since that is an importand change, I want to check with this list if
> everyone is ok with the change:
>
Great, ok :)
I'll go ahead and work with Sven to get some Gitpod integration going then
for prometheus/prometheus as a start, unless someone else objects.
On Tue, Aug 4, 2020 at 8:52 PM Julien Pivotto
wrote:
> On 04 Aug 20:47, Julius Volz wrote:
> > I think it could be a really useful
I think it could be a really useful addition, both for new contributors, as
well as for reviewers / maintainers.
Julien, are you still opposed to this in principle? Any opinions by other
team members?
On Tue, Jul 28, 2020 at 11:30 AM Sven Efftinge wrote:
>
>> Besides I would be a bit surprised
.com/d/msgid/prometheus-developers/5da59638-f9d4-4c76-9df3-0b793b6656fao%40googlegroups.com
> <https://groups.google.com/d/msgid/prometheus-developers/5da59638-f9d4-4c76-9df3-0b793b6656fao%40googlegroups.com?utm_medium=email_source=footer>
> .
>
--
Julius Volz
PromLabs - promlabs.com
ation itself has < 1000 users according to GitHub.
>
> Le dim. 26 juil. 2020 à 14:42, Julius Volz a
> écrit :
>
>> +CC Sven from Gitpod
>>
>> On Sun, Jul 26, 2020 at 2:40 PM Julius Volz
>> wrote:
>>
>>> Hi,
>>>
>>> I got to
+CC Sven from Gitpod
On Sun, Jul 26, 2020 at 2:40 PM Julius Volz wrote:
> Hi,
>
> I got to know the people from Gitpod.io (https://www.gitpod.io/), and
> when I learned about their capability to not only use Gitpod as a regular
> online web-based dev environment, but t
Hi,
I got to know the people from Gitpod.io (https://www.gitpod.io/), and when
I learned about their capability to not only use Gitpod as a regular online
web-based dev environment, but to create ad-hoc environments based off PR
branches as CI checks, I thought it would be a really neat thing to
stop receiving emails from it, send
>>> an email to prometheus-devel...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/prometheus-developers/c731c457-f9c8-44da-b8f1-3253dab6cbffo%40googlegroups.com
>>> <https://groups
57-f9c8-44da-b8f1-3253dab6cbffo%40googlegroups.com
> <https://groups.google.com/d/msgid/prometheus-developers/c731c457-f9c8-44da-b8f1-3253dab6cbffo%40googlegroups.com?utm_medium=email_source=footer>
> .
>
--
Julius Volz
PromLabs - promlabs.com
--
You received this message beca
subscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-developers/20200703185353.GA486029%40oxygen
> .
>
--
Julius Volz
PromLabs - promlabs.com
--
You received this message because you are subscribed to the Google Groups
"Prome
ps.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-developers/26c62a54-059d-466c-a958-3e41aa3eb8fdn%40googlegroups.com
> <https://groups.google.com/d/msgid/prometheus-developers/26c62a54-059d-466c-a958-3e41aa3eb8fdn%40googlegroups.com?ut
Circling back on this vote long after its end date:
There have been 10 YES votes and no explicit NO votes, so the proposal has
passed.
On Thu, May 28, 2020 at 9:30 PM Julius Volz wrote:
> Dear Prometheans,
>
> https://github.com/prometheus/docs/pull/1640 proposes to list an
On Tue, Jun 23, 2020 at 9:47 AM Ben Kochie wrote:
> One subject that I don't see covered in the doc is spacing. There are
> several places where whitespace is optional, and it would be good to have a
> consistent opinion on it.
>
> * Between label selectors {foo="foo",bar="bar"} vs {foo="foo",
+CC Björn, who has been looking into sparse histograms for a while.
On Sun, Jun 21, 2020 at 2:44 AM Bashar Al Rawi
wrote:
> Hi all,
>
> I would like to propose a new format for storing bucket counts that can
> provide substantial improvements for sparse/bi-modal metrics along with
> changes to
Btw. in case we do end up going for a rename, I think Probe Exporter or
Prober Exporter would be a nice and descriptive name for what it's doing
(active probing of things).
On Thu, Jun 11, 2020, 12:03 Julius Volz wrote:
> Hi,
>
> Good motivation, personally I think that kind of re
Hi,
Good motivation, personally I think that kind of replacement is a good
thing to do with blacklist/whitelist (as is happening with flag names in
the Node Exporter). But I don't know how people feel about blackbox /
whitebox yet, as it doesn't carry the same negative/positive association
with
On Thu, May 28, 2020 at 10:53 PM Brian Brazil <
brian.bra...@robustperception.io> wrote:
> On Thu, 28 May 2020 at 20:30, Julius Volz wrote:
>
>> Dear Prometheans,
>>
>> https://github.com/prometheus/docs/pull/1640 proposes to list an
>> exporter for Fo
t can we make sure to mention* what kind of vote is
> it? (*majority/supermajority/yolo)
>
> I personally don't have opinion on this topic, but don't want to block the
> vote as well.
>
> Kind Regards,
> Bartek
>
> On Thu, 28 May 2020 at 20:35, Julius Volz wrote:
>
&
Dear Prometheans,
https://github.com/prometheus/docs/pull/1640 proposes to list an exporter
for Fortigate devices that uses a REST API. Brian's stance so far has been
to only add exporters for metrics that cannot be already produced by
another exporter on the list at
YES
After reading the arguments, I agree that Kelvin / temperature is special
enough to warrant an exception.
Overall I think it's good that we have rules like "base units only", but
it's ok to have occasional exceptions if enough people think it's worth it.
On Thu, May 28, 2020 at 8:52 PM
source*. Our license (Apache 2) allows almost
> anything. Free distribution, modification, forking etc. This ensures that
> there is always an open path if there will be a major blocker or conflict
> etc. It does not mean that forks are often.
>
> Kind Regards,
> Bartek
>
>
> On Tu
On Tue, May 26, 2020 at 10:57 PM Julien Pivotto
wrote:
> On 26 May 22:55, Julius Volz wrote:
> > On Tue, May 26, 2020 at 10:17 PM Bartłomiej Płotka
> > wrote:
> >
> > > Hi
> > >
> > > I support 100% of what Julius said:
> > >
> &
> Kind Regards,
> Bartek
>
> On Mon, 25 May 2020 at 20:53, Julien Pivotto
> wrote:
>
>> On 25 May 19:41, Richard Hartmann wrote:
>> > On Mon, May 25, 2020 at 7:08 PM Julius Volz
>> wrote:
>> >
>> > > I would also want to understand a bit more
t; >
> > Kind Regards,
> > Bartek
> >
> > On Mon, 25 May 2020 at 20:53, Julien Pivotto >
> > wrote:
> >
> > > On 25 May 19:41, Richard Hartmann wrote:
> > > > On Mon, May 25, 2020 at 7:08 PM Julius Volz
> > > wrote:
In general, +10 for a change in this direction, since currently the balance
is too much in favor of inaction - it's really easy to veto something, but
really hard to unblock it because team-wide votes are high-overhead.
I would also want to understand a bit more specifically how this would work
following the raw results as they come in live,
they are written into this spreadsheet:
https://docs.google.com/spreadsheets/d/1piPNpm-JaksUxHoMlJvxFOy35Mwhtt2iSLInihPPe7w/edit?usp=sharing
On Fri, May 22, 2020 at 3:34 PM Julius Volz wrote:
> Hi everyone,
>
> the Prometheus Team would like
Hi everyone,
the Prometheus Team would like to learn more about how people use and
operate Prometheus. For this purpose, we would love it if you could take a
couple of minutes to fill out this survey:
https://forms.gle/jjp2AqHttZYYrYkR7
Note that all questions are *optional*, so feel free to
both platforms
> and get the benefits of both projects. We could see if this in practice
> reaps any practical benefits during the course of a trial period of a
> couple of months.
>
> On Wednesday, 13 May 2020 18:56:20 UTC+1, Julius Volz wrote:
>>
>> +cc Yevgeny fr
:)
> Best regards,
> —octo
>
> (*) In theory. I'm not operating such a setup myself.
>
> On 2020-05-10 13:22, Julius Volz wrote:
> > That's a good question - googling I found
> > https://collectd.org/wiki/index.php/Plugin:Write_Prometheus, which
> > says:
> >
>
och wrote:
> On Sat, May 9, 2020, at 04:23, Ben Kochie wrote:
>
> On Fri, May 8, 2020, 16:10 Julius Volz wrote:
>
> By some historic accident I became the maintainer of the collectd exporter
> (https://github.com/prometheus/collectd_exporter), although I have never
> use
Hi everyone,
By some historic accident I became the maintainer of the collectd exporter (
https://github.com/prometheus/collectd_exporter), although I have never
used collectd myself and know very little about it. This has led to some
neglect from my side...
Does anyone feel invested in collectd
Ping... Ben, any opinion on how to proceed?
On Thu, Apr 16, 2020 at 2:24 PM Julius Volz wrote:
> +cc SuperQ (Ben)
>
> Sounds reasonable to me at a first glance.
>
> On Wed, Apr 15, 2020 at 2:56 PM Naseem Ullah wrote:
>
>> bump
>>
>> --
>> You receiv
Agreed as well under these circumstances.
On Thu, Apr 23, 2020 at 1:53 PM Matthias Rampke
wrote:
> I agree, if we plan on releasing 1.0, have an RC, a security review for a
> feature marked experimental doesn't need to hold things up. We should make
> it clear when we consider TLS "ready for
Hi Sudhakar,
This is the development mailing list for Prometheus - questions about usage
are better asked (and you'll get better replies) on the Prometheus users
mailing list: https://groups.google.com/forum/#!forum/prometheus-users (see
also https://prometheus.io/community/).
Cheers,
Julius
On
On Fri, Apr 17, 2020 at 5:46 PM 'Diana Payton' via Prometheus Developers <
prometheus-developers@googlegroups.com> wrote:
>
>
>> Question is, does someone feel called upon (and has the capacity) to
>> coordinate such a style guide and structural master plan?
>>
>
> I would recommend starting with
Agreed with everything that Björn said. Great that we actually all agree on
more than the controversial tone here could have suggested.
Question is, does someone feel called upon (and has the capacity) to
coordinate such a style guide and structural master plan?
On Fri, Apr 17, 2020 at 1:19 PM
1 - 100 of 112 matches
Mail list logo
