Repo per doc metrics #390
Merged
Repo per doc metrics #390
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
alexjg
force-pushed
the
repo-per-doc-metrics
branch
from
9f082b1 to
f36efc4
Compare
Problem: when analyzing a sync server under heavy load it is difficult to identify what is causing the load. There are lots of questions we might have such as "what documents are in memory?" or "which documents are taking longest in `receiveSyncMessage`?". Solution: expose a `"doc-metrics"` event on `Repo` which is fired whenever a documnt is loaded or receives a sync message. This can be wired up to Prometheus or other monitoring tools to allow operators to answer these questions. Add num ops and changes to events
alexjg
force-pushed
the
repo-per-doc-metrics
branch
from
f36efc4 to
fdcee17
Compare
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.
Problem: when analyzing a sync server under heavy load it is difficult
to identify what is causing the load. There are lots of questions we
might have such as "what documents are in memory?" or "which documents are
taking longest in
receiveSyncMessage?".Solution: expose a
"doc-metrics"event onRepowhich is firedwhenever a documnt is loaded or receives a sync message. This can be
wired up to Prometheus or other monitoring tools to allow operators to
answer these questions.