For now, this just adds some logging around the errors thrown in the collections API. Why are we doing this? We periodically receive malicious probing requests to this service looking for vulnerabilities and would like to increase our visibility of the errors these requests are throwing.
How should a reviewer test this change?
This is a very small change and should be a no-op in production. It can be tested by hitting an unimplemented collections API endpoint and seeing a new client error appear in the logs.
How can success be measured?
Who should look at this?
Tested? Documented?
[ ] locally by committer
[ ] locally by Guardian reviewer
[ ] on the Guardian's TEST environment
[ ] relevant documentation added or amended (if needed)
All deployment options
- [Deploy build 12487 to TEST](https://riffraff.gutools.co.uk/deployment/deployAgain?project=media-service%3A%3Agrid%3A%3Aall&build=12487&stage=TEST&updateStrategy=MostlyHarmless&action=deploy)
- [Deploy parts of build 12487 to TEST by previewing it first](https://riffraff.gutools.co.uk/preview/yaml?project=media-service%3A%3Agrid%3A%3Aall&build=12487&stage=TEST&updateStrategy=MostlyHarmless)
github-actions[bot]
commented
4 months ago
What does this change?
For now, this just adds some logging around the errors thrown in the collections API. Why are we doing this? We periodically receive malicious probing requests to this service looking for vulnerabilities and would like to increase our visibility of the errors these requests are throwing.
How should a reviewer test this change?
This is a very small change and should be a no-op in production. It can be tested by hitting an unimplemented collections API endpoint and seeing a new client error appear in the logs.
How can success be measured?
Who should look at this?
Tested? Documented?