# Static lookup in Visualization

**URL:** <https://discuss.elastic.co/t/static-lookup-in-visualization/230934>\
**Category:** Kibana\
**Created:** [May 4, 2020, 7:37am UTC](https://discuss.elastic.co/t/static-lookup-in-visualization/230934 "2020-05-04T07:37:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rohitarora275](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohitarora275/32/66210_2.png) [@rohitarora275](https://discuss.elastic.co/u/rohitarora275)\
**Post date:** [May 4, 2020, 7:37am UTC](https://discuss.elastic.co/t/static-lookup-in-visualization/230934/1 "2020-05-04T07:37:13Z")

</div>

Hi Team ,

I am trying to use static lookup field in Visualization **include** tag but I am not get appropriate result. I have written around static lookup value in INSTANCE field. However if I use the output in **include** , I am not getting appropriate result on the visualization window.

Can someone please help me in writing a logic so that it can work with output values, as I cannot write 1000 values in **include**  
PFA screenhot for static field

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/e/0e7ddd7d1037ec0838578aa9edd719a60a29a7d2.png)

PFA screenshot when I pass the input value in **include**

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/d/ed5c147a2e35fee479611bc62bb741e20413a63d.png)

PFA screenshot when I pass the Output value in **include**

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/0/606cdba674e37a1676c8f2575b7e202fa45873e2.png)

---

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [May 4, 2020, 9:39pm UTC](https://discuss.elastic.co/t/static-lookup-in-visualization/230934/2 "2020-05-04T21:39:39Z")

</div>

The static lookup value is only used for output formatting so it cannot be used in queries. If there's a specific rule by which you create the lookup, i would look into creating a scripted field. And you can filter by that.

---

<div class="post-metadata">

**Author:** ![rohitarora275](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohitarora275/32/66210_2.png) [@rohitarora275](https://discuss.elastic.co/u/rohitarora275)\
**Post date:** [May 5, 2020, 5:05am UTC](https://discuss.elastic.co/t/static-lookup-in-visualization/230934/3 "2020-05-05T05:05:35Z")

</div>

Hi Marius\_Dragomir,

Thanks for your response, so are you suggesting to write all these conditions in scripted fields?

I am just afraid that it will be impacting the performance. Please suggest

---

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [May 5, 2020, 1:21pm UTC](https://discuss.elastic.co/t/static-lookup-in-visualization/230934/4 "2020-05-05T13:21:37Z")

</div>

If it's just one scripted field, it should be OK. It all depends on your data and it's size.

---

<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:** [June 2, 2020, 1:21pm UTC](https://discuss.elastic.co/t/static-lookup-in-visualization/230934/5 "2020-06-02T13:21:45Z")

</div>

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