External requests made without Scout account configured

[abraham]

Without a Scout account, external requests are still made. It would be better if no requests were made by default. This makes it so I can't use this gem on a number of projects with more stringent security policies.

[itsderek23]

Good catch. We'll investigate.

/cc @cschneid - feels like a "passive" mode would help here. I can't recall if setting monitor: false still runs instrumentation, but just throws the output away.

Ideally, it'd be nice to not require a scout_apm.yml config file and run in passive mode so server_timing is more plug-and-play.

[daveallie]

Setting monitor: false no longer reports timing in the request header.

We don't use Scout, however were interested in this gem in development environments. To prevent the requests back to Scout, we just monkey patched ScoutApm::Reporter:

module ScoutApm
  class Reporter
    def report(_payload, _headers = {})
      # Do nothing
    end
  end
end

Request information still works, but no external requests to Scout.