You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
?The text was updated successfully, but these errors were encountered: