Restrict payload per chained query


(David Garza) #1

We are running a watcher every minute which may return many documents (1000s). We run the query results through a few different transformations using chained inputs. Of the 3 scripted transforms, I only need one of the inputs logged to the .watcher-history index but the others not.

How can I use the data for each chained input at runtime but selectively not log the data per chained input in the watcher history?


(Alexander Reelsen) #2

there is currently no way of changing what is written into the history.

Do you really need all of the document data/fields or could you use source filtering to reduce this?

(system) #3

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