This is a good question - I would love to learn more about your goal here. I imagine a few reasons:
- Get notified when any configured watches exceed their configured timeouts
- Ensure consistent watch execution times for short-interval watches
Are there other goals you had in mind?
Today, you can specify a timeout in the search input request body, and we do record the search execution information (e.g. execution_result.input.search.payload.took, and timed_out) in the watch history. These fields aren't indexed today, but it's something we could consider adding, so you could create a watch that looks at the watch history for timed_out ES queries.