chore: rename prometheus registry and metrics for better consistency #373
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.
This will break existing dashboards (of which there are few well defined examples I believe), but it will make building new ones much easier as all metrics will start with
ceramic_one_
now. This also renamedhttp_api_http_api
toceramic_one_http_api_info
andceramic_store_store_query_durations
will now beceramic_one_store_query_durations
, and other store metrics will be underceramic_one_store
.The existing tokio, recon, libp2p, bitswap subregistries are all under ceramic_one now: