Some observations with Curator

Elastic Stack Elasticsearch
1

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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/39d8300d-27fc-42da-b10b-3bb8280573d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

I am still fully in the nothing but E stack! Is anyone else using
Elasticsearch for ... search? :slight_smile:

--
Ivan

On Tue, Aug 5, 2014 at 10:50 AM, Brian brian.from.fl@gmail.com 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+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/39d8300d-27fc-42da-b10b-3bb8280573d4%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/39d8300d-27fc-42da-b10b-3bb8280573d4%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQAd_07%3DkKv2EndY_uyfm%2B7CVwLR3mBXgWgv5E%2B6GR-bSA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

3

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 :slight_smile: 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+unsubscribe@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.

4

Aaron,

Well, now I feel a little foolish. Perhaps it was from my initial attempt
to put --logfile at the end of the command instead of before the action:

$ curator delete --older-than 8 --logfile /tmp/curator.log
usage: curator [-h] [-v] [--host HOST] [--url_prefix URL_PREFIX] [--port
PORT]
[--ssl] [--auth AUTH] [-t TIMEOUT] [--master-only] [-n] [-D]
[--loglevel LOG_LEVEL] [-l LOG_FILE] [--logformat LOGFORMAT]
{show,allocation,alias,snapshot,close,bloom,optimize,delete}
...
curator: error: unrecognized arguments: --logfile /tmp/curator.log

So I changed it to -l before I moved it, based on the error message above.
But you're correct: It does accept both forms of the option:

For testing: Works fine and stores the log in /tmp/curator.log

$ curator --logfile /tmp/curator.log delete --older-than 8

Older CentOS server; it's 2.7.5 on my MacBook (Mavericks) and

HP laptop (Ubuntu 14.04 LTS):

$ python --version
Python 2.6.6

Latest released version:

$ curator --version
curator 1.2.2

Brian

On Tuesday, August 5, 2014 8:18:24 PM UTC-4, Aaron Mildenstein wrote:

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 :slight_smile: Nice acronym.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/764826ca-3da6-419e-807a-f940cd86a8a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.