Thanks. I will check the state of those dashboards you referenced at swarm.hiveeyes.org[1] and then get back to you after whitelisting this domain.
That depends on what you mean by “forwarded”. If they will redirect to http://sheffieldair.gopingur.com/, then they will not have to be handled in any way as the former one is the one and only origin talking to our Grafana.
Please make sure to get Let’s Encrypt certificates. While I don’t know for sure, browsers might be increasingly picky about mixing SSL vs. non-SSL resources [2].
With kind regards,
Andreas.
JFYI: They should really be on weather.hiveeyes.org to which you should link/embed by using grafana.panodata.net. That might be just a detail, but actually there are two different machines where the former one (swarm) should be dedicated to all things Hiveeyes data acquisition. You are partly seeing bits of the development history there where we haven’t been able to keep up with appropriate maintenance. Now, when handing out embed-links, we would like to improve the situation on that beforehand. ↩︎
Admittedly – probably only into one direction when embedding non-SSL content on SSL-based pages. But nevertheless, I believe it is to some extent obligatory these days to serve SSL-only and Let’s Encrypt will get you certificates without much ado. ↩︎
Yes, that’s right it will redirect to http://sheffieldair.gopingur.com/. I have asked the IT guys here at the University to check on the encryption - good point.
AH, didn’t know about the swarm. I will use the panels from the dashboards in weather.hiveeyes.org version then, thanks for letting me know.
sorry for interrupting. I’ve just deliberately updated your post to use grafana.panodata.net[1] instead of writing another response, I hope you don’t mind.
In this manner, we will be able to better keep track of the stuff we hand out to people to use within their own applications.
For example, when the demand grows and we will be able to cope, we might want to serve this endpoint from a different machine and so forth. It is just about flexibility on our end and respective planning into the future.
With kind regards,
Andreas.
It is just an alias to the very same Grafana instance for now. ↩︎
That is fine, I can imagine how difficult can it be to maintain all these. Even the visible part of the work is tremendous, I keep loosing track. Thanks for the changes, that helps. Please let me know as and when I would be able to use them. Excited to bring the data on the website!
I’ve just added the domain sheffieldair.gopingur.com to the whitelist of the frame-ancestors content security policy. Let me know if this works for you.
I just recognized that some of the map panels are displaying PM10 particulates, while others are displaying PM2.5 ones. Let me know what would fit your bill better. Primarily taking care about the whole machinery behind the infrastructure, I am personally not that much into the domain specific details of particulate measurements (cc @wtf).
Thank you, just to confirm, the panels work now on dev website. You’re a star!
Can I request to whitelist https://sheffieldair.co.uk/ as well please, my bad. The site is actually live here till we obtain .ac.uk domain from JISC. Thanks so much.
Hello Andreas, Good Morning. I was just going through the map panels on the GB dahboard. While you have changed it to PM2.5 and when I hover on any sensor points - it does show the PM2.5 measurements, but in brackets say P10. Maybe some text needs to change?
Lovely, thanks.
I have added a modified ‘About’ panel copied from the dashboards to give the credits on the website, Hope this is okay, please let me know if any changes required.
Is there a way to improve the loading of the dashboard? Currently, It takes roughly 23 seconds on my computer.
While it takes roughly 15 seconds on my machine, I well hear you that there is definitively room for improvements.
I’ve just created Improve Grafana panel load times for keeping track of this issue. As this will need us to go back to the machine room and maybe rethink and adjust things we have been conceiving some years ago already, I humbly ask for your understanding that this will probably need some time to be resolved.