PHPCBA-3: Request Identification

Issue Information

Issue Type: New Feature
Priority: Major
Status: Closed

Reported By:
Ben Tasker
Assigned To:
Ben Tasker
Project: PHPChangedBinaries (PHPCBA)
Resolution: Done (2015-01-30 12:46:24)
Components: PHP Client ,

Created: 2014-12-18 23:50:18
Time Spent Working

I occasionally see ChangedBinaries reports that include

API Request failed

But it's incredibly difficult to track down why they failed, especially if it's one request amongst may successful ones.

Need to think of the best way around it, although including a timestamp with the error string would be a start.

To help track down the failed request, it might be worth including a unique serial number within the URI of the request to the API (sha1 of time() and hostname maybe?) and including that in the error message.

It'd then be easier to see whether the requests are getting through to the API and failing for some reason, or simply not reaching the API at all.

Toggle State Changes


Repo: PHPChangedBinaries
Commit: bf81f2c5055d66a9eca66ec7346f9f0ba44fcd8f
Author: Ben Tasker <github@<Domain Hidden>>

Date: Thu Dec 18 23:57:38 2014 +0000
Commit Message: Basic per-request signature implemented to ease debugging of API comms issues. See PHPCBA-3

Modified (-)(+)

Webhook User-Agent


View Commit

Change has been deployed to a couple of systems that occasionally experience issues talking to the API, as it worked OK on the test server it should help identify the root cause for those systems too.
Murphys law being what it is, I've not had any more failed API requests since making this change. As the change hasn't introduced any issues, I'll close this issue.
btasker changed status from 'Open' to 'Resolved'
btasker added 'Done' to resolution
btasker changed status from 'Resolved' to 'Closed'