Skip to content
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

[receiver/filestats] Size of folder should reflect actual used bytes of the folder containing files similar to du #33016

Closed
robsliwi opened this issue May 13, 2024 · 3 comments
Labels

Comments

@robsliwi
Copy link

Component(s)

receiver/filestats

Is your feature request related to a problem? Please describe.

Given most of the Linux systems out there, when specifying a folder for the filestats receiver it will output 4096 as value (smallest allocation unit of the filesystem for a folder).
No matter how large the actual directory is. We'd like to monitor some certain directories for growth and this would be a great addition.

A config:

receivers:
  filestats:
    collection_interval: 10s
    include: "/tmp"
exporters:
  debug:
    verbosity: detailed
service:
  pipelines:
    metrics:
      receivers: [ filestats ]
      exporters: [ debug ]

will return

----->&-----
Metric #1
Descriptor:
     -> Name: file.size
     -> Description: The size of the file or folder, in bytes.
     -> Unit: b
     -> DataType: Gauge
NumberDataPoints #0
StartTimestamp: 2024-05-13 13:02:35.753366344 +0000 UTC
Timestamp: 2024-05-13 13:02:36.756113856 +0000 UTC
Value: 4096
----->&-----

in comparison to du

$ du -sh /tmp
5,1 G

Describe the solution you'd like

An option to output folder stats as du does it.

Describe alternatives you've considered

No response

Additional context

No response

@robsliwi robsliwi added enhancement New feature or request needs triage New item requiring triage labels May 13, 2024
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant