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: packages/dashmate/docs/config/core.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,15 +73,15 @@ The `core.zmq` section configures the ZeroMQ notification interface, which provi
73
73
74
74
| Option | Description | Default | Example |
75
75
|--------|-------------|---------|---------|
76
-
|`core.zmq.port`| Port for ZMQ notifications |`29998`|`30998`|
76
+
|`core.zmq.port`| Port for ZMQ notifications |`29998`(mainnet),`39998` (testnet), `49998` (local) |`30998`|
77
77
|`core.zmq.host`| Host binding for Docker port mapping |`127.0.0.1`|`0.0.0.0`|
78
78
79
79
ZMQ settings control real-time blockchain event notifications:
80
80
- ZMQ provides low-latency notifications for blocks, transactions, and other blockchain events
81
81
-**host**: Controls Docker port exposure:
82
82
-`127.0.0.1`: ZMQ port exposed only on localhost (local machine access)
83
83
-`0.0.0.0`: ZMQ port exposed on all interfaces (public internet access - use with caution)
84
-
-**port**: The port number for ZMQ notifications
84
+
-**port**: The port number for ZMQ notifications. Dashmate offsets the default to prevent clashes between environments (`29998` mainnet, `39998` testnet, `49998` local presets).
85
85
- DAPI uses ZMQ to receive real-time blockchain data for streaming to clients
86
86
- ZMQ notifications include raw transactions, blocks, instantlocks, and chainlocks
87
87
- ZMQ is always enabled in Dash Core as it's used by internal components
Copy file name to clipboardExpand all lines: packages/dashmate/docs/config/dapi.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,10 +53,12 @@ This timeout setting controls how long DAPI will wait for state transition resul
53
53
| Option | Description | Default | Example |
54
54
|--------|-------------|---------|---------|
55
55
|`platform.dapi.rsDapi.metrics.host`| Host interface exposed on the Docker host |`127.0.0.1`|`0.0.0.0`|
56
-
|`platform.dapi.rsDapi.metrics.port`| Host port for both health checks and Prometheus metrics |`9091`|`9191`|
56
+
|`platform.dapi.rsDapi.metrics.port`| Host port for both health checks and Prometheus metrics |`9091`(mainnet), `19091` (testnet), `29091` (local) |`9191`|
57
57
58
58
The rs-dapi metrics server exposes `/health` and `/metrics`. Prometheus-compatible metrics are served from `/metrics` on the configured port, allowing separate node instances on the same machine to use distinct ports. The `/health` endpoint aggregates dependency checks (Drive, Tenderdash, Core) and returns `503` when any upstream component is unhealthy.
59
59
60
+
Dashmate offsets the default metrics port per preset (mainnet 9091, testnet 19091, local 29091) to avoid clashes when running multiple environments concurrently.
The rs-dapi metrics server exposes health endpoints alongside Prometheus data on `/metrics` from the same port.
159
+
The rs-dapi metrics server exposes health endpoints alongside Prometheus data on `/metrics` from the same port. Dashmate applies network-specific defaults (mainnet 9091, testnet 19091, local 29091) so multiple presets can coexist on a host without conflicts.
0 commit comments