Do not run minutely probes on console

[unflxw]

When running the Rails console, the minutely probes should not be active.

Fixes #962.

[backlog-helper]

✔️ All good!

New issue guide | Backlog management | Rules | Feedback

[unflxw]

Forgot to add changeset, pushed it directly to main 🙊 d63d176 -- Nevermind, I played myself. There was already a changeset. Undone.

[jjb]

Great! Does this essentially disable all aspects of appsignal for console, or just the minutely probe? If some parts are left on, is that by design?

I have this in my bin/rails stub:

if ARGV.include?('console') || ARGV.include?('c')
  ENV['APPSIGNAL_ACTIVE'] = 'false'
end

[unflxw]

@jjb This disables the minutely probes only.

I suppose we could disable all of AppSignal on the console by default, but I'm thinking that it might be convenient for AppSignal to be active in the Rails console, in order to be able to use it to test AppSignal itself. I'll raise this with the team.

I take it that your preference would be for it to be disabled? If so, could you elaborate on why? Have you encountered any issues when AppSignal is active in the Rails console?

[jjb]

gotcha

If i remember correctly from several months ago, the problems were:

• mystery hosts with unhelpful names showing up on the appsignal dashboard (but maybe this was not from console but instead from things like rails db:migrate... or maybe both)
• maybe some sort of logging output when console was starting up? only in some environments?