You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docs/get_started/running/docker.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ To start Commit-Boost run:
23
23
docker compose --env-file ".cb.env" -f ".cb.docker-compose.yml" up -d
24
24
```
25
25
26
-
This will run the all the configured services, including PBS, signer and modules (if any).
26
+
This will run all the configured services, including PBS, signer and modules (if any).
27
27
28
28
The MEV-Boost server will be exposed at `pbs.port` from the config, `18550` in our example. You'll need to point your CL/Validator client to this port to be able to source blocks from the builder market.
Commit-Boost can be configured to collect metrics from the different services and expose them to be scraped from Prometheus.
8
8
9
-
Make use to add the `[metrics]` section to your config file:
9
+
Make sure to add the `[metrics]` section to your config file:
10
10
11
11
```toml
12
12
[metrics]
13
-
use_metrics = true
13
+
enabled = true
14
14
```
15
15
If the section is missing, metrics collection will be disabled. If you generated the `docker-compose.yml` file with `commit-boost-cli`, metrics ports will be automatically configured, and a sample `target.json` file will be created. If you're running the binaries directly, you will need to set the correct environment variables, as described in the [previous section](/get_started/running/binary#common).
0 commit comments