Support weekly indices about curator

[divanikus]

It would be nice to have custom date format. I'm using an app creating indexes with dd-mm-YYYY format, which makes curator completely useless in my case.

[jordansissel]

We could reuse the same syntax from either logstash or from kibana:

• logstash: some text here %{+TIME FORMAT HERE} ...
• kibana: [some text here ]TIME FORMAT HERE

[jordansissel]

@divanikus You could make curator useful to you by patching it to support your use case, btw. :)

[divanikus]

@jordansissel Yeah, I know, and thats rather simple. But I prefer to have support of such things in "upstream" :)

[untergeek]

We do accept pull requests...

[divanikus]

It's simple to hack it for my case, but not that simple to make more generic option...

[untergeek]

@honzakral and I will be getting together at our company meetup next week to discuss the future of Curator. We will consider this becoming part of Curator 2.0.

[divanikus]

Actually, it would be nice to have a generic cli tool for es, to be able to interact with it with unix shell comfortably. I mean something like

es indices | grep -05- | xargs es close

Currently there is no such tool, most of present ones are just for one thing only, like es2unix or curator.

[untergeek]

Generic CLI tools don't deal with timeouts and things very well, unfortunately. Elasticsearch can be local, or it might be across the datacenter, or somewhere else in AWS.

[divanikus]

You can always make --host & --port options...

[jordansissel]

You can achieve 'es indices | ... ' with the _cat api and xargs and curl. Grep will never understand time, so it's not a fit for what curator focuses on today (time-oriented indices)

% curl -s localhost:9200/_cat/indices | fex 2 | grep logstash- | xargs -n1 sh -c 'curl -XPOST localhost:9200/$1/_close' -
{"acknowledged":true}

Or really, your specific case, you don't need grep.

% curl -s localhost:9200/*-05-*/_close

[divanikus]

Yes, but typing so much curl is pain.