bosun: Adding instrumentation around schedule lock. #1113
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| waitTime := s.mutexWaitTime | ||
| s.mutex.Unlock() | ||
| collect.Put("bosun.schedule.lock.wait", opentsdb.TagSet{"caller": holder}, waitTime) | ||
| collect.Put("bosun.schedule.lock.held", opentsdb.TagSet{"caller": holder}, time.Now().Sub(start)/time.Millisecond) |
There was a problem hiding this comment.
time.Now().Sub(start) -> time.Since(start)
|
LGTM if you squish it. |
captncraig
added a commit
that referenced
this pull request
Jul 1, 2015
bosun: Adding instrumentation around schedule lock.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here we emit metrics about how long a method spent waiting for a lock, as well as how long it held it.
I suspect the slowness on the dashboard is related to lock contention, and this should help diagnose it.