Setting defaults for new statusmap in Nagios Core 4.1.1

[Langalf]

The new "Current Status ... Map" (Network Map For All Hosts) in Nagios Core 4.1.1 seems to ignore the statusmap_background_image, default_statusmap_layout, and default_statuswrl_layout settings from cgi.cfg that applied to the old status map.

I can select the "Legacy" status map and see what I want, but I like some of the features in the new map. I would like to have the default for the new map be as close to the legacy as possible. I can select the settings from the Nagios Map menu, but there seems to be no way to save the changes. Also, there does not appear to be a setting for a background image on this menu.

Is there any way to apply a background image to the new Nagios Map? Is there any way to save default settings so I do not have to enter them each time?

[hsmith]

You can post what you believe to be bugs/feature requests on the Nagios Core GitHub located here.

If you want to edit the statusmap currently, you can find all of the files for the map under/usr/local/nagios/share. You should be able to make whatever javascript tweaks and HTML tweaks you want to it if the new version is not suiting your needs.

Which default settings are you referring to?

[Langalf]

@hsmith,

As I mentioned in my post, there are settings for a background image and layout type (I want a custom layout) in the cgi.cfg file that sets defaults for the legacy statusmap.cgi. It seems to be possible to change the layout for the new status map on-the-fly, but I see no way to force a default setting like I could on the legacy statusmap using the settings in cgi.cfg. There also does not seem to be a way to force a background image.

I will take a look at the contents of /usr/local/nagios/share or its equivalent on my system (I am running Nagwin).

[rkennedy]

As @hsmith mentioned, if you believe this is a bug with Nagios Core submit it to the GitHub. Nagwin is a different product, which is not one of ours. Your best bet is to ask them for support.

[Langalf]

<sighs>

I never said or thought this was a bug. I am asking for help with a behavior the Nagios Core exhibits. It does not matter whether I am using a commercial implementation or not; the behavior is with the Nagios Core. I was directed to this forum by Nagios support. Clearly, they and I were in error to believe anyone here would have a clue.

Thank you.

[tmcdonald]

I was directed to this forum by Nagios support.

We are Nagios support. However Nagwin is not our product, even though it may be based on our product. For this reason, we do not provide support for Nagwin just as we do not provide support for Icinga, Naemon, or any of the other products that are Nagios-based. We have posts going back to 2012 that reinforce this: https://support.nagios.com/forum/viewto ... 938#p32938

Nagios XI is the commercial version of Nagios and is complete with easy install and configuration wizards. A 60 day trial can be downloaded here
http://www.nagios.com/downloadxi/

Nagios Core is the free community version, and while a great solid product does require manual configuration. Core can be downloaded here
http://www.nagios.org/download

Nagwin is a windows implementation of Nagios that was not produced by Nagios Enterprises, so I am not even familiar with where the correct place to download it would be.

If you would like to see a feature added or a bug addressed, you can open up an issue on our GitHub page, otherwise I would be happy to file one myself if you do not have an account, provided we are able to replicate the behavior in-house on a supported Core install.

Clearly, they and I were in error to believe anyone here would have a clue.

I don't think that was necessary. If you are going to post, please keep it civil.

[Langalf]

I apologize for my snarky comment. I have posted my question as a feature request / bug report to GitHub.

Still and all, my original question, which relates generically to Nagios Core 4.1.1, stands. It is not a feature specific to a vendor implementation of Nagios. Does anyone know of a way to save default settings to the new Nagios Map? Would I need to modify the javascript? I am not real familiar with that language, so I am not sure how to proceed.

[tmcdonald]

It's not built-in at the moment (the developer who made these maps is no longer working on the project) and will not respect the cgi.cfg settings. I was able to hack it in, but it is not pretty. I edited /usr/local/nagios/share/map.html and changed the body tag like so:

<body ng-controller="mapCtrl" style="background-image: url('http://i.imgur.com/5SzPzEv.jpg');">

which uses the following image, though it is too big to inline here: http://i.imgur.com/5SzPzEv.jpg

You will need to mess a bit with the CSS if you have an image that is smaller than the screen, since it will probably tile itself.

You can follow the GitHub posting here: https://github.com/NagiosEnterprises/na ... /issues/86

For the sake of organization, I would like to continue this discussion on GitHub, so please let me know if this thread is okay to close.

[jfrickson]

Fixed by commit https://github.com/NagiosEnterprises/na ... 4667f42689
in branch https://github.com/NagiosEnterprises/na ... 4.1.2-Pre1