delta/gitlab/gitlab-ce.git/config/initializers/sentry.rb, branch document-lambda-deploy gitlab.com: gitlab-org/gitlab-ce.git refactor: remove Sentry from application settings 2019-06-25T19:17:19+00:00 Roger Meier r.meier@siemens.com 2019-04-30T20:06:08+00:00 946ffc67b711b39512a789213779d2736fcc0049 






feat: allow Sentry configuration to be passed on gitlab.yml
2019-04-30T16:10:57+00:00

Roger Meier
r.meier@siemens.com

2019-04-07T19:21:52+00:00

aebb2f70257882dd530b820f3cfdd67621d2a3fd












Send schema cache to Sentry on MissingAttributeError
2019-03-19T13:49:31+00:00

Sean McGivern
sean@gitlab.com

2019-03-15T19:28:00+00:00

58643cd5325f731799686daca8e1d9806851c320

We don't know why this happens, so this is an attempt to debug the
issue by sending a full list of all columns ActiveRecord knows about
when the error is raised.





We don't know why this happens, so this is an attempt to debug the
issue by sending a full list of all columns ActiveRecord knows about
when the error is raised.







Extract process_name from GitLab::Sentry
2019-01-16T13:29:05+00:00

Andrew Newdigate
andrew@gitlab.com

2019-01-16T13:29:05+00:00

2c0d69d310489af72f8689a07f3a28efd8065d8c

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.





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.







Log and pass correlation-id between Unicorn, Sidekiq and Gitaly
2018-12-06T19:46:14+00:00

Kamil Trzciński
ayufan@ayufan.eu

2018-12-05T20:54:40+00:00

39c1731a53d1014eab7c876d70632b1abf738712

The Correlation ID is taken or generated from received X-Request-ID.
Then it is being passed to all executed services (sidekiq workers
or gitaly calls).

The Correlation ID is logged in all structured logs as `correlation_id`.





The Correlation ID is taken or generated from received X-Request-ID.
Then it is being passed to all executed services (sidekiq workers
or gitaly calls).

The Correlation ID is logged in all structured logs as `correlation_id`.







Replace Gitlab::REVISION with Gitlab.revision and handle installations without a .git directory
2018-05-24T08:14:01+00:00

Rémy Coutable
remy@rymai.me

2018-05-24T07:57:54+00:00

d50a80a282b2ca145841774f4be154a977cccfd8

Signed-off-by: Rémy Coutable <remy@rymai.me>





Signed-off-by: Rémy Coutable <remy@rymai.me>







Send API parameters as extra data for sentry errors
2017-10-05T21:31:34+00:00

Alejandro Rodríguez
alejorro70@gmail.com

2017-10-03T00:52:19+00:00

60a35e4230404b84d4aee8015fb7821b0b194277












`current_application_settings` belongs on `Gitlab::CurrentSettings`
2017-08-31T12:38:33+00:00

Sean McGivern
sean@gitlab.com

2017-08-31T09:47:03+00:00

5883ce95efcc4cc04f949f9b4e66d73fbede94e2

The initializers including this were doing so at the top level, so every object
loaded after them had a `current_application_settings` method. However, if
someone had rack-attack enabled (which was loaded before these initializers), it
would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't
have that method.

To fix this:

1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need
   `Object.new.current_application_settings` to work.
2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it
   like that in several places.
3. Change the initializers to use that new form.





The initializers including this were doing so at the top level, so every object
loaded after them had a `current_application_settings` method. However, if
someone had rack-attack enabled (which was loaded before these initializers), it
would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't
have that method.

To fix this:

1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need
   `Object.new.current_application_settings` to work.
2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it
   like that in several places.
3. Change the initializers to use that new form.







Merge branch 'rs-filter-authentication_token' into 'security'

2016-12-09T00:23:09+00:00

Douwe Maan
douwe@gitlab.com

2016-12-06T01:05:06+00:00

6e1b52b8b9b83cb774a5f2f52d4b4355590f14f7


Add authentication_token to filter_parameters list

See merge request !2041





Add authentication_token to filter_parameters list

See merge request !2041






Don't send Private-Token headers to Sentry
2016-10-04T14:57:01+00:00

Jacob Vosmaer
jacob@gitlab.com

2016-10-04T14:35:41+00:00

437bebb0ff6e7deba6fd157ec6b55112e125731f

Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/22537





Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/22537