Monitoring SpiderOak
We need to implement some monitoring of SpiderOak to make sure that it runs without failure, or we get notified. This is not that straight forward:
- when SpiderOak runs in headless mode, the client can not be launched to do any other action like e.g. getting a list of selected directories
- the log files are accessible only to the user running the SpiderOak service, so other tools like NetData or FluentD can not easily access them
- calling the SpiderOak API from a different host is not simple because before calling into the data of a specific account you need to download the full database for that account which is often many GB in size and takes quite some time to update before being able to query it
I have asked SpiderOak support for some best practice guidance.