集成不同的Nagios网络服务器(Integrate different Nagios webservers)

集成不同的Nagios网络服务器(Integrate different Nagios webservers)

我有不同的站点在每个位置运行4到5台服务器。 所有位置都有一个带Nagios的监控服务器。 现在我想创建一个中心位置，并希望结合在每个位置运行的所有nagios服务。 谁能指点我这些类型的工作的一些文件。

I have different sites running with 4 to 5 server at each location. All the locations have one monitoring server with Nagios. Now I want to create a central location and want to combine all the nagios services running at each location. Can anyone please point me to some documentation for these type of jobs.

最满意答案

您可以采取两种方法。

像在每个位置一样安装新的Nagios核心，并在每个远程主机上执行活动检查。 您可能最终会在每个位置的每个远程主机上安装NRPE，并可以阅读此文档以获取详细信息： http ： //nagios.sourceforge.net/docs/nrpe/NRPE.pdf 。 如果远程服务器是Windows服务器，则可以将NSClient用于NRPE为Linux主机执行的大部分操作。 这有效地集中了您的监控服务器。 我还写了一些如何使用NRPE来运行特权命令的样式条目http://blog.gnucom.cc/?p=479或运行事件处理程序http://blog.gnucom.cc/?p=458 。 如果您厌倦了安装NRPE，可以在http://blog.gnucom.cc/?p=185使用我的脚本。 我还有http://blog.gnucom.cc/?p=201安装NSClient的说明。

像在每个位置一样安装新的Nagios核心，并通过指示远程Nagios核心将其结果提供给新的中央Nagios核心的被动命令文件来执行被动检查。 我自己没有这样做，所以我将在这里指出社区文档http://nagios.sourceforge.net/docs/2_0/passivechecks.html 。 您可以查看我的事件处理程序帖子，以设置将检查发送到主服务器的事件处理程序。

根据我的个人经验，我提到的第一个选项更容易实现，并且易于管理。 但是，随着服务器机队的增长，您将开始看到主要Nagios核心的主要CPU瓶颈。 这是被动检查将变得有益的地方，因为主要的Nagios核心只是等待将关键检查发送给它而不是必须自己检查它们。

希望这可以帮助。 :)

There are two approaches that you can take.

Install a new Nagios core as you did at each location and perform active checks on each of the remote hosts. You'll likely end up installing NRPE on each of the remote hosts at each location and can read this document for the details: http://nagios.sourceforge.net/docs/nrpe/NRPE.pdf. If your remote servers are Windows servers, you can use NSClient to much of the same things that NRPE does for Linux hosts. This effectively centralizes your monitoring server. I also wrote some how-to style entries for using NRPE to run privileged commands http://blog.gnucom.cc/?p=479 or to run event handlers http://blog.gnucom.cc/?p=458. If you get tired of installing NRPE, you can use my script here http://blog.gnucom.cc/?p=185. I also have instructions to install NSClient here http://blog.gnucom.cc/?p=201.

Install a new Nagios core as you did at each location and perform passive checks by instructing the remote Nagios cores to feed their results to the new central Nagios core's passive command file. I haven't done this myself, so I'm going to point you to the communities documentation here http://nagios.sourceforge.net/docs/2_0/passivechecks.html. You could probably look at my event handler post to set up event handlers that send checks to the main server.

From my personal experience, the first option I mentioned is easier to implement, and is far easy to administer. However, as your server fleet grows you'll start seeing major CPU bottlenecks with the main Nagios core. This is where passive checks would become beneficial, as the main Nagios core simply waits for critical checks to be sent to it rather than having to check them itself.

Hope this helps. :)