add Prometheus bridge to otel

[jmank88]

https://smartcontract-it.atlassian.net/browse/CRE-4426

This PR adds a Prometheus bridge to forward metrics through otel. It is disabled by default, but can be enabled in whole or for a subset of prefixes via TOML config:

# The Prometheus bridge automatically forwards metrics through open telemetry.
[Telemetry.PrometheusBridge]
# **ADVANCED**
# Enabled enables the Promtheus bridge.
Enabled = false # Default
# Prefixes is a set of filters to restrict which prometheus metrics are forwarded based on prefix matching.
# By default, we only forward the go runtime metrics. Empty means forward everything.
Prefixes = ["go_"] # Default

Requires:

• pkg/beholder: bridge prometheus metrics through otel chainlink-common#2053
• move package promutil out of sqlutil chainlink-common#2084

[github-actions]

✅ No conflicts with other open PRs targeting develop

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

[github-actions]

I see you added a changeset file but it does not contain a tag. Please edit the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[jmank88]

We could also configure a list of labels/attributes to augment, but IIRC we will already be picking many up from beholder that will allow us to differentiate them when necessary.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube