We use cookies or similar technologies to personalize your online experience & tailor marketing to you. Many of our product features require cookies to function properly.

Read our privacy policy I accept cookies from this site

Host Metrics Beta

OpenTelemetry Collector comes standard with a hostmetrics receiver, which collects diagnostic information at regular intervals about the system it runs on. These instructions describe how to install OpenTelemetry Collector, enable this receiver, and send this data into Honeycomb.

How It Works  🔗

OpenTelemetry Collector can be widely deployed across all your hosts, and regularly scrape system metrics such as information about memory, CPU, network, and filesystem utilization. It will then forward these signals to Honeycomb over the OpenTelemetry Line Protocol (OTLP).

An architecture diagram depicting OpenTelemetry Collector running on a host, scraping metrics and sending data to Honeycomb over OTLP.

Installing and running OpenTelemetry Collector  🔗

Find and download a recent release of OpenTelemetry Collector from the Releases page on GitHub.

OpenTelemetry Collector requires a configuration file to run (find more details below). If your configuration file exists in the current working directory at otel_collector_config.yaml, you can then run it using the following command:

otel-collector --config $(pwd)/otel_collector_config.yaml

See more about using OpenTelemetry Collector with Honeycomb.

Configuring OpenTelemetry Collector  🔗

To capture host metrics, you’ll need to set up a pipeline that starts with a hostmetrics receiver and ends with an otlp exporter pointing to Honeycomb. Pipelines are specified in an OpenTelemetry Collector configuration file. Here’s a barebones example of a configuration file configured to send local host metrics to Honeycomb:

receivers:
  hostmetrics:
    collection_interval: 1m
    scrapers:
      cpu:
      disk:
      filesystem:
      load:
      memory:
      network:
      paging:

exporters:
  otlp/metrics:
    endpoint: "api.honeycomb.io:443"
    headers:
      "x-honeycomb-team": "YOUR_API_KEY"
      "x-honeycomb-dataset": "DESTINATION_DATASET_NAME"

service:
  pipelines:
    metrics:
      receivers: [hostmetrics]
      processors: []
      exporters: [otlp/metrics]