For what it is worth, I get escalations due to minerstat overwriting configs. It seems folk don't realize that minerstat snapshots their configuration and re-applies it... I guess that is part of your workflow (control via web)? It is especially concerning when minerstat is installed before the customer has configured their machine completely and snapshots an older config.
-j
efudd, I had a feeling that you have understood how it works quite well when I've explained it to you on the Discord ~2 months ago.
You are correct, minerstat is meant for remote management and so it does save the config on the first sync and then overwrites the config based on user's actions. Everything is managed remotely, this is why it's called remote management after all. Need to get used to it.
Also, it doesn't really matter if minerstat is installed before customer has configured their machine or not, this shouldn't be a concern at all, because they can always change the config on the dashboard, that's not just normal and expected, but it's also the whole point of minerstat - the remote management.
If users decide they will no longer use the software, they can easily uninstall it.
So now you know how it works, please be kind enough and explain it to your users when they will ask you about it next time or feel free to forward them to us. They will get our full attention.