{"id":42026,"date":"2016-12-21T17:38:03","date_gmt":"2016-12-21T12:08:03","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=42026"},"modified":"2016-12-22T13:45:34","modified_gmt":"2016-12-22T08:15:34","slug":"how-to-integrate-nagios-with-pagerduty","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/how-to-integrate-nagios-with-pagerduty\/","title":{"rendered":"How to Integrate Nagios with PagerDuty"},"content":{"rendered":"

Nagios<\/a> is an open-source infrastructure monitoring tool<\/a>. It monitors your Hosts & Services that are defined\u00a0and\u00a0alerts you if any of the hosts or services go down by the different alert mechanism like email, SMS, etc.<\/p>\n

PagerDuty\u00a0is an enterprise incident resolution service that gives you an\u00a0alert on email, SMS & call. By integrating PagerDuty\u00a0with Nagios\u00a0you can get an\u00a0alert on call and can resolve or escalate it to the next level from the call directly.<\/p>\n

\"download\"\u00a0 \u00a0 \u00a0\u00a0\"Nagios-Logo\"<\/p>\n

Steps to integrate\u00a0PagerDuty with Nagios:<\/p>\n

1. Create a new service or edit existing service in your PagerDuty account.<\/p>\n

2. Add an Integration policy and select Nagios as an Integration\u00a0Type.<\/p>\n

\"Integrating<\/p>\n

3. Copy your integration key to configure alerts in Nagios server.<\/p>\n

\"Integrate<\/p>\n

4. Install PagerDuty on your Nagios Server:<\/p>\n

[code]
\nwget -O – https:\/\/packages.pagerduty.com\/GPG-KEY-pagerduty | sudo apt-key add –
\nsudo sh -c ‘echo &quot;deb deb\/&quot; &gt; \/etc\/apt\/sources.list.d\/pdagent.list’
\nsudo apt-get update
\nsudo apt-get install pdagent pdagent-integrations
\n[\/code]<\/p>\n

5. Create a new contact group on your Nagios server and add the code below. Enter your PagerDuty integration key that you copied in step 3, at the place of PAGERDUTY-SERVICE-KEY.<\/p>\n

[code]
\ndefine contact {
\ncontact_name pagerduty
\nalias PagerDuty
\nContact service_notification_period 24×7
\nhost_notification_period 24×7
\nservice_notification_options w,u,c,r
\nhost_notification_options d,r
\nservice_notification_commands notify-service-by-pagerduty
\nhost_notification_commands notify-host-by-pagerduty
\npager PAGERDUTY-SERVICE-KEY
\n}[\/code]<\/p>\n

6. Create a new command file or edit the existing command file and add the below code to it. If you are not creating a new command file in your Nagios config directory, you need to add the complete path of your command file in the Nagios main config file and restart the Nagios service.<\/p>\n

[code]define command {
\ncommand_name notify-service-by-pagerduty
\ncommand_line \/usr\/share\/pdagent-integrations\/bin\/pd-nagios -n service -k $CONTACTPAGER$ -t &quot;$NOTIFICATIONTYPE$&quot; -f SERVICEDESC=&quot;$SERVICEDESC$&quot; -f SERVICESTATE=&quot;$SERVICESTATE$&quot; -f HOSTNAME=&quot;$HOSTNAME$&quot; -f HOSTDISPLAYNAME=&quot;$HOSTDISPLAYNAME$&quot; -f SERVICEDISPLAYNAME=&quot;$SERVICEDISPLAYNAME$&quot; -f SERVICEPROBLEMID=&quot;$SERVICEPROBLEMID$&quot; -f SERVICEOUTPUT=&quot;$SERVICEOUTPUT$&quot;
\n}
\ndefine command {
\ncommand_name notify-host-by-pagerduty
\ncommand_line \/usr\/share\/pdagent-integrations\/bin\/pd-nagios -n host -k $CONTACTPAGER$ -t &quot;$NOTIFICATIONTYPE$&quot; -f HOSTNAME=&quot;$HOSTNAME$&quot; -f HOSTSTATE=&quot;$HOSTSTATE$&quot; -f HOSTDISPLAYNAME=&quot;$HOSTDISPLAYNAME$&quot; -f HOSTPROBLEMID=&quot;$HOSTPROBLEMID$&quot;
\n}[\/code]<\/p>\n

7. Add ‘Pagerduty’ user which you have created in step 5, in the main contact group that you are using to send alerts. \u00a0By default\u00a0Nagios uses ‘\/etc\/nagios3\/conf.d\/contacts_nagios2.cfg’ file and uses the admin contact group.<\/p>\n

[code]define contactgroup{
\n contactgroup_name admins
\n alias Nagios Administrators
\n members root,pagerduty \/\/ Adding PagerDuty User
\n}[\/code]<\/p>\n

8. Restart your Nagios service and you will start getting alerts if any host or service goes down.<\/p>\n

TroubleShooting:<\/strong><\/p>\n

1. You can check your PagerDuty Agent status running on your Nagios\u00a0server and stop\/start\/restart it too.<\/p>\n

[code]sudo service pdagent status \/\/ Check Agent Status
\nsudo service pdagent restart \/\/ Restart Agent[\/code]<\/p>\n

2. Send events manually on PagerDuty to check your integration key.<\/p>\n

[code]pd-send -k PD_SERVICE_KEY -t trigger -d &quot;Service Description&quot;
\npd-send –help \/\/ for more help[\/code]<\/p>\n

3. Check your Agent queue status by using below command.<\/p>\n

\"Integrate<\/p>\n

If you have configured multiple keys on your Nagios server, it will show you multiple entries against each key.<\/p>\n

4. To send error events again you can use retry command as below.<\/p>\n

[js]pd-queue retry -k YOUR-PAGERDUTY-KEY \/\/ retry givens key’s alert
\npd-queue retry -a \/\/ retry all keys’ alert[\/js]<\/p>\n

By following the above steps, you can use both the services as per your use case. Here is another blog giving\u00a0some useful configuration tips for configuring Nagios monitoring system<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Nagios is an open-source infrastructure monitoring tool. It monitors your Hosts & Services that are defined\u00a0and\u00a0alerts you if any of the hosts or services go down by the different alert mechanism like email, SMS, etc. PagerDuty\u00a0is an enterprise incident resolution service that gives you an\u00a0alert on email, SMS & call. By integrating PagerDuty\u00a0with Nagios\u00a0you can […]<\/p>\n","protected":false},"author":678,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":34},"categories":[1174,2348,1],"tags":[4315,4316,1500,4314,4313],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/42026"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/678"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=42026"}],"version-history":[{"count":1,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/42026\/revisions"}],"predecessor-version":[{"id":53733,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/42026\/revisions\/53733"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=42026"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=42026"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=42026"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}