Dashing issues with refreshing data

[hkdanalyser]

All,

I am using the latest vagrant icinga2 build / latest files from the dashing-icinga2 repo and having issues with pulling data and viewing it on the dashboard.

I am able to view the widget data when i restart the dashboard, but if I go to any other part of the site and come back to the dashboard, i get no data.

Any light on this issue will be appreciated. Thanks.

[dnsmichi]

You are using it as iframe in Icinga Web 2. That might cause troubles with its own reload and the Dashing triggered events. Try it standalone.

[flyck]

I have the same issue with the standalone server.

While I don't know the solution I have explored the problem a bit.

The data is provided by jobs/icinga2.rb. A simple "icinga.run" seems to gather all the data. Afterwards it sends the data to the "widgets" (all these square boxes) using "send_event()".
When i navigate to the dashing page and open the Chrome Console, i only see messages like this "No lastUpdate, setting one col1", which hints towards the widgets not getting the updates.

After stopping dashing (this is when i first see something on the dashboard as described) another log-message is displayed: "xxx.xxx.xxx.xxx - - [28/Aug/2017 14:24:11] "GET /events HTTP/1.1" 200 - 42.6906". So it seems like the "events" page is loading for 42 seconds (the whole runtime of the server in this case) and only after closing the server the page returns the result, which can then finally be displayed on the widgets.

When i refresh the page the events page also returns but the widgets stay empty. I guess upon refresh we call it again right away, which might stop the data from being displayed, but that doesnt sound right.

Now the open question is, why does the events page only return when shutting down the server, and how can that be fixed. I dont know more about this.

I read somewhere else that someone might hand in a pull request which migrates the webserver dashing is running on from "thin" to "puma", which might resolve this issue, so I am looking forward to that!

[dnsmichi]

To be honest, I have no idea here. If one comes up with a PoC/PR for puma, much appreciated.

[dnsmichi]

Please continue in #47 which acts as a general issue to replace thin with something else, or find any other solution.