From b02f2c07bad4abdb128f5249b4e1a9eabfde4ce9 Mon Sep 17 00:00:00 2001 From: Diego Date: Fri, 30 Jan 2015 01:17:07 -0300 Subject: = play: use our own dispatcher instead of Akka's default dispatcher and reduce verbosity of log in test --- .../src/main/scala/kamon/system/sigar/ProcessCpuMetrics.scala | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'kamon-system-metrics') diff --git a/kamon-system-metrics/src/main/scala/kamon/system/sigar/ProcessCpuMetrics.scala b/kamon-system-metrics/src/main/scala/kamon/system/sigar/ProcessCpuMetrics.scala index 436fadda..73dcc6dc 100644 --- a/kamon-system-metrics/src/main/scala/kamon/system/sigar/ProcessCpuMetrics.scala +++ b/kamon-system-metrics/src/main/scala/kamon/system/sigar/ProcessCpuMetrics.scala @@ -36,7 +36,7 @@ class ProcessCpuMetrics(sigar: Sigar, instrumentFactory: InstrumentFactory) exte * while CPU usage time doesn't update. But supposing that it could be zero load for a process for some time, * We used an arbitrary duration of 2000 milliseconds, after which the same CPU usage time value become legal, and it is supposed that the load is really zero. * - * @see [[http://stackoverflow.com/questions/19323364/using-sigar-api-to-get-jvm-cpu-usage "Stack Overflow: Using Sigar API to get JVM Cpu usage"]] + * @see [[http://stackoverflow.com/questions/19323364/using-sigar-api-to-get-jvm-cpu-usage "StackOverflow: Using Sigar API to get JVM Cpu usage"]] */ def update(): Unit = { val currentProcCpu = sigar.getProcCpu(pid) -- cgit v1.2.3