feature/BCF-2604-metrics: instrumenting prometheus metrics #49
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.
Instruments default go prometheus metrics.
Note: And bumps go to 1.20.0
go 1.17.0 is required for the /x/sys library. I bumped to 1.20.0 to match the go version of
/smartcontractkit/chainlink
Library consumers can obtain metrics by running the new
ServeMetrics
API exposed byServer
. LikeServe
,ServeMetrics
is blocking and the resources associated with the metrics server are closed by the done signal.The default endpoint for the metrics is
:2112/metrics
, though the port can be configured by the consumer.To test, checkout
examples/simple/server
and rungo run .
in one terminal. In a separate terminal runcurl http://localhost:2112/metrics
. The beginning of the output should look like the following: