Codecov Report

Merging #1385 (b91a5ba) into master (2ccfcf3) will increase coverage by 0.50%.
The diff coverage is 97.22%.

@@            Coverage Diff             @@
##           master    #1385      +/-   ##
==========================================
+ Coverage   98.10%   98.60%   +0.50%     
==========================================
  Files         208      114      -94     
  Lines        9264     5460    -3804     
==========================================
- Hits         9088     5384    -3704     
+ Misses        176       76     -100     

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2ccfcf3...b91a5ba. Read the comment docs.

@st0012 since this was introduced, Sentry has gotten a bit noisier, particularly at app startup:

D, [2021-07-22T12:01:45.585642 #4] DEBUG -- sentry: Sentry HTTP Transport connecting to [redacted]
D, [2021-07-22T12:01:45.586754 #4] DEBUG -- sentry: config.async is set, BackgroundWorker is disabled

Neither of these pieces of information are really helpful/informative, even when debugging, and I'm wondering if some kind of configuration option could be made available to turn off these kinds of startup messages.

Also noticed a lot more noise on the INFO front @agrobbin. Is there a way to easily disable this or change the logging level for only Sentry (not my application logger's level)? So that I don't get INFO logs, only WARN+ logs? @st0012

Sending envelope [event] 239be5b06db81a09bdc3186d66723b21 to Sentry
Sending envelope [event] 239be5b06db81a09bdc3186d66723b22 to Sentry
Sending envelope [event] 239be5b06db81a09bdc3186d66723b23 to Sentry
Sending envelope [event] 239be5b06db81a09bdc3186d66723b24 to Sentry
Sending envelope [event] 239be5b06db81a09bdc3186d66723b25 to Sentry
Sending envelope [event] 239be5b06db81a09bdc3186d66723b26 to Sentry
Sending envelope [event] 239be5b06db81a09bdc3186d66723b27 to Sentry

@agrobbin @nvolker Sorry for the long delay. I just spotted this during PR searching.
Uou can give the SDK its own logger to: 1) silent the SDK logging completely 2) give it a different log level.

Example:

config.logger =Logger.new(nil)

# or

config.logger = Logger.new($stdout)
config.logger.level = Logger::WARN