-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Fuel-Executor Metrics #807
Comments
Question regarding "histogram: I/O (db) time per block" - what we actually try to measure here? Are we interested in how much time was spent on the DB operations in This would require measuring call-chain such as:
And then, next to
we can add
Alternatively, we might want to work on a generic method of opt-in for measured DB reads, like Any opinions? @xgreenx @acerone85 |
The gas price is not available from the block importer, but rather from the producer. |
Also, what would be the suggested values for FEE_BUCKETS and GAS_PRICE_BUCKETS buckets. |
cc: @MitchTurner |
Perhaps we put the metrics on the |
As for now, we're not gonna be doing the "gas price" metric. Rationale: Since we don't have DA gas price yet, we can derive the total gas price from gas used and fee. |
Closes #807 ## Description This PR adds a couple of additional metrics (block importer and p2p) and also contains slight refactor of how we initialize bucket sized for histogram based metrics. The `metrics` command-line parameter has been replaced with `disable-metrics`. Metrics are now enabled by default, with the option to disable them entirely or on a per-module basis. This change is _breaking_ for all dependencies that use CLI to setup the `fuel-core-client` ``` --disable-metrics <METRICS> Disables all metrics, or specify a comma-separated list of modules to disable metrics for specific ones. Available options: importer, p2p, producer, txpool, graphql [env: METRICS=] [default: ] ``` Startup logs also show the metrics config: ``` 2024-10-14T20:17:37.536840Z INFO fuel_core_bin::cli::run: 308: Metrics config: Disable modules: txpool ``` ## Checklist - [X] Breaking changes are clearly marked as such in the PR description and changelog - [X] New behavior is reflected in tests ### Before requesting review - [X] I have reviewed the code myself --------- Co-authored-by: acerone85 <andrea.cerone@gmail.com> Co-authored-by: rymnc <43716372+rymnc@users.noreply.github.com> Co-authored-by: Green Baneling <XgreenX9999@gmail.com>
Everything looks completed :) |
Scope changes:
The following metrics will be added
The following metric will not be added as a part of this issue. We will discuss if we want some more sophisticated mechanism to measure other operations that touch DB
The following metric will not be added
Rationale: Fuel-Executor Metrics #807 (comment)
cc: @acerone85 @MitchTurner
The text was updated successfully, but these errors were encountered: