docs: stop claiming neo has never answered SNMP - #24
Merged
Conversation
It has. #23 wrote "never answered an SNMP poll at all" into four files on the strength of max_over_time(up{instance="10.7.7.2"}[30d]) == 0. That measured Prometheus retention, not the device: all four SNMP series carry ~23,127 samples and begin together when the current stack was built, so the TSDB holds no SNMP data from before that point and the window cannot speak to it. The switch last polled successfully in November 2025, under a hand-tuned minimal module. What is true is narrower and still enough to keep #9 open: neo is not answering now, and has not for the whole span of available data. Also records the sharper reading of the ICMP/TCP-pass, UDP-fail split — that is what a wedged SNMP agent looks like, not a dead device. Refs #9, #22 Co-Authored-By: Claude Opus 5 <[email protected]>
Gerrrt
added a commit
that referenced
this pull request
Aug 19, 2026
docs: stop claiming neo has never answered SNMP
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
1 participant
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.
Corrects an overstatement introduced in #23.
What changed
#23 asserted
neo"has never answered an SNMP poll at all" inSECURITY.md,docs/security.md,docs/roadmap.mdandREADME.md. The evidence behind itwas
max_over_time(up{job="snmp",instance="10.7.7.2"}[30d]) == 0.That measured retention, not the device. All four SNMP targets carry ~23,127
samples and their series begin together — the TSDB has no SNMP data from before
the current stack was built, so a zero across the window says nothing about
what the switch did earlier. It in fact last polled successfully in November
2025, under a hand-tuned minimal module.
The corrected claim is narrower and still supports keeping #9 open: neo is not
answering now, and has not for the entire span of available data. Whether it
still accepts the leaked community remains unknown.
Blast radius
None — documentation only.
secrets/*.sops.yamlVerification
./scripts/validate.sh— all checks pass.markdownlint-cli2via npx, 0 issues.make validatepassesRefs #9, #22