{"action":"opened","issue":{"url":"https://api.github.com/repos/airbrake/airbrake/issues/759","repository_url":"https://api.github.com/repos/airbrake/airbrake","labels_url":"https://api.github.com/repos/airbrake/airbrake/issues/759/labels{/name}","comments_url":"https://api.github.com/repos/airbrake/airbrake/issues/759/comments","events_url":"https://api.github.com/repos/airbrake/airbrake/issues/759/events","html_url":"https://github.com/airbrake/airbrake/issues/759","id":236200366,"number":759,"title":"Using server IP address not as useful in real world debugging","user":{"login":"urkle","id":101123,"avatar_url":"https://avatars3.githubusercontent.com/u/101123?v=3","gravatar_id":"","url":"https://api.github.com/users/urkle","html_url":"https://github.com/urkle","followers_url":"https://api.github.com/users/urkle/followers","following_url":"https://api.github.com/users/urkle/following{/other_user}","gists_url":"https://api.github.com/users/urkle/gists{/gist_id}","starred_url":"https://api.github.com/users/urkle/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/urkle/subscriptions","organizations_url":"https://api.github.com/users/urkle/orgs","repos_url":"https://api.github.com/users/urkle/repos","events_url":"https://api.github.com/users/urkle/events{/privacy}","received_events_url":"https://api.github.com/users/urkle/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-06-15T13:55:54Z","updated_at":"2017-06-15T13:55:54Z","closed_at":null,"body":"(from bug #266 )\r\n> Remote address in the summary tab shows IP address of the server that sent the error. This is useful when you have different versions of the code deployed on different servers. So this is a feature, not a bug.\r\n\r\nThis is actually not very useful, as I have other identifiers to know which server the error came from.. Most of the time when I'm needing to look are remote IP & remote country I am wanting to know what client address caused the issue..  that is I want the ability to see if a bunch of requests causing errors are coming in from a single country or IP address..\r\n\r\nRight now I have GLOBALLY pinned env.headers.HTTP_X_FORWARDED_FOR, however that uses up one of the FEW global pins I have. and it doesn't give me the country information readily either.\r\n\r\nIMHO these two fields are very badly named and they should be labeled \"Server addresses\" and \"Server countries\" as that will greatly reduce confusion."}}
{"actor":{"display_login":"urkle"}}