From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/28242] extend server http-response metrics with artifact-type content
Date: Wed, 06 Oct 2021 21:14:29 +0000 [thread overview]
Message-ID: <bug-28242-10460-U4Uj6C50cE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28242-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28242
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Frank Ch. Eigler <fche at redhat dot com> ---
commit 260a3105cc0e378882110ba787cd58815183c454 (HEAD -> master, origin/master,
origin/HEAD)
Author: Di Chen <dichen@redhat.com>
Date: Wed Oct 6 17:04:08 2021 -0400
PR28242: debuginfod prometheus metric widening
This patch aims to extend http_responses_* metrics with another label
"type" by getting the extra artifact-type content added as a new
key=value tag.
v2, tweaked patch to perform artifact-type sanitization at point of
vulnerability rather than in general metric tabulation logic.
Signed-off-by: Di Chen <dichen@redhat.com>
Signed-off-by: Frank Ch. Eigler <fche@redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-10-06 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 14:15 [Bug debuginfod/28242] New: extend server http-response metrics with result code fche at redhat dot com
2021-09-10 16:01 ` [Bug debuginfod/28242] " dichen at redhat dot com
2021-09-20 15:47 ` dichen at redhat dot com
2021-09-21 16:19 ` [Bug debuginfod/28242] extend server http-response metrics with artifact-type content dichen at redhat dot com
2021-10-06 21:14 ` fche at redhat dot com [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=bug-28242-10460-U4Uj6C50cE@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.org \
/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).