{"action":"opened","issue":{"url":"https://api.github.com/repos/cloudfoundry/gorouter/issues/148","repository_url":"https://api.github.com/repos/cloudfoundry/gorouter","labels_url":"https://api.github.com/repos/cloudfoundry/gorouter/issues/148/labels{/name}","comments_url":"https://api.github.com/repos/cloudfoundry/gorouter/issues/148/comments","events_url":"https://api.github.com/repos/cloudfoundry/gorouter/issues/148/events","html_url":"https://github.com/cloudfoundry/gorouter/issues/148","id":173564469,"number":148,"title":"X-Request-Id instead of X-Vcap-Request-Id","user":{"login":"oppegard","id":86445,"avatar_url":"https://avatars.githubusercontent.com/u/86445?v=3","gravatar_id":"","url":"https://api.github.com/users/oppegard","html_url":"https://github.com/oppegard","followers_url":"https://api.github.com/users/oppegard/followers","following_url":"https://api.github.com/users/oppegard/following{/other_user}","gists_url":"https://api.github.com/users/oppegard/gists{/gist_id}","starred_url":"https://api.github.com/users/oppegard/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oppegard/subscriptions","organizations_url":"https://api.github.com/users/oppegard/orgs","repos_url":"https://api.github.com/users/oppegard/repos","events_url":"https://api.github.com/users/oppegard/events{/privacy}","received_events_url":"https://api.github.com/users/oppegard/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-26T23:51:21Z","updated_at":"2016-08-26T23:51:21Z","closed_at":null,"body":"By default, a Ruby on Rails app will tag all logs with the value of X-Request-Id. For example, here's a request to a Rails 5 app on Pivotal Web Services:\r\n\r\n```sh\r\n$ curl -I https://rails5.cfapps.io/\r\nHTTP/1.1 200 OK\r\nContent-Type: text/html; charset=utf-8\r\nDate: Fri, 26 Aug 2016 23:30:36 GMT\r\nX-Request-Id: 55bdeb17-ad2d-4c59-b033-bee8a8e6430d\r\nX-Runtime: 0.002347\r\nX-Vcap-Request-Id: 4bf49bd8-7e62-4a09-720c-2cd4443e8d87\r\nConnection: keep-alive\r\n```\r\n\r\nAnd the corresponding `cf logs` output:\r\n```\r\n2016-08-26T17:30:36.49-0600 [APP/0]      OUT I, [2016-08-26T23:30:36.498456 #20]  INFO -- : [55bdeb17-ad2d-4c59-b033-bee8a8e6430d] method=HEAD path=/ format=*/* controller=WelcomeController action=index status=200 duration=1.13 view=0.81 db=0.00 params={}\r\n2016-08-26T17:30:36.50-0600 [RTR/3]      OUT rails5.cfapps.io - [26/08/2016:23:30:36.497 +0000] \"HEAD / HTTP/1.1\" 200 0 0 \"-\" \"curl/7.43.0\" 10.10.2.230:38653 x_forwarded_for:\"50.232.79.2\" x_forwarded_proto:\"https\" vcap_request_id:4bf49bd8-7e62-4a09-720c-2cd4443e8d87 response_time:0.007176212 app_id:3e7d31a6-e880-4f50-ae05-149fc44c4257\r\n```\r\n\r\nThe app log includes X-Request-Id of `55bdeb17-ad2d-4c59-b033-bee8a8e6430d`. Has there been consideration of adopting X-Request-Id in place of X-Vcap-Request-Id? It would improve the developer experience of correlating gorouter logs with application logs."}}
{"actor":{"display_login":"oppegard"}}