/graylog2-server

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

after upgrade to 2.0, some dashboard problems #2163

Closed
cmock opened this Issue Apr 29, 2016 · 8 comments

Comments

Assignees

@edmundoa edmundoa

Labels
Projects
None yet
Milestone
  2.0.2
5 participants
@cmock @kroepke @dennisoelkers @edmundoa @supfors
@cmock

cmock commented Apr 29, 2016

Problem description

After the upgrade to 2.0, all of my pre-existing dashboards are broken, some more, some less.

Three of the five are completely empty, that is, no widgets are visible.

The other two do show all widgets; however, most of the "Quick values"-generated data tables are empty, except for those that I've added recently (with graylog 1.3). Their frame and title shows, but there is no table.

The screenshot shows a non-working and a recently added working table.
graylog

All the charts/histograms do show up fine.

Environment

  • Graylog Version: 2.0.0-5 (debian package)
  • Elasticsearch Version: 2.3.2
  • MongoDB Version: 2.6.12
  • Operating System: Debian Stable (8.4)
  • Browser version: Firefox 46.0

@kroepke kroepke added bug S2 P3 web labels May 2, 2016

@kroepke

This comment has been minimized.

Sign in to view
Member

kroepke commented May 2, 2016

Are there any errors in the Javascript console of your browser or any failed requests?

All of the widgets should continue to work in 2.0.
@cmock

This comment has been minimized.

Sign in to view

cmock commented May 2, 2016

Some javascript errors, see attachment; however, none of them occurs after going to an affected dashboard (the log is from a fresh browser session, including login).

Only a single non-200 HTTP code, right at the start of the session, a 401 in response to a request for /api/system/sessions, before logging in.

I didn't change the dashboard, so if you let me know how to export the data from mongo, I'd be happy to share the configuration.

ffconsole.txt
@dennisoelkers

This comment has been minimized.

Sign in to view
Member

dennisoelkers commented May 10, 2016

Is there anything in your server logs when trying to view an affected dashboard?

@dennisoelkers dennisoelkers added the cannot reproduce label May 10, 2016

@edmundoa

This comment has been minimized.

Sign in to view
Member

edmundoa commented May 10, 2016

It would also help if you could share with us the configuration of one of the affected widgets. You can use the /dashboards/<dashboardId> resource in the REST API to get a dashboard configuration (including its widgets).
@cmock

This comment has been minimized.

Sign in to view

cmock commented May 11, 2016

There's nothing in the server logs.

The API output is attached.
54a6c996e4b093ce4aac32ae.txt
@supfors

This comment has been minimized.

Sign in to view

supfors commented May 17, 2016

I've had the same issue. "Fixed" it by deleting the "positions" key sfrom the mongo graylog collection > Dashboards > (id).
@edmundoa

This comment has been minimized.

Sign in to view
Member

edmundoa commented May 19, 2016

I have been able to reproduce two different issues with the dashboard @cmock kindly shared:

  • When the positions object does not contain width and height, the dashboard does not render at all
  • Quickvalues widgets created in old Graylog versions (before the pie charts were introduced) will not render neither the data table, nor the pie chart.

@edmundoa edmundoa self-assigned this May 19, 2016

edmundoa added a commit that referenced this issue May 19, 2016

@edmundoa
Always render quickvalues data table by default 
Quickvalues widgets created before introducing pie charts may not render
neither a data table, nor a pie chart. In this commit we ensure we
always render the data table by default.

Refs #2163
c5f062c

edmundoa added a commit that referenced this issue May 19, 2016

@edmundoa
Be more picky getting widgets dimensions 
Dashboards created in old Graylog versions may have a positions object
that does not contain widget width or height. Instead of relying on what
that positions object had, this commit ensures each component of the
widget position is initialized with the persisted value or its default.

Refs #2163
Loading status checks…
c041a49

@edmundoa edmundoa referenced this issue May 19, 2016

Merged

Fix issues with old dashboards #2262

@edmundoa edmundoa added this to the 2.0.2 milestone May 19, 2016

dennisoelkers added a commit that referenced this issue May 24, 2016

@edmundoa @dennisoelkers
Fix issues with old dashboards (#2262) 
* Always render quickvalues data table by default

Quickvalues widgets created before introducing pie charts may not render
neither a data table, nor a pie chart. In this commit we ensure we
always render the data table by default.

Refs #2163

* Fix typo

* Be more picky getting widgets dimensions

Dashboards created in old Graylog versions may have a positions object
that does not contain widget width or height. Instead of relying on what
that positions object had, this commit ensures each component of the
widget position is initialized with the persisted value or its default.

Refs #2163
Loading status checks…
d2fcddb

dennisoelkers added a commit that referenced this issue May 24, 2016

@edmundoa @dennisoelkers
Fix issues with old dashboards (#2262) 
* Always render quickvalues data table by default

Quickvalues widgets created before introducing pie charts may not render
neither a data table, nor a pie chart. In this commit we ensure we
always render the data table by default.

Refs #2163

* Fix typo

* Be more picky getting widgets dimensions

Dashboards created in old Graylog versions may have a positions object
that does not contain widget width or height. Instead of relying on what
that positions object had, this commit ensures each component of the
widget position is initialized with the persisted value or its default.

Refs #2163

(cherry picked from commit d2fcddb)
Loading status checks…
d1b65af
@dennisoelkers

This comment has been minimized.

Sign in to view
Member

dennisoelkers commented May 24, 2016

Closing this, as it has been fixed now.

@dennisoelkers dennisoelkers closed this May 24, 2016

@kroepke kroepke added the triaged label Sep 21, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment