Zabbix + ELK In A Box
-
Anyone has tried working with Zabbix and ELK at the same time before ?
Zabbix+ELK -
I would not want to mix those workloads.
-
@scottalanmiller I have an idea as to why I wouldn't want to put both on the same box.
But why would you not put both on the same box?
-
Well first, I don't mix unrelated workloads ever. Especially not on Linux where there is no licensing reason to do that. Just a bad idea in general.
-
Second those are systems you want monitoring each other and reporting on each other.
Third you want separation of duties around security and monitoring.
Fourth those have very different performance needs and profiles so mixing them makes it hard to tune and identify issues.
-
@scottalanmiller said in Zabbix + ELK In A Box:
Second those are systems you want monitoring each other and reporting on each other.
Third you want separation of duties around security and monitoring.
Fourth those have very different performance needs and profiles so mixing them makes it hard to tune and identify issues.
So... Pretty much, the same thing I was thinking.
-
From the page itself
We haven’t performed any major capacity planning exercises or performance validation exercises to validate the limits of what Zabbix + ELK In A Box can do at the recommended configuration i.e. 2 vCPU’s, 4 GB RAM. However, we would highly recommend that you use limit use of Zabbix + ELK In A Box to a small setup i.e. ~15-20 machines. For larger environments we would highly recommend designing and building your own scalable monitoring and log file analysis solution from scratch to meet your requirements.
Seems more like a quick way to get a PoC environment up before investing in learning how to deploy the applications.
-
@donaldlandru said in Zabbix + ELK In A Box:
From the page itself
We haven’t performed any major capacity planning exercises or performance validation exercises to validate the limits of what Zabbix + ELK In A Box can do at the recommended configuration i.e. 2 vCPU’s, 4 GB RAM. However, we would highly recommend that you use limit use of Zabbix + ELK In A Box to a small setup i.e. ~15-20 machines. For larger environments we would highly recommend designing and building your own scalable monitoring and log file analysis solution from scratch to meet your requirements.
Seems more like a quick way to get a PoC environment up before investing in learning how to deploy the applications.
That would be fine. But still a bad idea in general.
Also that page mentioned Ununtu 14. Just WTF
-
If nothing else, separate them with LXC containers.
-
@jaredbusch said in Zabbix + ELK In A Box:
@donaldlandru said in Zabbix + ELK In A Box:
From the page itself
We haven’t performed any major capacity planning exercises or performance validation exercises to validate the limits of what Zabbix + ELK In A Box can do at the recommended configuration i.e. 2 vCPU’s, 4 GB RAM. However, we would highly recommend that you use limit use of Zabbix + ELK In A Box to a small setup i.e. ~15-20 machines. For larger environments we would highly recommend designing and building your own scalable monitoring and log file analysis solution from scratch to meet your requirements.
Seems more like a quick way to get a PoC environment up before investing in learning how to deploy the applications.
That would be fine. But still a bad idea in general.
Also that page mentioned Ununtu 14. Just WTF
Agreed! Bad designed, and the article is over 2 years old.
