Skip to content

fix(bootstrap): Enable bootstrap metrics listener#1579

Draft
rkuris wants to merge 1 commit intomainfrom
rkuris/enable-bootstrap-metrics
Draft

fix(bootstrap): Enable bootstrap metrics listener#1579
rkuris wants to merge 1 commit intomainfrom
rkuris/enable-bootstrap-metrics

Conversation

@rkuris
Copy link
Member

@rkuris rkuris commented Dec 22, 2025

Due to a change in avalanchego, we're no longer collecting metrics locally when running the bootstrapping tests. This was super convenient before, and adding new metrics and changing dashboards is much harder without this test grafana environment working.

This appears to be the result of several separate problems:

  1. Avalanchego doesn't enable a prometheus listener on port 6060, most likely due to the changes in feat(reexecute/c): explicit metrics port avalanchego#4418.
  2. Firewood is no longer opened with a prometheus listener on port 3000.
  3. Firewood does not enable the metrics server when opening the database, unless expensive metrics are enabled.

I think we don't want firewood listening directly, so I'm not fixing #2. However, prometheus should still attempt to listen on port 3000 for the other benchmark tests, so I'm leaving the prometheus listener running on that port for launched instances.

Issue #3 is a problem in avalanchego. We probably should not consider all metrics expensive though, so we should initialize the metrics server regardless of this setting. This is a separate avalanchego bug that should be fixed as part of #1524

Why this should be merged

How this works

How this was tested

Due to a change in avalanchego, we're no longer collecting metrics
locally when running the bootstrapping tests. This was super convenient
before, and adding new metrics and changing dashboards is much harder
without this test grafana environment working.

This appears to be the result of several separate problems:

 1. Avalanchego doesn't enable a prometheus listener on port 6060, most
    likely due to the changes in ava-labs/avalanchego#4418.
 2. Firewood is no longer opened with a prometheus listener on port
    3000.
 3. Firewood does not enable the metrics server when opening the
    database, unless expensive metrics are enabled.

I think we don't want firewood listening directly, so I'm not fixing #2.
However, prometheus should still attempt to listen on port 3000 for the
other benchmark tests, so I'm leaving the prometheus listener running on
that port for launched instances.

Issue #3 is a problem in avalanchego. We probably should not consider
all metrics expensive though, so we should initialize the metrics server
regardless of this setting. This is a separate avalanchego bug that
should be fixed as part of #1524
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant