Many issues with monitoring is due to the OS date/time. For example, if a change in the date/time settings resulted in the historical stat data being incorrect. You may see "time jump" errors in the access log. To resolve this, you will need to make sure that your date/time/timezone settings are correct for your OS, archive or move the contents of the stats folder in your Wowza installation, and restart the Wowza services to re-generate the stats files.
The stats files are corrupted. If so, follow the resolution in step 2 above.
We've seen this occur when the Virtual Host can't assign a Host Port due to some other process being bound to it. So if it does happen for anyone else check your wowzastreamingengine_access.log for any BIND failures being reported. If so then change the port on one of the services to prevent them from clashing.
Was there any resolution to this? I'm having the same issue.
Since I was running a test install on a test server I just reloaded the a new VM to resolve the issue. I suspect there was a java issue there was a java upgrade that took place after prior to the dashboards going blank. WSE functioned as expected except for monitoring. I was testing an additional monitoring tool also WMSPanel which also failed to work on that install. So the short answer may be to do a fresh install if that's possibility or check the version of java installed and see if an upgrade took place recently.