You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue: Metrics Not Reporting Correctly for Substreams Sink Noop
The substreams_sink_noop_chain_head_block_number metric is consistently returning a value of 0. Additionally, the substreams_sink_noop_backprocessing_completion metric also remains at 0, even when the substreams_sink_noop_head_block_reached metric shows 1, indicating that the head block has been reached. Could you clarify at which point this metric should reflect meaningful values?
Enhancement Request: Labeling for Metrics
To improve observability and ease of dashboard creation, it would be highly beneficial to include a native label, such as app = substreams_sink, across all sink-related metrics (similar to the blockmeta label). This would greatly aid in distinguishing between native substreams and substreams sinks when building dashboards with common metrics. .i.e. head_block_time_drift
The text was updated successfully, but these errors were encountered:
Issue: Metrics Not Reporting Correctly for Substreams Sink Noop
The substreams_sink_noop_chain_head_block_number metric is consistently returning a value of 0. Additionally, the substreams_sink_noop_backprocessing_completion metric also remains at 0, even when the substreams_sink_noop_head_block_reached metric shows 1, indicating that the head block has been reached. Could you clarify at which point this metric should reflect meaningful values?
Enhancement Request: Labeling for Metrics
To improve observability and ease of dashboard creation, it would be highly beneficial to include a native label, such as app = substreams_sink, across all sink-related metrics (similar to the blockmeta label). This would greatly aid in distinguishing between native substreams and substreams sinks when building dashboards with common metrics. .i.e.
head_block_time_drift
The text was updated successfully, but these errors were encountered: