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
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Prometheus metrics are currently being prefixed with polkadot_, substrate_ or differently depending on the chain name. This makes dashboards based on these metrics unnecessarily restricted to a certain chain even though the metrics represent the same kind of information e.g. polkadot_block_height vs substrate_block_height. creating graphs and alerts for both kinds of chains would require writing queries like {__name__=~"(polkadot|substrate)_block_height"}. This can be avoided using a chain label indicating the network the client is operating in and for compatibiltiy reasons allow only the polkadot_ prefix to remain.
Changing this will make dashboards and existing alerts more universally usable and removes the ambiguity where these metrics belong to resp originate from.
Prometheus metrics are currently being prefixed with
polkadot_
,substrate_
or differently depending on the chain name. This makes dashboards based on these metrics unnecessarily restricted to a certain chain even though the metrics represent the same kind of information e.g.polkadot_block_height
vssubstrate_block_height
. creating graphs and alerts for both kinds of chains would require writing queries like{__name__=~"(polkadot|substrate)_block_height"}
. This can be avoided using achain
label indicating the network the client is operating in and for compatibiltiy reasons allow only thepolkadot_
prefix to remain.Changing this will make dashboards and existing alerts more universally usable and removes the ambiguity where these metrics belong to resp originate from.
Such a
chain
label could be directly added to the constructor: https://docs.rs/prometheus/0.12.0/prometheus/struct.Registry.html#method.new_customsee also https://github.com/paritytech/devops/issues/1013
The text was updated successfully, but these errors were encountered: