From: "Frank Ch. Eigler" <fche@redhat.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH] debuginfod: print filename for "cannot open archive" error
Date: Wed, 17 Aug 2022 06:58:46 -0400 [thread overview]
Message-ID: <20220817105846.GA4328@redhat.com> (raw)
In-Reply-To: <1d95d22d-9582-755a-9de1-3f5d8fc3ebe0@suse.cz>
Hi -
> Report the file that has such a problem so that one can inspect it.
> Signed-off-by: Martin Liska <mliska@suse.cz>
The complication with this type of change is that the exception text
objects also make it into the prometheus metrics. When file names and
such variables show up, they will bifurcate all the affected error
metrics into families.
Not sure what is the best solution to that. A separate verbose log
print to explain the specifics of this error? An extra parameter to
the exception object, which is only logged but not passed to
prometheus metric naming? Some other way?
- FChE
next prev parent reply other threads:[~2022-08-17 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 7:12 Martin Liška
2022-08-17 10:58 ` Frank Ch. Eigler [this message]
2022-08-17 11:18 ` [PATCH v2] " Martin Liška
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=20220817105846.GA4328@redhat.com \
--to=fche@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=mliska@suse.cz \
/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).