Replace opentelemetry by tikv/rust-prometheus

[eval-exec]

What problem does this PR solve?

Issue Number: close #3866

Problem Summary:

This PR want to drop opentelemetry and replace it by rust-prometheus on util/metrics

What is changed and how it works?

What's Changed:

Related changes

• Drop opentelemetry, and replace it by rust-prometheus

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code ci-runs-only: [ quick_checks,linters ]

Side effects

• None

Release note

Title Only: Include only the PR title in the release note.

[doitian]

We may add reason as a label, but let's defer it until we really need this.

[eval-exec]

I think we can expose reason to Prometheus, but it's preferable for reason to be an enumerated value known at compile time. This way, reason won't occupy too much memory space.

[doitian]

It's easy to break, for example, if someone formats a message and adds the peer id into it.

[eval-exec]

In current code base, metrics are always collected, but these metrics won't be exposed unless we specific [metrics.exporter.prometheus] in ckb.toml config file.

We don't have a way to disable to collect metrics.

@doitian Do we need to add a [feature] enable_metrics for CKB to control whether to collect metrics on these points?

[doitian]

In current code base, metrics are always collected, but these metrics won't be exposed unless we specific [metrics.exporter.prometheus] in ckb.toml config file.

We don't have a way to disable to collect metrics.

@doitian Do we need to add a [feature] enable_metrics for CKB to control whether to collect metrics on these points?

We can use a macro wrapper to turn the code like

ckb_metrics::CKB_NETWORK_BAN_PEER.inc();

into

if (metrics_enabled!()) {
    ckb_metrics::CKB_NETWORK_BAN_PEER.inc();
}

[eval-exec]

We can use a macro wrapper to turn the code like

Agreed, I will go ahead and implement it.

[eval-exec]

In the current implementation, the values of "labels" exposed in ckb_message_bytes are difficult to understand as they are represented by numbers. like:

ckb_message_bytes{direction="out",item_id="6",protocol="101",status="101"} 62
ckb_message_bytes{direction="out",item_id="7",protocol="101",status="101"} 11390

After communicating with @gpBlockchain, I should update the "labels" field with meaningful values, like:

ckb_message_bytes{direction="out",item_id="GetBlockProposal",protocol="RelayV2",status="Ignored"} 62
ckb_message_bytes{direction="out",item_id="BlockProposal",protocol="RelayV2",status="Ignored"} 11390

Cc. @doitian

[eval-exec]

Considering use Histogram type to record ckb_message_bytes.
https://prometheus.io/docs/practices/histograms/#quantiles