Scrutiny
Monitor hard drive health with a web UI. Track historical S.M.A.R.T. data, use real-world failure thresholds, and receive timely notifications to prevent data loss.
Standard command-line S.M.A.R.T. monitoring often falls short. It typically lacks historical data, making it difficult to spot slow degradation, and relies on manufacturer thresholds that may not accurately predict drive failure. This tool provides a web-based dashboard to give you a clear view of your hard drive health.
It enhances standard monitoring by merging manufacturer S.M.A.R.T. metrics with real-world failure rate data, offering more reliable insights into drive longevity. By tracking metrics over time, you can identify trends and proactively replace drives before they fail and cause data loss. The system is designed for easy deployment and use, especially for servers with multiple drives.
Key features include:
- A focused Web UI Dashboard for at-a-glance health checks.
- Historical S.M.A.R.T. metric tracking to identify degrading drives.
- Auto-detection of all connected hard drives for simple setup.
- Configurable notifications via Webhooks, Email, Slack, Discord, and more.
- Simple deployment using an all-in-one Docker image.
Directory Structure
scrutiny
config
influxdb
.env
docker-compose.yml
docker-compose.yml
services:
scrutiny:
image: ghcr.io/analogj/scrutiny:master-omnibus
container_name: scrutiny
cap_add:
- SYS_RAWIO
- SYS_ADMIN
ports:
- "8080:8080"
- "8086:8086"
volumes:
- /run/udev:/run/udev:ro
- ./config:/opt/scrutiny/config
- ./influxdb:/opt/scrutiny/influxdb
devices:
- /dev/sda:/dev/sda
- /dev/sdb:/dev/sdb
restart: unless-stopped.env
# Scrutiny Omnibus does not require sensitive environment variables by default.
# Advanced configuration is handled via the scrutiny.yaml file in the config directory.Categories:
Tags:
Ad
Similar to Scrutiny