summaryrefslogtreecommitdiff
path: root/lib/gitlab
Commit message (Collapse)AuthorAgeFilesLines
* DRY up upload and download servicesapi-project-uploadDouwe Maan2016-01-081-1/+1
|
* Satisfy RubocpDouwe Maan2016-01-071-1/+1
|
* Add API project upload endpointDouwe Maan2016-01-072-8/+3
|
* Revert "Store SQL/view timings in milliseconds"Yorick Peterse2016-01-072-11/+3
| | | | | | | | This reverts commit 7549102bb727daecc51da84af39956b32fc41537. Apparently I was wrong about ActiveSupport::Notifications::Event#duration returning the duration in seconds, instead it returns it in milliseconds already.
* Remove InfluxDB username/passwordremove-influxdb-credentialsYorick Peterse2016-01-061-5/+1
| | | | | InfluxDB over UDP doesn't use authentication, thus there's no need for these settings.
* Store SQL/view timings in millisecondsYorick Peterse2016-01-062-3/+11
| | | | | Transaction timings are also already stored in milliseconds, this keeps things consistent.
* Ensure that we're only importing local pull requestsDouglas Barbosa Alexandre2016-01-052-1/+9
|
* Generate separate comments when importing GitHub Issues into GitLabDouglas Barbosa Alexandre2016-01-055-72/+114
|
* Refactoring GithubImport::ImporterDouglas Barbosa Alexandre2016-01-053-61/+174
|
* Extract methods to import comments on a GitHub Pull RequestDouglas Barbosa Alexandre2016-01-051-24/+28
|
* Doesn't import GitHub PR where branches were no longer availableDouglas Barbosa Alexandre2016-01-051-38/+44
|
* Import comments on the diff of a GitHub Pull Request into GitLabDouglas Barbosa Alexandre2016-01-051-0/+16
|
* Import comments on GitHub Pull Request into GitLabDouglas Barbosa Alexandre2016-01-051-0/+14
|
* Import GitHub Pull Requests into GitLabDouglas Barbosa Alexandre2016-01-051-7/+57
|
* Merge branch 'metrics-tuning' into 'master' Dmitriy Zaporozhets2016-01-058-112/+59
|\ | | | | | | | | | | | | Tuning of metrics data to store This removes data we don't really need, as well as making sure we don't overload any cache stores or databases. See merge request !2265
| * Automatically prefix transaction series namesYorick Peterse2016-01-043-12/+11
| | | | | | | | | | This ensures Rails and Sidekiq transactions are split into the series "rails_transactions" and "sidekiq_transactions" respectively.
| * Use separate series for Rails/Sidekiq sample statsYorick Peterse2016-01-041-5/+14
| | | | | | | | | | This removes the need for any tags to differentiate between Sidekiq and Rails statistics while still being able to separate the two.
| * Track total method call times per transactionYorick Peterse2016-01-041-0/+2
| | | | | | | | | | This makes it easier to see where time is spent without having to aggregate all the individual points in the method_calls series.
| * Track total query/view timings in transactionsYorick Peterse2016-01-042-0/+23
| |
| * Ability to increment custom transaction valuesYorick Peterse2016-01-041-2/+13
| | | | | | | | | | | | This will be used to store/increment the total query/view rendering timings on a per transaction basis. This in turn can greatly reduce the amount of metrics stored.
| * Removed tracking of hostnames for metricsYorick Peterse2015-12-312-10/+2
| | | | | | | | | | This isn't hugely useful and mostly wastes InfluxDB space. We can re-add this whenever needed (but only once we really need it).
| * Use separate series for Rails/Sidekiq transactionsYorick Peterse2015-12-314-8/+10
| | | | | | | | This removes the need for tagging all metrics with a "process_type" tag.
| * Cache InfluxDB settings after the first useYorick Peterse2015-12-311-14/+18
| | | | | | | | | | This ensures we don't need to load anything from either PostgreSQL or the Rails cache whenever creating new InfluxDB connections.
| * Removed tracking of raw SQL queriesYorick Peterse2015-12-312-95/+0
| | | | | | | | | | | | | | | | | | | | | | | | This particular setup had 3 problems: 1. Storing SQL queries as tags is very inefficient as InfluxDB ends up indexing every query (and they can get pretty large). Storing these as values instead means we can't always display the SQL as easily. 2. We already instrument ActiveRecord query methods, thus we already have timing information about database queries. 3. SQL obfuscation is difficult to get right and I'd rather not expose sensitive data by accident.
* | Simplify `ContributionsCalendar#starting_year` and `#starting_month`Robert Speicher2016-01-011-2/+2
|/
* Removed various default metrics tagsreduce-influxdb-tagsYorick Peterse2015-12-311-5/+2
| | | | | | | | While it's useful to keep track of the different versions (Ruby, GitLab, etc) doing so for every point wastes disk space and possibly also RAM (which InfluxDB is all to eager to gobble up). If we want to see the performance differences between different GitLab versions simply looking at the performance since the last release date should suffice.
* Make sure that is no pending migrations in Gitlab::CurrentSettingsfix-buildDouglas Barbosa Alexandre2015-12-301-1/+3
|
* Use Gitlab::CurrentSettings for InfluxDBYorick Peterse2015-12-291-25/+11
| | | | | This ensures we can still start up even when not connecting to a database.
* Write to InfluxDB directly via UDPYorick Peterse2015-12-296-13/+40
| | | | | | | | | | | | | 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.
* Strip newlines from obfuscated SQLYorick Peterse2015-12-291-1/+1
| | | | | Newlines aren't really needed and they may mess with InfluxDB's line protocol.
* Merge branch 'feature/recaptcha_settings' into 'master' Dmitriy Zaporozhets2015-12-291-0/+14
|\ | | | | | | | | | | | | Makes reCAPTCHA configurable through Application Settings screen Following the work made by @stanhu here: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2216, made it configurable without needing to restart Gitlab See merge request !2231
| * reCAPTCHA is configurable through Admin Settings, no reload needed.Gabriel Mazetto2015-12-281-0/+14
| |
* | Handle missing settings table for metricsYorick Peterse2015-12-281-6/+10
|/ | | | | This ensures we can still boot, even when the "application_settings" table doesn't exist.
* Move InfluxDB settings to ApplicationSettingrelocate-influxdb-settingsYorick Peterse2015-12-281-8/+24
|
* Merge branch 'influxdb' into 'master' Dmitriy Zaporozhets2015-12-2812-0/+702
|\ | | | | | | | | | | | | Storing of application metrics in InfluxDB This adds support for tracking metrics in InfluxDB, which in turn can be visualized using Grafana. For more information see #2936. See merge request !2042
| * Added host option for InfluxDBinfluxdbYorick Peterse2015-12-281-1/+2
| |
| * Use String#delete for removing double quotesYorick Peterse2015-12-281-1/+1
| |
| * Track object counts using the "allocations" GemYorick Peterse2015-12-172-3/+26
| | | | | | | | | | This allows us to track the counts of actual classes instead of "T_XXX" nodes. This is only enabled on CRuby as it uses CRuby specific APIs.
| * Support for instrumenting class hierarchiesYorick Peterse2015-12-171-0/+23
| | | | | | | | This will be used to (for example) instrument all ActiveRecord models.
| * Only track method calls above a certain thresholdYorick Peterse2015-12-172-3/+9
| | | | | | | | | | | | | | 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.
| * Allow filtering of what methods to instrumentYorick Peterse2015-12-171-2/+17
| | | | | | | | | | This makes it possible to determine if a method should be instrumented or not using a block.
| * Track location information as tagsYorick Peterse2015-12-172-12/+22
| | | | | | | | | | | | This allows the information to be displayed when using certain functions (e.g. top()) as well as making it easier to aggregate on a per file basis.
| * Replace double quotes when obfuscating SQLYorick Peterse2015-12-171-1/+9
| | | | | | | | | | | | | | InfluxDB escapes double quotes upon output which makes it a pain to deal with. This ensures that if we're using PostgreSQL we don't store any queries containing double quotes in InfluxDB, solving the escaping problem.
| * Track object count types as tagsYorick Peterse2015-12-171-1/+3
| |
| * Only instrument methods defined directlyYorick Peterse2015-12-171-3/+7
| | | | | | | | | | | | | | | | | | | | When using instrument_methods/instrument_instance_methods we only want to instrument methods defined directly in a class, not those included via mixins (e.g. whatever RSpec throws in during development). In case an externally included method _has_ to be instrumented we can still use the regular instrument_method/instrument_instance_method methods.
| * Added Instrumentation.configureYorick Peterse2015-12-171-0/+4
| | | | | | | | | | This makes it easier to instrument multiple modules without having to type the full namespace over and over again.
| * Methods for instrumenting multiple methodsYorick Peterse2015-12-171-0/+23
| | | | | | | | | | | | The methods Instrumentation.instrument_methods and Instrumentation.instrument_instance_methods can be used to instrument all methods of a module at once.
| * Proper method instrumentation for special symbolsYorick Peterse2015-12-171-4/+5
| | | | | | | | | | This ensures that methods such as "==" can be instrumented without producing syntax errors.
| * Use custom code for instrumenting method callsYorick Peterse2015-12-172-48/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The use of ActiveSupport would slow down instrumented method calls by about 180x due to: 1. ActiveSupport itself not being the fastest thing on the planet 2. caller_locations() having quite some overhead The use of caller_locations() has been removed because it's not _that_ useful since we already know the full namespace of receivers and the names of the called methods. The use of ActiveSupport has been replaced with some custom code that's generated using eval() (which can be quite a bit faster than using define_method). This new setup results in instrumented methods only being about 35-40x slower (compared to non instrumented methods).
| * Use string evaluation for method instrumentationYorick Peterse2015-12-172-9/+11
| | | | | | | | | | This is faster than using define_method since we don't have to keep block bindings around.
View Lorry Controller Status