Skip to content

fix(taskworker) Add dimensions to memory_change metric #94000

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

Merged
merged 3 commits into from
Jun 23, 2025

Conversation

markstory
Copy link
Member

We'd need taskname as a dimension to find which task was increasing memory usage.

We'd need taskname as a dimension to find which task was increasing
memory usage.
@markstory markstory requested a review from a team as a code owner June 20, 2025 21:33
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jun 20, 2025
Copy link

codecov bot commented Jun 20, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #94000      +/-   ##
==========================================
- Coverage   88.02%   88.02%   -0.01%     
==========================================
  Files       10349    10349              
  Lines      598482   598486       +4     
  Branches    23244    23244              
==========================================
  Hits       526822   526822              
- Misses      71190    71194       +4     
  Partials      470      470              

@@ -309,7 +309,9 @@ def _execute_activation(task_func: Task[Any, Any], activation: TaskActivation) -
origin="taskworker",
)
with (
track_memory_usage("taskworker.worker.memory_change"),
track_memory_usage(
"taskworker.worker.memory_change", tags={"taskname": activation.taskname}
Copy link
Member

Choose a reason for hiding this comment

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

Can we add namespace to this too?

@markstory markstory merged commit a3d8dc4 into master Jun 23, 2025
64 checks passed
@markstory markstory deleted the fix-taskworker-memory-metric branch June 23, 2025 17:51
@github-actions github-actions bot locked and limited conversation to collaborators Jul 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants