feat(metrics): Monitor and publish metrics to Prometheus.

[arijitAD]

Changes

• Monitor and publish metrics to Prometheus.

Tests

make gossamer
 ./bin/gossamer init --config chain/gssmr/config.toml --basepath ~/.gossamer_alice --genesis-raw genesis-raw.json --force
 ./bin/gossamer --port 7000 --config chain/gssmr/config.toml --key alice --basepath ~/.gossamer_alice --rpcport 8540 --rpc --publish-metrics --metrics-port 9871
curl http://127.0.0.1:9871/metrics

Checklist

• I have read CODE_OF_CONDUCT and CONTRIBUTING
• I have provided as much information as possible and necessary
• I have reviewed my own pull request before requesting a review
• All integration tests and required coverage checks are passing

Issues

• Related to Add Prometheus and Grafana for metric tracking/monitoring #1398

[RyRy79261]

When running the Init command I receive this error

[noot]

@RyRy79261 you can omit the --genesis-raw gen-raw.json, it should automatically find the genesis file

[noot]

great work, it works for me!

INFO[03-05|09:49:28] Enabling stand-alone metrics HTTP endpoint address=127.0.0.1:7012 caller=node.go:297
INFO[03-05|09:49:28] Starting metrics server                  addr=http://127.0.0.1:7012/metrics caller=node.go:308

$ curl http://127.0.0.1:7012/metrics
# TYPE network_node_latency gauge
network_node_latency 0

# TYPE network_node_peerCount gauge
network_node_peerCount 0

# TYPE network_node_totalConnection gauge
network_node_totalConnection 0

# TYPE service_blocks_sync gauge
service_blocks_sync 0

# TYPE system_cpu_goroutines gauge
system_cpu_goroutines 82

# TYPE system_cpu_procload gauge
system_cpu_procload 125

# TYPE system_cpu_sysload gauge
system_cpu_sysload 201

# TYPE system_cpu_syswait gauge
system_cpu_syswait 0

# TYPE system_memory_allocs gauge
system_memory_allocs 241501003

# TYPE system_memory_frees gauge
system_memory_frees 238847505

# TYPE system_memory_held gauge
system_memory_held 467861504

# TYPE system_memory_pauses gauge
system_memory_pauses 8204387

# TYPE system_memory_used gauge
system_memory_used 371083400

could you add a --metrics-port flag that specifies what port the prometheus server should run on?

[arijitAD]

great work, it works for me!

INFO[03-05|09:49:28] Enabling stand-alone metrics HTTP endpoint address=127.0.0.1:7012 caller=node.go:297
INFO[03-05|09:49:28] Starting metrics server                  addr=http://127.0.0.1:7012/metrics caller=node.go:308

$ curl http://127.0.0.1:7012/metrics
# TYPE network_node_latency gauge
network_node_latency 0

# TYPE network_node_peerCount gauge
network_node_peerCount 0

# TYPE network_node_totalConnection gauge
network_node_totalConnection 0

# TYPE service_blocks_sync gauge
service_blocks_sync 0

# TYPE system_cpu_goroutines gauge
system_cpu_goroutines 82

# TYPE system_cpu_procload gauge
system_cpu_procload 125

# TYPE system_cpu_sysload gauge
system_cpu_sysload 201

# TYPE system_cpu_syswait gauge
system_cpu_syswait 0

# TYPE system_memory_allocs gauge
system_memory_allocs 241501003

# TYPE system_memory_frees gauge
system_memory_frees 238847505

# TYPE system_memory_held gauge
system_memory_held 467861504

# TYPE system_memory_pauses gauge
system_memory_pauses 8204387

# TYPE system_memory_used gauge
system_memory_used 371083400

could you add a --metrics-port flag that specifies what port the prometheus server should run on?

Updated with metrics port flag.

[noot]

maybe I missed it but I don't see this being set anywhere? eg in dot/services.go createNetworkService?

[arijitAD]

Thanks for pointing it. I missed it while refactoring the metrics package.

[noot]

looks good! please double check that network config PublishMetrics is being set