More metrics #408
Merged
More metrics #408
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
added 2 commits
December 12, 2016 20:06
We recently had a case of a user accidentally pushing a large number of tags to their repository and wondering why the CI was so busy building things. It would have been easier to see what the cause was with these metrics. Signed-off-by: Thomas Leonard <thomas.leonard@docker.com>
It's useful to see e.g. graphs of warning and error log messages. This metric uses multiple labels (level and src), and includes a fix to make that work. Signed-off-by: Thomas Leonard <thomas.leonard@docker.com>
|
Travis failures seem unrelated (no deps changed in this PR): The following dependencies couldn't be met:
|
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.
Report number of tags, branches and open PRs
We recently had a case of a user accidentally pushing a large number of
tags to their repository and wondering why the CI was so busy building
things. It would have been easier to see what the cause was with these
metrics.
Report metrics for log messages
It's useful to see e.g. graphs of warning and error log messages.
This metric uses multiple labels (level and src), and includes a fix to make that work.