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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more metrics #2310
Add more metrics #2310
Changes from 31 commits
eb5525c
260b745
c84204b
8c5a979
ddb424e
27fb0fd
09357db
088b918
76b1084
090ada8
bd8b64b
f205434
de98ec5
58cf08b
c897f8a
f184a61
b86efce
b8241a0
94f3d42
4166809
3b128b5
8817d1a
9bc707c
3badebd
aadc59f
87eed6d
fa60c9e
10e3407
0978160
3920e74
703a89d
b10178e
b41331b
ef13002
5387bc9
853100d
37d4cdc
2297804
11a6cfe
c921a09
0785b2d
aa751cd
0f85f04
21ebbc9
523932d
1b5c428
2fba5d2
f23b469
e67ae19
c043ed7
7d17f99
e0124b6
f12185f
be71c4b
a128622
395f491
eb3872f
bee9c6f
8da222a
8c0cccc
aa6120a
5aea57a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The low end could also be informative in metrics. 1 is good to know and it's a very state of the chain between 1 and even 2 or 3, so I'd prefer to have 1-5 all there I think. And then probably 200, 400, 800, 1600, 3200 on the high end for now. We can always add more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated these buckets so that we are very detailed at low, then we reach your proposed high end around 16th bucket, but then I left a few at the very end for the high values. Commit is here: ef13002
Distribution visualisation:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably should still specify that this is in Gwei.
Also, I don't know if we should bother having so much granularity up high. When I said 50 ETH in our convo, I was thinking in terms of the Maximum conceiveable fee, well beyond what will happen any time soon.
We should have many, much lower.
For example a single tx from testnet here:
This is during low volume, etc, but it's an idea of what we could be working with, much more likely than even 0.05 ETH.
So perhaps we break it down like: 0, 100, 200, 400, 800, 1_600, etc... It's less aggressive than log_10, and gives us helpful granularity.
The highest for now can just be
52_428_800.0
? Are we okay with 20 buckets?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The metric itself is explicit about the unit:
I see that we don't use gwei across the fuel-core codebase (except for the
fuel-gas-price-algorithm
crate), which I think makes "gwei" unit a default for developers.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's a good observation, thanks. I think we're good with ~20 buckets, we can still re-adjust them once we start observing real-world data.
Updated in b41331b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think some smaller values are useful here too. Down to 0... or whatever header + mint comes to :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in 5387bc9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we log these metrics only if config.metrics is enabled?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I put up a draft PR, because I'm not sure about how to approach this correctly. Please see the description of this PR: #2323
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per the convo, metrics have been moved to the importer and this commit makes the importer respect the
--metrics
parameter.