summaryrefslogtreecommitdiffhomepage
path: root/pkg/sentry/time
diff options
context:
space:
mode:
authorNayana Bidari <nybidari@google.com>2021-04-26 17:35:16 -0700
committergVisor bot <gvisor-bot@google.com>2021-04-26 17:37:29 -0700
commit5b207fe7834d9c6541bd99bf75e3dfeebce2d9d5 (patch)
tree7783dbac4f1189e065412745701724336527b79a /pkg/sentry/time
parent509f5aa57fa079d113411f10fc26d9f8432ec511 (diff)
Remove metrics: fallback, vsyscallCount and partialResult
The newly added Weirdness metric with fields should be used instead of them. Simple query for weirdness metric: http://shortn/_DGNk0z2Up6 PiperOrigin-RevId: 370578132
Diffstat (limited to 'pkg/sentry/time')
-rw-r--r--pkg/sentry/time/calibrated_clock.go8
1 files changed, 1 insertions, 7 deletions
diff --git a/pkg/sentry/time/calibrated_clock.go b/pkg/sentry/time/calibrated_clock.go
index 94f98d746..39bf1e0de 100644
--- a/pkg/sentry/time/calibrated_clock.go
+++ b/pkg/sentry/time/calibrated_clock.go
@@ -25,11 +25,6 @@ import (
"gvisor.dev/gvisor/pkg/syserror"
)
-// fallbackMetric tracks failed updates. It is not sync, as it is not critical
-// that all occurrences are captured and CalibratedClock may fallback many
-// times.
-var fallbackMetric = metric.MustCreateNewUint64Metric("/time/fallback", false /* sync */, "Incremented when a clock falls back to system calls due to a failed update")
-
// CalibratedClock implements a clock that tracks a reference clock.
//
// Users should call Update at regular intervals of around approxUpdateInterval
@@ -102,8 +97,7 @@ func (c *CalibratedClock) resetLocked(str string, v ...interface{}) {
c.Warningf(str+" Resetting clock; time may jump.", v...)
c.ready = false
c.ref.Reset()
- fallbackMetric.Increment()
- metric.WeirdnessMetric.Increment("fallback")
+ metric.WeirdnessMetric.Increment("time_fallback")
}
// updateParams updates the timekeeping parameters based on the passed