Skip to content
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

Metrics Issues #4

Open
kw1knode opened this issue Oct 17, 2024 · 0 comments
Open

Metrics Issues #4

kw1knode opened this issue Oct 17, 2024 · 0 comments

Comments

@kw1knode
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant