elastic/curator

Curator: Tending your Elasticsearch indices

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 22nd, 2026
Created on August 20th, 2013
Open Issues & Pull Requests: 117 (+0)
GitHub issues: Enabled
Number of forks: 626
Total Stargazers: 3,078 (+0)
Total Subscribers: 387 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 90.9 days
Mean response time: 332.2 days
90th percentile: 1226.5 days
Tracked items: 23

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 839 days
Stale 30+ days: 9
Stale 90+ days: 8

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • feature_request (2)
  • bug (1)
  • more_info_required (1)
  • not curator (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Curator is a Python tool for managing Elasticsearch indices through automated curation and lifecycle operations.

Curator addresses the challenge of managing large numbers of indices in Elasticsearch clusters by providing a framework to automate common administrative tasks. It works by reading configuration files that define actions to perform on indices matching specified filters, allowing operators to apply operations like deletion, snapshots, and index optimization across many indices without manual intervention.

Teams running Elasticsearch should consider Curator if they need to automate index lifecycle management at scale. It suits clusters with time-series data or high index churn where manual management becomes impractical. The tool maintains version alignment with Elasticsearch itself, with major versions tracking corresponding Elasticsearch releases. The client connection layer has been separated into a dedicated module to allow independent updates to connection handling without requiring full Curator releases.

The project receives steady maintenance with updates addressing compatibility across Elasticsearch versions, including backported support for older minor versions. Configuration changes are introduced thoughtfully, with the action file structure remaining stable while the client configuration was modernized to support the new es_client module. The team actively manages version support across multiple Elasticsearch generations.