From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@redhat.com>, elfutils-devel@sourceware.org
Subject: Re: PATCH: PR27092 debuginfod improve low-memory operations
Date: Fri, 05 Feb 2021 23:09:52 +0100 [thread overview]
Message-ID: <e40c07cd2e346be8394e0cc15812d775015f6c11.camel@klomp.org> (raw)
In-Reply-To: <57bb92a3e14dde7fa9c2121aef447b2ce796b0f6.camel@klomp.org>
Hi,
Just for the list to have it archived.
We did briefly discuss this on irc.
The changes have already been pushed.
On Fri, 2021-02-05 at 18:24 +0100, Mark Wielaard wrote:
> On Thu, 2021-02-04 at 20:45 -0500, Frank Ch. Eigler via Elfutils-
> devel wrote:
> > - New prometheus metrics to track filesystem freespace, and more
> > details about some errors.
>
> This part looks fine.
>
> Maybe this is a general question about exposing metrics. But does this
> help people who want to do denial of service attacks? I mean by seeing
> what effect some queries might have on freespace/errors?
>
> Not a showstopper, but maybe something to think about before
> encouraging people to expose their metrics?
yeah hypothetically, and yet at the same time one needs that info more
to detect problems early
> > - Frequent checking of $TMPDIR freespace, to trigger fdcache
> > emergency flushes.
>
> This too looks fine.
>
> > - Switch to floating point prometheus metrics, to communicate
> > fractions - and short time intervals - accurately.
>
> You move all metrics to use doubles. Including the metrics that use
> integral values using inc_metric (the threads, _total and _count ones).
> I cannot tell how that looks on the Prometheus side. Isn't it better to
> keep those as integrals? Aka maybe inc_metric shouldn't call through to
> add_metric? Or maybe have two metric maps, one for counts and one for
> values/durations?
doubles are the native type for prometheus consumers, the textual form
doesn't really matter (and ieee doubles propagate 40+bit integers
exactly so that's okay)
might tweak the formatting to add all the digits of precision rather
than the c++ default, easily
> All code changes look fine. Please feel free to push if you think my
> questions above are a little silly :) The actual changes seem to do
> what you intended.
Cheers,
Mark
prev parent reply other threads:[~2021-02-05 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 1:45 Frank Ch. Eigler
2021-02-05 17:24 ` Mark Wielaard
2021-02-05 22:09 ` Mark Wielaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e40c07cd2e346be8394e0cc15812d775015f6c11.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=fche@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).