Limited Time Offer!

For Less Than the Cost of a Starbucks Coffee, Access All DevOpsSchool Videos on YouTube Unlimitedly.
Master DevOps, SRE, DevSecOps Skills!

Enroll Now
Icinga

List of All terminogy used in Icinga

May 15, 2024 Leave a Comment

Here’s a list of common terminology used in Icinga along with short definitions:

  1. Icinga Core: The central component of Icinga that handles the logic for monitoring operations and processes check results.
  2. Icinga Web 2: The modern web interface for Icinga that provides a graphical view of the network and server status, and allows for configuration and administration.
  3. Host: In Icinga, a host typically represents a network device such as a server, router, switch, or a workstation that needs to be monitored.
  4. Service: A service in Icinga refers to a specific process, application, or any operational aspect of a host that needs monitoring, like HTTP, FTP, or CPU load.
  5. Check: A test Icinga performs on a host or service to determine its status, such as “UP”, “DOWN”, “OK”, or “CRITICAL”.
  6. Plugin: A script or program that Icinga uses to perform a check. Plugins return the status of the host or service along with optional performance data.
  7. Command: A configuration object in Icinga that defines how to execute a check, including the command line, arguments, and any necessary execution options.
  8. Notification: Alerts generated by Icinga when the status of a host or service changes or meets specific criteria. Notifications can be sent via email, SMS, or other methods.
  9. Contact: A user or administrator who receives notifications from Icinga. Contacts can be grouped and managed to control who is notified and when.
  10. Time Period: A definition in Icinga that specifies when notifications can be sent and when hosts and services can be checked.
  11. Dependency: A configuration that specifies relationships between hosts or services, influencing how and when notifications are sent based on the status of dependent objects.
  12. Scheduled Downtime: A predefined time period during which the selected hosts or services are expected to be down or unreachable, and during which notifications are suppressed.
  13. Event Handler: A script or command that Icinga executes in response to changes in the status of a host or service, often used for proactive problem resolution.
  14. Template: In Icinga, a template is a predefined set of configuration attributes that can be applied to multiple hosts or services to ensure consistent settings across similar objects.
  15. Icinga Director: A module for Icinga Web 2 designed to make Icinga configuration easier through a web-based interface, enabling automation and templating.
  16. Icinga API: Provides a programmable interface to Icinga, allowing for control and access to configuration and status data programmatically.
  17. Satellite: In distributed monitoring, a satellite is an instance of Icinga that performs checks and communicates results back to a central Icinga server.
  18. Zone: A concept in distributed monitoring where Icinga instances are grouped to manage checks and notifications within a defined network segment or location.
  19. Endpoint: In a distributed setup, an endpoint is an individual Icinga instance within a zone, capable of executing checks and communicating with other instances.
  20. Icinga DSL (Domain Specific Language): A powerful configuration language used in Icinga 2 for defining complex behaviors, dependencies, and notifications with conditional logic.
Rajesh Kumar
Follow me
Latest posts by Rajesh Kumar (see all)
Subscribe
Notify of
guest
0 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x