# AggConfig object not found

**URL:** <https://discuss.elastic.co/t/aggconfig-object-not-found/157005>\
**Category:** Kibana\
**Created:** [November 16, 2018, 8:14am UTC](https://discuss.elastic.co/t/aggconfig-object-not-found/157005 "2018-11-16T08:14:36Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![MishMick](https://avatars.discourse-cdn.com/v4/letter/m/ecccb3/32.png) [@MishMick](https://discuss.elastic.co/u/MishMick)\
**Post date:** [November 16, 2018, 8:14am UTC](https://discuss.elastic.co/t/aggconfig-object-not-found/157005/1 "2018-11-16T08:14:36Z")

</div>

![07%20PM](https://us1.discourse-cdn.com/elastic/original/3X/d/c/dc9ac144fd090322eb623f4c52793e10de2b97c7.png)

Getting this error after upgrading ELK stack from 6.3.2 to 6.5.0.

My custom Kibana plugin has stopped rendering. Are there some necessary changes need to be made as part of the upgrade?

---

<div class="post-metadata">

**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\
**Post date:** [November 16, 2018, 7:09pm UTC](https://discuss.elastic.co/t/aggconfig-object-not-found/157005/2 "2018-11-16T19:09:33Z")

</div>

Can u please provide more details ? What are the errors on ES and Kibana logs?

cc @tylersmalley

THanks  
Rashmi

---

<div class="post-metadata">

**Author:** ![pchakour](https://avatars.discourse-cdn.com/v4/letter/p/e36b37/32.png) [@pchakour](https://discuss.elastic.co/u/pchakour)\
**Post date:** [November 18, 2018, 7:41pm UTC](https://discuss.elastic.co/t/aggconfig-object-not-found/157005/3 "2018-11-18T19:41:15Z")

</div>

I'm trying to upgrade some custom plugins and I've the same issue.  
It's seems to be caused by the new courier request handler.

---

<div class="post-metadata">

**Author:** ![pchakour](https://avatars.discourse-cdn.com/v4/letter/p/e36b37/32.png) [@pchakour](https://discuss.elastic.co/u/pchakour)\
**Post date:** [November 19, 2018, 5:55pm UTC](https://discuss.elastic.co/t/aggconfig-object-not-found/157005/4 "2018-11-19T17:55:09Z")

</div>

In my case, the console print the following error :

> TypeError: Cannot read property 'aggConfig' of undefined  
> at collectBucket (tabify.js:62)  
> at tabify.js:78  
> at \_buckets.js:67  
> at Array.forEach ()  
> at TabifyBuckets.forEach (\_buckets.js:66)  
> at collectBucket (tabify.js:70)  
> at tabify.js:78  
> at \_buckets.js:67  
> at Array.forEach ()  
> at TabifyBuckets.forEach (\_buckets.js:66)  
> at collectBucket (tabify.js:70)  
> at tabify.js:78  
> at \_buckets.js:67  
> at Array.forEach ()  
> at TabifyBuckets.forEach (\_buckets.js:66)  
> at collectBucket (tabify.js:70)

The courier retrieve all needed data from elasticsearch.

---

<div class="post-metadata">

**Author:** ![MishMick](https://avatars.discourse-cdn.com/v4/letter/m/ecccb3/32.png) [@MishMick](https://discuss.elastic.co/u/MishMick)\
**Post date:** [November 20, 2018, 4:26am UTC](https://discuss.elastic.co/t/aggconfig-object-not-found/157005/5 "2018-11-20T04:26:38Z")

</div>

@pchakour Were you able to solve it?

---

<div class="post-metadata">

**Author:** ![pchakour](https://avatars.discourse-cdn.com/v4/letter/p/e36b37/32.png) [@pchakour](https://discuss.elastic.co/u/pchakour)\
**Post date:** [November 20, 2018, 9:54am UTC](https://discuss.elastic.co/t/aggconfig-object-not-found/157005/6 "2018-11-20T09:54:47Z")

</div>

Not yet. I'm currently looking for a way to fix it.  
It's possible to create a custom request handler to avoid the problem but I want to use the standard courier.

@rashmi, do you have any ideas about our issue ?

---

<div class="post-metadata">

**Author:** ![pchakour](https://avatars.discourse-cdn.com/v4/letter/p/e36b37/32.png) [@pchakour](https://discuss.elastic.co/u/pchakour)\
**Post date:** [November 22, 2018, 2:11pm UTC](https://discuss.elastic.co/t/aggconfig-object-not-found/157005/7 "2018-11-22T14:11:20Z")

</div>

I've more informations about my issue. It's happen when my custom plugin has only one bucket define in the schema. I patch the kibana code to handle this case.

It's a bug of kibana or it's something expected ?

---

<div class="post-metadata">

**Author:** ![MishMick](https://avatars.discourse-cdn.com/v4/letter/m/ecccb3/32.png) [@MishMick](https://discuss.elastic.co/u/MishMick)\
**Post date:** [November 22, 2018, 2:37pm UTC](https://discuss.elastic.co/t/aggconfig-object-not-found/157005/8 "2018-11-22T14:37:02Z")

</div>

Can you pls share the patch details ?

---

<div class="post-metadata">

**Author:** ![pchakour](https://avatars.discourse-cdn.com/v4/letter/p/e36b37/32.png) [@pchakour](https://discuss.elastic.co/u/pchakour)\
**Post date:** [November 22, 2018, 4:59pm UTC](https://discuss.elastic.co/t/aggconfig-object-not-found/157005/9 "2018-11-22T16:59:29Z")

</div>

This is a link with the git diff [http://www.rapidshare.com.cn/B52ntSD](http://www.rapidshare.com.cn/B52ntSD)

I don't think usefull for you because you have metrics and buckets in your visualization.

---

<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:** [December 20, 2018, 5:01pm UTC](https://discuss.elastic.co/t/aggconfig-object-not-found/157005/10 "2018-12-20T17:01:18Z")

</div>

Closed on December 20, 2018, 5:01pm UTC

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