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.

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

Smart: fetch the values 177, 231 and 233 as normalized instead of raw #472

Merged
merged 1 commit into from
Jun 19, 2023

Conversation

JamesMenetrey
Copy link
Contributor

Dear LibreNMS developers,

After investigating how SMART can be monitored efficiently, I discovered that the values 177 Wear Range Delta, 231 Life Left (SSDs) and 233 Media Wearout Indicator are typically read as normalized numbers rather than interpreting their raw numbers.

While the raw value 177 defines the delta between most-worn and least-worn Flash blocks, describing how good/bad the wear levelling of the SSD works, its normalized value is a number between 100 and 0, where 100 is the best state and 0 the worst. Having this 100-0 range is way easier to set up alert rules, compared to a value where the threshold may be manufacturer dependant.

Regarding values 231 and 233, Wikipedia describes them as normalized values, except in very old disks, in which they are also referenced in other numbers. Normalizing these values will also help set up alert rules, instead of internal manufacturer numbers.

Cheers!

Sources:

@VVelox
Copy link
Collaborator

VVelox commented Jun 19, 2023

Awesome! Looks good, thanks dude!

@VVelox VVelox merged commit 5567606 into librenms:master Jun 19, 2023
3 checks passed
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.

None yet

2 participants