{"id":46249,"date":"2024-05-15T01:26:13","date_gmt":"2024-05-15T01:26:13","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=46249"},"modified":"2024-05-29T03:05:10","modified_gmt":"2024-05-29T03:05:10","slug":"list-of-all-terminogy-used-in-icinga","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/list-of-all-terminogy-used-in-icinga\/","title":{"rendered":"List of All terminogy used in Icinga"},"content":{"rendered":"\n

Here’s a list of common terminology used in Icinga along with short definitions:<\/p>\n\n\n\n

    \n
  1. Icinga Core<\/strong>: The central component of Icinga that handles the logic for monitoring operations and processes check results.<\/li>\n\n\n\n
  2. Icinga Web 2<\/strong>: The modern web interface for Icinga that provides a graphical view of the network and server status, and allows for configuration and administration.<\/li>\n\n\n\n
  3. Host<\/strong>: In Icinga, a host typically represents a network device such as a server, router, switch, or a workstation that needs to be monitored.<\/li>\n\n\n\n
  4. Service<\/strong>: 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.<\/li>\n\n\n\n
  5. Check<\/strong>: A test Icinga performs on a host or service to determine its status, such as “UP”, “DOWN”, “OK”, or “CRITICAL”.<\/li>\n\n\n\n
  6. Plugin<\/strong>: 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.<\/li>\n\n\n\n
  7. Command<\/strong>: A configuration object in Icinga that defines how to execute a check, including the command line, arguments, and any necessary execution options.<\/li>\n\n\n\n
  8. Notification<\/strong>: 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.<\/li>\n\n\n\n
  9. Contact<\/strong>: A user or administrator who receives notifications from Icinga. Contacts can be grouped and managed to control who is notified and when.<\/li>\n\n\n\n
  10. Time Period<\/strong>: A definition in Icinga that specifies when notifications can be sent and when hosts and services can be checked.<\/li>\n\n\n\n
  11. Dependency<\/strong>: A configuration that specifies relationships between hosts or services, influencing how and when notifications are sent based on the status of dependent objects.<\/li>\n\n\n\n
  12. Scheduled Downtime<\/strong>: A predefined time period during which the selected hosts or services are expected to be down or unreachable, and during which notifications are suppressed.<\/li>\n\n\n\n
  13. Event Handler<\/strong>: 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.<\/li>\n\n\n\n
  14. Template<\/strong>: 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.<\/li>\n\n\n\n
  15. Icinga Director<\/strong>: A module for Icinga Web 2 designed to make Icinga configuration easier through a web-based interface, enabling automation and templating.<\/li>\n\n\n\n
  16. Icinga API<\/strong>: Provides a programmable interface to Icinga, allowing for control and access to configuration and status data programmatically.<\/li>\n\n\n\n
  17. Satellite<\/strong>: In distributed monitoring, a satellite is an instance of Icinga that performs checks and communicates results back to a central Icinga server.<\/li>\n\n\n\n
  18. Zone<\/strong>: A concept in distributed monitoring where Icinga instances are grouped to manage checks and notifications within a defined network segment or location.<\/li>\n\n\n\n
  19. Endpoint<\/strong>: In a distributed setup, an endpoint is an individual Icinga instance within a zone, capable of executing checks and communicating with other instances.<\/li>\n\n\n\n
  20. Icinga DSL (Domain Specific Language)<\/strong>: A powerful configuration language used in Icinga 2 for defining complex behaviors, dependencies, and notifications with conditional logic.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

    Here’s a list of common terminology used in Icinga along with short definitions:<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[8217],"tags":[],"class_list":["post-46249","post","type-post","status-publish","format-standard","hentry","category-icinga"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/46249","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=46249"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/46249\/revisions"}],"predecessor-version":[{"id":46250,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/46249\/revisions\/46250"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=46249"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=46249"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=46249"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}