Small useful things. How to make access from nagios / icinga to the host management interface through Google Chrome and MS IE browsers

Introduction

When working with nagios / icinga, sooner or later a situation arises when it is annoying to run separately each time into the host control interface — to click somewhere, to drive addresses and names with your hands (the login / password is sacred). It would be best to have a link on hand in nagios / icinga for a detailed analysis of the source of anxiety and troubleshooting. Googling the Internet on this topic did nothing, because the developers of nagios and icinga do not omit such “trifles”, but the problem remains - we still want a convenient interface for the monitoring system.



The ability to fasten management interfaces to nagios / icinga hosts, although through places not intended for this, still exists in this small article, I would like to share how this can be done.

Properly use Notes URL

In any configurator (for example, nagiosql or nconf) we have the Notes URL available, which is intended to take notes on the behavior of the host, but usually it is not used at all and we can use it for our purposes. After filling it in, the daddy icon appears in the host display; by pointing the mouse at it, we will be able to go to the host control interface.



For different hosts, we may have different versions of the Notes URL, which will also behave differently in different browsers. For example:

')





The easiest thing to do with http access is in our example ilo2 on the hp-srvr-blade10-hardware blade server (Hewlett-Packard bl460c g6). By clicking on the folder icon, the ilo2 interface will open in the same window:







Good? Yes. It is very convenient for printers and any other devices where the http management interface is the main one.



And then a low voice is heard from the back row: “But we would also have some kind of rdp connection ... It’s necessary to go to the Windows server ...”.



And here everything is a bit more complicated.

RDP for Google Chrome

If you have Chrome, then under it in the Chrome store there is an excellent Chrome RDP extension. This is a full-fledged rdp client that runs from a browser. Perfectly supports the Russian keyboard, there are no significant differences from Microsoft RDP.



But for our case, Chrome RDP will have two small spoons of tar:

• He does not know how to open connections in the current nagios / icinga window (this is most likely a restriction of the parent application). The problem is solved if you open the rdp-window by right-clicking on the host and opening the connection in a new tab. Then everything will be fine and beautiful. Various chrome extensions that allow you to open a clickable link in a new tab do not help.
• Chrome RDP client is paid. It is inexpensive - about $ 5, the version, in fact, the trial version - works for exactly one month, and then the “Dengi come on!” Window starts to be thrown out. Each time, dragging a license from computer to computer (and monitoring systems often from unexpected locations) is not very good. Buying and installing wherever possible is also wrong.

If the restrictions do not scare us, then install Chrome RDP, buy and register a license. Copy-paste in Notes URL view sequence

chrome-extension: //cbkkbcmdlboombapidmoeolnmdacpkch/nacl.html#$HOSTADDRESS$

Save the configuration in nagios / icinga; now after clicking with the right button on the host and choosing to open the link in a new window, we will run the RDP client for this server.



There are many RDP clients under hrome, but most of them go through the secondary server. Either it should be deployed in the corporate network; or, which is many times more dangerous, is someone's server on the Internet through which your passwords are transmitted. We must always bear this in mind and not neglect the rules of elementary security.

RDP for MS Internet Explorer

To start the rdp client from MSIE, register the protocol as CustomURL. There is a fairly detailed document in MSDN that describes this mechanism and the sequence of steps for manually registering a protocol: Registering an Application to a URI Scheme



Of course, you can do everything with your hands, but there is a small utility that simplifies this process and does not make mistakes when manually editing the registry. We swing it from here .



A couple of installation moments:

• Administrator rights are required; by default, the program tries to copy itself to C: \ Windows \ System32.
• For everything to work on 64-bit Windows 7 / Windows Vista systems, you need to copy the utility in C: \ Windows \ SysWOW64

Run it, click on the add protocol (Add) and enter something like this:







where% Authority%, in this case, is the host + port combination. If the port is non-standard, then you can manually specify everything -% Host%: 3888, for example.



In the same way, you can register and ssh protocol, if for ideological reasons you do not want to use the http-interface. This example is shown on the utility website .



After all the manipulations performed, using MS IE, you can run the rdp client in one click and quickly manage the hosts from the nagios / icinga monitoring system.



You can, of course, ask yourself, is it really necessary to get in touch with IE when we have lots of other great browsers? It is necessary. At least, again for two reasons:

• For IE, the registration of a user protocol is made much easier (see above).
• IE like iron makers, like Hewlett-Packard. HP iLO (especially old versions), honestly says that working with it is better through IE, and all other browsers are limited to those supported. The management interface of HP EVA Onboard Administrator can display information with errors if it opens even through the latest Chrome or FF.

By the way, despite the presence of the registered CustomURL in the system, Chrome completely ignores them. This problem was understood in Google Groups, but there is still no universal stable solution to the problem. If someone knows how to run mstsc.exe from under Google Chrome - let me know.