gitlab-org--gitlab-foss/lib/gitlab/metrics
Yorick Peterse be3b878443 Track method call times/counts as a single metric
Previously we'd create a separate Metric instance for every method call
that would exceed the method call threshold. This is problematic because
it doesn't provide us with information to accurately get the _total_
execution time of a particular method. For example, if the method
"Foo#bar" was called 4 times with a runtime of ~10 milliseconds we'd end
up with 4 different Metric instances. If we were to then get the
average/95th percentile/etc of the timings this would be roughly 10
milliseconds. However, the _actual_ total time spent in this method
would be around 40 milliseconds.

To solve this problem we now create a single Metric instance per method.
This Metric instance contains the _total_ real/CPU time and the call
count for every instrumented method.
2016-06-17 13:09:55 -04:00
..
subscribers Add cache count metrics to rails cache 2016-05-15 19:47:41 +01:00
delta.rb Storing of application metrics in InfluxDB 2015-12-17 17:25:48 +01:00
instrumentation.rb Track method call times/counts as a single metric 2016-06-17 13:09:55 -04:00
method_call.rb Track method call times/counts as a single metric 2016-06-17 13:09:55 -04:00
metric.rb Use more accurate timestamps for InfluxDB. 2016-04-08 16:39:44 +02:00
rack_middleware.rb Filter out sensitive parameters of metrics data 2016-06-17 18:14:25 +02:00
sampler.rb Filter out classes without names in the sampler 2016-06-14 18:09:06 +02:00
sidekiq_middleware.rb Tag all transaction metrics with an "action" tag 2016-01-11 16:51:01 +01:00
system.rb Store block timings as transaction values 2016-04-11 13:09:36 +02:00
transaction.rb Track method call times/counts as a single metric 2016-06-17 13:09:55 -04:00