Skip to content
Gary Gao edited this page Apr 23, 2016 · 16 revisions

Todos we will do in the future

  • code docs

  • Rest API

  • Web UI

  • Solve Performance Problems

    • big overhead when creating hundreds of indices at one time
  • make everything easy to use and more intelligent !!

    • integrate sense UI, a very powerful elasticsearch query UI

    • support elasticsearch from 1.5 ~ 5.0 (especially for elasticsearch-py)

    • manage(create, close, delete ...) index in Web UI on demand.

    • easy to setup, support different version of OS and Python

    • do not rely on redis

    • If well

    • auto detect unmanaged indices with ignoring list and present in webui, alert.

  • monitoring and alerting

*    no data

*    data indexing trends ( maybe we can using machine learning algorithms) 
  • Aggregator

Aggregate elasticsearch index data by daily/week/month with different requirements.

  • Index Management
*    create

    *    settings, mappings generator

    *    follow mappings

*    snapshot

*    alias

*    currently we support index level(Alias, Close, Create, Delete, Optimize, Snapshot) management, possibly we will support shard level management :Allocation(use case: hot/cold data), replicas

*    if task fails, it will recover and eventally succeed.

*    Do we need to support fixed name index such as .kibana
  • timezone and locale

https://docs.djangoproject.com/en/1.9/topics/i18n/timezones/

  • Have a look at these

https://www.elastic.co/guide/en/elasticsearch/guide/current/index-management.html

http://www.elastichq.org/features.html

http://tech.superhappykittymeow.com/?p=296

http://techblog.netflix.com/2014/11/introducing-raigad-elasticsearch-sidecar.html