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:
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:
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:
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
