Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include Heroku dyno name in exception reports #333

Closed
jturkel opened this issue Nov 17, 2016 · 0 comments
Closed

Include Heroku dyno name in exception reports #333

jturkel opened this issue Nov 17, 2016 · 0 comments

Comments

@jturkel
Copy link

jturkel commented Nov 17, 2016

It would be useful to know which Heroku dyno exceptions are coming from so we can more easily correlate Bugsnag exception reports with log information.

It looks like Configuration#default_hostname explicitly doesn't return the hostname when running in Heroku which makes sense since hostnames are ephemeral. Would it be possible to instead return the dyno name when running in Heroku i.e. change the implementation of this method to ENV["DYNO"] || Socket.gethostname?

kattrali added a commit that referenced this issue Oct 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant