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
Given a brand spanking new Rails app with bugsnag configured with `app_type="service-a"`
When I run `bin/rake bugsnag:test_exception`
Then I receive an exception with an app_type of `rake`
Instead I would like to receive an exception with the app_type of `service-a`
Because we have a service oriented architecture, we were planning to use the app_type to distinguish between the many different services in our deployments, (mailer-api, mailer-worker, mailer-rake) so that all exceptions stream in to the same project and can be filtered/explored/acted upon in this manner.
The text was updated successfully, but these errors were encountered:
Consider the following scenario:
When looking at the rack middleware, I noticed that it used an
||=
to set the app_type; which seems reasonable. However on rake, it always sets the app_type torake
Because we have a service oriented architecture, we were planning to use the
app_type
to distinguish between the many different services in our deployments, (mailer-api
,mailer-worker
,mailer-rake
) so that all exceptions stream in to the same project and can be filtered/explored/acted upon in this manner.The text was updated successfully, but these errors were encountered: