Notifications in Nagios

 • The decision to send out notifications is made in the service check and host check logic

• Each host and service definition has a <contact_groups> option that specifies what contact groups receive notifications for that particular host or service

• There are several filters that notifications encounters before reaching to the receiver


Prerequisites for delivering notification

 Nagios supports optional detection of hosts and services that are "flapping"

 Flapping occurs when a service or host changes state too frequently, resulting a problem and recovery notifications


Nagios Notification Methods

• There are many ways through which Nagios notifies about a problem or recovery Example: Mail, Instant message, Audio alert etc.

• How notifications are sent depend on the notification commands that are defined in your object definition files

• While writing your notification commands, you need to take into account what type of notification is occurring

• The $NOTIFICATIONTYPE$ macro (macroinstruction)contains a string that identifies the type of notification occurring


Program Wide Filters

• Filter to test of whether or not notifications are enabled on a program-wide basis

• This is initially determined by the enable_notifications directive in the main config file

• If notifications are disabled on a program-wide basis, no host or service notifications can be sent out or else notifications move to the next filter


Service & Host Filters

• This filter is a check to see if

• The host or service is in a period of scheduled downtime

• The host or service is flapping

• Notifications can be sent out for warning states, critical states, and recoveries

• Notifications fall in valid notification time period

• Scheduled downtime- Scheduled periods of planned downtime for hosts and service that you're monitoring.

• This is an event of taking a server down for an upgrade, etc.


Contact Filter

 At this point the notification has passed the program mode filter and all host or service filters and Nagios starts to notify all the people it should

 Contact filters are specific to each contact and do not affect other contacts receive notifications

Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources and services.
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed without them. If these are not fulfilled, the project is con
Read more

Kubernetes

  Using containers to host applications and other processes has gone mainstream. As more and more workload is moved into containers, management systems are needed to handle the demands of containerized applications at scale. One of the most popular options for managing  container-based workload is Kubernetes . Kubernetes combines container management automation with an extensible API to create a cloud-native application management powerhouse. At its core, Kubernetes manages the placement of pods, which can consist of one or more containers, on a Kubernetes cluster node. Additionally, if one of these pods crashes, Kubernetes can create a new instance of it. If a cluster node is removed, Kubernetes can move any affected workload to a different node in the cluster. On top of that, Kubernetes pods can be scaled to provide more or less throughput to meet scale demands and these scale operations can be triggered manually or automatically using Kuberentes horizontal pod auto-scaling. Finally,
Read more