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

per code PROMREMOTEBENCH_INTERVAL is not relevant for scraping #10

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

xmcqueen
Copy link

Its confusing for users to wonder about how PROMREMOTEBENCH_INTERVAL might interact with the scraper's own interval. Its actually not used when running in the scrape-target mode. Its best to get this line out of the README.

Copy link

@gibbscullen gibbscullen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this apply to both the remote write and scrape benchmarking manifests?

@xmcqueen
Copy link
Author

I'm not sure what you're question is. The PROMREMOTEBENCH_INTERVAL is not used for Scrape Benchmarking as far as I could tell by looking at the code (when promremotebench is being scraped). It IS needed for the Remote Write Benchmarking (when promremotebench is jamming metrics into some remote data store). It should be removed from the Scrape Benchmarking example yaml on the README because users will be very puzzled about what it could mean, when it actually means nothing. This commit is just a change to the README, so people will have a non-confusing first encounter with the tool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants