# Suggest to avoid localStorage limitations

**URL:** <https://discuss.elastic.co/t/suggest-to-avoid-localstorage-limitations/29369>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring\
**Created:** [September 16, 2015, 7:25am UTC](https://discuss.elastic.co/t/suggest-to-avoid-localstorage-limitations/29369 "2015-09-16T07:25:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![comdiv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/comdiv/32/44902_2.png) [@comdiv](https://discuss.elastic.co/u/comdiv)\
**Post date:** [September 16, 2015, 7:25am UTC](https://discuss.elastic.co/t/suggest-to-avoid-localstorage-limitations/29369/1 "2015-09-16T07:25:03Z")

</div>

Sometimes query size exceed localStorage limitations. For examply when debug attachment data type working in sense (large B64 fields).

In this cases sense doesn't show anything in result because it got exception on localStorage operation before rendering result.

I have fix it directly in optimized app.js:  
localStorage.setItem(l,JSON.stringify({time:a,server:e,endpoint:t,method:i,data:r})) -\>  
try{localStorage.setItem(l,JSON.stringify({time:a,server:e,endpoint:t,method:i,data:r}))}catch(e){}

so now it work fine. But i think it's not much wise.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 16, 2015, 7:37am UTC](https://discuss.elastic.co/t/suggest-to-avoid-localstorage-limitations/29369/2 "2015-09-16T07:37:30Z")

</div>

Is this a Marvel issue?

---

<div class="post-metadata">

**Author:** ![comdiv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/comdiv/32/44902_2.png) [@comdiv](https://discuss.elastic.co/u/comdiv)\
**Post date:** [November 10, 2015, 5:12pm UTC](https://discuss.elastic.co/t/suggest-to-avoid-localstorage-limitations/29369/3 "2015-11-10T17:12:37Z")

</div>

After moving sense to kibana it doesn't make sence in Marvel. It was an issue in optimized JS code shipped with Marvel so i think it's marvel's sense issue

---

<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 6, 2017, 1:47pm UTC](https://discuss.elastic.co/t/suggest-to-avoid-localstorage-limitations/29369/4 "2017-07-06T13:47:11Z")

</div>