lp-scanner-team team mailing list archive
-
lp-scanner-team team
-
Mailing list archive
-
Message #00038
[Bug 1191017] Re: Logging the response the body for errors spams the e-mail report
Talked to Kevin some on this. I think what we're going to do is just
include error type, error code, and OOPS ID if there is one by default
and the entire response body if a debug flag is set to True
--
You received this bug notification because you are a member of The
Launchpad Security Scanner Dev Team, which is subscribed to lp-scanner.
https://bugs.launchpad.net/bugs/1191017
Title:
Logging the response the body for errors spams the e-mail report
Status in The Launchpad Security Scanner Project:
New
Bug description:
The only aspects of the LP error we really need are: error type, error
code, and an OOPS ID if one was generated. The rest is mostly garbage
which has an adverse affect on the e-mail reports readability. We
should either figure out a way to just report the error type, error
code, and OOPS ID in the report or log it to a separate file and
attach it to the e-mail. For example, the e-mail body could be a
short form of the log which just includes the potential security /
privacy violations and the attachment can be the full log that
includes all the error details if an error occurs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lp-scanner/+bug/1191017/+subscriptions
References