vectordotdev/vector

could you pls add sensors info in host_metrics

Closed

#21,389 opened on Oct 1, 2024

View on GitHubContributor guide
 (1 comment) (3 reactions) (0 assignees)Rust (2,126 forks)batch import
good first issuesource: host_metrics

Repository metrics

Stars
 (21,837 stars)
PR merge metrics
 (Avg merge 8d 16h) (110 merged PRs in 30d)

Description

A note for the community

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Use Cases

No response

Attempted Solutions

No response

Proposal

if the metrics info has sensors data like below ,that would be perfect. Thanks!

coretemp-isa-0000 Adapter: ISA adapter Package id 0: +48.0°C (high = +105.0°C, crit = +105.0°C) Core 0: +43.0°C (high = +105.0°C, crit = +105.0°C) Core 1: +43.0°C (high = +105.0°C, crit = +105.0°C) Core 2: +43.0°C (high = +105.0°C, crit = +105.0°C) Core 3: +43.0°C (high = +105.0°C, crit = +105.0°C)

nvme-pci-0100 Adapter: PCI adapter Composite: +52.9°C (low = -273.1°C, high = +82.8°C) (crit = +84.8°C)

acpitz-acpi-0 Adapter: ACPI interface temp1: +27.8°C

References

No response

Version

No response

Contributor guide

Research direction
Review Vector's existing host metrics component at src/sources/host metrics/ to understand how CPU, memory, and disk metrics are collected. Investigate Rust sensor libraries like `sensors` (sysfs) or `lm sensors` bindings. The issue proposes adding temperature data similar to `sensors` command output. Look at the `sensors` crate or implement direct sysfs reading. Integrate into the existing metrics collection loop, ensuring proper labeling and unit conversion.
Tech stack
rust
Domain
observabilitybackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
basic Rust knowledgeunderstanding of vector's metrics pipeline
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50