Change Details

In order to provide data to SRE to triage 429 or other kinds of error, we need to capture endpoint called in log. We are already capturing the error message returned. **Implementation notes** - In the `(c *Client) do() ` method in `general/wmf`, log request URL alongside the error string. - Update unit test **Acceptance criteria** Once deployed and when an wmf API error occur, we should be able to see endpoint called and error message in the cloudwatch.

In order to provide data to SRE to triage 429 or other kinds of error, we need to capture endpoint called in log. We are already capturing the error message returned. **Implementation notes:** - In the `(c *Client) do() ` method in `general/wmf`, log request URL alongside the error string. - Update unit test **Acceptance criteria:** Once deployed and when an wmf API error occur, we should be able to see endpoint called and error message in the cloudwatch.

In order to provide data to SRE to triage 429 or other kinds of error, we need to capture endpoint called in log. We are already capturing the error message returned. **Implementation notes:** - In the `(c *Client) do() ` method in `general/wmf`, log request URL alongside the error string. - Update unit test **Acceptance criteria:** Once deployed and when an wmf API error occur, we should be able to see endpoint called and error message in the cloudwatch.