*woosh* (C)
On Fri, May 22, 2015 at 9:54 AM, Adam Armstrong adama@memetic.org wrote:
Try 150,000 ports, then VM overheads will make you cry :)
adam.
Sent from Mailbird http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird
On 22/05/2015 14:49:11, Simon Smith simonsmith5521@gmail.com wrote: I run our observium on Proxmox OpenVZ container!
2GB ram, 2 cores, 20GB HDD
never uses more than 1.5Gb ram and 22% cpu
thats monitoring 50 devices and 600 ports, and even using syslog integrated with observium too
works brilliant too when i need to do hardware maintaince, i just migrate the container to another server and it just carrys on :)
Simon
On 22 May 2015, at 2:43 pm, Adam Armstrong adama@memetic.org wrote:
Or that, but virtualization is not a great solution for a heavily loaded observium installation.
Adam.
Sent with AquaMail for Android http://www.aqua-mail.com
On 22 May 2015 14:36:25 Dan Yasny dyasny@gmail.com wrote:
Why work so hard? Anything can be made HA when put into VMs. My monitoring server is a VM, if the hardware it's on dies, it simply gets started elsewhere
On Fri, May 22, 2015 at 9:27 AM, Adam Armstrong adama@memetic.org wrote:
Quis custodiet ipsos custodes?
You seem to be trying terribly hard to vastly overcomplicate your deployment.
You can certainly run two installations (though that would require two licenses), but they won't communicate in any way, since we don't have any form of replication.
I'd be inclined to just rsync RRDs and copy the database and config periodically to a second server, so you can switch over to a second system if the first one explodes. You'll lose data between the most recent backup and the system failure, but you'll gain not having to spend the £20,000 we'd be charging if we supported full active/active replication.
I don't consider metric collection and monitoring to be a business critical service, so doesn't really require replication and failover. Even losing a few hours of billing data isn't really an issue.
Just have a decent backup/restore procedure and you that's sufficient.
It's also true that a decent backup policy is far safer than relying on active replication, since a software or configuration issue will destroy both of your instances. Just ask people who've run VSS!
adam.
On 2015-05-22 14:17, Farshid Abediny wrote:
We want install on 2 node that when our first node goes down the second node can monitor for example node 1 connection lost
On Friday, May 22, 2015, Adam Armstrong adama@memetic.org wrote:
No. And since it only takes 15 minutes to install a new system,
we're not convinced that the massive increase in complexity (and network load) would be a good idea.
Observium is literally config.php, a MySQL database and a directory of RRDs. Complex stuff isn't really needed, nor particularly helpful.
Just make periodic backups and make sure you know how to restore the MySQL database and RRD directory on failure.
adam.
Sent from Mailbird [2]
On 22/05/2015 14:11:52, Farshid Abediny farshidabediny@gmail.com
wrote:hi I want know can we install observium on 2 server and if one server fail then use our second server for monitoring is it possible? Thanks _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [1]
Links:
[1] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [2]
http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm...
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium