summaryrefslogtreecommitdiff
path: root/lib/gitlab
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | Optimize LDAP and add a search timeoutDrew Blessing2016-01-113-11/+25
| | | |
* | | | Tag all transaction metrics with an "action" tagYorick Peterse2016-01-113-12/+18
|/ / / | | | | | | | | | | | | | | | | | | Without this it's impossible to find out what methods/views/queries are executed by a certain controller or Sidekiq worker. While this will increase the total number of series it should stay within reasonable limits due to the amount of "actions" being small enough.
* | | Merge gitlab.com:gitlab-org/gitlab-ceJeroen Nijhof2016-01-113-8/+4
|\ \ \
| * \ \ Merge branch 'api-project-upload' into 'master' Robert Speicher2016-01-082-8/+3
| |\ \ \ | | |/ / | |/| | | | | | | | | | | | | | | | | | Add API project upload endpoint Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/4317 See merge request !2329
| | * | 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
| | | |
| * | | Merge branch 'suppress-allow-failure-builds' into 'master' Stan Hu2016-01-081-0/+1
| |\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Suppress e-mails on failed builds if allow_failure is set Every time I push to GitLab, I get > 2 emails saying a spec failed when I don't care about the benchmarks and others that have `allow_failure` set to `true`. @ayufan mentioned creating a summary e-mail to prevent getting one e-mail per build, but the latter might actually be desirable. For example, I do want to know if Rubocop errors fail right away. See merge request !2178
| | * | | Suppress e-mails on failed builds if allow_failure is setStan Hu2016-01-071-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Every time I push to GitLab, I get > 2 emails saying a spec failed when I don't care about benchmarks and other specs that have `allow_failure` set to `true`.
* | | | | Merge gitlab.com:gitlab-org/gitlab-ceJeroen Nijhof2016-01-081-0/+3
|\ \ \ \ \ | |/ / / /
| * | | | Merge branch 'current-settings-handle-missing-db' into 'master' Yorick Peterse2016-01-081-0/+3
| |\ \ \ \ | | | | | | | | | | | | See merge request !2346
| | * | | | Handle missing DBs in connect_to_db?Yorick Peterse2016-01-081-0/+3
| | |/ / / | | | | | | | | | | | | | | | | | | | | This ensures CurrentSettings#connect_to_db? returns "false" in the event of a database not existing, instead of raising an error.
* | | | | Merge gitlab.com:gitlab-org/gitlab-ceJeroen Nijhof2016-01-083-6/+8
|\ \ \ \ \ | |/ / / /
| * | | | Merge branch 'milestone-ref' into 'master' Robert Speicher2016-01-071-1/+1
| |\ \ \ \ | | |/ / / | |/| | | | | | | | | | | | | | | | | | | | | | | Link to milestone in "Milestone changed" system note Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/4141 See merge request !2203
| | * | | Merge branch 'master' into milestone-refDouwe Maan2016-01-0515-10/+710
| | |\ \ \
| | * \ \ \ Merge branch 'master' into milestone-refDouwe Maan2015-12-243-4/+13
| | |\ \ \ \
| | * | | | | Render milestone links as referencesDouwe Maan2015-12-241-1/+1
| | | | | | |
| * | | | | | Store request methods/URIs as valuesYorick Peterse2016-01-072-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since filtering by these values is very rare (they're mostly just displayed as-is) we don't need to waste any index space by saving them as tags. By storing them as values we also greatly reduce the number of series in InfluxDB.
| * | | | | | Removed UUIDs from metrics transactionsYorick Peterse2016-01-071-3/+1
| | |_|_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | While useful for finding out what methods/views belong to a transaction this might result in too much data being stored in InfluxDB.
* | | | | | Merge gitlab.com:gitlab-org/gitlab-ceJeroen Nijhof2016-01-071-5/+1
|\ \ \ \ \ \ | |/ / / / /
| * | | | | 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.
* | | | | | Merge gitlab.com:gitlab-org/gitlab-ceJeroen Nijhof2016-01-0692-2034/+2528
|\ \ \ \ \ \ | |/ / / / /
| * | | | | 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
| | | | |
View Lorry Controller Status