3 ms·
About 7 years ago we brought in the ELK stack for security log ingestion and basic analytics. It took at least three FTEs to maintain the cluster, along with co
by unethical_ban 6y ago
About 7 years ago we brought in the ELK stack for security log ingestion and basic analytics. It took at least three FTEs to maintain the cluster, along with constant issues of queries crashing clusters, or provisioning/building/repairing the dozens of servers and storage units to handle the several terabytes per day of ingest.
To be able to throw that behind an infinite, horizontally scalable mechanism would have saved us a lot of pain and troubleshooting.
- mlyle 6y agoHow much of those 3 FTEs would you have needed anyways, though? that's the point-- to compare apples to apples. Also, dozens of servers is past the point we're talking about, I think. Bare metal and your own infrastructure makes a lot of sense really small (a few servers); and it may start to make sense again at some point really large.
- dijit 6y agoAbout 7 years ago I did the same. 2 engineers, 2,500~ physical machines (6 were elastic search nodes). We were highly effective, sure, but like, it’s not as hard as people seem to claim as long as you’re paying for the datacenter space already.