Benefits/Drawbacks of using custom HTTP calls VS curator?


I am thinking to use normal HTTP calls to DELETE some indexes instead of using curator. IS curator except DELETE also executes more checks? What are the drawbacks of just using simple HTTP calls?

Thank you


Basically, it is perfectly fine to delete indexes by calling the REST API. This is the same API which is used by curator. The only thing curator helps you is by providing a configuration file for when indexes should be deleted, which indexes should be deleted. This needs to be defined by you when calling the API directly.

One note though: Depending on your version you might be better of by using the curator successor Index Lifecycle Management which runs in ELasticSearch and is configurable in Kibana.

Best regards

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.