Closed elasticmachine closed 2 weeks ago
Original comment by @pickypg:
(and dependencies?)
One of the best things about Watches is that they are completely self-contained with one exception: indexed scripts.
This includes both Mustache and Painless scripts.
Original comment by @rasroh:
cc / @elastic/kibana-management
Pinging @elastic/es-ui
@alexfrancoeur The first thing that pops into my head is to suggest the user create a snapshot of the .watches
index and then restore that snapshot elsewhere. Looks like this was our advice to a user regarding this on the forums: https://discuss.elastic.co/t/list-backup-restore-watchers/123403.
Would this address the use cases you're aware of? Or are there use cases where the user needs a super-low-friction way of sharing Watches? (If so I'd love to hear more details about this).
The ability to create watches in a test/dev environment, and then export them and reimport them into a production environment would be a benefit to users who have strong change management procedures.
an absolute necessity. this could be an option under the saved objects export / import a little check mark to include watches just like the index-patterns, viz, dashboards.
Not planned work at this time
Original comment by @alexfrancoeur:
Similar to the new experimental import / export dashboard API (https://github.com/elastic/kibana/pull/10858), customers would like to be able to import / export watches (and dependencies?) directly from an API.