gitlab-org--gitlab-foss/lib/gitlab/metrics
Sean McGivern 5883ce95ef current_application_settings belongs on Gitlab::CurrentSettings
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.
2017-08-31 13:38:33 +01:00
..
subscribers
base_sampler.rb Add sidekiq metrics endpoint and add http server to sidekiq 2017-08-07 17:13:02 +00:00
delta.rb
influx_db.rb current_application_settings belongs on Gitlab::CurrentSettings 2017-08-31 13:38:33 +01:00
influx_sampler.rb Instrument Unicorn with Ruby exporter 2017-07-04 15:28:34 +00:00
instrumentation.rb
method_call.rb
metric.rb
null_metric.rb
prometheus.rb Update Prometheus gem to version that explicitly calls munmap 2017-07-19 08:54:39 +00:00
rack_middleware.rb
requests_rack_middleware.rb Rename ConnectionRackMiddleware to RequestsRackMiddleware. 2017-07-13 00:46:17 +02:00
sidekiq_metrics_exporter.rb Add sidekiq metrics endpoint and add http server to sidekiq 2017-08-07 17:13:02 +00:00
sidekiq_middleware.rb
system.rb Enable Style/DotPosition Rubocop 👮 2017-06-21 13:48:12 +00:00
transaction.rb
unicorn_sampler.rb Instrument Unicorn with Ruby exporter 2017-07-04 15:28:34 +00:00