-
-
Notifications
You must be signed in to change notification settings - Fork 717
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
add prometheus metric for time and memory used per task prefix #7406
Conversation
04ff2d1
to
127bdab
Compare
e76ec9c
to
bc06bc9
Compare
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 24 files ±0 24 suites ±0 10h 2m 26s ⏱️ - 8m 31s For more details on these failures, see this check. Results for commit b8f554d. ± Comparison against base commit fae59c4. ♻️ This comment has been updated with latest results. |
6e488b0
to
dcd4fcc
Compare
7cf3097
to
29b72e4
Compare
29b72e4
to
74a9765
Compare
Co-authored-by: Nat Tabris <46289310+ntabris@users.noreply.github.com>
docs/source/prometheus.rst
Outdated
Total time (per prefix) spent computing tasks | ||
dask_scheduler_tasks_transfer_seconds_total | ||
Total time (per prefix) spent transferring | ||
dask_scheduler_tasks_output_bytes_total |
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 changed the labels.
This makes me think that it could be valuable to measure the input bytes as well, so that we can get information about compression / expansion points in the graph.
TaskPrefix.nbytes_total is the current size in memory, not a cumulative history. I changed the metric to a Gauge. |
closes #7341
pre-commit run --all-files