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

Stacked chart doesn't load (displays N/A) #5742

Closed
Tastyep opened this issue Mar 4, 2019 · 1 comment · Fixed by #6003
Closed

Stacked chart doesn't load (displays N/A) #5742

Tastyep opened this issue Mar 4, 2019 · 1 comment · Fixed by #6003

Comments

@Tastyep
Copy link

Tastyep commented Mar 4, 2019

Hello,

After upgrading my version of graylog to 3.0, I noticed that stacked charts failed to load properly.

Current Behavior

Loading the stacked chart from a content pack fails with the following error:
There was an error fetching a resource: cannot GET http://172.19.0.5:9000/api/dashboards/5c7d40573ecd49000dbc23a6/widgets/8119956c-682d-4f7b-913f-484a1560b3c4/value (500). Additional information: Null from
The widget loads, but its content is just a text equal to N/A.

Steps to Reproduce (for bugs)

I don't have a live example, but the problem is fairly easy to reproduce.

  1. Go on a stream and generate two charts
  2. Merge the two charts
  3. Add them to a dashboard
  4. Create a new content pack from the current revision (include both the modified dashboard and the stream)
  5. Uninstall the content pack, then reinstall.
  6. Go on the dashboard and see the problem.

Context

I want to create a combined graph of mean and max latency for requests.

Your Environment

  • Graylog Version: 3.0 or 3.0.0-1, taken from docker hub
  • Elasticsearch Version: 5.6.15
  • MongoDB Version: 3.6.8
  • Operating System: Debian, kernel 4.19.0.2, graylog is running in docker
  • Browser version: Firefox 65.0.1
@Tastyep
Copy link
Author

Tastyep commented May 2, 2019

Bumping this to add some details.
The problem occurs when exporting the content pack, the stacked chart as an empty series field = [],
by modifying manually the JSON I managed to make it work. Correctly exporting it should fix this issue.

@kmerz kmerz self-assigned this Jun 6, 2019
@kmerz kmerz added this to the 3.1.0 milestone Jun 6, 2019
kmerz added a commit that referenced this issue Jun 7, 2019
Prior this change we missed support of maps in list of
a ReferenceMap. This is needed to support configurations
(like DashboardWidget) which can contain a list of maps.
(e.g series when two charts are merged into one)

This change will call toReferenceMap for every list item
which is a map.

Fixes #5742
bernd pushed a commit that referenced this issue Jul 1, 2019
Prior this change we missed support of maps in list of
a ReferenceMap. This is needed to support configurations
(like DashboardWidget) which can contain a list of maps.
(e.g series when two charts are merged into one)

This change will call toReferenceMap for every list item
which is a map.

Fixes #5742
bernd pushed a commit that referenced this issue Jul 1, 2019
Prior this change we missed support of maps in list of
a ReferenceMap. This is needed to support configurations
(like DashboardWidget) which can contain a list of maps.
(e.g series when two charts are merged into one)

This change will call toReferenceMap for every list item
which is a map.

Fixes #5742

(cherry picked from commit a661710)
kmerz pushed a commit that referenced this issue Jul 2, 2019
Prior this change we missed support of maps in list of
a ReferenceMap. This is needed to support configurations
(like DashboardWidget) which can contain a list of maps.
(e.g series when two charts are merged into one)

This change will call toReferenceMap for every list item
which is a map.

Fixes #5742

(cherry picked from commit a661710)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants