record tmax timeout error in adapter error metric #3104
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have a bidderRequest loop, which goes through each bidder request. Inside this loop, PBS sends a request to the bidder server and handles the bidder's response or any errors that may occur.
Within this loop, we gather all errors related to bidders using errorsToMetric() and then record these errors into
AdapterErrors
metric using RecordAdapterRequest()PR makes changes to handle tmax timeout error. This means that if a tmax timeout error occurs then it should be included and recorded in the
AdapterErrors
metric as well.