Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SNMP Uptime is not always ignored for spikekills #5355

Closed
netniV opened this issue Jun 8, 2023 · 2 comments
Closed

SNMP Uptime is not always ignored for spikekills #5355

netniV opened this issue Jun 8, 2023 · 2 comments
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team porting required Requires porting to develop resolved A fixed issue
Milestone
v1.2.25

Comments

@netniV
Copy link
Member

netniV commented Jun 8, 2023

Describe the bug

When getting system host statistics, the SMNP host time, the alternate .1.3.6.1.6.3.10.2.1.3.0 is not ignored by SpikeKill and should be consistent with the older uptime 1.3.6.1.2.1.1.3.0
@netniV netniV added bug Undesired behaviour unverified Some days we don't have a clue resolved A fixed issue confirmed Bug is confirm by dev team and removed unverified Some days we don't have a clue labels Jun 8, 2023
@netniV netniV added this to the v1.2.25 milestone Jun 8, 2023
netniV added a commit that referenced this issue Jun 8, 2023
@netniV
SNMP Uptime is not always ignored for spikekills (#5355)
09f0eba 
Closes #5355
@TheWitness
Copy link
Member

Good catch. Same with spine?

@netniV
Copy link
Member Author

netniV commented Jun 8, 2023

Yup had the same on spine, I made some SNMP related changes to availability. They seem to be working for me, and both spine and lib/ping now use the exact same logic for availability check.

@TheWitness TheWitness added the porting required Requires porting to develop label Jun 11, 2023
netniV added a commit that referenced this issue Jun 12, 2023
@netniV
SNMP Uptime is not always ignored for spikekills (#5355)
98bd9c0 
Closes #5355
@github-actions github-actions bot locked and limited conversation to collaborators Sep 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team porting required Requires porting to develop resolved A fixed issue
Projects
None yet
Milestone
v1.2.25
Development

No branches or pull requests
2 participants
@TheWitness @netniV