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

Document the mute_process_*_error configuration options available in the process scraper #30779

Open
woody1872 opened this issue Jan 25, 2024 · 3 comments
Labels
documentation Improvements or additions to documentation receiver/hostmetrics Stale

Comments

@woody1872
Copy link

woody1872 commented Jan 25, 2024

Component(s)

receiver/hostmetrics

Describe the issue you're reporting

At the time of writing, there are four mute_process_*_error configuration options, those are:

mute_process_name_error
mute_process_exe_error
mute_process_io_error
mute_process_user_error

However, there doesn't appear to be any documentation for these options. It's not clear what they are or why they exist - so they presently exist in the documentation unexplained.

I was looking to modify and test some existing process scraping configuration, and I wanted to understand if any of these options were applicable to the changes I was making, but I was unable to find any information that helped.

@woody1872 woody1872 added the needs triage New item requiring triage label Jan 25, 2024
@atoulme atoulme added receiver/hostmetrics and removed needs triage New item requiring triage labels Jan 25, 2024
Copy link
Contributor

Pinging code owners for receiver/hostmetrics: @dmitryax @braydonk. See Adding Labels via Comments if you do not have permissions to add labels yourself.

@crobert-1 crobert-1 added the documentation Improvements or additions to documentation label Jan 25, 2024
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 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.

@github-actions github-actions bot added the Stale label Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation receiver/hostmetrics Stale
Projects
None yet
3 participants