Icinga and InfluxDB Integration

Input and output integration overview

This plugin gathers services & hosts status using Icinga2 Remote API, providing an interface to monitor your infrastructure effectively.

The InfluxDB plugin writes metrics to the InfluxDB HTTP service, allowing for efficient storage and retrieval of time series data.

Integration details

Icinga

The Icinga2 Plugin enables users to gather status information from Icinga2’s Remote API. Icinga2 is a powerful monitoring system that checks the health of hosts and services and provides detailed monitoring capabilities. The plugin facilitates retrieving metrics such as the state of hosts and services, as well as detailed API status metrics. This integration is vital for users looking to keep an eye on their infrastructure’s health and performance metrics automatically, leveraging the Icinga2’s extensive API. By utilizing this plugin, users can easily integrate Icinga2 monitoring data with other systems, providing a comprehensive view of their infrastructure status.

InfluxDB

The InfluxDB Telegraf plugin serves to send metrics to the InfluxDB HTTP API, facilitating the storage and query of time series data in a structured manner. Integrating seamlessly with InfluxDB, this plugin provides essential features such as token-based authentication and support for multiple InfluxDB cluster nodes, ensuring reliable and scalable data ingestion. Through its configurability, users can specify options like organization, destination buckets, and HTTP-specific settings, providing flexibility to tailor how data is sent and stored. The plugin also supports secret management for sensitive data, which enhances security in production environments. This plugin is particularly beneficial in modern observability stacks where real-time analytics and storage of time series data are crucial.

Configuration

Icinga

[[inputs.icinga2]]
  ## Required Icinga2 server address
  # server = "https://localhost:5665"

  ## Collected Icinga2 objects ("services", "hosts")
  ## Specify at least one object to collect from /v1/objects endpoint.
  # objects = ["services"]

  ## Collect metrics from /v1/status endpoint
  ## Choose from:
  ##     "ApiListener", "CIB", "IdoMysqlConnection", "IdoPgsqlConnection"
  # status = []

  ## Credentials for basic HTTP authentication
  # username = "admin"
  # password = "admin"

  ## Maximum time to receive response.
  # response_timeout = "5s"

  ## Optional TLS Config
  # tls_ca = "/etc/telegraf/ca.pem"
  # tls_cert = "/etc/telegraf/cert.pem"
  # tls_key = "/etc/telegraf/key.pem"
  ## Use TLS but skip chain & host verification
  # insecure_skip_verify = true

InfluxDB

[[outputs.influxdb]]
  ## The full HTTP or UDP URL for your InfluxDB instance.
  ##
  ## Multiple URLs can be specified for a single cluster, only ONE of the
  ## urls will be written to each interval.
  # urls = ["unix:///var/run/influxdb.sock"]
  # urls = ["udp://127.0.0.1:8089"]
  # urls = ["http://127.0.0.1:8086"]

  ## Local address to bind when connecting to the server
  ## If empty or not set, the local address is automatically chosen.
  # local_address = ""

  ## The target database for metrics; will be created as needed.
  ## For UDP url endpoint database needs to be configured on server side.
  # database = "telegraf"

  ## The value of this tag will be used to determine the database.  If this
  ## tag is not set the 'database' option is used as the default.
  # database_tag = ""

  ## If true, the 'database_tag' will not be included in the written metric.
  # exclude_database_tag = false

  ## If true, no CREATE DATABASE queries will be sent.  Set to true when using
  ## Telegraf with a user without permissions to create databases or when the
  ## database already exists.
  # skip_database_creation = false

  ## Name of existing retention policy to write to.  Empty string writes to
  ## the default retention policy.  Only takes effect when using HTTP.
  # retention_policy = ""

  ## The value of this tag will be used to determine the retention policy.  If this
  ## tag is not set the 'retention_policy' option is used as the default.
  # retention_policy_tag = ""

  ## If true, the 'retention_policy_tag' will not be included in the written metric.
  # exclude_retention_policy_tag = false

  ## Write consistency (clusters only), can be: "any", "one", "quorum", "all".
  ## Only takes effect when using HTTP.
  # write_consistency = "any"

  ## Timeout for HTTP messages.
  # timeout = "5s"

  ## HTTP Basic Auth
  # username = "telegraf"
  # password = "metricsmetricsmetricsmetrics"

  ## HTTP User-Agent
  # user_agent = "telegraf"

  ## UDP payload size is the maximum packet size to send.
  # udp_payload = "512B"

  ## Optional TLS Config for use on HTTP connections.
  # tls_ca = "/etc/telegraf/ca.pem"
  # tls_cert = "/etc/telegraf/cert.pem"
  # tls_key = "/etc/telegraf/key.pem"
  ## Use TLS but skip chain & host verification
  # insecure_skip_verify = false

  ## HTTP Proxy override, if unset values the standard proxy environment
  ## variables are consulted to determine which proxy, if any, should be used.
  # http_proxy = "http://corporate.proxy:3128"

  ## Additional HTTP headers
  # http_headers = {"X-Special-Header" = "Special-Value"}

  ## HTTP Content-Encoding for write request body, can be set to "gzip" to
  ## compress body or "identity" to apply no encoding.
  # content_encoding = "gzip"

  ## When true, Telegraf will output unsigned integers as unsigned values,
  ## i.e.: "42u".  You will need a version of InfluxDB supporting unsigned
  ## integer values.  Enabling this option will result in field type errors if
  ## existing data has been written.
  # influx_uint_support = false

  ## When true, Telegraf will omit the timestamp on data to allow InfluxDB
  ## to set the timestamp of the data during ingestion. This is generally NOT
  ## what you want as it can lead to data points captured at different times
  ## getting omitted due to similar data.
  # influx_omit_timestamp = false

Input and output integration examples

Icinga

1. Centralized Monitoring Dashboard: Integrate the Icinga2 plugin with a visualization tool to create a centralized monitoring dashboard that presents real-time statuses of all monitored services and hosts. This setup allows teams to quickly identify issues and to respond proactively, ensuring minimal downtime.

2. Automated Incident Response: Use the metrics collected by the plugin to trigger automated incident response workflows. For instance, if a service is reported as critical, an automated system could notify relevant team members and even attempt to restart the service, reducing manual intervention and speeding resolution times.

3. Service Reliability Reporting: Combine data from the Icinga with business reporting systems to generate insights on service reliability. By analyzing trends in service states over time, organizations can identify weak points in their infrastructure and improve service availability based on factual data.

4. Cross-System Alerting: Leverage the collected metrics to integrate with various alerting systems. This could route notifications based on specific Icinga2 service states to different departments or teams depending on their roles, enabling tailored and timely responses to potential issues in the infrastructure.

InfluxDB

1. Real-Time System Monitoring: Utilize the InfluxDB plugin to capture and store metrics from a range of system components, such as CPU usage, memory consumption, and disk I/O. By pushing these metrics into InfluxDB, you can create a live dashboard that visualizes system performance in real time. This setup not only helps in identifying performance bottlenecks but also assists in proactive capacity planning by analyzing trends over time.

2. Performance Tracking for Web Applications: Automatically gather and push metrics related to web application performance, such as request durations, error rates, and user interactions, to InfluxDB. By employing this plugin in your monitoring stack, you can use the stored metrics to generate reports and analyses that help understand user behavior and application efficiency, thus guiding development and optimization efforts.

3. IoT Data Aggregation: Leverage the InfluxDB Telegraf plugin to collect sensor data from various IoT devices and store it in a centralized InfluxDB instance. This use case enables you to analyze trends and patterns in environmental or machine data over time, facilitating smarter decisions and predictive maintenance strategies. By integrating IoT data into InfluxDB, organizations can harness the power of historical data analysis to drive innovation and operational efficiency.

4. Analyzing Historical Metrics for Forecasting: Set up the InfluxDB plugin to send historical metric data into InfluxDB and use it to drive forecasting models. By analyzing past performance metrics, you can create predictive models that forecast future trends and demands. This application is particularly useful for business intelligence purposes, helping organizations prepare for fluctuations in resource needs based on historical usage patterns.

Feedback

Thank you for being part of our community! If you have any general feedback or found any bugs on these pages, we welcome and encourage your input. Please submit your feedback in the InfluxDB community Slack.