[MXS-1373] nagios checks shouldn't use ssh themselves Created: 2017-08-23 Updated: 2019-06-21 Resolved: 2019-06-21 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Plugin |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | Heinz Wiesinger | Assignee: | Todd Stoffel (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
Currently the supplied nagios check scripts use ssh to execute the checks on a remote host. However, both nagios as well as icinga have mechanisms to run checks on remote hosts that would be much better suited for that purpose. Furthermore, since the scripts require the use of ssh, there's effectively no good way to use nagios'/icinga's own mechanism to do remote host execution. It would be best if the checks just assumed they are run on localhost. That way the nagios/icinga admin can decide how to do remote host execution. |
| Comments |
| Comment by markus makela [ 2017-08-24 ] |
|
The scripts were most likely changed to support use of the maxadmin socket interface while the scripts themselves were still run from a remote host. Removing the use of ssh should be done since the monitoring systems are capable of executing the remote checks. For 2.2, the MaxScale REST API should be used to fetch the information instead of using maxadmin. |