Hmm. What version of python are you using? I am able to use --logfile or -l interchangeably.
I'm glad you like Curator, and I like KELTIC :) Nice acronym. On Tuesday, August 5, 2014 11:50:06 AM UTC-6, Brian wrote: > > Using the most recent release (1.2.2) of Curator, I noticed that the > documentation says --logfile while curator itself rejects --logfile > anywhere and requires -l in front of the other options to direct its log > entries. No big deal; I just tested it until it worked before adding it to > the cron job. And it is working superbly. > > We will be standing up several ELK instances in various QA data centers to > analyze several independent product load tests. These ELK instances are > also independent, as we do not wish to flood the logstash data across any > of our inter-data-center VPN / router connections. And because they are > independent, our operations folks are leery of manually keeping track of > multiple instances of the ELK stack with which they have no familiarity. > > And so, Elasticsearch Curator is becoming an integral part of the > automation of the ELK stack for us, as it helps to keep our hard-working > operations folks from overload. We wish for ELK to be an asset and not an > added drain on time and effort, and Curator is a vital part of that goal. > To the point where I no longer think of it as simply the ELK stack, but > rather the KELTIC stack: > > *Kibana, Elasticsearch, Logstash, Time-based Indices, Curator*. > > But whether ELK or KELTIC, the stack is awesome! Many thanks to all who > contributed and who continue to drive it forward! > > Brian > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c806e490-b533-4b6d-a629-da2a1d031d7f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
