public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/28242] New: extend server http-response metrics with result code
Date: Tue, 17 Aug 2021 14:15:31 +0000	[thread overview]
Message-ID: <bug-28242-10460@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=28242

            Bug ID: 28242
           Summary: extend server http-response metrics with result code
           Product: elfutils
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: debuginfod
          Assignee: unassigned at sourceware dot org
          Reporter: fche at redhat dot com
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

Now, the http_requests_total{} prometheus metric includes only a
type={debuginfo,...} label, but not a http-result label (like in the
http_responses_* metrics).  That makes sense because the metrics are collected
at different times (beginning vs. end of request), but it makes computing
quantities like .... "how many successful debuginfo requests are we serving",
"how large are they"?.  We should consider merging the two metrics, or
synthesizing a new one that contains both request classification and success
labeling.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-08-17 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17 14:15 fche at redhat dot com [this message]
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

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@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).