I pretend to do stuff with Linux.
I've used Graylog previously. We used limited amounts of the dashboards in Graylog and we mostly created our own in Grafana to display things we needed. The advantage to Graylog over Elastic Stack is RBAC is included out of the box, you don't have to purchase X-Pack or custom build anything to get that functionality.
But I don't believe it works natively with Wazuh like @IRJ mentioned.
From her past posts, I'm assuming it's going to be something aligning with open compute and taking things like how Facebook designed their racks/servers into account.
Like here:
https://twitter.com/jessfraz/status/1106336080956018689?lang=en
I'll have to check my laptop to compare kernels. Mine won't go to sleep. If I shut the lid and open it again it does a hard reboot instead of resuming from sleep.
Or there may be one already for your backup utility. Heres one for Borg written in Bash.
@scottalanmiller said in Centrally Controlled Local Backup System Options:
@jmoore said in Centrally Controlled Local Backup System Options:
@scottalanmiller said in Centrally Controlled Local Backup System Options:
For those wondering why email doesn't cut it.... literally had an unrelated situation where they were using Veeam with email alerts and it didn't alert and no one knew it wasn't backing up for four months! The customer presumably knew that they had removed the backup target and not replaced it or communicated with anyone. But nonetheless, had there been the central console for this local backup job, we would have known instantly.
Reminds me of a couple weeks ago when we had an emergency alert go out on campus. I know this is fairly unrelated but but it does describe a flaw with email. I did not get an email giving me the notice because we were also having email issues at the time. So i walked out of a classroom at 4:00 in the afternoon and there was no staff left on campus but me. So yeah, have to have something else working besides email.
Yeah, the problem with any email based system is you don't know when you don't receive something. Email alerting is based on the "tell me when something is wrong" concept, which is fine to do. But alone is rarely enough. We need a "tell me that everything is okay, all the time" approach. We need to have constant verification that nothing has failed.
That's why I said Prometheus. It should be fairly easy to create an exporter to monitor this.
@dafyre said in Centrally Controlled Local Backup System Options:
The endpoint pricing seems to be ~$10 /user /month.
How does that work with multiple sites? I'm one user backing up 100 sites, so it's just $10 a month?
@scottalanmiller said in Centrally Controlled Local Backup System Options:
@stacksofplates said in Centrally Controlled Local Backup System Options:
I mean an outside the box scenario is you could use Jenkins to schedule all of this. Then just use something like Restic or Borg to do the backups either locally or to a central location.
Then you can have Jenkins send messages/emails on a failure. You'd just need a Jenkins slave at every site (can be whatever you are running the backup on).
Not specifically looking to trigger the backups remotely. Would like them to trigger locally and just report because if the Internet goes down, you don't want things to not keep going.
Salt or Ansible should be able to do this too. And you could script the responses.
I assumed that Jenkins would have the Ansible plugin (or Salt if there is one, not sure) so the slave could do whatever it needed with that tool. You could always deploy script and then just have a Jenkins job to scrape the data.
Probably more of a realistic scenario is to just have the scripts at each site deploy to the location (remote or local) and then have Prometheus monitor that. You could pretty easily have an exporter report any failures on the systemd unit (or whatever service you want).
@Obsolesce said in Centrally Controlled Local Backup System Options:
@stacksofplates said in Centrally Controlled Local Backup System Options:
I mean an outside the box scenario is you could use Jenkins to schedule all of this. Then just use something like Restic or Borg to do the backups either locally or to a central location.
Then you can have Jenkins send messages/emails on a failure. You'd just need a Jenkins slave at every site (can be whatever you are running the backup on).
Hmm, Jenkins running Onprem or remotely from the MSP?
Jenkins master running wherever for the MSP, build boxes on prem at customer sites to actually do the work.
I use Borg for my laptop and it's been running forever. It's just a systemd timer, but you could easily have that script customized for each site and run the exact same job at each site, just the script would determine what happens.