Skip to content

docs(mesa): node status reporting is off by default on the Mesa release - #1217

Merged
dkijania merged 1 commit into
mainfrom
dkijania/mesa-node-status-off-by-default
Aug 13, 2026
Merged

docs(mesa): node status reporting is off by default on the Mesa release#1217
dkijania merged 1 commit into
mainfrom
dkijania/mesa-node-status-off-by-default

Conversation

@dkijania

Copy link
Copy Markdown
Member

Two Mesa pages state that the Node Status reporting service is enabled by default on the Mesa daemon. It is not. On release/mesa the service starts only when the operator gives --node-status-url, which defaults to None:

(* src/lib/mina_lib/mina_lib.ml *)
match t.config.node_status_url with
| Some node_status_url -> (* start the service *)
| None -> ()

An operator who reads the current text will believe their Mesa node is reporting when it is silent, and will pass a flag that does not do what the page says.

What is corrected

1. Default. Reporting is off by default on the Mesa release. --node-status-url is both the collector address and the on/off control.

2. --disable-node-status is a different feature. The pages present it as the way to opt out of telemetry. It is not: it controls whether your node answers node-status queries from other peers, and its own help text says so — "Disable reporting node status to other nodes (default: enabled)". Passing it does not stop a single report from being sent to a collector. The correction is called out in an admonition, because anyone who set it believing they had opted out is still reporting if they also set --node-status-url.

3. --simplified-node-stats takes a value. The page documents it as (no value). It is declared optional_with_default true bool, so it takes true or false and defaults to true. It selects the size of the report, never whether one is sent — setting false sends more data, which is the opposite of what the flag name suggests.

4. --node-stats-type. The old note said this argument "was never accepted by the daemon" and named --disable-node-status as the real opt-out. The first half is right for Mesa; the second is not. Reworded.

Files

  • docs/network-upgrades/mesa/upgrade-steps/post-upgrade.mdx — the Help Monitor the Network section
  • docs/network-upgrades/mesa/glossary.mdx — the Node Status Service entry
  • static/llms-full.txt — regenerated, as check-llms-txt requires

Not touched

upgrade-steps/index.mdx still says the simplified Node Status service is enabled by default in the pre-upgrade stop-slot release. That statement is about the pre-fork build, not Mesa, and is out of scope here.

Testing

npm run check-llms-txt exits 0. npx docusaurus build succeeds; the only broken-anchor warnings are pre-existing ones on the Mesa index page pointing into the glossary, which this PR does not touch.

🤖 Generated with Claude Code

@vercel

vercel Bot commented Aug 12, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs2 Ready Ready Preview Aug 12, 2026 9:26pm

Request Review

@dkijania
dkijania merged commit 4853ea3 into main Aug 13, 2026
4 checks passed
@dkijania
dkijania deleted the dkijania/mesa-node-status-off-by-default branch August 13, 2026 12:51
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.

2 participants