mirror of
https://github.com/XRPLF/rippled.git
synced 2026-09-27 15:28:03 +00:00
178fc58c34
The collector readiness note claimed docker-compose.yml publishes only 4317, 4318 and 8889 and that 13133 comes from a workload stack. It publishes 13133, and that stack is not part of this branch. Probe health_check on 13133 and drop the note; the troubleshooting entry now points at the same check instead of carrying a second, weaker copy. Stop restating BUILD.md. The hardcoded conan and cmake lines had drifted from it, -Dtelemetry=ON is redundant because the Conan toolchain carries it, and the conan-release preset resolves only from the repo root, builds into .build/build/Release rather than .build, and sets no -Dxrpld=ON. Defer to BUILD.md and docs/build/telemetry.md. Test 2's keygen step reused the Devnet config with -a --start, which wrote a genesis chain into the Devnet store, took RPC port 5005 from node 1, and was followed by an rm -rf that also destroyed the mainnet node's store and every log. Give it its own config under the test's temp root, as the script does. The manual path also needs XRPLD_LOG_DIR, or the collector tails the wrong root and Test 3 finds nothing without erroring. Neither the template nor the script set [network_id], so a local cluster stamped xrpl.network.type=mainnet and shared dashboard series with real mainnet data. Set a private id in both, and say which label it produces. Also drop a duplicate metrics_endpoint from the generated config. Split the consensus trigger row: six families fire on a standalone ledger_accept, and the remaining seven need the establish phase, a validator key, or a peer. ledger.validate needs peers too, because checkAccept is unreachable in standalone. Correct the trace-id note to 16 bytes, and name the strategy it depends on. The pathfinding bullet said raw account values reach Grafana Cloud. Both accounts are already tokens when they leave the node; what differs is that the base config hashes them a second time, so one account carries two tokens across configs and traces must not be joined across them. Also: the Loki allow-list is a fixed 18 keys on the pinned image with k8s and cloud enumerated rather than wildcarded, the runbook documents 9 of 15 dashboards, and the spanmetrics block now uses one spelling with a note that the cloud config uses the other.