Elastic Web Crawler API or configuration transport


we are using the Elastic Web Crawler. In our environment we have a lot of websites to crawl with different extraction rules, schedules etc. It is a lot of manual work to configure this with the Kibana GUI and a staging between non-prod and prod environments is nearly impossible and also a backup is hard.

Unfortunately the Elastic Web Crawler has'nt an API - and it is not an option to use the App Search Crawler, because we need access to Elasticsearch indices and alyo content extraction.

The comparison between App Search and Elastic Web Crawler.
API Reference | App Search documentation [8.10] | Elastic

Dies anybody know a good approach to avoid manually configuration of the Elastic Web Crawler? Is there an hidden API or any other approach to transport configuration between different stages or environments?



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