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

New component: filestatsreceiver #19729

Closed
2 tasks
atoulme opened this issue Mar 15, 2023 · 1 comment · Fixed by #20282
Closed
2 tasks

New component: filestatsreceiver #19729

atoulme opened this issue Mar 15, 2023 · 1 comment · Fixed by #20282
Labels
Accepted Component New component has been sponsored

Comments

@atoulme
Copy link
Contributor

atoulme commented Mar 15, 2023

The purpose and use-cases of the new component

This receiver communicates metrics related to file information.

The component exposes the following metrics:

  • file.size: size of the file or folder in bytes.
  • file.mtime: last modification timestamp of the file, in seconds since Epoch.
  • file.ctime: last modification or permission change timestamp of the file, in seconds since Epoch.
  • file.atime: last access timestamp of the file, in seconds since Epoch.

Each metric will come with the following attributes:

* `file.path`: the absolute path to the file or folder

This receiver acts like a scraper, with a default collection interval of 30s. The receiver accepts the following configuration:

Field Default Description
include required A list of file glob patterns that match the file or folder paths to be scraped
exclude [] A list of file or folder glob patterns to exclude from scraping

In case of error with a specific file during scraping, the receiver will log a partial scraping error and continue to try on other files.

Example configuration for the component

filestats:
  include: ["/etc/apache/sites-enabled/*"]
  exclude: ["/etc/apache/sites-enabled/README"]
  metrics:
    file.size:
      enabled: false
    file.atime:
      enabled: true

Telemetry data types supported

metrics

Is this a vendor-specific component?

  • This is a vendor-specific component
  • If this is a vendor-specific component, I am proposing to contribute this as a representative of the vendor.

Sponsor (optional)

No response

Additional context

No response

@atoulme atoulme added needs triage New item requiring triage Sponsor Needed New component seeking sponsor and removed needs triage New item requiring triage labels Mar 15, 2023
@dmitryax
Copy link
Member

I'll sponsor this component

@dmitryax dmitryax added Accepted Component New component has been sponsored and removed Sponsor Needed New component seeking sponsor labels Mar 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Component New component has been sponsored
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants