IPMI Sensor and Azure Application Insights Integration

Powerful performance with an easy integration, powered by Telegraf, the open source data connector built by InfluxData.

info

This is not the recommended configuration for real-time query at scale. For query and compression optimization, high-speed ingest, and high availability, you may want to consider IPMI and InfluxDB.

5B+

Telegraf downloads

#1

Time series database
Source: DB Engines

1B+

Downloads of InfluxDB

2,800+

Contributors

Table of Contents

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Input and output integration overview

The IPMI Sensor Plugin facilitates the collection of server health metrics directly from hardware via the IPMI protocol, querying sensor data from either local or remote systems.

This plugin writes Telegraf metrics to Azure Application Insights, enabling powerful monitoring and diagnostics.

Integration details

IPMI Sensor

The IPMI Sensor plugin is designed to gather bare metal metrics via the command line utility ipmitool, which interfaces with the Intelligent Platform Management Interface (IPMI). This protocol provides management and monitoring capabilities for hardware components in server systems, allowing for the retrieval of critical system health metrics such as temperature, fan speeds, and power supply status from both local and remote servers. When configured without specified servers, the plugin defaults to querying the local machine’s sensor statistics using the ipmitool sdr command. In scenarios covering remote hosts, authentication is supported through username and password using the command format ipmitool -I lan -H SERVER -U USERID -P PASSW0RD sdr. This flexibility allows users to monitor systems effectively across various environments. The plugin also supports multiple sensor types, including chassis power status and DCMI power readings, catering to administrators needing real-time insight into server operations.

Azure Application Insights

The Azure Application Insights plugin integrates Telegraf with Azure’s Application Insights service, facilitating the seamless transmission of metrics from various sources to a centralized monitoring platform. This plugin empowers users to harness the capabilities of Azure Application Insights, a powerful application performance management tool, allowing developers and IT operations teams to gain valuable insights into the performance, availability, and usage of their applications. By employing this plugin, users can monitor application telemetry and operational data efficiently, contributing to better diagnostics and improved application performance.

Key features of this plugin include the ability to specify an instrumentation key for the Application Insights resource, configure the endpoint URL for tracking, and enable additional diagnostic logging for a more comprehensive analysis. Furthermore, the plugin provides context tagging capabilities, allowing the addition of specific Application Insights context tags to enhance the contextual information associated with metrics being sent. These features collectively make the Azure Application Insights Output Plugin a vital tool for organizations looking to optimize their monitoring capabilities within Azure.

Configuration

IPMI Sensor

[[inputs.ipmi_sensor]]
  ## Specify the path to the ipmitool executable
  # path = "/usr/bin/ipmitool"

  ## Use sudo
  ## Setting 'use_sudo' to true will make use of sudo to run ipmitool.
  ## Sudo must be configured to allow the telegraf user to run ipmitool
  ## without a password.
  # use_sudo = false

  ## Servers
  ## Specify one or more servers via a url. If no servers are specified, local
  ## machine sensor stats will be queried. Uses the format:
  ##  [username[:password]@][protocol[(address)]]
  ##  e.g. root:passwd@lan(127.0.0.1)
  # servers = ["USERID:PASSW0RD@lan(192.168.1.1)"]

  ## Session privilege level
  ## Choose from: CALLBACK, USER, OPERATOR, ADMINISTRATOR
  # privilege = "ADMINISTRATOR"

  ## Timeout
  ## Timeout for the ipmitool command to complete.
  # timeout = "20s"

  ## Metric schema version
  ## See the plugin readme for more information on schema versioning.
  # metric_version = 1

  ## Sensors to collect
  ## Choose from:
  ##   * sdr: default, collects sensor data records
  ##   * chassis_power_status: collects the power status of the chassis
  ##   * dcmi_power_reading: collects the power readings from the Data Center Management Interface
  # sensors = ["sdr"]

  ## Hex key
  ## Optionally provide the hex key for the IMPI connection.
  # hex_key = ""

  ## Cache
  ## If ipmitool should use a cache
  ## Using a cache can speed up collection times depending on your device.
  # use_cache = false

  ## Path to the ipmitools cache file (defaults to OS temp dir)
  ## The provided path must exist and must be writable
  # cache_path = ""

Azure Application Insights

[[outputs.application_insights]]
  ## Instrumentation key of the Application Insights resource.
  instrumentation_key = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx"

  ## Regions that require endpoint modification https://docs.microsoft.com/en-us/azure/azure-monitor/app/custom-endpoints
  # endpoint_url = "https://dc.services.visualstudio.com/v2/track"

  ## Timeout for closing (default: 5s).
  # timeout = "5s"

  ## Enable additional diagnostic logging.
  # enable_diagnostic_logging = false

  ## NOTE: Due to the way TOML is parsed, tables must be at the END of the
  ## plugin definition, otherwise additional config options are read as part of
  ## the table

  ## Context Tag Sources add Application Insights context tags to a tag value.
  ##
  ## For list of allowed context tag keys see:
  ## https://github.com/microsoft/ApplicationInsights-Go/blob/master/appinsights/contracts/contexttagkeys.go
  # [outputs.application_insights.context_tag_sources]
  #   "ai.cloud.role" = "kubernetes_container_name"
  #   "ai.cloud.roleInstance" = "kubernetes_pod_name"

Input and output integration examples

IPMI Sensor

  1. Centralized Monitoring Dashboard: Utilize the IPMI Sensor plugin to gather metrics from multiple servers and compile them into a centralized monitoring dashboard. This enables real-time visibility into server health across data centers. Administrators can track metrics like temperature and power usage, helping them make data-driven decisions about resource allocation, potential failures, and maintenance schedules.

  2. Automated Power Alerts: Incorporate the plugin into an alerting system that monitors chassis power status and triggers alerts when anomalies are detected. For instance, if the power status indicates a failure or if watt values exceed expected thresholds, automated notifications can be sent to operations teams, ensuring prompt attention to hardware issues.

  3. Energy Consumption Analysis: Leverage the DCMI power readings collected via the plugin to analyze energy consumption patterns of hardware over time. By integrating these readings with analytics platforms, organizations can identify opportunities to reduce power usage, optimize efficiency, and potentially decrease operational costs in large server farms or cloud infrastructures.

  4. Health Check Automation: Schedule regular health checks by using the IPMI Sensor Plugin to collect data from a fleet of servers. This data can be logged and compared against historical performance metrics to identify trends, outliers, or signs of impending hardware failure, allowing IT teams to take proactive measures and reduce downtime.

Azure Application Insights

  1. Application Performance Monitoring: Utilize the Azure Application Insights plugin to continuously monitor the performance of your web applications or microservices. By sending Telegraf metrics directly to Application Insights, teams can visualize real-time application performance data, enabling proactive tuning and optimization of application resources. This setup not only enhances the reliability of applications but also ensures user satisfaction through consistent performance monitoring.

  2. Integrated Logging and Telemetry: Combine this plugin with centralized logging solutions to provide a comprehensive observability stack. By sending telecom data to Azure Application Insights, teams can correlate performance metrics with log data and gain deeper insights into application behavior, allowing for more efficient troubleshooting and root cause analysis.

  3. Contextual Monitoring of Cloud Resources: Use the context tagging feature to enrich your application metrics with specific contextual information related to your cloud environment. This enhanced context can be invaluable for understanding the performance of cloud-native applications, enabling better scaling decisions and resource management based on real usage patterns.

  4. Real-time Alerts Setup: Configure Application Insights to trigger alerts based on specific metrics received via this plugin. This allows teams to be notified of performance degradation or anomalies in real-time, enabling immediate action to mitigate issues and maintain high availability of applications.

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.

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Related Integrations

HTTP and InfluxDB Integration

The HTTP plugin collects metrics from one or more HTTP(S) endpoints. It supports various authentication methods and configuration options for data formats.

View Integration

Kafka and InfluxDB Integration

This plugin reads messages from Kafka and allows the creation of metrics based on those messages. It supports various configurations including different Kafka settings and message processing options.

View Integration

Kinesis and InfluxDB Integration

The Kinesis plugin allows for reading metrics from AWS Kinesis streams. It supports multiple input data formats and offers checkpointing features with DynamoDB for reliable message processing.

View Integration