gitlab-org--gitlab-foss/Gemfile.lock

1050 lines
25 KiB
Text
Raw Normal View History

2011-10-08 17:36:38 -04:00
GEM
remote: https://rubygems.org/
2011-10-08 17:36:38 -04:00
specs:
2015-11-25 11:18:44 -05:00
CFPropertyList (2.3.2)
RedCloth (4.2.9)
ace-rails-ap (2.0.1)
2015-11-25 11:18:44 -05:00
actionmailer (4.2.4)
actionpack (= 4.2.4)
actionview (= 4.2.4)
activejob (= 4.2.4)
mail (~> 2.5, >= 2.5.4)
2015-11-25 11:18:44 -05:00
rails-dom-testing (~> 1.0, >= 1.0.5)
actionpack (4.2.4)
actionview (= 4.2.4)
activesupport (= 4.2.4)
rack (~> 1.6)
rack-test (~> 0.6.2)
2015-11-25 11:18:44 -05:00
rails-dom-testing (~> 1.0, >= 1.0.5)
rails-html-sanitizer (~> 1.0, >= 1.0.2)
actionview (4.2.4)
activesupport (= 4.2.4)
2014-05-29 08:13:01 -04:00
builder (~> 3.1)
erubis (~> 2.7.0)
2015-11-25 11:18:44 -05:00
rails-dom-testing (~> 1.0, >= 1.0.5)
rails-html-sanitizer (~> 1.0, >= 1.0.2)
activejob (4.2.4)
activesupport (= 4.2.4)
globalid (>= 0.3.0)
activemodel (4.2.4)
activesupport (= 4.2.4)
2014-05-29 08:13:01 -04:00
builder (~> 3.1)
2015-11-25 11:18:44 -05:00
activerecord (4.2.4)
activemodel (= 4.2.4)
activesupport (= 4.2.4)
arel (~> 6.0)
2015-08-25 21:42:46 -04:00
activerecord-deprecated_finders (1.0.4)
2015-11-25 11:18:44 -05:00
activerecord-session_store (0.1.2)
2015-08-25 21:42:46 -04:00
actionpack (>= 4.0.0, < 5)
activerecord (>= 4.0.0, < 5)
railties (>= 4.0.0, < 5)
2015-11-25 11:18:44 -05:00
activesupport (4.2.4)
i18n (~> 0.7)
2014-05-29 08:13:01 -04:00
json (~> 1.7, >= 1.7.7)
minitest (~> 5.1)
2015-11-25 11:18:44 -05:00
thread_safe (~> 0.3, >= 0.3.4)
2014-05-29 08:13:01 -04:00
tzinfo (~> 1.1)
2015-03-28 19:39:32 -04:00
acts-as-taggable-on (3.5.0)
activerecord (>= 3.2, < 5)
addressable (2.3.8)
2015-11-25 11:18:44 -05:00
after_commit_queue (1.3.0)
activerecord (>= 3.0)
allocations (1.0.3)
2015-08-25 21:42:46 -04:00
annotate (2.6.10)
activerecord (>= 3.2, <= 4.3)
rake (~> 10.4)
2015-11-25 11:18:44 -05:00
arel (6.0.3)
2015-11-25 17:03:30 -05:00
asana (0.4.0)
faraday (~> 0.9)
faraday_middleware (~> 0.9)
faraday_middleware-multi_json (~> 0.0)
oauth2 (~> 1.0)
2015-11-25 11:18:44 -05:00
asciidoctor (1.5.3)
2015-08-25 21:42:46 -04:00
ast (2.1.0)
astrolabe (1.3.1)
parser (~> 2.2)
attr_encrypted (1.3.4)
encryptor (>= 1.3.0)
2014-12-19 09:15:29 -05:00
attr_required (1.0.0)
2016-01-01 21:11:39 -05:00
autoprefixer-rails (6.2.3)
2015-02-19 18:02:49 -05:00
execjs
json
2013-09-29 08:44:49 -04:00
awesome_print (1.2.0)
2015-08-25 21:42:46 -04:00
axiom-types (0.1.1)
descendants_tracker (~> 0.0.4)
ice_nine (~> 0.11.0)
thread_safe (~> 0.3, >= 0.3.1)
babosa (1.0.2)
2015-08-25 21:42:46 -04:00
bcrypt (3.1.10)
benchmark-ips (2.3.0)
2013-09-29 08:44:49 -04:00
better_errors (1.0.1)
coderay (>= 1.0.0)
2013-05-01 06:29:29 -04:00
erubis (>= 2.6.6)
2013-06-24 15:03:32 -04:00
binding_of_caller (0.7.2)
debug_inspector (>= 0.0.1)
2016-01-01 21:11:39 -05:00
bootstrap-sass (3.3.6)
autoprefixer-rails (>= 5.2.1)
sass (>= 3.3.4)
2015-12-27 21:19:01 -05:00
brakeman (3.1.4)
2015-03-02 20:28:47 -05:00
erubis (~> 2.6)
fastercsv (~> 1.5)
haml (>= 3.0, < 5.0)
2015-12-27 21:19:01 -05:00
highline (>= 1.6.20, < 2.0)
2015-03-02 20:28:47 -05:00
multi_json (~> 1.2)
2015-12-27 21:19:01 -05:00
ruby2ruby (>= 2.1.1, < 2.3.0)
ruby_parser (~> 3.7.0)
safe_yaml (>= 1.0)
2015-03-02 20:28:47 -05:00
sass (~> 3.0)
2015-12-27 21:19:01 -05:00
slim (>= 1.3.6, < 4.0)
2015-03-02 20:28:47 -05:00
terminal-table (~> 1.4)
2015-11-25 11:18:44 -05:00
browser (1.0.1)
2014-05-29 08:13:01 -04:00
builder (3.2.2)
2015-11-25 11:18:44 -05:00
bullet (4.14.10)
activesupport (>= 3.0.0)
uniform_notifier (~> 1.9.0)
bundler-audit (0.4.0)
bundler (~> 1.2)
thor (~> 0.18)
Storing of application metrics in InfluxDB This adds the ability to write application metrics (e.g. SQL timings) to InfluxDB. These metrics can in turn be visualized using Grafana, or really anything else that can read from InfluxDB. These metrics can be used to track application performance over time, between different Ruby versions, different GitLab versions, etc. == Transaction Metrics Currently the following is tracked on a per transaction basis (a transaction is a Rails request or a single Sidekiq job): * Timings per query along with the raw (obfuscated) SQL and information about what file the query originated from. * Timings per view along with the path of the view and information about what file triggered the rendering process. * The duration of a request itself along with the controller/worker class and method name. * The duration of any instrumented method calls (more below). == Sampled Metrics Certain metrics can't be directly associated with a transaction. For example, a process' total memory usage is unrelated to any running transactions. While a transaction can result in the memory usage going up there's no accurate way to determine what transaction is to blame, this becomes especially problematic in multi-threaded environments. To solve this problem there's a separate thread that takes samples at a fixed interval. This thread (using the class Gitlab::Metrics::Sampler) currently tracks the following: * The process' total memory usage. * The number of file descriptors opened by the process. * The amount of Ruby objects (using ObjectSpace.count_objects). * GC statistics such as timings, heap slots, etc. The default/current interval is 15 seconds, any smaller interval might put too much pressure on InfluxDB (especially when running dozens of processes). == Method Instrumentation While currently not yet used methods can be instrumented to track how long they take to run. Unlike the likes of New Relic this doesn't require modifying the source code (e.g. including modules), it all happens from the outside. For example, to track `User.by_login` we'd add the following code somewhere in an initializer: Gitlab::Metrics::Instrumentation. instrument_method(User, :by_login) to instead instrument an instance method: Gitlab::Metrics::Instrumentation. instrument_instance_method(User, :save) Instrumentation for either all public model methods or a few crucial ones will be added in the near future, I simply haven't gotten to doing so just yet. == Configuration By default metrics are disabled. This means users don't have to bother setting anything up if they don't want to. Metrics can be enabled by editing one's gitlab.yml configuration file (see config/gitlab.yml.example for example settings). == Writing Data To InfluxDB Because InfluxDB is still a fairly young product I expect the worse. Data loss, unexpected reboots, the database not responding, you name it. Because of this data is _not_ written to InfluxDB directly, instead it's queued and processed by Sidekiq. This ensures that users won't notice anything when InfluxDB is giving trouble. The metrics worker can be started in a standalone manner as following: bundle exec sidekiq -q metrics The corresponding class is called MetricsWorker.
2015-12-09 10:45:51 -05:00
byebug (8.2.1)
2016-01-01 21:29:21 -05:00
cal-heatmap-rails (3.5.1)
2015-07-06 19:50:36 -04:00
capybara (2.4.4)
2011-10-08 17:36:38 -04:00
mime-types (>= 1.16)
nokogiri (>= 1.3.3)
rack (>= 1.0.0)
rack-test (>= 0.5.4)
xpath (~> 2.0)
2015-08-25 21:42:46 -04:00
capybara-screenshot (1.0.11)
2015-04-25 14:10:09 -04:00
capybara (>= 1.0, < 3)
launchy
carrierwave (0.9.0)
activemodel (>= 3.2.0)
activesupport (>= 3.2.0)
json (>= 1.7)
Storing of application metrics in InfluxDB This adds the ability to write application metrics (e.g. SQL timings) to InfluxDB. These metrics can in turn be visualized using Grafana, or really anything else that can read from InfluxDB. These metrics can be used to track application performance over time, between different Ruby versions, different GitLab versions, etc. == Transaction Metrics Currently the following is tracked on a per transaction basis (a transaction is a Rails request or a single Sidekiq job): * Timings per query along with the raw (obfuscated) SQL and information about what file the query originated from. * Timings per view along with the path of the view and information about what file triggered the rendering process. * The duration of a request itself along with the controller/worker class and method name. * The duration of any instrumented method calls (more below). == Sampled Metrics Certain metrics can't be directly associated with a transaction. For example, a process' total memory usage is unrelated to any running transactions. While a transaction can result in the memory usage going up there's no accurate way to determine what transaction is to blame, this becomes especially problematic in multi-threaded environments. To solve this problem there's a separate thread that takes samples at a fixed interval. This thread (using the class Gitlab::Metrics::Sampler) currently tracks the following: * The process' total memory usage. * The number of file descriptors opened by the process. * The amount of Ruby objects (using ObjectSpace.count_objects). * GC statistics such as timings, heap slots, etc. The default/current interval is 15 seconds, any smaller interval might put too much pressure on InfluxDB (especially when running dozens of processes). == Method Instrumentation While currently not yet used methods can be instrumented to track how long they take to run. Unlike the likes of New Relic this doesn't require modifying the source code (e.g. including modules), it all happens from the outside. For example, to track `User.by_login` we'd add the following code somewhere in an initializer: Gitlab::Metrics::Instrumentation. instrument_method(User, :by_login) to instead instrument an instance method: Gitlab::Metrics::Instrumentation. instrument_instance_method(User, :save) Instrumentation for either all public model methods or a few crucial ones will be added in the near future, I simply haven't gotten to doing so just yet. == Configuration By default metrics are disabled. This means users don't have to bother setting anything up if they don't want to. Metrics can be enabled by editing one's gitlab.yml configuration file (see config/gitlab.yml.example for example settings). == Writing Data To InfluxDB Because InfluxDB is still a fairly young product I expect the worse. Data loss, unexpected reboots, the database not responding, you name it. Because of this data is _not_ written to InfluxDB directly, instead it's queued and processed by Sidekiq. This ensures that users won't notice anything when InfluxDB is giving trouble. The metrics worker can be started in a standalone manner as following: bundle exec sidekiq -q metrics The corresponding class is called MetricsWorker.
2015-12-09 10:45:51 -05:00
cause (0.1)
2015-11-10 10:56:05 -05:00
charlock_holmes (0.7.3)
2015-11-25 11:18:44 -05:00
chunky_png (1.3.5)
cliver (0.3.2)
coderay (1.1.0)
coercible (1.0.0)
descendants_tracker (~> 0.0.1)
2015-05-29 00:05:14 -04:00
coffee-rails (4.1.0)
2011-10-08 17:36:38 -04:00
coffee-script (>= 2.2.0)
railties (>= 4.0.0, < 5.0)
2015-05-29 00:05:14 -04:00
coffee-script (2.4.1)
2011-10-08 17:36:38 -04:00
coffee-script-source
execjs
coffee-script-source (1.10.0)
colorize (0.7.7)
2015-12-10 12:45:36 -05:00
concurrent-ruby (1.0.0)
2015-08-25 21:42:46 -04:00
connection_pool (2.2.0)
2015-11-25 11:18:44 -05:00
coveralls (0.8.9)
json (~> 1.8)
rest-client (>= 1.6.8, < 2)
simplecov (~> 0.10.0)
term-ansicolor (~> 1.3)
thor (~> 0.19.1)
2015-11-25 11:18:44 -05:00
tins (~> 1.6.0)
Storing of application metrics in InfluxDB This adds the ability to write application metrics (e.g. SQL timings) to InfluxDB. These metrics can in turn be visualized using Grafana, or really anything else that can read from InfluxDB. These metrics can be used to track application performance over time, between different Ruby versions, different GitLab versions, etc. == Transaction Metrics Currently the following is tracked on a per transaction basis (a transaction is a Rails request or a single Sidekiq job): * Timings per query along with the raw (obfuscated) SQL and information about what file the query originated from. * Timings per view along with the path of the view and information about what file triggered the rendering process. * The duration of a request itself along with the controller/worker class and method name. * The duration of any instrumented method calls (more below). == Sampled Metrics Certain metrics can't be directly associated with a transaction. For example, a process' total memory usage is unrelated to any running transactions. While a transaction can result in the memory usage going up there's no accurate way to determine what transaction is to blame, this becomes especially problematic in multi-threaded environments. To solve this problem there's a separate thread that takes samples at a fixed interval. This thread (using the class Gitlab::Metrics::Sampler) currently tracks the following: * The process' total memory usage. * The number of file descriptors opened by the process. * The amount of Ruby objects (using ObjectSpace.count_objects). * GC statistics such as timings, heap slots, etc. The default/current interval is 15 seconds, any smaller interval might put too much pressure on InfluxDB (especially when running dozens of processes). == Method Instrumentation While currently not yet used methods can be instrumented to track how long they take to run. Unlike the likes of New Relic this doesn't require modifying the source code (e.g. including modules), it all happens from the outside. For example, to track `User.by_login` we'd add the following code somewhere in an initializer: Gitlab::Metrics::Instrumentation. instrument_method(User, :by_login) to instead instrument an instance method: Gitlab::Metrics::Instrumentation. instrument_instance_method(User, :save) Instrumentation for either all public model methods or a few crucial ones will be added in the near future, I simply haven't gotten to doing so just yet. == Configuration By default metrics are disabled. This means users don't have to bother setting anything up if they don't want to. Metrics can be enabled by editing one's gitlab.yml configuration file (see config/gitlab.yml.example for example settings). == Writing Data To InfluxDB Because InfluxDB is still a fairly young product I expect the worse. Data loss, unexpected reboots, the database not responding, you name it. Because of this data is _not_ written to InfluxDB directly, instead it's queued and processed by Sidekiq. This ensures that users won't notice anything when InfluxDB is giving trouble. The metrics worker can be started in a standalone manner as following: bundle exec sidekiq -q metrics The corresponding class is called MetricsWorker.
2015-12-09 10:45:51 -05:00
crack (0.4.3)
safe_yaml (~> 1.0.0)
2015-11-24 15:42:42 -05:00
creole (0.5.0)
Storing of application metrics in InfluxDB This adds the ability to write application metrics (e.g. SQL timings) to InfluxDB. These metrics can in turn be visualized using Grafana, or really anything else that can read from InfluxDB. These metrics can be used to track application performance over time, between different Ruby versions, different GitLab versions, etc. == Transaction Metrics Currently the following is tracked on a per transaction basis (a transaction is a Rails request or a single Sidekiq job): * Timings per query along with the raw (obfuscated) SQL and information about what file the query originated from. * Timings per view along with the path of the view and information about what file triggered the rendering process. * The duration of a request itself along with the controller/worker class and method name. * The duration of any instrumented method calls (more below). == Sampled Metrics Certain metrics can't be directly associated with a transaction. For example, a process' total memory usage is unrelated to any running transactions. While a transaction can result in the memory usage going up there's no accurate way to determine what transaction is to blame, this becomes especially problematic in multi-threaded environments. To solve this problem there's a separate thread that takes samples at a fixed interval. This thread (using the class Gitlab::Metrics::Sampler) currently tracks the following: * The process' total memory usage. * The number of file descriptors opened by the process. * The amount of Ruby objects (using ObjectSpace.count_objects). * GC statistics such as timings, heap slots, etc. The default/current interval is 15 seconds, any smaller interval might put too much pressure on InfluxDB (especially when running dozens of processes). == Method Instrumentation While currently not yet used methods can be instrumented to track how long they take to run. Unlike the likes of New Relic this doesn't require modifying the source code (e.g. including modules), it all happens from the outside. For example, to track `User.by_login` we'd add the following code somewhere in an initializer: Gitlab::Metrics::Instrumentation. instrument_method(User, :by_login) to instead instrument an instance method: Gitlab::Metrics::Instrumentation. instrument_instance_method(User, :save) Instrumentation for either all public model methods or a few crucial ones will be added in the near future, I simply haven't gotten to doing so just yet. == Configuration By default metrics are disabled. This means users don't have to bother setting anything up if they don't want to. Metrics can be enabled by editing one's gitlab.yml configuration file (see config/gitlab.yml.example for example settings). == Writing Data To InfluxDB Because InfluxDB is still a fairly young product I expect the worse. Data loss, unexpected reboots, the database not responding, you name it. Because of this data is _not_ written to InfluxDB directly, instead it's queued and processed by Sidekiq. This ensures that users won't notice anything when InfluxDB is giving trouble. The metrics worker can be started in a standalone manner as following: bundle exec sidekiq -q metrics The corresponding class is called MetricsWorker.
2015-12-09 10:45:51 -05:00
d3_rails (3.5.11)
railties (>= 3.1.0)
2015-08-25 21:42:46 -04:00
daemons (1.2.3)
2015-06-17 21:15:23 -04:00
database_cleaner (1.4.1)
debug_inspector (0.0.2)
debugger-ruby_core_source (1.3.8)
2015-08-25 21:42:46 -04:00
default_value_for (3.0.1)
activerecord (>= 3.2.0, < 5.0)
2015-08-25 21:42:46 -04:00
descendants_tracker (0.0.4)
thread_safe (~> 0.3, >= 0.3.1)
2016-01-18 16:39:31 -05:00
devise (3.5.4)
2014-07-09 07:17:45 -04:00
bcrypt (~> 3.0)
2012-07-06 02:50:24 -04:00
orm_adapter (~> 0.1)
railties (>= 3.2.6, < 5)
2015-09-19 21:12:32 -04:00
responders
2014-07-09 07:17:45 -04:00
thread_safe (~> 0.1)
warden (~> 1.2.3)
2014-07-09 07:17:45 -04:00
devise-async (0.9.0)
devise (~> 3.2)
2015-11-25 11:18:44 -05:00
devise-two-factor (2.0.1)
2015-03-27 18:35:26 -04:00
activesupport
attr_encrypted (~> 1.3.2)
2015-09-19 21:12:32 -04:00
devise (~> 3.5.0)
2015-08-25 21:42:46 -04:00
railties
rotp (~> 2)
diff-lcs (1.2.5)
2015-08-25 21:42:46 -04:00
diffy (3.0.7)
2014-09-02 16:13:14 -04:00
docile (1.1.5)
2015-11-25 11:18:44 -05:00
domain_name (0.5.25)
unf (>= 0.0.5, < 1.0.0)
doorkeeper (2.2.2)
2015-03-20 08:47:19 -04:00
railties (>= 3.2)
2015-11-25 11:18:44 -05:00
dropzonejs-rails (0.7.2)
rails (> 3.1)
2015-08-18 20:02:26 -04:00
email_reply_parser (0.5.8)
email_spec (1.6.0)
2012-11-18 15:51:49 -05:00
launchy (~> 2.1)
mail (~> 2.2)
2015-03-27 18:35:26 -04:00
encryptor (1.3.0)
2015-08-25 21:42:46 -04:00
equalizer (0.0.11)
2011-10-08 17:36:38 -04:00
erubis (2.7.0)
escape_utils (1.1.0)
2015-08-25 21:42:46 -04:00
eventmachine (1.0.8)
excon (0.45.4)
execjs (2.6.0)
2014-07-28 05:47:27 -04:00
expression_parser (0.9.0)
factory_girl (4.3.0)
2012-08-28 01:28:09 -04:00
activesupport (>= 3.0.0)
factory_girl_rails (4.3.0)
factory_girl (~> 4.3.0)
2012-08-28 01:28:09 -04:00
railties (>= 3.0.0)
2015-10-07 21:54:15 -04:00
faraday (0.9.2)
multipart-post (>= 1.2, < 3)
2015-08-25 21:42:46 -04:00
faraday_middleware (0.10.0)
faraday (>= 0.7.4, < 0.10)
2015-11-25 17:03:30 -05:00
faraday_middleware-multi_json (0.0.6)
faraday_middleware
multi_json
2015-03-02 20:28:47 -05:00
fastercsv (1.5.5)
ffaker (2.0.0)
2015-08-25 21:42:46 -04:00
ffi (1.9.10)
fission (0.5.0)
CFPropertyList (~> 2.2)
flay (2.6.1)
ruby_parser (~> 3.0)
sexp_processor (~> 4.0)
flog (4.3.2)
ruby_parser (~> 3.1, > 3.1.0)
sexp_processor (~> 4.4)
2015-11-25 11:18:44 -05:00
flowdock (0.7.1)
httparty (~> 0.7)
multi_json
2016-01-11 11:41:11 -05:00
fog (1.36.0)
fog-aliyun (>= 0.1.0)
fog-atmos
fog-aws (>= 0.6.0)
fog-brightbox (~> 0.4)
2016-01-11 11:41:11 -05:00
fog-core (~> 1.32)
fog-dynect (~> 0.0.2)
fog-ecloud (~> 0.1)
fog-google (<= 0.1.0)
fog-json
2016-01-11 11:41:11 -05:00
fog-local
fog-powerdns (>= 0.1.1)
fog-profitbricks
fog-radosgw (>= 0.0.2)
2016-01-11 11:41:11 -05:00
fog-riakcs
fog-sakuracloud (>= 0.0.4)
2016-01-11 11:41:11 -05:00
fog-serverlove
fog-softlayer
2016-01-11 11:41:11 -05:00
fog-storm_on_demand
fog-terremark
fog-vmfusion
fog-voxel
2016-01-11 11:41:11 -05:00
fog-xenserver
fog-xml (~> 0.1.1)
ipaddress (~> 0.5)
nokogiri (~> 1.5, >= 1.5.11)
2016-01-11 11:41:11 -05:00
fog-aliyun (0.1.0)
fog-core (~> 1.27)
fog-json (~> 1.0)
ipaddress (~> 0.8)
xml-simple (~> 1.1)
fog-atmos (0.1.0)
fog-core
fog-xml
fog-aws (0.8.1)
fog-core (~> 1.27)
fog-json (~> 1.0)
fog-xml (~> 0.1)
ipaddress (~> 0.8)
Storing of application metrics in InfluxDB This adds the ability to write application metrics (e.g. SQL timings) to InfluxDB. These metrics can in turn be visualized using Grafana, or really anything else that can read from InfluxDB. These metrics can be used to track application performance over time, between different Ruby versions, different GitLab versions, etc. == Transaction Metrics Currently the following is tracked on a per transaction basis (a transaction is a Rails request or a single Sidekiq job): * Timings per query along with the raw (obfuscated) SQL and information about what file the query originated from. * Timings per view along with the path of the view and information about what file triggered the rendering process. * The duration of a request itself along with the controller/worker class and method name. * The duration of any instrumented method calls (more below). == Sampled Metrics Certain metrics can't be directly associated with a transaction. For example, a process' total memory usage is unrelated to any running transactions. While a transaction can result in the memory usage going up there's no accurate way to determine what transaction is to blame, this becomes especially problematic in multi-threaded environments. To solve this problem there's a separate thread that takes samples at a fixed interval. This thread (using the class Gitlab::Metrics::Sampler) currently tracks the following: * The process' total memory usage. * The number of file descriptors opened by the process. * The amount of Ruby objects (using ObjectSpace.count_objects). * GC statistics such as timings, heap slots, etc. The default/current interval is 15 seconds, any smaller interval might put too much pressure on InfluxDB (especially when running dozens of processes). == Method Instrumentation While currently not yet used methods can be instrumented to track how long they take to run. Unlike the likes of New Relic this doesn't require modifying the source code (e.g. including modules), it all happens from the outside. For example, to track `User.by_login` we'd add the following code somewhere in an initializer: Gitlab::Metrics::Instrumentation. instrument_method(User, :by_login) to instead instrument an instance method: Gitlab::Metrics::Instrumentation. instrument_instance_method(User, :save) Instrumentation for either all public model methods or a few crucial ones will be added in the near future, I simply haven't gotten to doing so just yet. == Configuration By default metrics are disabled. This means users don't have to bother setting anything up if they don't want to. Metrics can be enabled by editing one's gitlab.yml configuration file (see config/gitlab.yml.example for example settings). == Writing Data To InfluxDB Because InfluxDB is still a fairly young product I expect the worse. Data loss, unexpected reboots, the database not responding, you name it. Because of this data is _not_ written to InfluxDB directly, instead it's queued and processed by Sidekiq. This ensures that users won't notice anything when InfluxDB is giving trouble. The metrics worker can be started in a standalone manner as following: bundle exec sidekiq -q metrics The corresponding class is called MetricsWorker.
2015-12-09 10:45:51 -05:00
fog-brightbox (0.10.1)
fog-core (~> 1.22)
fog-json
inflecto (~> 0.0.2)
2015-11-25 11:18:44 -05:00
fog-core (1.35.0)
2013-07-08 02:47:31 -04:00
builder
excon (~> 0.45)
formatador (~> 0.2)
2016-01-11 11:41:11 -05:00
fog-dynect (0.0.2)
fog-core
fog-json
fog-xml
fog-ecloud (0.3.0)
fog-core
fog-xml
fog-google (0.1.0)
fog-core
fog-json
fog-xml
fog-json (1.0.2)
fog-core (~> 1.0)
multi_json (~> 1.10)
2016-01-11 11:41:11 -05:00
fog-local (0.2.1)
fog-core (~> 1.27)
fog-powerdns (0.1.1)
fog-core (~> 1.27)
fog-json (~> 1.0)
fog-xml (~> 0.1)
2015-08-25 21:42:46 -04:00
fog-profitbricks (0.0.5)
fog-core
fog-xml
nokogiri
2016-01-11 11:41:11 -05:00
fog-radosgw (0.0.5)
fog-core (>= 1.21.0)
fog-json
fog-xml (>= 0.0.1)
2016-01-11 11:41:11 -05:00
fog-riakcs (0.1.0)
fog-core
fog-json
fog-xml
fog-sakuracloud (1.7.5)
fog-core
fog-json
fog-serverlove (0.1.2)
fog-core
fog-json
fog-softlayer (1.0.3)
fog-core
fog-json
2016-01-11 11:41:11 -05:00
fog-storm_on_demand (0.1.1)
fog-core
fog-json
fog-terremark (0.1.0)
fog-core
fog-xml
fog-vmfusion (0.1.0)
fission
fog-core
fog-voxel (0.1.0)
fog-core
fog-xml
2016-01-11 11:41:11 -05:00
fog-xenserver (0.2.2)
fog-core
fog-xml
fog-xml (0.1.2)
fog-core
nokogiri (~> 1.5, >= 1.5.11)
2015-11-25 11:18:44 -05:00
font-awesome-rails (4.5.0.0)
railties (>= 3.2, < 5.0)
2015-08-25 21:42:46 -04:00
foreman (0.78.0)
thor (~> 0.19.1)
formatador (0.2.5)
2015-06-25 21:43:24 -04:00
fuubar (2.0.0)
rspec (~> 3.0)
ruby-progressbar (~> 1.4)
gemnasium-gitlab-service (0.2.6)
2015-02-25 10:14:10 -05:00
rugged (~> 0.21)
Storing of application metrics in InfluxDB This adds the ability to write application metrics (e.g. SQL timings) to InfluxDB. These metrics can in turn be visualized using Grafana, or really anything else that can read from InfluxDB. These metrics can be used to track application performance over time, between different Ruby versions, different GitLab versions, etc. == Transaction Metrics Currently the following is tracked on a per transaction basis (a transaction is a Rails request or a single Sidekiq job): * Timings per query along with the raw (obfuscated) SQL and information about what file the query originated from. * Timings per view along with the path of the view and information about what file triggered the rendering process. * The duration of a request itself along with the controller/worker class and method name. * The duration of any instrumented method calls (more below). == Sampled Metrics Certain metrics can't be directly associated with a transaction. For example, a process' total memory usage is unrelated to any running transactions. While a transaction can result in the memory usage going up there's no accurate way to determine what transaction is to blame, this becomes especially problematic in multi-threaded environments. To solve this problem there's a separate thread that takes samples at a fixed interval. This thread (using the class Gitlab::Metrics::Sampler) currently tracks the following: * The process' total memory usage. * The number of file descriptors opened by the process. * The amount of Ruby objects (using ObjectSpace.count_objects). * GC statistics such as timings, heap slots, etc. The default/current interval is 15 seconds, any smaller interval might put too much pressure on InfluxDB (especially when running dozens of processes). == Method Instrumentation While currently not yet used methods can be instrumented to track how long they take to run. Unlike the likes of New Relic this doesn't require modifying the source code (e.g. including modules), it all happens from the outside. For example, to track `User.by_login` we'd add the following code somewhere in an initializer: Gitlab::Metrics::Instrumentation. instrument_method(User, :by_login) to instead instrument an instance method: Gitlab::Metrics::Instrumentation. instrument_instance_method(User, :save) Instrumentation for either all public model methods or a few crucial ones will be added in the near future, I simply haven't gotten to doing so just yet. == Configuration By default metrics are disabled. This means users don't have to bother setting anything up if they don't want to. Metrics can be enabled by editing one's gitlab.yml configuration file (see config/gitlab.yml.example for example settings). == Writing Data To InfluxDB Because InfluxDB is still a fairly young product I expect the worse. Data loss, unexpected reboots, the database not responding, you name it. Because of this data is _not_ written to InfluxDB directly, instead it's queued and processed by Sidekiq. This ensures that users won't notice anything when InfluxDB is giving trouble. The metrics worker can be started in a standalone manner as following: bundle exec sidekiq -q metrics The corresponding class is called MetricsWorker.
2015-12-09 10:45:51 -05:00
gemojione (2.1.1)
2015-03-11 19:05:01 -04:00
json
2015-08-25 21:42:46 -04:00
get_process_mem (0.2.0)
gherkin-ruby (0.3.2)
Storing of application metrics in InfluxDB This adds the ability to write application metrics (e.g. SQL timings) to InfluxDB. These metrics can in turn be visualized using Grafana, or really anything else that can read from InfluxDB. These metrics can be used to track application performance over time, between different Ruby versions, different GitLab versions, etc. == Transaction Metrics Currently the following is tracked on a per transaction basis (a transaction is a Rails request or a single Sidekiq job): * Timings per query along with the raw (obfuscated) SQL and information about what file the query originated from. * Timings per view along with the path of the view and information about what file triggered the rendering process. * The duration of a request itself along with the controller/worker class and method name. * The duration of any instrumented method calls (more below). == Sampled Metrics Certain metrics can't be directly associated with a transaction. For example, a process' total memory usage is unrelated to any running transactions. While a transaction can result in the memory usage going up there's no accurate way to determine what transaction is to blame, this becomes especially problematic in multi-threaded environments. To solve this problem there's a separate thread that takes samples at a fixed interval. This thread (using the class Gitlab::Metrics::Sampler) currently tracks the following: * The process' total memory usage. * The number of file descriptors opened by the process. * The amount of Ruby objects (using ObjectSpace.count_objects). * GC statistics such as timings, heap slots, etc. The default/current interval is 15 seconds, any smaller interval might put too much pressure on InfluxDB (especially when running dozens of processes). == Method Instrumentation While currently not yet used methods can be instrumented to track how long they take to run. Unlike the likes of New Relic this doesn't require modifying the source code (e.g. including modules), it all happens from the outside. For example, to track `User.by_login` we'd add the following code somewhere in an initializer: Gitlab::Metrics::Instrumentation. instrument_method(User, :by_login) to instead instrument an instance method: Gitlab::Metrics::Instrumentation. instrument_instance_method(User, :save) Instrumentation for either all public model methods or a few crucial ones will be added in the near future, I simply haven't gotten to doing so just yet. == Configuration By default metrics are disabled. This means users don't have to bother setting anything up if they don't want to. Metrics can be enabled by editing one's gitlab.yml configuration file (see config/gitlab.yml.example for example settings). == Writing Data To InfluxDB Because InfluxDB is still a fairly young product I expect the worse. Data loss, unexpected reboots, the database not responding, you name it. Because of this data is _not_ written to InfluxDB directly, instead it's queued and processed by Sidekiq. This ensures that users won't notice anything when InfluxDB is giving trouble. The metrics worker can be started in a standalone manner as following: bundle exec sidekiq -q metrics The corresponding class is called MetricsWorker.
2015-12-09 10:45:51 -05:00
github-linguist (4.7.3)
charlock_holmes (~> 0.7.3)
escape_utils (~> 1.1.0)
mime-types (>= 1.19)
rugged (>= 0.23.0b)
2015-08-25 21:42:46 -04:00
github-markup (1.3.3)
gitlab-flowdock-git-hook (1.0.1)
flowdock (~> 0.7)
gitlab-grit (>= 2.4.1)
multi_json
2015-08-25 21:42:46 -04:00
gitlab-grit (2.7.3)
charlock_holmes (~> 0.6)
diff-lcs (~> 1.1)
mime-types (~> 1.15)
posix-spawn (~> 0.3)
2015-11-25 11:18:44 -05:00
gitlab_emoji (0.2.0)
gemojione (~> 2.1)
gitlab_git (7.2.23)
2015-08-11 08:11:58 -04:00
activesupport (~> 4.0)
charlock_holmes (~> 0.7.3)
github-linguist (~> 4.7.0)
rugged (~> 0.23.3)
gitlab_meta (7.0)
2015-03-17 12:15:39 -04:00
gitlab_omniauth-ldap (1.2.1)
net-ldap (~> 0.9)
omniauth (~> 1.0)
pyu-ruby-sasl (~> 0.0.3.1)
rubyntlm (~> 0.3)
2015-11-25 11:18:44 -05:00
globalid (0.3.6)
activesupport (>= 4.1.0)
2015-08-25 21:42:46 -04:00
gollum-grit_adapter (1.0.0)
2015-03-20 09:15:56 -04:00
gitlab-grit (~> 2.7, >= 2.7.1)
gollum-lib (4.1.0)
2015-08-25 21:42:46 -04:00
github-markup (~> 1.3.3)
gollum-grit_adapter (~> 1.0)
nokogiri (~> 1.6.4)
rouge (~> 1.9)
sanitize (~> 2.1.0)
stringex (~> 2.5.1)
2015-11-24 15:36:36 -05:00
gon (6.0.1)
actionpack (>= 3.0)
json
2015-11-24 15:36:36 -05:00
multi_json
request_store (>= 1.0)
grape (0.13.0)
2012-11-18 15:51:49 -05:00
activesupport
builder
hashie (>= 2.1.0)
2012-11-18 15:51:49 -05:00
multi_json (>= 1.3.2)
multi_xml (>= 0.5.2)
2013-05-01 06:29:29 -04:00
rack (>= 1.3.0)
2012-11-18 15:51:49 -05:00
rack-accept
2012-06-27 05:26:16 -04:00
rack-mount
2013-12-09 14:50:36 -05:00
virtus (>= 1.0.0)
2015-08-25 21:42:46 -04:00
grape-entity (0.4.8)
activesupport
multi_json (>= 1.3.2)
haml (4.0.7)
2013-03-01 08:09:11 -05:00
tilt
2015-10-07 21:59:16 -04:00
haml-rails (0.9.0)
2014-05-29 08:13:01 -04:00
actionpack (>= 4.0.1)
activesupport (>= 4.0.1)
2015-10-07 21:59:16 -04:00
haml (>= 4.0.6, < 5.0)
html2haml (>= 1.0.1)
2014-05-29 08:13:01 -04:00
railties (>= 4.0.1)
2015-11-25 11:18:44 -05:00
hashie (3.4.3)
2015-12-27 21:19:01 -05:00
highline (1.7.8)
2013-06-24 15:03:32 -04:00
hike (1.2.3)
2015-08-25 21:42:46 -04:00
hipchat (1.5.2)
2013-06-24 15:03:32 -04:00
httparty
2015-03-30 18:53:24 -04:00
mimemagic
html-pipeline (1.11.0)
activesupport (>= 2)
nokogiri (~> 1.4)
2015-10-07 21:59:16 -04:00
html2haml (2.0.0)
erubis (~> 2.7.0)
haml (~> 4.0.0)
nokogiri (~> 1.6.0)
ruby_parser (~> 3.5)
http-cookie (1.0.2)
domain_name (~> 0.5)
http_parser.rb (0.5.3)
2015-11-25 11:18:44 -05:00
httparty (0.13.7)
json (~> 1.8)
2013-02-28 14:11:12 -05:00
multi_xml (>= 0.5.2)
2015-11-24 15:48:49 -05:00
httpclient (2.7.0.1)
i18n (0.7.0)
2015-08-25 21:42:46 -04:00
ice_nine (0.11.1)
inflecto (0.0.2)
Storing of application metrics in InfluxDB This adds the ability to write application metrics (e.g. SQL timings) to InfluxDB. These metrics can in turn be visualized using Grafana, or really anything else that can read from InfluxDB. These metrics can be used to track application performance over time, between different Ruby versions, different GitLab versions, etc. == Transaction Metrics Currently the following is tracked on a per transaction basis (a transaction is a Rails request or a single Sidekiq job): * Timings per query along with the raw (obfuscated) SQL and information about what file the query originated from. * Timings per view along with the path of the view and information about what file triggered the rendering process. * The duration of a request itself along with the controller/worker class and method name. * The duration of any instrumented method calls (more below). == Sampled Metrics Certain metrics can't be directly associated with a transaction. For example, a process' total memory usage is unrelated to any running transactions. While a transaction can result in the memory usage going up there's no accurate way to determine what transaction is to blame, this becomes especially problematic in multi-threaded environments. To solve this problem there's a separate thread that takes samples at a fixed interval. This thread (using the class Gitlab::Metrics::Sampler) currently tracks the following: * The process' total memory usage. * The number of file descriptors opened by the process. * The amount of Ruby objects (using ObjectSpace.count_objects). * GC statistics such as timings, heap slots, etc. The default/current interval is 15 seconds, any smaller interval might put too much pressure on InfluxDB (especially when running dozens of processes). == Method Instrumentation While currently not yet used methods can be instrumented to track how long they take to run. Unlike the likes of New Relic this doesn't require modifying the source code (e.g. including modules), it all happens from the outside. For example, to track `User.by_login` we'd add the following code somewhere in an initializer: Gitlab::Metrics::Instrumentation. instrument_method(User, :by_login) to instead instrument an instance method: Gitlab::Metrics::Instrumentation. instrument_instance_method(User, :save) Instrumentation for either all public model methods or a few crucial ones will be added in the near future, I simply haven't gotten to doing so just yet. == Configuration By default metrics are disabled. This means users don't have to bother setting anything up if they don't want to. Metrics can be enabled by editing one's gitlab.yml configuration file (see config/gitlab.yml.example for example settings). == Writing Data To InfluxDB Because InfluxDB is still a fairly young product I expect the worse. Data loss, unexpected reboots, the database not responding, you name it. Because of this data is _not_ written to InfluxDB directly, instead it's queued and processed by Sidekiq. This ensures that users won't notice anything when InfluxDB is giving trouble. The metrics worker can be started in a standalone manner as following: bundle exec sidekiq -q metrics The corresponding class is called MetricsWorker.
2015-12-09 10:45:51 -05:00
influxdb (0.2.3)
cause
json
2016-01-11 11:41:11 -05:00
ipaddress (0.8.2)
jquery-atwho-rails (1.3.2)
jquery-rails (4.0.5)
rails-dom-testing (~> 1.0)
railties (>= 4.2.0)
thor (>= 0.14, < 2.0)
jquery-scrollto-rails (1.4.3)
railties (> 3.1, < 5.0)
jquery-turbolinks (2.1.0)
2013-04-29 03:10:45 -04:00
railties (>= 3.1.0)
turbolinks
jquery-ui-rails (5.0.5)
railties (>= 3.2.16)
json (1.8.3)
2015-11-25 11:18:44 -05:00
jwt (1.5.2)
kaminari (0.16.3)
2012-02-11 13:34:25 -05:00
actionpack (>= 3.0.0)
activesupport (>= 3.0.0)
2015-11-25 11:18:44 -05:00
kgio (2.10.0)
launchy (2.4.3)
2012-11-18 15:51:49 -05:00
addressable (~> 2.3)
letter_opener (1.1.2)
2013-06-24 15:03:32 -04:00
launchy (~> 2.2)
listen (3.0.5)
2013-05-01 06:29:29 -04:00
rb-fsevent (>= 0.9.3)
rb-inotify (>= 0.9)
2015-11-25 11:18:44 -05:00
loofah (2.0.3)
nokogiri (>= 1.5.9)
2015-05-27 10:37:22 -04:00
macaddr (1.7.1)
systemu (~> 2.6.2)
mail (2.6.3)
mime-types (>= 1.16, < 3)
mail_room (0.6.1)
method_source (0.8.2)
mime-types (1.25.1)
2015-03-30 18:53:24 -04:00
mimemagic (0.3.0)
2015-12-16 14:55:48 -05:00
mini_portile2 (2.0.0)
2015-08-25 21:42:46 -04:00
minitest (5.7.0)
2014-08-21 04:14:31 -04:00
mousetrap-rails (1.4.6)
2015-08-10 03:18:02 -04:00
multi_json (1.11.2)
multi_xml (0.5.5)
2015-10-07 21:54:15 -04:00
multipart-post (2.0.0)
2015-08-25 21:42:46 -04:00
mysql2 (0.3.20)
nested_form (0.3.2)
2015-11-25 11:18:44 -05:00
net-ldap (0.12.1)
net-ssh (3.0.1)
netrc (0.11.0)
Storing of application metrics in InfluxDB This adds the ability to write application metrics (e.g. SQL timings) to InfluxDB. These metrics can in turn be visualized using Grafana, or really anything else that can read from InfluxDB. These metrics can be used to track application performance over time, between different Ruby versions, different GitLab versions, etc. == Transaction Metrics Currently the following is tracked on a per transaction basis (a transaction is a Rails request or a single Sidekiq job): * Timings per query along with the raw (obfuscated) SQL and information about what file the query originated from. * Timings per view along with the path of the view and information about what file triggered the rendering process. * The duration of a request itself along with the controller/worker class and method name. * The duration of any instrumented method calls (more below). == Sampled Metrics Certain metrics can't be directly associated with a transaction. For example, a process' total memory usage is unrelated to any running transactions. While a transaction can result in the memory usage going up there's no accurate way to determine what transaction is to blame, this becomes especially problematic in multi-threaded environments. To solve this problem there's a separate thread that takes samples at a fixed interval. This thread (using the class Gitlab::Metrics::Sampler) currently tracks the following: * The process' total memory usage. * The number of file descriptors opened by the process. * The amount of Ruby objects (using ObjectSpace.count_objects). * GC statistics such as timings, heap slots, etc. The default/current interval is 15 seconds, any smaller interval might put too much pressure on InfluxDB (especially when running dozens of processes). == Method Instrumentation While currently not yet used methods can be instrumented to track how long they take to run. Unlike the likes of New Relic this doesn't require modifying the source code (e.g. including modules), it all happens from the outside. For example, to track `User.by_login` we'd add the following code somewhere in an initializer: Gitlab::Metrics::Instrumentation. instrument_method(User, :by_login) to instead instrument an instance method: Gitlab::Metrics::Instrumentation. instrument_instance_method(User, :save) Instrumentation for either all public model methods or a few crucial ones will be added in the near future, I simply haven't gotten to doing so just yet. == Configuration By default metrics are disabled. This means users don't have to bother setting anything up if they don't want to. Metrics can be enabled by editing one's gitlab.yml configuration file (see config/gitlab.yml.example for example settings). == Writing Data To InfluxDB Because InfluxDB is still a fairly young product I expect the worse. Data loss, unexpected reboots, the database not responding, you name it. Because of this data is _not_ written to InfluxDB directly, instead it's queued and processed by Sidekiq. This ensures that users won't notice anything when InfluxDB is giving trouble. The metrics worker can be started in a standalone manner as following: bundle exec sidekiq -q metrics The corresponding class is called MetricsWorker.
2015-12-09 10:45:51 -05:00
newrelic-grape (2.1.0)
grape
newrelic_rpm
newrelic_rpm (3.9.4.245)
nokogiri (1.6.7.1)
2015-12-16 14:55:48 -05:00
mini_portile2 (~> 2.0.0.rc2)
nprogress-rails (0.1.6.7)
2012-09-12 00:48:22 -04:00
oauth (0.4.7)
2015-08-25 21:42:46 -04:00
oauth2 (1.0.0)
faraday (>= 0.8, < 0.10)
jwt (~> 1.0)
multi_json (~> 1.3)
multi_xml (~> 0.5)
2012-09-12 00:48:22 -04:00
rack (~> 1.2)
2015-08-25 21:42:46 -04:00
octokit (3.7.1)
2014-12-31 08:07:48 -05:00
sawyer (~> 0.6.0, >= 0.5.3)
omniauth (1.2.2)
hashie (>= 1.2, < 4)
rack (~> 1.0)
2016-01-07 12:27:01 -05:00
omniauth-azure-oauth2 (0.0.6)
jwt (~> 1.0)
omniauth (~> 1.0)
omniauth-oauth2 (~> 1.1)
2015-02-17 10:59:50 -05:00
omniauth-bitbucket (0.0.2)
multi_json (~> 1.7)
omniauth (~> 1.1)
omniauth-oauth (~> 1.0)
2015-11-11 23:25:31 -05:00
omniauth-cas3 (1.1.3)
addressable (~> 2.3)
nokogiri (~> 1.6.6)
omniauth (~> 1.2)
2015-11-03 11:58:12 -05:00
omniauth-facebook (3.0.0)
omniauth-oauth2 (~> 1.2)
2015-08-25 21:42:46 -04:00
omniauth-github (1.1.2)
2012-09-12 00:48:22 -04:00
omniauth (~> 1.0)
omniauth-oauth2 (~> 1.1)
2015-11-25 11:18:44 -05:00
omniauth-gitlab (1.0.1)
2015-01-27 18:37:19 -05:00
omniauth (~> 1.0)
omniauth-oauth2 (~> 1.0)
2015-11-25 11:18:44 -05:00
omniauth-google-oauth2 (0.2.10)
addressable (~> 2.3)
jwt (~> 1.0)
multi_json (~> 1.3)
omniauth (>= 1.1.1)
omniauth-oauth2 (~> 1.3.1)
2015-10-06 21:48:19 -04:00
omniauth-kerberos (0.3.0)
2014-12-16 06:57:40 -05:00
omniauth-multipassword
timfel-krb5-auth (~> 0.8)
2015-08-25 21:42:46 -04:00
omniauth-multipassword (0.4.2)
2014-12-16 06:57:40 -05:00
omniauth (~> 1.0)
2015-08-25 21:42:46 -04:00
omniauth-oauth (1.1.0)
2012-09-12 00:48:22 -04:00
oauth
omniauth (~> 1.0)
2015-08-25 21:42:46 -04:00
omniauth-oauth2 (1.3.1)
oauth2 (~> 1.0)
omniauth (~> 1.2)
omniauth-saml (1.4.1)
2015-05-27 10:37:22 -04:00
omniauth (~> 1.1)
ruby-saml (~> 1.0.0)
2015-10-06 22:03:42 -04:00
omniauth-shibboleth (1.2.1)
omniauth (>= 1.0.0)
2015-10-06 21:42:32 -04:00
omniauth-twitter (1.2.1)
json (~> 1.3)
omniauth-oauth (~> 1.1)
2015-08-31 06:59:52 -04:00
omniauth_crowd (2.2.3)
activesupport
nokogiri (>= 1.4.4)
omniauth (~> 1.0)
2014-12-29 01:22:56 -05:00
org-ruby (0.9.12)
2014-08-13 09:45:48 -04:00
rubypants (~> 0.2)
orm_adapter (0.5.0)
2015-11-25 11:18:44 -05:00
paranoia (2.1.4)
2015-08-25 21:42:46 -04:00
activerecord (~> 4.0)
2015-11-25 11:18:44 -05:00
parser (2.2.3.0)
ast (>= 1.1, < 3.0)
2015-11-25 11:18:44 -05:00
pg (0.18.4)
2015-12-16 14:55:48 -05:00
poltergeist (1.8.1)
capybara (~> 2.1)
cliver (~> 0.3.1)
multi_json (~> 1.0)
websocket-driver (>= 0.2.0)
2015-08-25 21:42:46 -04:00
posix-spawn (0.3.11)
2015-12-14 14:18:32 -05:00
powerpack (0.1.1)
2015-11-25 11:18:44 -05:00
pry (0.10.3)
2015-08-25 21:42:46 -04:00
coderay (~> 1.1.0)
method_source (~> 0.8.1)
2013-03-27 16:21:32 -04:00
slop (~> 3.4)
2015-08-25 21:42:46 -04:00
pry-rails (0.3.4)
pry (>= 0.9.10)
2012-01-21 13:36:14 -05:00
pyu-ruby-sasl (0.0.3.3)
2015-08-25 21:42:46 -04:00
quiet_assets (1.0.3)
2013-05-01 06:29:29 -04:00
railties (>= 3.1, < 5.0)
2015-11-25 11:18:44 -05:00
rack (1.6.4)
2012-11-18 15:51:49 -05:00
rack-accept (0.4.5)
rack (>= 0.4)
rack-attack (4.3.1)
2013-09-24 14:13:25 -04:00
rack
2015-10-07 22:08:30 -04:00
rack-cors (0.4.0)
2012-06-27 05:26:16 -04:00
rack-mount (0.8.3)
rack (>= 1.0.0)
2015-11-24 15:48:49 -05:00
rack-oauth2 (1.2.1)
2014-12-19 09:15:29 -05:00
activesupport (>= 2.3)
attr_required (>= 0.0.5)
2015-08-25 21:42:46 -04:00
httpclient (>= 2.4)
2014-12-19 09:15:29 -05:00
multi_json (>= 1.3.6)
rack (>= 1.1)
2015-08-25 21:42:46 -04:00
rack-protection (1.5.3)
2011-10-08 17:36:38 -04:00
rack
rack-test (0.6.3)
2011-10-08 17:36:38 -04:00
rack (>= 1.0)
2015-11-25 11:18:44 -05:00
rails (4.2.4)
actionmailer (= 4.2.4)
actionpack (= 4.2.4)
actionview (= 4.2.4)
activejob (= 4.2.4)
activemodel (= 4.2.4)
activerecord (= 4.2.4)
activesupport (= 4.2.4)
bundler (>= 1.3.0, < 2.0)
2015-11-25 11:18:44 -05:00
railties (= 4.2.4)
sprockets-rails
rails-deprecated_sanitizer (1.0.3)
activesupport (>= 4.2.0.alpha)
rails-dom-testing (1.0.7)
activesupport (>= 4.2.0.beta, < 5.0)
nokogiri (~> 1.6.0)
rails-deprecated_sanitizer (>= 1.0.1)
rails-html-sanitizer (1.0.2)
loofah (~> 2.0)
railties (4.2.4)
actionpack (= 4.2.4)
activesupport (= 4.2.4)
2011-10-08 17:36:38 -04:00
rake (>= 0.8.7)
thor (>= 0.18.1, < 2.0)
rainbow (2.0.0)
2015-08-25 21:42:46 -04:00
raindrops (0.15.0)
2016-01-18 16:39:31 -05:00
rake (10.5.0)
2013-08-31 18:04:22 -04:00
raphael-rails (2.1.2)
2015-11-25 11:18:44 -05:00
rb-fsevent (0.9.6)
rb-inotify (0.9.5)
ffi (>= 0.5.0)
rblineprof (0.3.6)
debugger-ruby_core_source (~> 1.3)
2013-02-28 14:06:16 -05:00
rdoc (3.12.2)
json (~> 1.4)
recaptcha (1.0.2)
json
redcarpet (3.3.3)
2015-11-25 11:18:44 -05:00
redis (3.2.2)
redis-actionpack (4.0.1)
actionpack (~> 4)
redis-rack (~> 1.5.0)
redis-store (~> 1.1.0)
2015-11-25 11:18:44 -05:00
redis-activesupport (4.1.5)
activesupport (>= 3, < 5)
redis-store (~> 1.1.0)
2015-08-25 21:42:46 -04:00
redis-namespace (1.5.2)
2014-11-28 13:06:21 -05:00
redis (~> 3.0, >= 3.0.4)
redis-rack (1.5.0)
rack (~> 1.5)
redis-store (~> 1.1.0)
redis-rails (4.0.0)
redis-actionpack (~> 4)
redis-activesupport (~> 4)
redis-store (~> 1.1.0)
2015-11-25 11:18:44 -05:00
redis-store (1.1.7)
2013-08-29 13:32:40 -04:00
redis (>= 2.2)
2015-11-25 11:18:44 -05:00
request_store (1.2.1)
rerun (0.11.0)
listen (~> 3.0)
2016-01-18 16:39:31 -05:00
responders (2.1.1)
railties (>= 4.2.0, < 5.1)
rest-client (1.8.0)
http-cookie (>= 1.0.2, < 2.0)
mime-types (>= 1.16, < 3.0)
netrc (~> 0.7)
2015-09-09 04:06:35 -04:00
rinku (1.7.3)
rotp (2.1.1)
2015-09-10 16:38:43 -04:00
rouge (1.10.1)
2015-08-25 21:42:46 -04:00
rqrcode (0.7.0)
chunky_png
2015-03-27 18:35:26 -04:00
rqrcode-rails3 (0.1.7)
rqrcode (>= 0.4.2)
2015-06-25 21:43:24 -04:00
rspec (3.3.0)
rspec-core (~> 3.3.0)
rspec-expectations (~> 3.3.0)
rspec-mocks (~> 3.3.0)
2015-08-25 21:42:46 -04:00
rspec-core (3.3.2)
2015-06-17 18:05:48 -04:00
rspec-support (~> 3.3.0)
2015-08-25 21:42:46 -04:00
rspec-expectations (3.3.1)
diff-lcs (>= 1.2.0, < 2.0)
2015-06-17 18:05:48 -04:00
rspec-support (~> 3.3.0)
2015-08-25 21:42:46 -04:00
rspec-mocks (3.3.2)
2015-06-17 18:05:48 -04:00
diff-lcs (>= 1.2.0, < 2.0)
rspec-support (~> 3.3.0)
2015-08-25 21:42:46 -04:00
rspec-rails (3.3.3)
2015-06-17 18:05:48 -04:00
actionpack (>= 3.0, < 4.3)
activesupport (>= 3.0, < 4.3)
railties (>= 3.0, < 4.3)
rspec-core (~> 3.3.0)
rspec-expectations (~> 3.3.0)
rspec-mocks (~> 3.3.0)
rspec-support (~> 3.3.0)
rspec-support (3.3.0)
2015-12-14 14:18:32 -05:00
rubocop (0.35.1)
astrolabe (~> 1.3)
2015-12-14 14:18:32 -05:00
parser (>= 2.2.3.0, < 3.0)
powerpack (~> 0.1)
rainbow (>= 1.99.1, < 3.0)
2015-12-14 14:18:32 -05:00
ruby-progressbar (~> 1.7)
tins (<= 1.6.0)
2015-09-15 16:09:32 -04:00
ruby-fogbugz (0.2.1)
crack (~> 0.4)
2015-08-25 21:42:46 -04:00
ruby-progressbar (1.7.5)
ruby-saml (1.0.0)
nokogiri (>= 1.5.10)
2015-05-27 10:37:22 -04:00
uuid (~> 2.3)
2015-12-27 21:19:01 -05:00
ruby2ruby (2.2.0)
2015-03-02 20:28:47 -05:00
ruby_parser (~> 3.1)
sexp_processor (~> 4.0)
2015-12-27 21:19:01 -05:00
ruby_parser (3.7.2)
2015-03-02 20:28:47 -05:00
sexp_processor (~> 4.1)
2015-08-25 21:42:46 -04:00
rubyntlm (0.5.2)
2014-05-28 06:23:03 -04:00
rubypants (0.2.0)
rufus-scheduler (3.1.10)
rugged (0.23.3)
safe_yaml (1.0.4)
sanitize (2.1.0)
nokogiri (>= 1.4.4)
2015-12-22 17:04:41 -05:00
sass (3.4.20)
sass-rails (5.0.4)
railties (>= 4.0.0, < 5.0)
2015-12-22 17:04:41 -05:00
sass (~> 3.1)
sprockets (>= 2.8, < 4.0)
sprockets-rails (>= 2.0, < 4.0)
tilt (>= 1.1, < 3)
2014-12-31 08:07:48 -05:00
sawyer (0.6.0)
addressable (~> 2.3.5)
faraday (~> 0.8, < 0.10)
sdoc (0.3.20)
json (>= 1.1.3)
rdoc (~> 3.10)
seed-fu (2.3.5)
activerecord (>= 3.1, < 4.3)
activesupport (>= 3.1, < 4.3)
2015-06-24 17:13:21 -04:00
select2-rails (3.5.9.3)
2013-03-13 15:36:26 -04:00
thor (~> 0.14)
2016-01-18 11:15:10 -05:00
sentry-raven (0.15.3)
faraday (>= 0.7.6)
settingslogic (2.0.9)
2015-08-25 21:42:46 -04:00
sexp_processor (4.6.0)
2015-08-04 18:21:12 -04:00
sham_rack (1.3.6)
rack
shoulda-matchers (2.8.0)
2012-06-08 06:28:19 -04:00
activesupport (>= 3.0.0)
2015-12-10 12:45:36 -05:00
sidekiq (4.0.1)
concurrent-ruby (~> 1.0)
connection_pool (~> 2.2, >= 2.2.0)
json (~> 1.0)
redis (~> 3.2, >= 3.2.1)
2015-12-10 12:45:36 -05:00
sidekiq-cron (0.4.0)
redis-namespace (>= 1.5.2)
rufus-scheduler (>= 2.0.24)
2015-12-10 12:45:36 -05:00
sidekiq (>= 4.0.0)
simple_oauth (0.1.9)
simplecov (0.10.0)
docile (~> 1.1.0)
json (~> 1.8)
simplecov-html (~> 0.10.0)
simplecov-html (0.10.0)
2015-08-25 21:42:46 -04:00
sinatra (1.4.6)
rack (~> 1.4)
2013-06-24 15:03:32 -04:00
rack-protection (~> 1.4)
2015-08-25 21:42:46 -04:00
tilt (>= 1.3, < 3)
2011-10-08 17:36:38 -04:00
six (0.2.0)
2015-10-07 21:51:05 -04:00
slack-notifier (1.2.1)
2015-12-27 21:19:01 -05:00
slim (3.0.6)
temple (~> 0.7.3)
tilt (>= 1.3.3, < 2.1)
slop (3.6.0)
2015-08-25 21:42:46 -04:00
spinach (0.8.10)
colorize
gherkin-ruby (>= 0.3.2)
json
2013-05-01 06:29:29 -04:00
spinach-rails (0.2.1)
capybara (>= 2.0.0)
2012-09-10 03:42:36 -04:00
railties (>= 3)
spinach (>= 0.4)
2015-05-20 18:39:33 -04:00
spring (1.3.6)
spring-commands-rspec (1.0.4)
2014-02-15 14:46:15 -05:00
spring (>= 0.9.1)
spring-commands-spinach (1.0.0)
spring (>= 0.9.1)
2015-05-06 16:50:47 -04:00
spring-commands-teaspoon (0.0.2)
spring (>= 0.9.1)
sprockets (2.12.4)
2011-10-08 17:36:38 -04:00
hike (~> 1.2)
2012-11-14 06:14:46 -05:00
multi_json (~> 1.0)
2011-10-08 17:36:38 -04:00
rack (~> 1.0)
tilt (~> 1.1, != 1.3.0)
2015-11-19 04:47:12 -05:00
sprockets-rails (2.3.3)
actionpack (>= 3.0)
activesupport (>= 3.0)
sprockets (>= 2.8, < 4.0)
2015-11-09 09:11:42 -05:00
state_machines (0.4.0)
state_machines-activemodel (0.3.0)
activemodel (~> 4.1)
state_machines (>= 0.4.0)
state_machines-activerecord (0.3.0)
activerecord (~> 4.1)
state_machines-activemodel (>= 0.3.0)
stringex (2.5.2)
2015-05-27 10:37:22 -04:00
systemu (2.6.5)
2015-04-29 15:02:41 -04:00
task_list (1.0.2)
html-pipeline
2015-05-06 16:50:47 -04:00
teaspoon (1.0.2)
railties (>= 3.2.5, < 5)
teaspoon-jasmine (2.2.0)
teaspoon (>= 1.0.0)
2015-12-27 21:19:01 -05:00
temple (0.7.6)
term-ansicolor (1.3.2)
tins (~> 1.0)
2015-08-25 21:42:46 -04:00
terminal-table (1.5.2)
2015-11-26 04:57:04 -05:00
test_after_commit (0.4.2)
2015-08-25 21:42:46 -04:00
activerecord (>= 3.2)
2015-11-25 11:18:44 -05:00
thin (1.6.4)
2015-08-25 21:42:46 -04:00
daemons (~> 1.0, >= 1.0.9)
2015-11-25 11:18:44 -05:00
eventmachine (~> 1.0, >= 1.0.4)
2015-08-25 21:42:46 -04:00
rack (~> 1.0)
thor (0.19.1)
thread_safe (0.3.5)
2013-06-24 15:03:32 -04:00
tilt (1.4.1)
timfel-krb5-auth (0.8.3)
2015-10-07 21:54:15 -04:00
tinder (1.10.1)
eventmachine (~> 1.0)
2015-10-07 21:54:15 -04:00
faraday (~> 0.9.0)
faraday_middleware (~> 0.9)
2015-10-07 21:54:15 -04:00
hashie (>= 1.0)
json (~> 1.8.0)
2015-10-07 21:54:15 -04:00
mime-types
multi_json (~> 1.7)
twitter-stream (~> 0.1)
2015-08-25 21:42:46 -04:00
tins (1.6.0)
2015-05-29 00:05:14 -04:00
turbolinks (2.5.3)
2013-04-29 03:10:45 -04:00
coffee-rails
twitter-stream (0.1.16)
eventmachine (>= 0.12.8)
http_parser.rb (~> 0.5.1)
simple_oauth (~> 0.1.4)
tzinfo (1.2.2)
2014-05-29 08:13:01 -04:00
thread_safe (~> 0.1)
2015-10-14 02:39:59 -04:00
uglifier (2.7.2)
2011-10-08 17:36:38 -04:00
execjs (>= 0.3.0)
json (>= 1.8.0)
underscore-rails (1.8.3)
unf (0.1.4)
unf_ext
unf_ext (0.0.7.1)
2015-08-25 21:42:46 -04:00
unicorn (4.8.3)
2013-07-08 02:47:31 -04:00
kgio (~> 2.6)
rack
raindrops (~> 0.7)
2015-11-25 11:18:44 -05:00
unicorn-worker-killer (0.4.4)
2015-08-25 21:42:46 -04:00
get_process_mem (~> 0)
2015-11-25 11:18:44 -05:00
unicorn (>= 4, < 6)
uniform_notifier (1.9.0)
uuid (2.3.8)
2015-05-27 10:37:22 -04:00
macaddr (~> 1.0)
version_sorter (2.0.0)
2015-08-25 21:42:46 -04:00
virtus (1.0.5)
axiom-types (~> 0.1)
coercible (~> 1.0)
2015-08-25 21:42:46 -04:00
descendants_tracker (~> 0.0, >= 0.0.3)
equalizer (~> 0.0, >= 0.0.9)
Storing of application metrics in InfluxDB This adds the ability to write application metrics (e.g. SQL timings) to InfluxDB. These metrics can in turn be visualized using Grafana, or really anything else that can read from InfluxDB. These metrics can be used to track application performance over time, between different Ruby versions, different GitLab versions, etc. == Transaction Metrics Currently the following is tracked on a per transaction basis (a transaction is a Rails request or a single Sidekiq job): * Timings per query along with the raw (obfuscated) SQL and information about what file the query originated from. * Timings per view along with the path of the view and information about what file triggered the rendering process. * The duration of a request itself along with the controller/worker class and method name. * The duration of any instrumented method calls (more below). == Sampled Metrics Certain metrics can't be directly associated with a transaction. For example, a process' total memory usage is unrelated to any running transactions. While a transaction can result in the memory usage going up there's no accurate way to determine what transaction is to blame, this becomes especially problematic in multi-threaded environments. To solve this problem there's a separate thread that takes samples at a fixed interval. This thread (using the class Gitlab::Metrics::Sampler) currently tracks the following: * The process' total memory usage. * The number of file descriptors opened by the process. * The amount of Ruby objects (using ObjectSpace.count_objects). * GC statistics such as timings, heap slots, etc. The default/current interval is 15 seconds, any smaller interval might put too much pressure on InfluxDB (especially when running dozens of processes). == Method Instrumentation While currently not yet used methods can be instrumented to track how long they take to run. Unlike the likes of New Relic this doesn't require modifying the source code (e.g. including modules), it all happens from the outside. For example, to track `User.by_login` we'd add the following code somewhere in an initializer: Gitlab::Metrics::Instrumentation. instrument_method(User, :by_login) to instead instrument an instance method: Gitlab::Metrics::Instrumentation. instrument_instance_method(User, :save) Instrumentation for either all public model methods or a few crucial ones will be added in the near future, I simply haven't gotten to doing so just yet. == Configuration By default metrics are disabled. This means users don't have to bother setting anything up if they don't want to. Metrics can be enabled by editing one's gitlab.yml configuration file (see config/gitlab.yml.example for example settings). == Writing Data To InfluxDB Because InfluxDB is still a fairly young product I expect the worse. Data loss, unexpected reboots, the database not responding, you name it. Because of this data is _not_ written to InfluxDB directly, instead it's queued and processed by Sidekiq. This ensures that users won't notice anything when InfluxDB is giving trouble. The metrics worker can be started in a standalone manner as following: bundle exec sidekiq -q metrics The corresponding class is called MetricsWorker.
2015-12-09 10:45:51 -05:00
warden (1.2.4)
2011-10-08 17:36:38 -04:00
rack (>= 1.0)
2015-11-25 11:18:44 -05:00
web-console (2.2.1)
activemodel (>= 4.0)
binding_of_caller (>= 0.7.2)
railties (>= 4.0)
sprockets-rails (>= 2.0, < 4.0)
webmock (1.21.0)
addressable (>= 2.3.6)
2013-05-01 06:29:29 -04:00
crack (>= 0.3.2)
2015-11-25 11:18:44 -05:00
websocket-driver (0.6.3)
2015-06-18 22:14:41 -04:00
websocket-extensions (>= 0.1.0)
websocket-extensions (0.1.2)
2015-09-09 04:06:35 -04:00
wikicloth (0.8.1)
2014-07-28 05:47:27 -04:00
builder
expression_parser
2015-09-09 04:06:35 -04:00
rinku
2016-01-11 11:41:11 -05:00
xml-simple (1.1.5)
xpath (2.0.0)
2011-10-08 17:36:38 -04:00
nokogiri (~> 1.3)
PLATFORMS
ruby
DEPENDENCIES
RedCloth (~> 4.2.9)
2015-08-25 21:42:46 -04:00
ace-rails-ap (~> 2.0.1)
activerecord-deprecated_finders (~> 1.0.3)
activerecord-session_store (~> 0.1.0)
2015-03-28 19:39:32 -04:00
acts-as-taggable-on (~> 3.4)
2015-08-25 21:42:46 -04:00
addressable (~> 2.3.8)
after_commit_queue
allocations (~> 1.0)
2015-08-25 21:42:46 -04:00
annotate (~> 2.6.0)
2015-11-25 17:03:30 -05:00
asana (~> 0.4.0)
asciidoctor (~> 1.5.2)
2015-08-25 21:42:46 -04:00
attr_encrypted (~> 1.3.4)
awesome_print (~> 1.2.0)
babosa (~> 1.0.2)
benchmark-ips
2015-08-25 21:42:46 -04:00
better_errors (~> 1.0.1)
binding_of_caller (~> 0.7.2)
2016-01-01 21:11:39 -05:00
bootstrap-sass (~> 3.3.0)
2015-12-27 21:19:01 -05:00
brakeman (~> 3.1.0)
browser (~> 1.0.0)
bullet
bundler-audit
2015-02-16 13:58:40 -05:00
byebug
2016-01-01 21:29:21 -05:00
cal-heatmap-rails (~> 3.5.0)
2015-07-06 19:50:36 -04:00
capybara (~> 2.4.0)
2015-04-25 14:10:09 -04:00
capybara-screenshot (~> 1.0.0)
2015-08-25 21:42:46 -04:00
carrierwave (~> 0.9.0)
charlock_holmes (~> 0.7.3)
2015-08-25 21:42:46 -04:00
coffee-rails (~> 4.1.0)
colorize (~> 0.7.0)
Storing of application metrics in InfluxDB This adds the ability to write application metrics (e.g. SQL timings) to InfluxDB. These metrics can in turn be visualized using Grafana, or really anything else that can read from InfluxDB. These metrics can be used to track application performance over time, between different Ruby versions, different GitLab versions, etc. == Transaction Metrics Currently the following is tracked on a per transaction basis (a transaction is a Rails request or a single Sidekiq job): * Timings per query along with the raw (obfuscated) SQL and information about what file the query originated from. * Timings per view along with the path of the view and information about what file triggered the rendering process. * The duration of a request itself along with the controller/worker class and method name. * The duration of any instrumented method calls (more below). == Sampled Metrics Certain metrics can't be directly associated with a transaction. For example, a process' total memory usage is unrelated to any running transactions. While a transaction can result in the memory usage going up there's no accurate way to determine what transaction is to blame, this becomes especially problematic in multi-threaded environments. To solve this problem there's a separate thread that takes samples at a fixed interval. This thread (using the class Gitlab::Metrics::Sampler) currently tracks the following: * The process' total memory usage. * The number of file descriptors opened by the process. * The amount of Ruby objects (using ObjectSpace.count_objects). * GC statistics such as timings, heap slots, etc. The default/current interval is 15 seconds, any smaller interval might put too much pressure on InfluxDB (especially when running dozens of processes). == Method Instrumentation While currently not yet used methods can be instrumented to track how long they take to run. Unlike the likes of New Relic this doesn't require modifying the source code (e.g. including modules), it all happens from the outside. For example, to track `User.by_login` we'd add the following code somewhere in an initializer: Gitlab::Metrics::Instrumentation. instrument_method(User, :by_login) to instead instrument an instance method: Gitlab::Metrics::Instrumentation. instrument_instance_method(User, :save) Instrumentation for either all public model methods or a few crucial ones will be added in the near future, I simply haven't gotten to doing so just yet. == Configuration By default metrics are disabled. This means users don't have to bother setting anything up if they don't want to. Metrics can be enabled by editing one's gitlab.yml configuration file (see config/gitlab.yml.example for example settings). == Writing Data To InfluxDB Because InfluxDB is still a fairly young product I expect the worse. Data loss, unexpected reboots, the database not responding, you name it. Because of this data is _not_ written to InfluxDB directly, instead it's queued and processed by Sidekiq. This ensures that users won't notice anything when InfluxDB is giving trouble. The metrics worker can be started in a standalone manner as following: bundle exec sidekiq -q metrics The corresponding class is called MetricsWorker.
2015-12-09 10:45:51 -05:00
connection_pool (~> 2.0)
coveralls (~> 0.8.2)
2015-11-24 15:42:42 -05:00
creole (~> 0.5.0)
2016-01-01 21:34:49 -05:00
d3_rails (~> 3.5.0)
2015-06-17 21:15:23 -04:00
database_cleaner (~> 1.4.0)
default_value_for (~> 3.0.0)
2016-01-18 16:39:31 -05:00
devise (~> 3.5.4)
2015-08-25 21:42:46 -04:00
devise-async (~> 0.9.0)
devise-two-factor (~> 2.0.0)
2014-04-15 11:02:02 -04:00
diffy (~> 3.0.3)
doorkeeper (~> 2.2.0)
2015-08-25 21:42:46 -04:00
dropzonejs-rails (~> 0.7.1)
email_reply_parser (~> 0.5.8)
email_spec (~> 1.6.0)
2015-08-25 21:42:46 -04:00
factory_girl_rails (~> 4.3.0)
ffaker (~> 2.0.0)
flay
flog
2016-01-11 11:41:11 -05:00
fog (~> 1.36.0)
2014-10-01 18:21:29 -04:00
font-awesome-rails (~> 4.2)
2012-01-11 02:35:21 -05:00
foreman
2015-06-25 21:43:24 -04:00
fuubar (~> 2.0.0)
gemnasium-gitlab-service (~> 0.2)
github-linguist (~> 4.7.0)
2015-08-25 21:42:46 -04:00
github-markup (~> 1.3.1)
gitlab-flowdock-git-hook (~> 1.0.1)
2015-12-05 17:49:32 -05:00
gitlab_emoji (~> 0.2.0)
gitlab_git (~> 7.2.23)
gitlab_meta (= 7.0)
2015-08-25 21:42:46 -04:00
gitlab_omniauth-ldap (~> 1.2.1)
gollum-lib (~> 4.1.0)
2015-11-24 15:36:36 -05:00
gon (~> 6.0.1)
grape (~> 0.13.0)
grape-entity (~> 0.4.2)
2015-10-07 21:59:16 -04:00
haml-rails (~> 0.9.0)
2015-03-30 18:53:24 -04:00
hipchat (~> 1.5.0)
html-pipeline (~> 1.11.0)
2015-08-25 21:42:46 -04:00
httparty (~> 0.13.3)
Storing of application metrics in InfluxDB This adds the ability to write application metrics (e.g. SQL timings) to InfluxDB. These metrics can in turn be visualized using Grafana, or really anything else that can read from InfluxDB. These metrics can be used to track application performance over time, between different Ruby versions, different GitLab versions, etc. == Transaction Metrics Currently the following is tracked on a per transaction basis (a transaction is a Rails request or a single Sidekiq job): * Timings per query along with the raw (obfuscated) SQL and information about what file the query originated from. * Timings per view along with the path of the view and information about what file triggered the rendering process. * The duration of a request itself along with the controller/worker class and method name. * The duration of any instrumented method calls (more below). == Sampled Metrics Certain metrics can't be directly associated with a transaction. For example, a process' total memory usage is unrelated to any running transactions. While a transaction can result in the memory usage going up there's no accurate way to determine what transaction is to blame, this becomes especially problematic in multi-threaded environments. To solve this problem there's a separate thread that takes samples at a fixed interval. This thread (using the class Gitlab::Metrics::Sampler) currently tracks the following: * The process' total memory usage. * The number of file descriptors opened by the process. * The amount of Ruby objects (using ObjectSpace.count_objects). * GC statistics such as timings, heap slots, etc. The default/current interval is 15 seconds, any smaller interval might put too much pressure on InfluxDB (especially when running dozens of processes). == Method Instrumentation While currently not yet used methods can be instrumented to track how long they take to run. Unlike the likes of New Relic this doesn't require modifying the source code (e.g. including modules), it all happens from the outside. For example, to track `User.by_login` we'd add the following code somewhere in an initializer: Gitlab::Metrics::Instrumentation. instrument_method(User, :by_login) to instead instrument an instance method: Gitlab::Metrics::Instrumentation. instrument_instance_method(User, :save) Instrumentation for either all public model methods or a few crucial ones will be added in the near future, I simply haven't gotten to doing so just yet. == Configuration By default metrics are disabled. This means users don't have to bother setting anything up if they don't want to. Metrics can be enabled by editing one's gitlab.yml configuration file (see config/gitlab.yml.example for example settings). == Writing Data To InfluxDB Because InfluxDB is still a fairly young product I expect the worse. Data loss, unexpected reboots, the database not responding, you name it. Because of this data is _not_ written to InfluxDB directly, instead it's queued and processed by Sidekiq. This ensures that users won't notice anything when InfluxDB is giving trouble. The metrics worker can be started in a standalone manner as following: bundle exec sidekiq -q metrics The corresponding class is called MetricsWorker.
2015-12-09 10:45:51 -05:00
influxdb (~> 0.2)
jquery-atwho-rails (~> 1.3.2)
jquery-rails (~> 4.0.0)
2015-08-25 21:42:46 -04:00
jquery-scrollto-rails (~> 1.4.3)
jquery-turbolinks (~> 2.1.0)
jquery-ui-rails (~> 5.0.0)
kaminari (~> 0.16.3)
2015-08-25 21:42:46 -04:00
letter_opener (~> 1.1.2)
mail_room (~> 0.6.1)
method_source (~> 0.8)
2015-08-25 21:42:46 -04:00
minitest (~> 5.7.0)
mousetrap-rails (~> 1.4.6)
mysql2 (~> 0.3.16)
nested_form (~> 0.3.2)
2015-11-25 11:18:44 -05:00
net-ssh (~> 3.0.1)
newrelic-grape
2015-08-25 21:42:46 -04:00
newrelic_rpm (~> 3.9.4.245)
nokogiri (= 1.6.7.1)
nprogress-rails (~> 0.1.6.7)
2015-08-25 21:42:46 -04:00
oauth2 (~> 1.0.0)
octokit (~> 3.7.0)
omniauth (~> 1.2.2)
omniauth-azure-oauth2 (~> 0.0.6)
2015-08-25 21:42:46 -04:00
omniauth-bitbucket (~> 0.0.2)
2015-11-11 23:25:31 -05:00
omniauth-cas3 (~> 1.1.2)
2015-11-03 11:58:12 -05:00
omniauth-facebook (~> 3.0.0)
2015-08-25 21:42:46 -04:00
omniauth-github (~> 1.1.1)
omniauth-gitlab (~> 1.0.0)
2015-10-06 22:03:42 -04:00
omniauth-google-oauth2 (~> 0.2.0)
2015-10-06 21:48:19 -04:00
omniauth-kerberos (~> 0.3.0)
omniauth-saml (~> 1.4.0)
2015-10-06 22:03:42 -04:00
omniauth-shibboleth (~> 1.2.0)
2015-10-06 21:42:32 -04:00
omniauth-twitter (~> 1.2.0)
omniauth_crowd (~> 2.2.0)
2015-08-25 21:42:46 -04:00
org-ruby (~> 0.9.12)
paranoia (~> 2.0)
pg (~> 0.18.2)
2015-12-16 14:55:48 -05:00
poltergeist (~> 1.8.1)
pry-rails
2015-08-25 21:42:46 -04:00
quiet_assets (~> 1.0.2)
rack-attack (~> 4.3.1)
2015-10-07 22:08:30 -04:00
rack-cors (~> 0.4.0)
2015-11-24 15:48:49 -05:00
rack-oauth2 (~> 1.2.1)
2015-11-25 11:18:44 -05:00
rails (= 4.2.4)
2015-11-26 08:48:01 -05:00
rails-deprecated_sanitizer (~> 1.0.3)
2013-08-31 18:04:22 -04:00
raphael-rails (~> 2.1.2)
rblineprof
2014-07-28 05:47:27 -04:00
rdoc (~> 3.6)
recaptcha
redcarpet (~> 3.3.3)
2015-12-10 12:45:36 -05:00
redis-namespace
2015-08-25 21:42:46 -04:00
redis-rails (~> 4.0.0)
request_store (~> 1.2.0)
rerun (~> 0.11.0)
2015-11-25 11:18:44 -05:00
responders (~> 2.0)
2015-12-01 09:02:26 -05:00
rouge (~> 1.10.1)
2015-08-25 21:42:46 -04:00
rqrcode-rails3 (~> 0.1.7)
2015-06-17 18:05:48 -04:00
rspec-rails (~> 3.3.0)
2015-12-14 14:18:32 -05:00
rubocop (~> 0.35.0)
2015-09-15 16:09:32 -04:00
ruby-fogbugz (~> 0.2.1)
sanitize (~> 2.0)
2015-12-22 17:04:41 -05:00
sass-rails (~> 5.0.0)
2015-08-25 21:42:46 -04:00
sdoc (~> 0.3.20)
seed-fu (~> 2.3.5)
2015-06-24 17:13:21 -04:00
select2-rails (~> 3.5.9)
2016-01-18 11:15:10 -05:00
sentry-raven
2015-08-25 21:42:46 -04:00
settingslogic (~> 2.0.9)
2015-08-04 18:21:12 -04:00
sham_rack
shoulda-matchers (~> 2.8.0)
2015-12-10 12:45:36 -05:00
sidekiq (~> 4.0)
sidekiq-cron (~> 0.4.0)
2015-08-25 21:42:46 -04:00
simplecov (~> 0.10.0)
sinatra (~> 1.4.4)
six (~> 0.2.0)
2015-10-07 21:51:05 -04:00
slack-notifier (~> 1.2.0)
2015-08-25 21:42:46 -04:00
spinach-rails (~> 0.2.1)
spring (~> 1.3.6)
spring-commands-rspec (~> 1.0.4)
2015-05-06 16:50:47 -04:00
spring-commands-spinach (~> 1.0.0)
spring-commands-teaspoon (~> 0.0.2)
sprockets (~> 2.12.3)
2015-11-09 09:11:42 -05:00
state_machines-activerecord (~> 0.3.0)
2015-08-25 21:42:46 -04:00
task_list (~> 1.0.2)
2015-05-06 16:50:47 -04:00
teaspoon (~> 1.0.0)
2015-08-25 21:42:46 -04:00
teaspoon-jasmine (~> 2.2.0)
2015-11-26 04:57:04 -05:00
test_after_commit (~> 0.4.2)
2015-08-25 21:42:46 -04:00
thin (~> 1.6.1)
2015-10-07 21:54:15 -04:00
tinder (~> 1.10.0)
2015-05-29 00:05:14 -04:00
turbolinks (~> 2.5.0)
2015-10-14 02:39:59 -04:00
uglifier (~> 2.7.2)
underscore-rails (~> 1.8.0)
2015-08-25 21:42:46 -04:00
unf (~> 0.1.4)
unicorn (~> 4.8.2)
unicorn-worker-killer (~> 0.4.2)
version_sorter (~> 2.0.0)
virtus (~> 1.0.1)
2015-11-25 11:18:44 -05:00
web-console (~> 2.0)
webmock (~> 1.21.0)
2015-09-09 04:06:35 -04:00
wikicloth (= 0.8.1)
2015-09-29 08:54:13 -04:00
BUNDLED WITH
2016-01-07 12:27:01 -05:00
1.11.2