Deploy tracking troubleshooting
For more general information on tracking your application’s deploys, Please read our article on deploy tracking.
Deploy Tracking is not resolving errors for your environment?
Reason 1: Environment name does not match exactly
Deploy tracking environment names are case sensitive. Therefore
production would be treated as different environments. Ensure that the
environment string you specify for your deploys is an exact match of the
environment string of your errors.
If you are using the airbrake Ruby gem,
you may want to check that
RAILS_ENV is identical to the
variable you initialized your notifier with.
Reason 2: Resolve all errors after a deploy is unchecked
The Resolve all errors after a deploy setting is enabled by default, but it can be disabled. It can be found on your project’s settings page.
Errors are not associated with deploys, and vice-versa
Deploys are considered ‘active’ until a new deploy to the same environment (e.g. ‘production’) replaces it. Airbrake associates new errors to the active deploy of the same environment.
If you use the optional App Version Airbrake
feature, Airbrake will only associate errors and deploys that have a matching
version string, in addition to a matching
Therefore, common solutions to errors and deploys not being associated are:
- Ensure that the
environmentstring is identical on the errors and the deploys.
- If you do not wish to use the App Version
behavior, do not specify
versionwith your errors or deploys.
- If you do wish to use the App Version
behavior, ensure the
versionof your errors and deploys are consistent.
If the notification of the deploy is not happening automatically when you do a
capistrano deploy, you may need to add
require 'airbrake/capistrano' to your
deploy.rb. Refer to the airbrake Ruby gem docs