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.

Sign up for GitHub

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

Jump to bottom

Investigate multiple scraper performance #3977

Closed
jrcamp opened this issue Jun 28, 2021 · 2 comments
Closed

Investigate multiple scraper performance #3977

jrcamp opened this issue Jun 28, 2021 · 2 comments
Assignees
@jrcamp
Labels
closed as inactive Stale

Comments

@jrcamp
Copy link
Contributor

jrcamp commented Jun 28, 2021

As part of #1395 (comment) there were performance issues discovered with having hundreds (thousands?) of scrapers.

Current theory is due to each scraper having its own ticker.
@jrcamp jrcamp self-assigned this Jun 28, 2021
@jrcamp jrcamp mentioned this issue Jun 28, 2021
Merged
@github-actions github-actions bot added the Stale label Jul 23, 2021
@bogdandrutu bogdandrutu reopened this Aug 9, 2021
@bogdandrutu bogdandrutu removed the Stale label Aug 9, 2021
hex1848 pushed a commit to hex1848/opentelemetry-collector-contrib that referenced this issue Jun 2, 2022
@mblauth
Finish removal of health_check extension from k8s example configurati…
45a848d 
…on (open-telemetry#3977)
@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2022

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.

@github-actions github-actions bot added the Stale label Nov 4, 2022
@github-actions
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 Mar 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jrcamp jrcamp

Labels
closed as inactive Stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jrcamp @bogdandrutu