Send errors and warnings only in debug mode

[bretg]

Consider:

• sending errors and warnings only in debug mode
• whether it would be valuable for errors and warnings to be separate from bidder HTTP requests and the resolvedrequest
• whether we should merge the ext.prebid.trace functionality with this somehow. Trace is currently used only for detailed module debug output.

We need to get feedback from publishers about their use cases around PBS output.

The Professor Prebid extension can set the debug flag to be able to highlight warnings and errors.

[bretg]

Discussed in committee. Leaning towards errors and warnings being separately configurable:

• returned by default
• go into debug (HTTP calls)
• go into trace (module tracing)

Definitions:

• "critical error" - PBS cancels the entire auction. e.g. JSON schema validation.
• "non-critical error" - something major, but PBS as a whole still ran the auction. BidderA did not like a parameter and decided not to bid.
• "warning" - something minor. e.g. BidderA prefers a different parameter but is still going to bid. (e.g. ignoring multiformat)

Consider making JSON schema validation result configurable as well.

Next steps: we're going to spend a chunk of time in next week's backlog review to see if we can come up with a vision for configurable error and warning treatment.

[bretg]

We spent some time in the backlog session, but did not finalize a proposal. There's general agreement that improvements could be made.

Next steps:

• pin down more precisely what is currently happening: when errors and warnings are emitted, how adapters distinguish
• outline a specific proposal. We may not make it in time for 3.0, which is ok.

[rajeshb10]

Error Message : {"description":"Server status is not ok!","status":"SERVER_STATUS_WARNING"}

[bretg]

@rajeshb10 - please help us understand what you're proposing here?