rawlinp commented on issue #4048: There should be a way to correlate logs on the request made. URL: https://github.com/apache/trafficcontrol/issues/4048#issuecomment-548074557 They're exposed in the info logs, not the access logs (see `reqid`): ``` INFO: routing.go:196: 2019-10-30T12:18:26.893542-06:00: DELETE /api/1.3/cdns/353? handling (reqid 61443) DEBUG: plugin.go:178: 2019-10-30T12:18:26.893553-06:00: DEBUG plugins.OnRequest calling 0 plugins DEBUG: shared_handlers.go:295: 2019-10-30T12:18:26.894426-06:00: changelog for delete on object [::1]:49701 - admin [30/Oct/2019:12:18:26 -0600] "DELETE /api/1.3/cdns/353? HTTP/1.1" 200 81 1 "to-api-v14-client-tests" INFO: routing.go:199: 2019-10-30T12:18:26.895136-06:00: DELETE /api/1.3/cdns/353? handled (reqid 61443) in 1.583052ms INFO: routing.go:196: 2019-10-30T12:18:26.8954-06:00: GET /api/1.3/cdns?name=cdn4 handling (reqid 61444) ``` Although, I'm not sure if the `ERROR` log line includes the `reqid`. We could probably prepend it to the error log line if not already. It's fairly easy to trace which requests caused errors if there are no concurrent requests, since the error should be logged between the `handling` and `handled` lines, but that goes out the window if TO-Go is handling concurrent requests.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
