-
Notifications
You must be signed in to change notification settings - Fork 48
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
No data on icinga2-Dashboard #115
Comments
Hi Rudi, thank you for providing so much information already. I reproduced your issue and it looks like v3.1.0 broke something I did not notice before. I will have to look into the matter further, until then you can try using v3.0.0 by cloning the tag:
v3.0.0 worked just fine on 'your' setup for me. I will report back in this thread once I sorted out the issues with v3.1.0 |
Hi again, I pushed some minor changes to It would be nice if you could confirm that the changes work for you so I can close this issue :) Best, |
Hi Daniel, thanks for the quick feedback! With the current version the access works again without problems. Also in the LOG now no errors are displayed. Thanks again! |
Great, glad we could fix your issue that quickly! |
we have recently installed the Icinga2 dashboard, unfortunately no information from Icinga2 is displayed after calling the page:

Steps to Reproduce (for bugs)
So far so good...
Unfortunately, no data is displayed when calling the Dashing page.
Your Environment
gem list --local dashing
): dashing (1.3.7)ruby -V
): ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux]git show -1
): commit d7fd55d (HEAD -> master, origin/master, origin/HEAD)git diff
):From our point of view, the access from the dashboard to the Icinga2 API is working (see HTTP 200), does anyone have a tip for us on how to fix it?
Thanks a lot for the help!!!
Greetings Rudi
The text was updated successfully, but these errors were encountered: