Hello,
Years ago we had the Nagios team write a custom dashlet for us, called Open Service Problems (displays unacknowledged service problems on a dashboard). We are currently running Nagios XI 5.4.13 and the dashlet works. However, once I upgrade to XI 5.5.9 the dashlet no longer loads, it sits and spins constantly.
Are there updates available to this dashlet so that it will work in the latest version of XI?
Open Service Problems Dashlet no longer works in XI 5.5.9
-
westernuniv
- Posts: 120
- Joined: Tue Aug 21, 2012 9:29 am
-
npolovenko
- Support Tech
- Posts: 3457
- Joined: Mon May 15, 2017 5:00 pm
Re: Open Service Problems Dashlet no longer works in XI 5.5.
Hello, @westernuniv. I imported this dashlet into my XI and it wasn't working either. I submitted the code to the dev team for internal review. As of right now, I don't have an estimate on how soon this will get reviewed.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
-
westernuniv
- Posts: 120
- Joined: Tue Aug 21, 2012 9:29 am
Re: Open Service Problems Dashlet no longer works in XI 5.5.
Thanks, I'll wait to receive the updated code so we can start using this dashlet on our dashboards.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Open Service Problems Dashlet no longer works in XI 5.5.
This dashboard was decommissioned, however I fiex it and you can upload the attached through Admin -> Manage dashboards
You do not have the required permissions to view the files attached to this post.
-
westernuniv
- Posts: 120
- Joined: Tue Aug 21, 2012 9:29 am
Re: Open Service Problems Dashlet no longer works in XI 5.5.
That's great! Thanks!
Confirmed it is now working as expected.
Confirmed it is now working as expected.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Open Service Problems Dashlet no longer works in XI 5.5.
Excellent!@westernuniv wrote:That's great! Thanks!
Confirmed it is now working as expected.
Locking thread