Set the environment for deploy reporting in Capistrano about appsignal-ruby HOT 7 CLOSED

The PR was merged.
I'll keep you up-to-date on a new gem release

from appsignal-ruby.

Hi @adamof, if I understand the issue correctly you're using multiple capistrano stages (staging and beta), but no different staging and beta Rails environments.

You do want to track the beta stage, which runs in the rails environment staging. However, since we listen to the beta capistrano stage you don't get a deploy notification on for beta deploys.

What we can do is allow you to set a specific appsignal_env in capistrano. By default it listens to the capistrano stage, but if these don't match, as in your case, you can override it.

# config/deploy/staging.rb
set :stage, :staging
set :rails_env, :staging
# AppSignal env is `:staging`

# config/deploy/beta.rb
set :stage, :beta
set :rails_env, :staging
set :appsignal_env, :staging

I think this would solve your problem?

As an aside: In your setup it does mean everything from both stages (staging and beta) are collected under the staging environment in AppSignal, which might clutter it a bit and you might not immediately be able to see what error comes from which stage.

from appsignal-ruby.

Hey @tombruijn thanks for the response! I think this solution would work great for us.
As far as the mixed environments go, this is not much of an issue for us at the minute.

from appsignal-ruby.

@adamof I made a PR for this change in PR #119

You can try it out by replacing gem 'appsignal' to this in your Gemfile:

# Gemfile
gem 'appsignal', git: '[email protected]:appsignal/appsignal-ruby.git', branch: 'capistrano_appsignal_env'

Let me know if this is the behavior you want.

from appsignal-ruby.

Yep, that works! 🎆

from appsignal-ruby.

Great to hear!

I'll get the PR reviewed, merged and released. Will update you once we release a new official gem version you can use directly.

from appsignal-ruby.

from appsignal-ruby.