{"id":7889,"date":"2019-01-08T14:05:46","date_gmt":"2019-01-08T18:05:46","guid":{"rendered":"http:\/\/dougmcclure.net\/blog\/?p=7889"},"modified":"2019-01-30T20:51:37","modified_gmt":"2019-01-31T00:51:37","slug":"nagios-xi-pagerduty-the-path-to-a-monitoring-service","status":"publish","type":"post","link":"https:\/\/dougmcclure.net\/blog\/2019\/01\/nagios-xi-pagerduty-the-path-to-a-monitoring-service\/","title":{"rendered":"Nagios XI & PagerDuty: The path to a \u201cMonitoring Service\u201d"},"content":{"rendered":"\n

Nagios (Core\/XI) is one of the top 5 most widely integrated tools across PagerDuty\u2019s 10K+ customers providing fundamental host and service monitoring and alerting capabilities. During my time here at PagerDuty, I\u2019ve had the opportunity to work with very very large and well established<\/g> enterprises and the latest up and coming start-ups \/ DevOps teams all still relying on good old Nagios monitoring for their infrastructure. I remember the SysAdmin teams I worked with back in the 2000\u2019s using early versions of Nagios, it\u2019s certainly been around for a long time and works well for the basics.<\/p>\n\n\n\n

From what I\u2019ve seen, many of PagerDuty\u2019s customers take a \u201cset it and forget it\u201d approach in their integrations. They\u2019ve followed the super simple integration guide (e.g. Nagios XI<\/a>) and created a \u201cmonitoring service\u201d in PagerDuty. In this configuration, Nagios host or service templates are updated to send all Nagios alerts to one single PagerDuty service integration key (the \u201cPagerDuty Contact\u201d pager<\/g> number) and ALL alerts are sent to PagerDuty notifying on-call responders of the latest Nagios alert. The key here with this default configuration is that everything monitored in Nagios whether it is a Windows or Linux server, network device, database or web server, all of the alert notifications are sent to the same \u201cPagerDuty Contact\u201d (the PagerDuty service) and notify whoever is on that single service’s escalation policy. Most integration guides include an FAQ section at the bottom of the guide with pointers on extending the default integration to address this, but few seem to go down this path. This default configuration pattern isn\u2019t the best practice for an ideal operational response and use of PagerDuty.<\/p>\n\n\n\n

When I say \u201cset it and forget it\u201d, what I\u2019m really saying is that the integration well-established up so quickly and \u2018just works\u2019, that teams just move<\/g> on to the next thing vying for their attention in their environment and accept what they have as \u2018good enough\u2019.  Some teams have more maturity within their team\/processes or have dedicated FTEs solely responsible for the care and feeding of their Nagios configurations as part of their configuration management, CI\/CD or similar release process.  Over time, the daily demands of the business and ops prohibit going back and optimizing the Nagios to PagerDuty integration to properly address many of the shortcomings in the default integration guide available today.<\/p>\n\n\n\n

What I\u2019d like to drill in on here are a few of these default configurations and their resulting alert, incident and reporting artifacts within PagerDuty and the operational implications over the next few blog posts how to move beyond the defaults to a best practice configuration in both Nagios and PagerDuty.<\/p>\n\n\n\n

The Guts of the Nagios XI – PagerDuty Default Integration<\/strong><\/p>\n\n\n\n

The core of the PagerDuty – Nagios XI integration comes down to two parts, the Nagios XI Contact configuration and the Nagios XI Command (and associated pd-nagios python script). Essentially, the contact defines the alert notification conditions and whom (or what) to send the notification details to and the command receives the alert notification metadata (via Nagios macros) and passes this data into the pd-nagios script resulting in a post to the PagerDuty Event API v1.<\/p>\n\n\n\n

In the service notification example below, when a service alert is triggered on a host, the configured contact alert conditions are evaluated the service notification command is executed. The default \u2018notify-service-by-pagerduty\u2019 command is called passing in a number of parameters to the pd-nagios python script.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Command Line:<\/strong> \/usr\/share\/pdagent-integrations\/bin\/pd-nagios -n service -k $CONTACTPAGER$ -t “$NOTIFICATIONTYPE$” -f SERVICEDESC=”$SERVICEDESC$” -f SERVICESTATE=”$SERVICESTATE$” -f HOSTNAME=”$HOSTNAME$” -f SERVICEOUTPUT=”$SERVICEOUTPUT$”<\/p>\n\n\n\n

This simple Nagios command and associated executable script and parameters is<\/g> where everything comes together. Let’s review this in more detail.<\/p>\n\n\n\n

-n [service|host]: notification_type:<\/strong> This parameter is used to signify if this is a service or host notification from Nagios. It’s used in the pd<\/g>–nagios<\/g> script to set up which macro values are mapped into PagerDuty event payload fields. This value is displayed in the alert key field.<\/p>\n\n\n\n

-k $CONTACTPAGER$<\/strong>: This is the pager<\/g> number\/address for the Nagios contact. This value is taken from the pager<\/a><\/g><\/em> directive in the contact definition<\/a>.  This macro value maps into the PagerDuty Event API v1<\/a> service_key<\/strong> field and represents the “Integration Key” for the Nagios XI integration configured on the PagerDuty service. This could also be an integration key for a Custom Event Transformer (CET) or the Global Event Routing API key. Set in step #12 of the PagerDuty – Nagios XI integration guide.<\/p>\n\n\n\n

-t $NOTIFICATIONTYPE$<\/strong>: A string identifying the type of notification<\/a> that is being sent (“PROBLEM”, “RECOVERY”, “ACKNOWLEDGEMENT”, “FLAPPINGSTART”, “FLAPPINGSTOP”, “FLAPPINGDISABLED”, “DOWNTIMESTART”, “DOWNTIMEEND”, or “DOWNTIMECANCELLED”). This macro value maps into the PagerDuty Event API v1<\/a> event_type<\/strong> field. Nagios XI \u201cPROBLEM\u201d maps to event_type \u2018trigger\u2019, \u201cACKNOWLEDGEMENT\u201d maps to event_type \u2018acknowledge\u2019 and \u201cRECOVERY\u201d maps to event_type \u2018resolve\u2019.<\/p>\n\n\n\n

-f $SERVICEDESC$<\/strong>: The long name\/description of the service (i.e. “Main Website”). This value is taken from the service_description<\/a><\/em> directive of the service definition<\/a>. This macro value is used in the PagerDuty incident description, alert key, service and custom details fields.<\/p>\n\n\n\n

-f $SERVICESTATE$<\/strong>: A string indicating the current state<\/a> of the service (“OK”, “WARNING”, “UNKNOWN”, or “CRITICAL”). This macro value maps into the PagerDuty Event API v1<\/a> severity<\/strong> field and is used in the PagerDuty incident description, severity, state and custom details fields.<\/p>\n\n\n\n

-f $HOSTNAME$<\/strong>: Short name for the host (i.e. “biglinuxbox<\/g>“). This value is taken from the host_name<\/a><\/em> directive in the host definition<\/a>. This macro value is used in the PagerDuty incident description, alert key, source, host and custom details fields.<\/p>\n\n\n\n

-f $SERVICEOUTPUT$<\/strong>: The first line of text output<\/a> from the last service check (i.e. “Ping OK”). This macro value is used in the PagerDuty incident service output and custom details fields.<\/p>\n\n\n\n

The results of the Nagios XI – PagerDuty Default Integration<\/strong><\/p>\n\n\n\n

Let’s explore how this default Nagios XI – PagerDuty integration looks as seen in various places the alert and incident could be displayed. We’ll use this Nagios XI alert as the example.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

This Nagios XI disk alert will trigger the ‘notify-service-by-pagerduty’ command and pass the macro values to the PagerDuty Event API v1 resulting in a new PagerDuty alert.<\/p>\n\n\n\n

This is the resulting PagerDuty alert display within the Alert tab. Note that I customized the column display to show the additional columns that could display alert information.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

If “View Message” is clicked on in the lower left corner, a portion of the PagerDuty Event API v1 payload can be seen.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

By clicking on the alert summary I can open the alert’s detailed display.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

By clicking on the link next to “Related to Incident:”, the PagerDuty incident details is displayed.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

If the PagerDuty user has configured their notification preferences to receive email, this is what they would be sent.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

If the PagerDuty user has configured their notification preferences to receive push notifications on the PagerDuty mobile app, this is what they’d see for the incident and alert detail.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In the next blog post, I’ll call out some of the reasons why running in this default configuration isn’t best practice and how this impacts an ops team’s response when using PagerDuty. I’ll also lay out the next steps that can be taken to move towards better practices when integrating Nagios with PagerDuty.<\/p>\n","protected":false},"excerpt":{"rendered":"

Nagios (Core\/XI) is one of the top 5 most widely integrated tools across PagerDuty\u2019s 10K+ customers providing fundamental host and service monitoring and alerting capabilities. During my time here at PagerDuty, I\u2019ve had the opportunity to work with very very large and well established enterprises and the latest up and coming start-ups \/ DevOps teams […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1084,1077,1078],"tags":[931,929,523,991,1073,1072],"class_list":{"0":"post-7889","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-integrations","7":"category-pagerduty","8":"category-pagerduty-best-practices","9":"tag-best-practices","10":"tag-events","11":"tag-integrations","12":"tag-monitoring","13":"tag-nagios-xi","14":"tag-pagerduty"},"_links":{"self":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/posts\/7889","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/comments?post=7889"}],"version-history":[{"count":5,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/posts\/7889\/revisions"}],"predecessor-version":[{"id":7910,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/posts\/7889\/revisions\/7910"}],"wp:attachment":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/media?parent=7889"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/categories?post=7889"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/tags?post=7889"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}