- 31 Mar, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 27 Mar, 2016 1 commit
-
-
Stan Hu authored
Closes #14361
-
- 19 Mar, 2016 1 commit
-
-
Yorick Peterse authored
This caches the output of Repository#exists? in Redis while making sure it's flushed properly when creating new repositories, deleting them, etc. For the ProjectWiki tests to work I had to make ProjectWiki#create_repo! public as testing private methods in RSpec is a bit of a pain.
-
- 17 Mar, 2016 2 commits
-
-
Jacob Vosmaer authored
-
Gabriel Mazetto authored
-
- 15 Mar, 2016 2 commits
-
-
Zeger-Jan van de Weg authored
-
Zeger-Jan van de Weg authored
Fixes #13261
-
- 03 Mar, 2016 1 commit
-
-
Jacob Vosmaer authored
-
- 23 Feb, 2016 1 commit
-
-
Yorick Peterse authored
This keeps all the cache expiration code in a single file/class instead of spreading it all across the codebase.
-
- 17 Feb, 2016 2 commits
-
-
Yorick Peterse authored
This ensures the caches for Repository#empty? and Repository#has_visible_content? are flushed after a repository has been imported or forked. Fixes gitlab-org/gitlab-ce#13505
-
James Lopez authored
-
- 15 Feb, 2016 1 commit
-
-
James Lopez authored
-
- 11 Feb, 2016 1 commit
-
-
James Lopez authored
-
- 29 Jan, 2016 1 commit
-
-
Josh Frye authored
-
- 28 Jan, 2016 1 commit
-
-
Josh Frye authored
-
- 26 Jan, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 29 Dec, 2015 1 commit
-
-
Yorick Peterse authored
This removes the need for Sidekiq and any overhead/problems introduced by TCP. There are a few things to take into account: 1. When writing data to InfluxDB you may still get an error if the server becomes unavailable during the write. Because of this we're catching all exceptions and just ignore them (for now). 2. Writing via UDP apparently requires the timestamp to be in nanoseconds. Without this data either isn't written properly. 3. Due to the restrictions on UDP buffer sizes we're writing metrics one by one, instead of writing all of them at once.
-
- 17 Dec, 2015 3 commits
-
-
Yorick Peterse authored
InfluxDB throws an error when trying to store a list of tags where one or more have an empty value.
-
Yorick Peterse authored
This ensures that e.g. line numbers used in tags are first casted to strings.
-
Yorick Peterse authored
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.
-
- 10 Dec, 2015 2 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 04 Dec, 2015 1 commit
-
-
Gabriel Mazetto authored
Updated Sidekiq to 3.5.x
-
- 30 Nov, 2015 1 commit
-
-
Valery Sizov authored
-
- 26 Nov, 2015 1 commit
-
-
Valery Sizov authored
-
- 25 Nov, 2015 1 commit
-
-
Valery Sizov authored
-
- 23 Nov, 2015 1 commit
-
-
Kamil Trzcinski authored
- Fix for Ci::Build state machine, allowing to process builds without the project - Forcefully update builds that didn't want to update with state machine - Fix saving GitLabCiService as Admin Template
-
- 20 Nov, 2015 1 commit
-
-
Rubén Dávila authored
It should exist in EE only.
-
- 18 Nov, 2015 3 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Zeger-Jan van de Weg authored
-
- 03 Nov, 2015 1 commit
-
-
Kamil Trzcinski authored
-
- 20 Oct, 2015 2 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
- 21 Sep, 2015 1 commit
-
-
Douwe Maan authored
-
- 18 Sep, 2015 1 commit
-
-
Valery Sizov authored
-
- 11 Sep, 2015 1 commit
-
-
Stan Hu authored
Use import_status to track async import status and give feedback to the user Closes #2388 Closes #2400
-
- 09 Sep, 2015 1 commit
-
-
Jared Szechy authored
-
- 28 Aug, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 26 Aug, 2015 1 commit
-
-
Douwe Maan authored
-