Nagios 如何实现自定义多功能告警

【推荐】2019 Java 开发者跳槽指南.pdf(吐血整理) >>>

Nagios 是一个插件式的监控系统，可以监控服务的运行状态和网络信息等，并能监视所指定的本地或远程主机参数以及服务，同时提供异常告警通知功能等。Nagios 支持客户端的数据采集，通过编写客户端插件，可以获取各种监控数据，并提供了 Web 管理界面进行数据查询。其产品的主要功能侧重于监控服务的可用性，根据设置的阀值进行告警，但大部分告警逻辑都是通过监控插件实现的。

目前 Nagios 告警支持的通知方式有短信和邮件，但是很明显，这两种通知方式会导致重要级别的告警无法及时查看，并解决相关问题，而且在产生告警风暴的时候，这两种通知方式就更无法满足用户的多样化通知需求，于是如何将告警通过用户的多样化需求达到多种化通知方式，并且有效的避免告警风暴，就成了目前的首要解决问题

智能告警平台 Cloud Alert是睿象云自研的一款告警管理平台，就能够完美解决这个问题！用户可以将告警通过不同的需求，指定多种化通知方式，目前支持的通知方式有电话、短信、微信、邮件、APP、钉钉等；并且当告警风暴来临时，用户可以通过勾选算法智能降噪或设置告警压缩规则，使得相同类型的告警进行压缩，有效的避免告警风暴。用户也可以将不同的监控平台接入到 Cloud Alert 内进行统一化管理。

接下来就说下是如何设置的吧~

主要分为三大部分，首先是将 Nagios 集成到此平台当中，其次设置分派策略，也就是指定条件（用户自定义）下的告警发生时通知的人，最后是设置通知策略，根据用户自身需求设置多元化的通知方式。

首先肯定是进入官网 www.aiops.com，登录账号。在这里插入图片描述

一．Nagios集成

在 Cloud Alert 中创建 Nagios 应用，点击集成 — 监控工具 — Nagios
填写“应用名称”，点击“保存并获取应用key”
下载Agent安装包

在 Nagios 服务器中，使用 root 或 nagios 用户下载

wget https://download.aiops.com/ca_agent/nagios/ca_agent-4.1.3.1-linux-x64.tar.gz

安装Agent

注：下文以Nagios默认安装路径/user/local/nagios/为例，如果你的Nagios服务器不是安装在该目录，请自行替换。

tar -xzf ca_agent-4.1.3.1-linux-x64.tar.gz

cp -R ca_agent /usr/local/nagios/libexec/

cp ca_agent/plugin/nagios-plugin/nagios /usr/local/nagios/libexec/

chmod +x /usr/local/nagios/libexec/nagios

cp ca-agent/plugin/nagios-plugin/cloudalert.cfg /usr/local/nagios/etc/objects/

修改配置

①修改/usr/local/nagios/etc/objects/cloudalert.cfg，设置pager为刚才点击保存所获取的appkey

vi /usr/local/nagios/etc/objects/cloudalert.cfg

define contact{

contact_name cloudalert ; The name of this contact template

alias ca ;

service_notification_period 24x7 ; service notifications can be sent anytime

host_notification_period 24x7 ;

host notifications can be sent anytime

service_notification_options w,u,c,r,f,s ; send notifications for all service states, flapping events, and scheduled downtime events

host_notification_options d,u,r,f,s ;

send notifications for all host states, flapping events, and scheduled downtime events

service_notification_commands notify-service-by-cloudalert ; send service notifications via email

host_notification_commands notify-host-by-cloudalert ; send host notifications via email

pager -- --处填入您新建应用时生成的appkey ;

}

② 修改/usr/local/nagios/etc/objects/contacts.cfg，新增cloudalert到默认联系组

vi /usr/local/nagios/etc/objects/contacts.cfg

define contactgroup{

contactgroup_name admins

alias Nagios Administrators

members nagiosadmin,cloudalert

}

③ 修改/usr/local/nagios/etc/nagios.cfg，将cloudalert.cfg新增到nagios.cfg中

vi /usr/local/nagios/etc/nagios.cfg

cfg_file=/usr/local/nagios/etc/objects/cloudalert.cfg

④ 可选：为了让告警信息显示更加友好，建议修改nagios.cfg由原来us更改为iso8601

vi /usr/local/nagios/etc/nagios.cfg

重启Nagios

重启前请检查配置是不是正确

/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

请使用root账号重启Nagios

service nagios restart

集成结果验证

登录Nagios页面控制台发送通知

注：请确认对应服务的notifications_enabled为1

define service{

use local-service ; Name of service template to use

host_name localhost

service_description Tomcat18080

check_command check_http18080

notifications_enabled 1

} 在这里插入图片描述 8. 查看agent日志，出现success字样代表成功

tail -f /usr/local/nagios/libexec/ca_agent/log/agent.log

10-05-2015 15:48:53,056 CST INFO [main] [com.upyoo.agent.NagiosClient@45] start to call alert ...

10-05-2015 15:48:53,063 CST INFO [main] [com.upyoo.agent.CommandClient@82] ``alarmName:PROBLEM Service Alert: 127.0.0.1/Tomcat18080 is CRITICAL

10-05-2015 15:48:53,064 CST INFO [main] [com.upyoo.agent.CommandClient@82] ``alarmContent:localhost/127.0.0.1/Tomcat18080 ``connect to address 127.0.0.1 and port 18080: Connection refused Date/Time: 2015-05-10 15:48:52

10-05-2015 15:48:53,064 CST INFO [main] [com.upyoo.agent.CommandClient@82] ``entityName:127.0.0.1/Tomcat18080

10-05-2015 15:48:53,066 CST INFO [main] [com.upyoo.agent.CommandClient@82] priority:CRITICAL

10-05-2015 15:48:53,066 CST INFO [main] [com.upyoo.agent.CommandClient@82] ``app:9c4bc722-6677-9fc9-fbdc-003d8977d17e

10-05-2015 15:48:53,067 CST INFO [main] [com.upyoo.agent.CommandClient@82]

10-05-2015 15:48:53,068 CST INFO [main] [com.upyoo.agent.CommandClient@82]

10-05-2015 15:48:53,069 CST INFO [main] [com.upyoo.agent.CommandClient@82]

10-05-2015 15:48:53,105 CST INFO [main] [com.upyoo.agent.CommandClient@58] start to post url:http://api.aiops.com/alert/api/event

10-05-2015 15:48:53,180 CST INFO [main] [com.upyoo.agent.CommandClient@65] body:{"app":"9c4bc722-6677-9fc9-fbdc-``003d8977d17e","alarmContent":"localhost/127.0.0.1/Tomcat18080 connect to address 127.0.0.1 and port 18080: Connection refused Date/Time: 2015-05-10 ``15:48:52","eventId":"8G8OGOYUCOOLOENYOGGENOOOOONYNOLU","priority":"3","alarmName":"PROBLEM Service Alert: 127.0.0.1/Tomcat18080 is CRITICAL","eventType":"trigger","entityName":"127.0.0.1/Tomcat18080"}

10-05-2015 15:48:53,775 CST INFO [main] [com.upyoo.agent.CommandClient@68] result:{"result":"success","message":null,"data":"3516","totalCount":0,"code":"200"}