-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenTelemetry Collector: Filesystem Metrics Showing Zero Values #34934
Comments
Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I noticed you installed the Collector with the Docker container. Can you try following these steps from the README to make sure you are collecting metrics from the host and not the container? |
Thanks, I used /hostfs/proc instead of /hostfs. My bad, and I am closing this issue. |
Issue: Filesystem Metrics Always Return ZeroDescription: Configuration: receivers:
hostmetrics:
root_path: ${env:HOST_PROC}
scrapers:
disk:
metrics:
system.disk.io_time:
enabled: false
system.disk.merged:
enabled: false
system.disk.operation_time:
enabled: false
system.disk.operations:
enabled: false
system.disk.pending_operations:
enabled: false
system.disk.weighted_io_time:
enabled: false
filesystem:
metrics:
system.filesystem.utilization:
enabled: true
system.filesystem.usage:
enabled: true
paging:
metrics:
system.paging.utilization:
enabled: true
collection_interval: 60s
exporters:
debug:
verbosity: detailed
service:
pipelines:
metrics/hostmetrics:
receivers: [hostmetrics]
processors: [resourcedetection/docker]
exporters: [clickhouse] Docker Compose: version: "3.7"
services:
otel-collector:
image: otel/opentelemetry-collector-contrib:0.104.0
volumes:
- /proc:/hostfs/proc
- /:/hostfs
env_file:
- .env
command: ["--config=/etc/otel/config.yaml"]
restart: always Environment Variable: HOST_PROC="/hostfs" Expected Behavior: Actual Behavior: Additional Information:
|
Component(s)
receiver/hostmetrics
What happened?
Description
The filesystem scraper within the hostmetrics receiver reports zero values for all filesystem-related metrics. This behavior is unexpected, as the underlying filesystem is not empty, and there are active inodes and space utilization.
Steps to Reproduce
Expected Result
The system.filesystem.usage, system.filesystem.utilization, and system.filesystem.inodes.usage metrics should reflect the actual usage and inodes status of the filesystem, showing non-zero values corresponding to the filesystem’s state.
Actual Result
The metrics consistently show zero values for the following:
• system.filesystem.inodes.usage
• system.filesystem.usage
• system.filesystem.utilization
Collector version
v0.104.0
Environment information
Environment Information
• OS: Ubuntu 20.04
• Collector Installation Method: Docker
• Docker Image: otel/opentelemetry-collector-contrib:0.104.0
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: