# Why vairable in SearchSlowLog won't be volitale

**URL:** <https://discuss.elastic.co/t/why-vairable-in-searchslowlog-wont-be-volitale/58012>\
**Category:** Elasticsearch\
**Created:** [August 15, 2016, 9:19am UTC](https://discuss.elastic.co/t/why-vairable-in-searchslowlog-wont-be-volitale/58012 "2016-08-15T09:19:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![makeyang](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@makeyang](https://discuss.elastic.co/u/makeyang)\
**Post date:** [August 15, 2016, 9:19am UTC](https://discuss.elastic.co/t/why-vairable-in-searchslowlog-wont-be-volitale/58012/1 "2016-08-15T09:19:36Z")

</div>

private long queryWarnThreshold;  
private long queryInfoThreshold;  
private long queryDebugThreshold;  
private long queryTraceThreshold;

since it need dynamicly updated, why not set them volitale?

---

<div class="post-metadata">

**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\
**Post date:** [August 15, 2016, 9:43am UTC](https://discuss.elastic.co/t/why-vairable-in-searchslowlog-wont-be-volitale/58012/2 "2016-08-15T09:43:03Z")

</div>

Good question, if you think they should be and have good reasons for this, would you mind opening a pull request to discuss this there?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 10:27pm UTC](https://discuss.elastic.co/t/why-vairable-in-searchslowlog-wont-be-volitale/58012/3 "2017-07-05T22:27:48Z")

</div>

Closed on July 5, 2017, 10:27pm UTC