Icinga and Microsoft SQL Server Integration

Input and output integration overview

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

Telegraf’s SQL plugin facilitates the storage of metrics in SQL databases. When configured for Microsoft SQL Server, it supports the specific DSN format and schema requirements, allowing for seamless integration with SQL Server.

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.

Microsoft SQL Server

Telegraf’s SQL output plugin for Microsoft SQL Server is designed to capture and store metric data by dynamically creating tables and columns that match the structure of incoming data. This integration leverages the go-mssqldb driver, which follows the SQL Server connection protocol through a DSN that includes server, port, and database details. Although the driver is considered experimental due to limited unit tests, it provides robust support for dynamic schema generation and data insertion, enabling detailed time-stamped records of system performance. This flexibility makes it a valuable tool for environments that demand reliable and granular metric logging, despite its experimental status.

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

Microsoft SQL Server

[[outputs.sql]]
  ## Database driver
  ## Valid options: mssql (Microsoft SQL Server), mysql (MySQL), pgx (Postgres),
  ## sqlite (SQLite3), snowflake (snowflake.com), clickhouse (ClickHouse)
  driver = "mssql"

  ## Data source name
  ## For Microsoft SQL Server, the DSN typically includes the server, port, username, password, and database name.
  ## Example DSN: "sqlserver://username:password@localhost:1433?database=telegraf"
  data_source_name = "sqlserver://username:password@localhost:1433?database=telegraf"

  ## Timestamp column name
  timestamp_column = "timestamp"

  ## Table creation template
  ## Available template variables:
  ##  {TABLE}        - table name as a quoted identifier
  ##  {TABLELITERAL} - table name as a quoted string literal
  ##  {COLUMNS}      - column definitions (list of quoted identifiers and types)
  table_template = "CREATE TABLE {TABLE} ({COLUMNS})"

  ## Table existence check template
  ## Available template variables:
  ##  {TABLE} - table name as a quoted identifier
  table_exists_template = "SELECT 1 FROM {TABLE} LIMIT 1"

  ## Initialization SQL (optional)
  init_sql = ""

  ## Maximum amount of time a connection may be idle. "0s" means connections are never closed due to idle time.
  connection_max_idle_time = "0s"

  ## Maximum amount of time a connection may be reused. "0s" means connections are never closed due to age.
  connection_max_lifetime = "0s"

  ## Maximum number of connections in the idle connection pool. 0 means unlimited.
  connection_max_idle = 2

  ## Maximum number of open connections to the database. 0 means unlimited.
  connection_max_open = 0

  ## Metric type to SQL type conversion
  ## You can customize the mapping if needed.
  #[outputs.sql.convert]
  #  integer       = "INT"
  #  real          = "DOUBLE"
  #  text          = "TEXT"
  #  timestamp     = "TIMESTAMP"
  #  defaultvalue  = "TEXT"
  #  unsigned      = "UNSIGNED"
  #  bool          = "BOOL"

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.

Microsoft SQL Server

1. Enterprise Application Monitoring: Leverage the plugin to capture detailed performance metrics from enterprise applications running on SQL Server. This setup allows IT teams to analyze system performance, track transaction times, and identify bottlenecks across complex, multi-tier environments.

2. Dynamic Infrastructure Auditing: Deploy the plugin to create a dynamic audit log of infrastructure changes and performance metrics in SQL Server. This use case is ideal for organizations that require real-time monitoring and historical analysis of system performance for compliance and optimization.

3. Automated Performance Benchmarking: Use the plugin to continuously record and analyze performance metrics of SQL Server databases. This enables automated benchmarking, where historical data is compared against current performance, helping to quickly identify anomalies or degradation in service.

4. Integrated DevOps Dashboards: Integrate the plugin with DevOps monitoring tools to feed real-time metrics from SQL Server into centralized dashboards. This provides a holistic view of application health, allowing teams to correlate SQL Server performance with application-level events for faster troubleshooting and proactive maintenance.

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.