Closed illia-malachyn closed 3 months ago
The recent changes enhance the event ingestion process by integrating a metrics collector, improving tracking and reporting capabilities throughout event processing. Key modifications include updated function signatures to accept the metrics collector, a new method for handling EVM block heights, and enhancements to existing collectors, fostering a more robust system for monitoring events effectively.
File | Change Summary |
---|---|
bootstrap/.../bootstrap.go |
Added collector parameter to Start and startIngestion functions for metrics tracking. |
metrics/.../collector.go |
Introduced EvmBlockHeightUpdated method in Collector interface and DefaultCollector . Added a gauge for EVM block height. |
metrics/.../noop_collector.go |
Added NewNoopCollector constructor and EvmBlockHeightUpdated , ApiErrorOccurred methods. |
services/.../ingestion/engine.go |
Enhanced Engine struct with collector field and updated NewEventIngestionEngine to accept it. Added metrics reporting to processEvents . |
sequenceDiagram
participant Client
participant Engine
participant Collector
Client->>Engine: Start processing events
Engine->>Collector: EvmBlockHeightUpdated()
Collector-->>Engine: Metrics recorded
Engine-->>Client: Event processing complete
In the meadow where rabbits play,
New metrics gather, come what may.
With each event, we hop and bound,
Collecting heights from underground.
A joyful leap with every change,
Our data dance, forever strange! 🐇📊
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
This covers "EVM height should be submitted as a value on event ingestion"
Summary by CodeRabbit
New Features
Bug Fixes
Documentation
Tests