Contract Pruning Metrics #770
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
peterjan
commented
Nov 29, 2023
api/metrcis.go
Outdated
| @@ -10,6 +10,7 @@ const ( | |||
| ChurnDirAdded = "added" | |||
| ChurnDirRemoved = "removed" | |||
|
|
|||
| MetricContractPrune = "contractprune" | |||
There was a problem hiding this comment.
I don't like both the metric name and the database table name. I wonder whether it makes sense to call it pruning... I don't like that it's not scoped but then otoh churn isn't either. Pruning is a broader term though.
…o pj/contract-pruning-metrics
ChrisSchinnerl
approved these changes
Dec 6, 2023
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.
This PR adds pruning metrics, as well as an integration test that covers all metrics we added so far.