# Restrict payload per chained query
**URL:** https://discuss.elastic.co/t/restrict-payload-per-chained-query/148352
**Category:** Elasticsearch
**Tags:** elastic-stack-alerting
**Created:** [September 12, 2018, 4:11pm UTC](https://discuss.elastic.co/t/restrict-payload-per-chained-query/148352 "2018-09-12T16:11:24Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@David\_Garza](https://discuss.elastic.co/u/David_Garza)
#### Post date: [September 12, 2018, 4:11pm UTC](https://discuss.elastic.co/t/restrict-payload-per-chained-query/148352/1 "2018-09-12T16:11:24Z")
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?
Thanks!
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [September 14, 2018, 11:29am UTC](https://discuss.elastic.co/t/restrict-payload-per-chained-query/148352/2 "2018-09-14T11:29:54Z")
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](https://www.elastic.co/guide/en/elasticsearch/reference/6.4/search-request-source-filtering.html) to reduce this?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 12, 2018, 11:29am UTC](https://discuss.elastic.co/t/restrict-payload-per-chained-query/148352/3 "2018-10-12T11:29:59Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.