Nagios Support Forum

I am testing out the log server on a free trial copy. I've been doing everything fine until now when the save button is greyed out and and doesn't turn red or green. I am unable to save anything so my dashboard resets when I close or refresh the tab. I've used it for 2 days now and this just started this morning. Is this an intended feature of the trial copy or is this a glitch of some sort? I checked the home page, and it says I am running on the latest version of Nagios Log Server as well.

Hi @PSI-Admin,

It sounds like you are editing an existing dashboard. In order to save it, you have to give it a unique name. Namely, rather than trying to hit the save button, click the downward-pointing arrow directly to the right, give it a new name, and save it either as a normal dashboard or a global dashboard.

Let us know if this works for you and if you have any other questions.

Thank you!

My Dashboard I'm currently editing has a unique name and is saved as a normal dashboard. After I give it a new name and save it as either normal dashboard or a global dashboard it still does not let me save the dashboard.

Hi @PSI-Admin,

I agree there's something odd going on with this functionality. I am able to edit some dashboards, but not others, particularly after saving a new dashboard. I've logged an issue for this. In the meantime, are you able to work around this issue by making changes to your dashboard and saving them as a new dashboard?

That will work in the meantime, is there going to be a fix for it eventually?
Thanks.

I don't have a timeline for you, but I did create an issue report for the bug in our development queue.

The dashboard's save icon does not appear to be operating properly. Clicking the icon does not initiate the saving process or offer any feedback. This problem hinders users from storing their work, which reduces productivity. Urgent care is required.
Fm Whatsapp

@Daisy98, did you try the approach gwesterman spelled out above? Save it as a new dashboard from the arrow next to the icon? jsimon wrote up an internal issue for us to take care of it, we just haven't gotten to it yet.