Enhance AMP debug responses

[bretg]

AMP requests don’t currently have a way to report rejects that happen within the modularity workflow.

When &debug=1 is on the /amp endpoint, right now only ext.debug is supplied on the response. I propose we send the whole seatbid array and other trace info as well – any ORTB that would have been sent to the /auction endpoint should be there in AMP debug mode.

e.g.

{
    "targeting": {
         ...
    },
    "ortb2": {
        ... entire PBS ORTB response here ...
    }
}

If there are automated tests hitting the debug endpoint and parsing the results, then this would be a breaking change because ext.debug would now be ortb2.ext.debug.

[bretg]

Discussed in committee. Resolved to move to ortb2 instead of ext and not implement the &verbose=1 flag.

Anyone who's built a monitor using the debug field, will need to update the location where they're looking for debug.

[bsardo]

@Net-burst we discussed this in backlog. The group doesn't think we should tackle this one but since it has the 4.0 label on it I wanted to check with you. Thoughts?

[Net-burst]

I agree with that, @bsardo. IDK whether we should close the issue or not. But I have my doubts that this will ever be needed.