refactor(engine-timings): updates #362
Merged
Conversation
This file contains hidden or 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
Member
mattevans
commented
Dec 19, 2025
mattevans
commented
- Replace hard-coded 1h/3h/6h buttons with TIME_RANGE_CONFIG map
- Add 24h and 7d ranges, drop 3h to keep UI compact
- Introduce hourly aggregated endpoints for newPayload & getBlobs
- Show per-slot charts only for 1h/6h; switch to hourly trends for 24h/7d
- Add P50/P95 toggle and success/valid-rate trend charts for long ranges
- ClientVersionBreakdown now accepts hourlyData to display true percentiles
- add new hourly endpoints for engine blobs & new-payload by EL client - introduce daily/hourly granular storage slot state & expiry services - replace 6-month-only expiry/reactivation services with 1/6/12/18/24m variants - remove obsolete daily/hourly status and monthly/weekly state size services - switch client baseUrl to localhost:8091 for local development feat(sdk.gen.ts): regenerate client to expose new hourly endpoints feat(sdk.gen.ts): add 1m/6m/12m/18m/24m expiry & reactivation endpoints feat(sdk.gen.ts): add daily/hourly storage slot state endpoints feat(sdk.gen.ts): add hourly engine blobs & new-payload endpoints refactor(sdk.gen.ts): remove obsolete daily/hourly status & weekly/monthly state size endpoints feat(types.gen.ts): add hourly aggregation types for engine_getBlobs and engine_newPayload feat(types.gen.ts): introduce storage slot state with configurable expiry policies feat(types.gen.ts): add daily and hourly storage slot state types feat(types.gen.ts): generate new response and service types for added entities refactor(types.gen.ts): remove daily/hourly status and monthly/weekly state size types feat(api): regenerate types to expose new fct_engine_get_blobs_by_slot endpoints refactor(api): replace per-status count fields with richer metrics in duration schema docs(api): update descriptions to reflect slot/block/status granularity feat(api): regenerate types to expose new fct_engine_new_payload_by_slot endpoint refactor(api): replace observation & status counts with block-level fields feat(api): add block_root, block_number, proposer_index, gas metrics feat(api): introduce unique_node_count and client implementation counts feat(api): expose p95 & p99 duration percentiles in payload endpoints feat(api): regenerate types to replace state-size endpoints with MEV & node-activity APIs feat(api): regenerate types to expose new node & storage slot endpoints refactor(api): replace mev-bid types with fct_node_active_last_24h & fct_storage_slot_state* filters docs(api): update comments to describe node & storage slot filters feat(api): regenerate types to expose new storage-slot-state endpoints Replace legacy fct_prepared_block and fct_storage_slot_state services with granular hourly/daily/6-month expiry variants. Adds dedicated filter fields for active_slots, effective_bytes, net deltas and cumulative metrics, enabling precise time-bucketed analytics. feat(api): regenerate types.gen.ts with new filter fields for custody, execution and storage APIs feat(types.gen.ts): replace custody probe types with new storage slot lifecycle types feat(types.gen.ts): add expiry, next-touch, and reactivation services for 1-24 month windows feat(types.gen.ts): introduce effective_bytes and touch_block filters across new endpoints feat(api): regenerate zod schemas to reflect new hourly & daily tables refactor(api): drop daily/weekly/monthly state-size & status tables feat(api): add expiry-policy variants (1m-24m) for storage slot models feat(api): introduce hourly aggregates for engine blobs & new-payload chore(api): remove obsolete response types and list/get services feat(api): regenerate zod schemas to align with new API surface - replace monthly/weekly execution-state-size schemas with head-first-seen - add daily/hourly variants for storage-slot-state and storage-slot-with-expiry - introduce new expiry and reactivation periods (1m,6m,12m,18m,24m) - add next-touch, diff-by-address-slot and execution-block-by-date schemas feat(timings): extend time range options to 24h and 7d with hourly aggregation - Replace hard-coded 1h/3h/6h buttons with TIME_RANGE_CONFIG map - Add 24h and 7d ranges, drop 3h to keep UI compact - Introduce hourly aggregated endpoints for newPayload & getBlobs - Show per-slot charts only for 1h/6h; switch to hourly trends for 24h/7d - Add P50/P95 toggle and success/valid-rate trend charts for long ranges - ClientVersionBreakdown now accepts hourlyData to display true percentiles
samcm
approved these changes
Dec 19, 2025
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.