Documentation

RAS Daemon Input Plugin

This plugin gathers statistics and error counts provided by the local RAS (reliability, availability and serviceability) daemon.

This plugin requires access to SQLite3 database from RASDaemon. Please make sure the Telegraf user has the required permissions to this database!

Introduced in: Telegraf v1.16.0 Tags: server OS support: linux

Global configuration options

Plugins support additional global and plugin configuration settings for tasks such as modifying metrics, tags, and fields, creating aliases, and configuring plugin ordering. See CONFIGURATION.md for more details.

Configuration

# RAS plugin exposes counter metrics for Machine Check Errors provided by RASDaemon (sqlite3 output is required).
# This plugin ONLY supports Linux on 386, amd64, arm, and arm64
[[inputs.ras]]
  ## Optional path to RASDaemon sqlite3 database.
  ## Default: /var/lib/rasdaemon/ras-mc_event.db
  # db_path = ""

In addition RASDaemon runs, by default, with --enable-sqlite3 flag. In case of problems with SQLite3 database please verify this is still a default option.

Metrics

  • ras
    • tags:
      • socket_id
    • fields:
      • memory_read_corrected_errors
      • memory_read_uncorrectable_errors
      • memory_write_corrected_errors
      • memory_write_uncorrectable_errors
      • cache_l0_l1_errors
      • tlb_instruction_errors
      • cache_l2_errors
      • upi_errors
      • processor_base_errors
      • processor_bus_errors
      • internal_timer_errors
      • smm_handler_code_access_violation_errors
      • internal_parity_errors
      • frc_errors
      • external_mce_errors
      • microcode_rom_parity_errors
      • unclassified_mce_errors

Please note that processor_base_errors is aggregate counter measuring the following MCE events:

  • internal_timer_errors
  • smm_handler_code_access_violation_errors
  • internal_parity_errors
  • frc_errors
  • external_mce_errors
  • microcode_rom_parity_errors
  • unclassified_mce_errors

Example Output

ras,host=ubuntu,socket_id=0 external_mce_base_errors=1i,frc_errors=1i,instruction_tlb_errors=5i,internal_parity_errors=1i,internal_timer_errors=1i,l0_and_l1_cache_errors=7i,memory_read_corrected_errors=25i,memory_read_uncorrectable_errors=0i,memory_write_corrected_errors=5i,memory_write_uncorrectable_errors=0i,microcode_rom_parity_errors=1i,processor_base_errors=7i,processor_bus_errors=1i,smm_handler_code_access_violation_errors=1i,unclassified_mce_base_errors=1i 1598867393000000000
ras,host=ubuntu level_2_cache_errors=0i,upi_errors=0i 1598867393000000000

Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2