- Curator Index Management:
- About
- Getting Started
- Flags
- --debug
- --dry-run
- --help
- --host
- --http_auth
- --logfile
- --logformat
- --loglevel
- --master-only
- --quiet
- --port
- --timeout
- --url_prefix
- --use_ssl
- --certificate
- --client-cert
- --client-key
- --ssl-no-validate
- --version
- --newer-than
- --older-than
- --prefix
- --suffix
- --time-unit
- --timestring
- --regex
- --exclude
- --index
- --all-indices
- --snapshot
- --all-snapshots
- --repository
- --skip-repo-validation
- Commands
- Subcommands
- Index & Snapshot Selection
- Frequently Asked Questions
- Q: How can I report an error in the documentation?
- Q: Can I delete only certain data from within indices?
- Q: Can Curator handle index names with strange characters?
- Q: I’m getting
DistributionNotFound
andentry_point
errors when I try to run Curator. What am I doing wrong? - Q: Snapshots seem to be working. Why am I getting
SnapshotMissingException
messages? - Q: How do I escape the
%
in the--timestring
for use with systemd?
- Contributing to Curator
- Glossary of terms
A newer version is available. For the latest information, see the
current release documentation.
Getting Started
editGetting Started
editLike a museum curator manages the exhibits and collections on display, Elasticsearch Curator helps you curate, or manage your Elasticsearch indices.
Curator performs many operations on your Elasticsearch indices, from delete to snapshot to shard allocation routing.
Was this helpful?
Thank you for your feedback.