- 07 1月, 2016 3 次提交
-
-
由 Jacob Vosmaer 提交于
-
由 Yorick Peterse 提交于
This reverts commit 7549102b. Apparently I was wrong about ActiveSupport::Notifications::Event#duration returning the duration in seconds, instead it returns it in milliseconds already.
-
由 koreamic 提交于
Using the fuzzy filter, develop "file finder" feature. - feedback(http://feedback.gitlab.com/forums/176466-general/suggestions/4987909-add-file-finder-fuzzy-input-in-files-tab-to-ju ) - fuzzy filter(https://github.com/jeancroy/fuzzaldrin-plus) - shortcuts(when "t" was hitted at tree view, go to 'file find' page and 'esc' is to go back) - depends on gitlab_git 7.2.22
-
- 06 1月, 2016 9 次提交
-
-
由 Yorick Peterse 提交于
Transaction timings are also already stored in milliseconds, this keeps things consistent.
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Robert Speicher 提交于
-
由 Robert Speicher 提交于
-
-
-
-
由 Douwe Maan 提交于
-
- 05 1月, 2016 5 次提交
-
-
由 Douwe Maan 提交于
-
由 Robert Speicher 提交于
Tell, Don't Ask.
-
由 Robert Speicher 提交于
-
由 Stan Hu 提交于
Closes #4708
-
由 Douwe Maan 提交于
Hotfix note mail with notification
-
- 04 1月, 2016 11 次提交
-
-
由 Jacob Schatz 提交于
-
由 Valery Sizov 提交于
-
由 Steve Norman 提交于
-
由 Yorick Peterse 提交于
-
-
由 Yorick Peterse 提交于
This ensures Rails and Sidekiq transactions are split into the series "rails_transactions" and "sidekiq_transactions" respectively.
-
由 Yorick Peterse 提交于
This removes the need for any tags to differentiate between Sidekiq and Rails statistics while still being able to separate the two.
-
由 Yorick Peterse 提交于
This makes it easier to see where time is spent without having to aggregate all the individual points in the method_calls series.
-
由 Yorick Peterse 提交于
-
由 Yorick Peterse 提交于
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.
-
由 Stan Hu 提交于
Attempting to use the /projects/:id API by specifying :id in "namespace/project" format would always result in a 404 if the namespace contained a dot. The reason? From http://guides.rubyonrails.org/routing.html#specifying-constraints: "By default the :id parameter doesn't accept dots - this is because the dot is used as a separator for formatted routes. If you need to use a dot within an :id add a constraint which overrides this - for example id: /[^\/]+/ allows anything except a slash." Closes https://github.com/gitlabhq/gitlabhq/issues/9573
-
- 03 1月, 2016 1 次提交
-
-
由 Robert Speicher 提交于
Closes #201 - two-year-old bug, woo!
💥 🎉
-
- 01 1月, 2016 6 次提交
-
-
由 Mike Wyatt 提交于
-
由 Mike Wyatt 提交于
-
由 Yorick Peterse 提交于
This isn't hugely useful and mostly wastes InfluxDB space. We can re-add this whenever needed (but only once we really need it).
-
由 Yorick Peterse 提交于
This removes the need for tagging all metrics with a "process_type" tag.
-
由 Yorick Peterse 提交于
This ensures we don't need to load anything from either PostgreSQL or the Rails cache whenever creating new InfluxDB connections.
-
由 Yorick Peterse 提交于
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.
-
- 31 12月, 2015 3 次提交
-
-
由 Yorick Peterse 提交于
Nokogiri produces inefficient XPath expressions when given CSS expressions such as "a.gfm". Luckily these expressions can be optimized quite easily while still achieving the same results. In the two cases where this optimization is applied the run time has been reduced from around 170 ms to around 15 ms.
-
由 Yorick Peterse 提交于
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.
-
由 Robert Speicher 提交于
Prior, if we were viewing a blob at `https://example.com/namespace/project/blob/master/doc/some-file.md` and it contained a relative link such as `[README](../README.md)`, the resulting link when viewing the blob would be: `https://example.com/namespace/project/blob/README.md` which omits the `master` ref, resulting in a 404.
-
- 30 12月, 2015 1 次提交
-
-
由 Mike Wyatt 提交于
-
- 29 12月, 2015 1 次提交
-
-
由 Yorick Peterse 提交于
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.
-