AnalogJ

You shouldn't lose your historical data, scrutiny has a data migration mechanism built-in. You might want to check that the mount path for the config dir is correct (/config vs /opt/scrutiny/config)

Currently there's no way to delete old drives. It's on my to-do list. It's not updating powered on data for your new drives? By default the collector runs once a day, so after 24h you should see a change to that number. If it doesn't can you open an issue on the Github (with logs)? https://github.com/AnalogJ/scrutiny/

Hey, This is AnalogJ, the developer of Scrutiny. I've seen some confusion around the SCRUTINY_API_ENDPOINT. If you're using the "all-in-one" container, which runs both the API and the collector, you do not need to touch that variable. Set it to the default value (http://localhost:8080). Within the container, the API is listening on localhost:8080, even if you bind that port to something else on your host. It's primarily used by users who are deploying scrutiny in a hub/spoke model -- one API server & db with multiple collectors. Hopefully that fixes most of your issues, however if any of you are still running into problems, feel free to open an issue on Github: https://github.com/AnalogJ/scrutiny. I can also be found on the Self-Hosted podcast discord & the LinuxServer.io discord: AnalogJ#3506 If you find Scrutiny useful, and you'd like to support my work, here's a link to my Github Sponsors page: https://github.com/sponsors/AnalogJ Thanks for your interest & support!