Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kibana 7.8.0: buckets/metrics are not loaded on Dashboard app #116

Closed
hoberhol opened this issue Jul 13, 2020 · 35 comments
Closed

Kibana 7.8.0: buckets/metrics are not loaded on Dashboard app #116

hoberhol opened this issue Jul 13, 2020 · 35 comments
Labels

Comments

@hoberhol
Copy link

Since the latest version 1.9.1 I'm getting the following error on a dashboard including an enhanced table visualization after the login:

In computed column "col['cnt'], column with label 'cnt' does not exists.

image

In the visualization editor the table is working correct. I can then open the dashboard and from now on all is working fine. After logout/login the error appears again.

image

image

I tried the following without any luck:

  • recreate my tables
  • use col1 instead of col['xxx']
  • create new simple table (as in the screenshot) with just one computed value
  • clear browser cache / restart browser / different browser chrome and firefox

The error appears on all my enhanced table visualizations I'm using in production for a long time already.
After I open one visualization in the editor and close again (does not even have to be saved) the error is gone also for the other visualizations until you relogin.

Thanks for your support.

@fbaligand
Copy link
Owner

fbaligand commented Jul 13, 2020

can you tell me:

  • what is your Kibana version?
  • what was the last plugin version you installed, that worked fine (without this issue) ?
  • when you speak about login/relogin, I guess you speak about Kibana authentication?

@hoberhol
Copy link
Author

  • what is your Kibana version?
    1.8.0
  • what was the last plugin version you installed, that worked fine (without this issue) ?
    1.9.1_7.7.1 (on Kibana 7.7.1)
  • when you speak about login/relogin, I guess you speak about Kibana authentication?
    yes, logout and login again to Kibana.
    The same error exist after I switch the space in Kibana without logout/login

@fbaligand
Copy link
Owner

I guess you reverse your two first answers?

@fbaligand
Copy link
Owner

To help me see where/when regression happened, could you tell me if you reproduce the issue with enhanced table v1.9.0?
And ideally, if you reproduce the issue with kibana 7.8.0?

@vladyslav-vasiliev
Copy link

Hi, @fbaligand, I've encountered the same issue.
The issue only occurs on visualizations and after investigations on inspection page I've found that there are no aggregations in the request.

  • what is your Kibana version?
    Kibana 7.8.0, enhanced-table-1.9.1_7.8.0

  • what was the last plugin version you installed, that worked fine (without this issue)?
    enhanced-table-1.9.0_7.6.2

@fbaligand
Copy link
Owner

@Ondee, thanks for your feedback.
Well, it seems that issue exists since kibana 7.7 and is not tied to 1.9.1 version.
To check that, could you test 1.9.1 version with kibana 7.6.2?

@vladyslav-vasiliev
Copy link

Yes, it works with version enhanced-table-1.9.1_7.6.2

@hoberhol
Copy link
Author

I did some more tests:

Working with version:

  • elasticsearch-7.7.1
  • kibana-7.7.1
  • enhanced-table-1.9.1_7.7.1.zip

Not working with version:

  • elasticsearch-7.8.0
  • kibana-7.8.0
  • enhanced-table-1.9.1_7.8.0.zip

You can reproduce this as follows:

  1. Install the version above from download page
  2. Install sample data (I used flight sample data)
  3. Create a vizualization and add a computed column referencing the metric count value and save as eg. test

image

image

  1. Create a new dashboard and add visualization to it and save as eg. test

  2. Create a new space with manage space and give it a name

  3. Switch to the new created space

  4. Switch back to the default space

  5. Open the dashboard you just created

  • with version 7.8.0 you will see the error

image

  • with version 7.7.1 no error occurs

image

Hope this helps and thanks a lot for your time and support on this topic*

@fbaligand
Copy link
Owner

fbaligand commented Jul 13, 2020

@hoberhol
Thanks for your precious additional tests!

So it is now clear that the issue is tied to Kibana 7.8.0 version.
I will investigate on it.

@tonykoval
Copy link

tonykoval commented Jul 15, 2020

@hoberhol Do you have also problem with discovery mode in Kibana 7.8.0? Error in console: Cannot read property 'call' of undefined

@hoberhol
Copy link
Author

I don't experience any problem with the discover function in Kibana 7.8.0. So far everything is working fine.
The mentioned problem only exists in conjuction with the enhanced table plugin.

@tonykoval
Copy link

@hoberhol thank you, I found out that was caused by the old version of chrome

@fbaligand fbaligand changed the title Error: "column with label 'xy' does not exists" since latest version 1.9.1 on Error: "column with label 'xy' does not exists" since latest version 1.9.1 on Kibana 7.8.0 Jul 16, 2020
@fbaligand fbaligand added the bug label Jul 17, 2020
@fbaligand
Copy link
Owner

Hi,
After investigation, I can say that:

So for now, I can only invite you either to wait for Kibana 7.8 fix, or to downgrade to Kibana v7.7.1.

@fbaligand fbaligand changed the title Error: "column with label 'xy' does not exists" since latest version 1.9.1 on Kibana 7.8.0 Error: "column with label 'xy' does not exist" on Kibana 7.8.0 Jul 17, 2020
@tonykoval
Copy link

Kibana 7.8.1 is released, but I didn't find this fix (71423) in the release notes.

@fbaligand
Copy link
Owner

Well, it is not on release notes.
But I can insure you that fix is included in kibana 7.8.1.
Proof is on this page:
https://github.com/elastic/kibana/commits/v7.8.1

You can see that “ [Visualizations] Pass 'aggs' parameter to custom request handlers” is part of v7.8.1 commits.
Thus, @fabiopipitone tested this morning and confirmed that enhanced table 1.9.1 works with kibana 7.8.1.

I will provide a package for kibana 7.8.1 as soon as I can.
But, in the meantime, you can just change kibana version in plugin’s package.json file, and install it on kibana 7.8.1 as is.

@guillermoc-infocorp
Copy link

Hi Fabien!
I downloaded new versions Elasticsearch+Kibana 7.8.1 from elastic.co (Windows Zip files), changed the package.json to 7.8.1 and installed successfully, but the error persists. Maybe I forgot something,
should I do something additional? please your confirmation.

https://artifacts.elastic.co/downloads/kibana/kibana-7.8.1-windows-x86_64.zip
https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.8.1-windows-x86_64.zip

@fabiopipitone
Copy link
Contributor

Hi there,

this morning I actually tested it to check whether it would work with different types of aggregation and bucket splits and it did work.

I'll carry out some further tests ASAP (tonight most likely) to test other and more specific enhanced table features.

I'll let you know!

@fbaligand
Copy link
Owner

@guillermoc-infocorp
Sorry that you still experience some issue.
As @fabiopipitone, I did some tests this afternoon on dashboard app, and it worked fine.
Buckets and Metrics are loaded correctly.

That's why I just published package for Kibana 7.8.1:
https://github.com/fbaligand/kibana-enhanced-table/releases/download/v1.9.1/enhanced-table-1.9.1_7.8.1.zip

I invite you to test with that package on your installation. And I invite you to empty your browser cache, to avoid browser cache side effect.

@guillermoc-infocorp
Copy link

@fbaligand
When I try with a new visualization and a new dashboard it automatically hides the aggr column. The test was made with simple "metric count" and a term aggr on a string field. When I change to another space and came back, it only shows one column: the count one. When I edit, I see both column.

After save&return, I see both ok.

With old visualizations, I still see the same error as in 7.8.0

Please let me know if you could replicate it.
Thanks!
Guillermo.

@fbaligand
Copy link
Owner

I just did some more tests, and you’re right, the bug is still there.

So the good news is that I identified and fixed the bug.
I will try to release 1.9.2 tomorrow with only one package for kibana 7.8.1

@guillermoc-infocorp
Copy link

Excellent! thank you!

@fbaligand
Copy link
Owner

fbaligand commented Jul 29, 2020

Hi all,

I'm glad to announce that enhanced-table 1.9.2 is out, with display on Dashboard app fixed!
https://github.com/fbaligand/kibana-enhanced-table/releases/tag/v1.9.2

Don't hesitate to download it, install it, test it and give feedback here to say it works as you expect! :)

BTW, there is also another minor bugfix that happened on Kibana 7.8.
Globally, I invite you to forget enhanced-table use with Kibana 7.8.0.
I will remove the package for 7.8.0 soon, as this bug is severe.

@fbaligand fbaligand changed the title Error: "column with label 'xy' does not exist" on Kibana 7.8.0 Kibana 7.8.0: buckets/metrics are not loaded on Dashboard app Jul 29, 2020
@guillermoc-infocorp
Copy link

Hi @fbaligand thanks for your notification!

is this the correct package?:
https://github.com/fbaligand/kibana-enhanced-table/releases/download/v1.9.2/enhanced-table-1.9.2_7.8.1.zip

(because in your post you write v1.9.1)

I've downloaded this (my link for 1.9.2) and is still hiding me all the buckets columns.
Also the original error still shows for old visualizations.

ES 7.8.1
Kibana 7.8.1
Enhanced-table-1.9.2
Last Chrome with empty caché

thanks in advance!
Guillermo.

@fbaligand
Copy link
Owner

Very sad to hear that.
And very surprised.
I made several tests with this version and I don’t have the errors you quote.

@hoberhol
Copy link
Author

Hi all

I can confirm that the same issue as described in the beginning of this thread still exists with the follwowing versions:

ES 7.8.1
Kibana 7.8.1
Enhanced-table 1.9.2

Thanks a lot for your support on this one.

Hans

@fabiopipitone
Copy link
Contributor

Hi there,

I confirm the issue's still there. During my first tests, being unaware of this opened issue, I didn't test the going forth and back to/from a new space and seeing what happens, hence when I noticed it was working with 7.8.1 in the Dashboard section I thought the bug was fixed.

Unfortunately I tested it with the 7.8.1 stack and release 1.9.2 and the problem's still there, as you can see from the following

et_192_error

Fabio

@fbaligand
Copy link
Owner

Thanks all for your feedback.
I will do more tests with xpack version to reproduce the issue and try to fix it.
I hope it does not require a new kibana code change.

@alaindixon
Copy link

WORKS !! thank you very much.

@fabiopipitone
Copy link
Contributor

WORKS !! thank you very much.

Does it? Have you tried refreshing the browser after loading the dashboard? Or switching to a new space and then back to the one with the faulty dashboard?

Which version of the stack are you using? OSS or basic xpack featured?

@fbaligand
Copy link
Owner

Hi all,

I did what @guillermoc-infocorp did:

All these steps work fine, I don't see any bug.

So I invite you (@guillermoc-infocorp, @fabiopipitone, @hoberhol) to fully reinstall the plugin:

  • delete "optimize" and "plugins" folder
  • install plugin using CLI tool: kibana-plugin.(bat|sh) install https://github.com/fbaligand/kibana-enhanced-table/releases/download/v1.9.2/enhanced-table-1.9.2_7.8.1.zip
  • start Kibana

@fabiopipitone
Copy link
Contributor

Ok so, I made a new test this morning, reinstalling the plugin and, most importantly, using the private browsing in Chrome. In so doing I had no problem at all. I guess it was a problem of something Chrome kept track of at this point. Beautiful!

@fbaligand
Copy link
Owner

Great news!

@guillermoc-infocorp
Copy link

Definitely you are right!! Thank you sooo much! All is Ok!

Only deleting the Optimize folder.

have a nice weekend!

@fbaligand
Copy link
Owner

Nice to hear that @guillermoc-infocorp !

@fbaligand
Copy link
Owner

After 3 successful checks (plus mine), I definitely consider the bug as resolved!
And so, I’m glad to officially close this issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants