集成不同的 Nagios Web 服务器

发布于 2024-09-07 20:03:50 字数 120 浏览 9 评论 0原文

我有不同的站点,每个位置都有 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.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

彡翼 2024-09-14 20:03:50

您可以采取两种方法。

  1. 像在每个位置一样安装新的 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。我这里还有安装 NSClient 的说明 http://blog.gnucom.cc/?p=201.

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

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

希望这有帮助。 :)

There are two approaches that you can take.

  1. 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.

  2. 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. :)

森林很绿却致人迷途 2024-09-14 20:03:50

您可能正在寻找集中式查看工具。有许多不同的选项可供选择。

  1. Nagiosfusion
  2. MK Livestatus
  3. Nagcen
  4. Thruk

A centralized view tool may be what you are looking for. There are a number of different options available.

  1. Nagiosfusion
  2. MK Livestatus
  3. Nagcen
  4. Thruk
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文