docs(mesa): node status reporting is off by default on the Mesa release - #1217
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
yamimaio
approved these changes
Aug 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two Mesa pages state that the Node Status reporting service is enabled by default on the Mesa daemon. It is not. On
release/mesathe service starts only when the operator gives--node-status-url, which defaults toNone: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-urlis both the collector address and the on/off control.2.
--disable-node-statusis 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-statstakes a value. The page documents it as(no value). It is declaredoptional_with_default true bool, so it takestrueorfalseand defaults totrue. It selects the size of the report, never whether one is sent — settingfalsesends 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-statusas 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 sectiondocs/network-upgrades/mesa/glossary.mdx— the Node Status Service entrystatic/llms-full.txt— regenerated, ascheck-llms-txtrequiresNot touched
upgrade-steps/index.mdxstill 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-txtexits 0.npx docusaurus buildsucceeds; 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