-
Notifications
You must be signed in to change notification settings - Fork 23
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
can't view puppetdb dashboard inside foreman, as template is missing #51
Comments
Just hit this issue with Foreman 1.17.0 and tfm-rubygem-puppetdb_foreman-4.0.0-1.fm1_17.el7.noarch |
Hey, |
I applied this fix @timogoebel and at least i get no errors now :) The PuppetDB Nodes page works fine, however the PuppetDB Dashboard appears to not load anything - this is clean install of PuppetDB and the foreman plugin Note based on Ubuntu not CentOS |
I note specifically this is because the following static resources are not proxied correctly http://localhost:8080/pdb/dashboard/d3.v2.js as a quick fix i downloaded these files manually into the public directory of my foreman install and things work again |
@anthonysomerset: Can you send me a screenshot of your Browser's console? Then I can take a look what's wrong. Alternatively, the correct path of the resources in puppetdb would help. |
Hi,
The installed packages:
Let me know if you need any more infos for debugging. |
Actually, I don't want to maintain the puppetdb dashboard any longer. Proxying this through foreman is a heck of a hack. |
Personally I used the proxied dashboard in Foreman as the way to view the dashboard to just get a sense of things in PuppetDB. I only exposed the non-SSL port for PuppetDB to Foreman server for purposes of viewing the dashboard. If the metrics in dashboard could be accessed via PuppetDB API, then can imagine just building a new dashboard based on those collected values. |
@treydock: I believe they are exposed via API. Can you name the parameters you'd want to see in the dashboard? |
The fact they all show as graphs with some amount of history is useful but can imagine would be challenging in Foreman unless this plugin resorted to storing historical metrics in the database in a way they didn't grow infinitely. Having just real-time numbers would still be useful though, especially the timing related metrics and JVM Heap. I don't know enough about the resource duplication and catalog duplication to know their usefulness so left those out of the list. |
Just wanted to let know, that I applied the same fix to Foreman 1.18 and it works there as well. |
@timogoebel Did you have any more thoughts on this? Not that I really use this feature much (I've only just noticed it's broken!) |
@alexjfisher: I believe the best approach would be to drop this feature for now. It's too much of a hack imho. |
Sure. Removing the feature is preferable to it being there but broken. |
hi,
i get following message inside 1.17-rc2 as i try to view the puppetdb-dashboard:
foreman is installed on a deb9 machine.
KR
David
The text was updated successfully, but these errors were encountered: