Yes, the outgoingRequestResult is specifically logging error messages we receive from third party sites only, not our final response. This logging was added to specifically diagnose issues we were having with upstream sites.

This does not mean the final result isn't resolved. We will still show an upstream error even if it was ultimately successful.

Final results aren't logged (I believe it is debug level) at this present time to production. I think historically we wanted to keep the amount of upstream logs to a minimum?

Final results are tallied via metrics instead, not logging: https://grafana.wikimedia.org/d/NJkCVermz/citoid?orgId=1&refresh=5m&from=now-30m&to=now

Sorry, it's a bit confusing!

If you wanted to get an idea on how many pdf links ultimately fail to resolve, then the best way right now is to look at the percentage of 415 errors, though we don't split that by content-type (though it is in the response). Could enhance metrics to do this, though!

Or I guess change logging to log the final result with the outgoingReqResult all in one log.

Change #1318714 had a related patch set uploaded (by WMDE-Fisch; author: WMDE-Fisch):

[mediawiki/services/citoid@master] Add contentType to response for logging

https://gerrit.wikimedia.org/r/1318714

Change #1318714 merged by jenkins-bot:

[mediawiki/services/citoid@master] Add contentType to response for logging

https://gerrit.wikimedia.org/r/1318714