-
Notifications
You must be signed in to change notification settings - Fork 47
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
Guidance modifying dashlet #127
Comments
I have also tried to use a host group, but it returns no result even though it works on the curl puts "Host listing: " + host_stats.to_s
|
I have also tried this
|
Hey Ben, from what I gathered, you want a widget showing a list of all host problems, is that right? You could do something like this:
This goes within the huge
This example will display all non- Does this help? |
Thank you for the response. Very helpful to see how you did this... However, I have tried using this to substitute my own HostGroup instead of 'dummy-hosts' and it does not seem to limit to just that group. It's still displaying service issues from all hosts. The actual hostgroup is defined in groups.conf and it loads correctly in Icinga2web with this filter:
|
Sorry for the long delay, would you mind sharing your edited |
Not a problem, thanks for the reply. Here are the files: |
Seems like you never actually use the data you prepare in your You might have to rearrange/uncomment some of the widgets, too. Let me know if I can be of further help. |
I could use a little guidance here. I want to create a public dashboard to show the status of various APIs that we have.
I am looking to modify the "Service Problems" to just show a list of hosts instead. I have a service group defined, but I cannot get the filter to work in the test/icinga.rb - and I'm not sure how I could adapt your "Service Problems" to be a list of "Main Services".
This works using the API to get the list that I want to use:
For example, I tried to define:
serviceFilter = "groups.service == mainnet"
but it results in an error:
The text was updated successfully, but these errors were encountered: