2c0d69d310
GitLab::Sentry has a program_context method to determine whether a Sentry exception occurred in Sidekiq or rails. Since we will need similar functionality for distributed tracing, this change extracts the program_context method into GitLab.process_name for more general consumption.
27 lines
937 B
Ruby
27 lines
937 B
Ruby
# Be sure to restart your server when you modify this file.
|
|
|
|
require 'gitlab/current_settings'
|
|
|
|
def configure_sentry
|
|
# allow it to fail: it may do so when create_from_defaults is executed before migrations are actually done
|
|
begin
|
|
sentry_enabled = Gitlab::CurrentSettings.current_application_settings.sentry_enabled
|
|
rescue
|
|
sentry_enabled = false
|
|
end
|
|
|
|
if sentry_enabled
|
|
Raven.configure do |config|
|
|
config.dsn = Gitlab::CurrentSettings.current_application_settings.sentry_dsn
|
|
config.release = Gitlab.revision
|
|
|
|
# Sanitize fields based on those sanitized from Rails.
|
|
config.sanitize_fields = Rails.application.config.filter_parameters.map(&:to_s)
|
|
# Sanitize authentication headers
|
|
config.sanitize_http_headers = %w[Authorization Private-Token]
|
|
config.tags = { program: Gitlab.process_name }
|
|
end
|
|
end
|
|
end
|
|
|
|
configure_sentry if Rails.env.production? || Rails.env.development?
|