IPMI Metrics

Ship your IPMI Metrics via Telegraf to your Logit.io Stack

Configure Telegraf to ship IPMI metrics to your Logit.io stacks via Logstash.

Install Integration

Please click on the Install Integration button to configure your stack for this source.

Install Telegraf

This integration allows you to configure a Telegraf agent to send your metrics, in multiple formats, to Logit.io.

Choose the installation method for your operating system:

When you paste the command below into Powershell it will download the Telegraf zip file. Once that is complete, press Enter again and the zip file will be extracted into C:\Program Files\InfluxData\telegraf\telegraf-1.31.2.

wget https://dl.influxdata.com/telegraf/releases/telegraf-1.31.2_windows_amd64.zip -UseBasicParsing -OutFile telegraf-1.31.2_windows_amd64.zip 
Expand-Archive .\telegraf-1.31.2_windows_amd64.zip -DestinationPath 'C:\Program Files\InfluxData\telegraf'

Configure the Telegraf input plugin

The configuration file below is pre-configured to scrape the system metrics from your hosts, add the following code to the configuration file /etc/telegraf/telegraf.conf from the previous step.

# Read metrics from the bare metal servers via IPMI
[[inputs.ipmi_sensor]]
  ## optionally specify the path to the ipmitool executable
  # path = "/usr/bin/ipmitool"
  ##
  ## 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
  ##
  ## optionally force session privilege level. Can be CALLBACK, USER, OPERATOR, ADMINISTRATOR
  # privilege = "ADMINISTRATOR"
  ##
  ## optionally specify one or more servers via a url matching
  ##  [username[:password]@][protocol[(address)]]
  ##  e.g.
  ##    root:passwd@lan(127.0.0.1)
  ##
  ## if no servers are specified, local machine sensor stats will be queried
  ##
  # servers = ["USERID:PASSW0RD@lan(192.168.1.1)"]
 
  ## Recommended: use metric 'interval' that is a multiple of 'timeout' to avoid
  ## gaps or overlap in pulled data
  interval = "30s"
 
  ## Timeout for the ipmitool command to complete. Default is 20 seconds.
  timeout = "20s"
 
  ## Schema Version: (Optional, defaults to version 1)
  metric_version = 2
 
  ## Optionally provide the hex key for the IMPI connection.
  # hex_key = ""
 
  ## If ipmitool should use a cache
  ## for me ipmitool runs about 2 to 10 times faster with cache enabled on HP G10 servers (when using ubuntu20.04)
  ## the cache file may not work well for you if some sensors come up late
  # 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 = ""

Read more about how to configure data scraping and configuration options for IPMI (opens in a new tab)

Configure The Output plugin

Once you have generated the configuration file, you need to set up the output plug-in to allow Telegraf to transmit your data to Logit.io in Prometheus format. This can be accomplished by incorporating the following code into your configuration file:

[[outputs.http]]
  url = "https://@metricsUsername:@metricsPassword@@metrics_id-vm.logit.io:@vmAgentPort/api/v1/write"
  data_format = "prometheusremotewrite"
 
  [outputs.http.headers]
    Content-Type = "application/x-protobuf"
    Content-Encoding = "snappy"

Start Telegraf

From the location where Telegraf was installed (C:\Program Files\InfluxData\telegraf\telegraf-1.31.2) run the program providing the chosen configuration file as a parameter:

.\telegraf.exe --config telegraf-demo.conf

Once Telegraf is running you should see output similar to the following, which confirms the inputs, output and basic configuration the application has been started with: Powershell Telegraf information

View your metrics

Data should now have been sent to your Stack.

View My Data

If you don't see take a look at How to diagnose no data in Stack below for how to diagnose common issues.

How to diagnose no data in Stack

If you don't see data appearing in your Stack after following the steps, visit the Help Centre guide for steps to diagnose no data appearing in your Stack or Chat to support now.

Telegraf IPMI Overview

To efficiently monitor and analyze IPMI metrics across diverse systems, it's crucial to implement a reliable and effective metrics management solution. Telegraf, an open-source server agent used for collecting and transmitting telemetry data, is exceptionally suitable for this task. It can gather IPMI metrics from a multitude of sources, such as operational servers, hardware monitoring interfaces, and other associated applications.

Telegraf comes with an extensive variety of input plugins, enabling users to collect metrics from different sources, such as CPU usage, memory utilization, temperature readings, fan speeds, and more. All these metrics are important for understanding the health and performance of hardware systems managed through IPMI. To store and analyze these collected metrics, organizations can leverage Prometheus, an open-source monitoring and alerting tool, recognized for its flexible querying language and impressive data visualization capabilities.

To transfer IPMI metrics from Telegraf to Prometheus, organizations need to configure Telegraf to output metrics in the Prometheus format and then set up Prometheus to scrape these metrics from the Telegraf server. This process involves configuring Telegraf to collect IPMI metrics, outputting them in the Prometheus format, setting up Prometheus to retrieve these metrics from the Telegraf server, and then interpreting the data using Prometheus's robust querying and graphical visualization tools.

Upon successful integration of the metrics into Prometheus, further analysis and visualization can be carried out using Grafana. Grafana, a leading open-source platform known for its monitoring and observability capabilities, is fully compatible with Prometheus. It allows users to create dynamic, interactive dashboards for an in-depth exploration of the metrics data, delivering a comprehensive understanding of performance trends and potential hardware issues managed through IPMI.

If you need any further assistance with shipping your log data to Logit.io we're here to help you get started. Feel free to get in contact with our support team by sending us a message via live chat & we'll be happy to assist.

HAproxy Metrics Jenkins Metrics