-
Notifications
You must be signed in to change notification settings - Fork 199
Worldmap panel is not rendered in view mode when using json endpoint location data #220
Comments
I think I am having the same issue. If the json endpoint takes longer to respond than the query, there are no map points rendered. I was able to get it to work when the query I was using took a long time to respond ( longer than the json location response), but when I optimized my query to run faster this behavior started. The workaround I am using is to hit the refresh button after the locations have had a chance to load. |
Dear @xiaobeiyang and @stevemandl, thanks for bringing this up. We might have improved this behavior already within our fork [1,2] through. Its most recent version can be installed side-by-side to Worldmap like outlined below. Please feel free to get back to me if this doesn't help. I will be happy to open a case for looking into the issue within one of the next development iterations then. With kind regards, [1] https://community.hiveeyes.org/t/grafana-map-panel-ng/1824
|
I tried this and it did not fix the problem. However, the fix in #221 does fix the problem. |
Dear @stevemandl, thanks for letting us know. We will consider integrating this update within one of the next development iterations on our fork [1]. With kind regards, |
Dear @stevemandl @amotl |
Dear Steve,
Thanks again for clarifying the behavior you are observing. We are now also tracking this within grafana-toolbox#53.
As far as we can see, the essence of #221 is already integrated into the fork. However, there still might be dragons regarding timing/synchronicity. With kind regards, |
Reproduce step:
json endpoint
.Result:
Can't see the dashboard.
Note:
I can reproduce this issue on Chrome & Edge & Safari. Can't reproduce on latest Firefox.

I think jsonp endpoint has the same behavior.The text was updated successfully, but these errors were encountered: