-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
roachtest: scrape prometheus metrics on demand #66657
Conversation
9bff031
to
07146f0
Compare
07146f0
to
0909766
Compare
c8b2973
to
bee464e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a minor comment or two, but I leave them to your discretion.
Thanks for addressing the previous comments
|
||
// MakeInsecureCockroachScrapeConfig creates scrape configs for the given | ||
// cockroach nodes. All nodes are assumed to be insecure and running on | ||
// port 26258. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe there is a way to get the port via roachprod if this function were to take a *cluser as well. But, I think that will com naturally if we decide to follow-up with local-mode support.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mmm, I'll defer to that ;)
This commit adds a prometheus scraper on TPC-C workloads and scrapes their metrics. This is configured by setting it in the tpccOptions setup. It is currently set up on the multi-region chaos tests. At the end of the run, we take a snapshot of the metrics of the workload and store it as an artifact, which can be used later. Release note: None
bee464e
to
f84cda0
Compare
thanks! bors r=stevendanna |
Build succeeded: |
This commit adds a prometheus scraper on TPC-C workloads and scrapes
their metrics. This is configured by setting it in the tpccOptions
setup. It is currently set up on the multi-region chaos tests.
At the end of the run, we take a snapshot of the metrics of the workload
and store it as an artifact, which can be used later.
Release note: None