-
Notifications
You must be signed in to change notification settings - Fork 763
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
feat(metrics): add progress metrics via collector #17359
base: main
Are you sure you want to change the base?
Conversation
9dba57d
to
b0a37b0
Compare
group_by_spill: ProgressValues, | ||
window_partition_spill: ProgressValues, | ||
) { | ||
let mut guard = self.inner.lock(); |
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.
Atomic is better?
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.
let me have a try
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.
tried to use an AtomicPtr instead but finally returned to the Mutex approach 🥲, the exlusive region is not big imo, it only held the lock when query is finished & metrics is scraped.
Docker Image for PR
|
Docker Image for PR
|
Docker Image for PR
|
I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/
Summary
this pr is a rework of #17266
instead of maintain a global metrics, this pr use prometheus's Collector to dump the metrics when /metrics is scraped.
Tests
Type of change
This change is![Reviewable](https://camo.githubusercontent.com/1541c4039185914e83657d3683ec25920c672c6c5c7ab4240ee7bff601adec0b/68747470733a2f2f72657669657761626c652e696f2f7265766965775f627574746f6e2e737667)