search

cityindex-attic / logsearch

[unmaintained] A development environment for ELK
Apache License 2.0
24 stars 8 forks source link

Run mini cluster to monitor our own clusters #165

Closed mrdavidlaing closed 10 years ago

mrdavidlaing commented 11 years ago

Quis custodiet ipsos custodes?

There is value in us using a single instance cluster to monitor our other clusters, eating our own dog food and all.

This can be a spot instance, since it doesn't really matter if we loose it.

sopel commented 11 years ago

Unfrozen due to being a) relevant (see https://github.com/cityindex/logsearch-config/issues/32) and b) actively worked upon by @dpb587 during the current milestone already (if I haven't misinterpreted the intent of this deployment and resp. comment):

I've got a logstash-1.2.1 mini-cluster setup at [...]. You can use it like the regular cluster (redis port forwarding for classic logstash client) and port 5043 is opened for lumberjack if you use the included certificate. It's currently using the same security group as the running cluster, so if you're having trouble accessing it, you may need to add your IP there). Let me know if you have any questions. I pasted sample configs for logstash and lumberjack on https://github.com/cityindex/logsearch/issues/184#issuecomment-27606018

sopel commented 11 years ago

Looking closer, this mini cluster appears to be primarily aimed at testing Logstash 1.2.x - anyway, I'll leave it as is for the upcoming hangout, insofar a) applies either way.

sopel commented 10 years ago

:information_source: This topic is meanwhile tracked via https://github.com/cityindex/logsearch-config/issues/39 due to it being more of an internal operational one right now (useful insights will trickle down here anyway in case).