An error occurred fetching the project authors.
- 03 Jun, 2016 1 commit
-
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 04 May, 2016 1 commit
-
-
Artem Sidorenko authored
-
- 27 Apr, 2016 1 commit
-
-
Stan Hu authored
These changes were pulled from GitLab EE to support configuring an alternative API URL than the default https://api.github.com. In addition, the `verify_ssl` flag allows users to disable SSL cert checking. One modification: add a default `args` option if it does not exist to avoid breaking existing configurations.
-
- 26 Apr, 2016 1 commit
-
-
Jacob Vosmaer authored
Daily seems to be to spammy, so let's default to weekly instead.
-
- 12 Apr, 2016 2 commits
-
-
DJ Mountney authored
-
Robert Speicher authored
Closes #15105
-
- 11 Apr, 2016 1 commit
-
-
Patricio Cano authored
-
- 07 Apr, 2016 1 commit
-
-
Jacob Schatz authored
-
- 06 Apr, 2016 2 commits
-
-
Patricio Cano authored
-
Jacob Vosmaer authored
-
- 05 Apr, 2016 1 commit
-
-
Patricio Cano authored
-
- 04 Apr, 2016 1 commit
-
-
Jacob Vosmaer authored
-
- 25 Mar, 2016 1 commit
-
-
Rémy Coutable authored
Improve and finish the fallback to the In-Reply-To and References header for the reply-by-email feature A few things to note: - The IncomingEmail feature is now enabled even without a correctly-formatted sub-address - Message-ID for new thread mail are kept the same so that subsequent notifications to this thread are grouped in the thread by the email service that receives the notification (i.e. In-Reply-To of the answer == Message-ID of the first thread message) - To maximize our chance to be able to retrieve the reply key, we look for it in the In-Reply-To header and the References header - The pattern for the fallback reply message id is "reply-[key]@[gitlab_host]" - Improve docs thanks to Axil
-
- 17 Mar, 2016 1 commit
-
-
Felipe Artur authored
-
- 16 Mar, 2016 1 commit
-
-
Daniel Carraro authored
-
- 10 Mar, 2016 1 commit
-
-
Felipe Artur authored
Prevent Groups to have smaller visibility than projects Add default_group_visibility_level to configuration Code improvements
-
- 19 Feb, 2016 1 commit
-
-
Douwe Maan authored
-
- 18 Feb, 2016 3 commits
-
-
Patricio Cano authored
-
Douwe Maan authored
This reverts commit c04e22fb, reversing changes made to 0feab326.
-
Patricio Cano authored
-
- 10 Feb, 2016 1 commit
-
-
Achilleas Pipinellis authored
[ci skip]
-
- 09 Feb, 2016 1 commit
-
-
Achilleas Pipinellis authored
[ci skip]
-
- 11 Jan, 2016 1 commit
-
-
Drew Blessing authored
-
- 28 Dec, 2015 5 commits
-
-
Gabriel Mazetto authored
-
Yorick Peterse authored
-
Yorick Peterse authored
-
Sytse Sijbrandij authored
-
Yorick Peterse authored
-
- 27 Dec, 2015 1 commit
-
-
Stan Hu authored
-
- 17 Dec, 2015 2 commits
-
-
Yorick Peterse authored
This ensures we don't end up wasting resources by tracking method calls that only take a few microseconds. By default the threshold is 10 milliseconds but this can be changed using the gitlab.yml configuration file.
-
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.
-
- 15 Dec, 2015 1 commit
-
-
tduehr authored
-
- 14 Dec, 2015 1 commit
-
-
Gabriel Mazetto authored
-
- 07 Dec, 2015 1 commit
-
-
Douwe Maan authored
-
- 23 Nov, 2015 1 commit
-
-
Kamil Trzcinski authored
-
- 19 Nov, 2015 1 commit
-
-
Marin Jankovski authored
-
- 16 Nov, 2015 1 commit
-
-
Marin Jankovski authored
-
- 13 Nov, 2015 1 commit
-
-
Kamil Trzcinski authored
- Enable CI by default for all new projects
-
- 03 Nov, 2015 1 commit
-
-
Douwe Maan authored
-
- 26 Oct, 2015 1 commit
-
-
Jacob Vosmaer authored
-