Skip to content

chore: improve gas price service log context#3249

Open
ming1523 wants to merge 1 commit intoFuelLabs:masterfrom
ming1523:chore-gas-price-log-context
Open

chore: improve gas price service log context#3249
ming1523 wants to merge 1 commit intoFuelLabs:masterfrom
ming1523:chore-gas-price-log-context

Conversation

@ming1523
Copy link
Copy Markdown

@ming1523 ming1523 commented Apr 1, 2026

Summary

  • replace generic gas price service debug logs with more contextual messages
  • include L2 block height / gas price information when processing L2 blocks
  • include DA bundle ids, L2 block ranges, and DA cost fields when buffering and applying DA block costs
  • log recorded height and next gas price updates with explicit fields

Why

This is a small follow-up for #1662. The gas price service already emits logs, but several of them are very generic (Received ..., Updating ...) or dump full debug payloads. This change keeps the same behavior while making the log stream more useful for operators and developers.

Validation

  • log-only change in crates/services/gas_price_service/src/v1/service.rs
  • no behavior changes to gas price calculation or persistence logic

Ref #1662

This change is operational/logging oriented. The no changelog label seems appropriate if maintainers agree.

@cursor
Copy link
Copy Markdown

cursor bot commented Apr 1, 2026

PR Summary

Low Risk
Log-only changes (message wording/fields) with no changes to gas price calculation, persistence, or control flow.

Overview
Improves observability of the GasPriceServiceV1 update loop by replacing generic/debug-dump logs with structured, field-rich tracing::debug! events.

Logs now include L2 block height/gas price (including explicit genesis/error cases), DA bundle id and L2 range/cost fields when buffering/applying DA costs, and explicit fields for persisted recorded DA height and the computed next gas price when updating the shared algorithm.

Written by Cursor Bugbot for commit 7be5552. This will update automatically on new commits. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant