Page MenuHomePhabricator

Count all running subtasks of the evaluator when monitoring for process issues, not just those that contain "wasm"
Open, MediumPublic

Description

Description

We currently populate our "WASM subprocess count" metric with pgrep wasm | wc -l. However, if the evaluator is failing due to an excess of processes, not all of the processes necessarily contain wasm (each wasmedge invocation spawns 1 or 2 additional child processes). We should just use ps aux instead of pgrep.

Desired behavior/Acceptance criteria (returned value, expected error, performance expectations, etc.)

  • change the command used to track subprocess count
  • change the name in the Grafana dashboard to reflect that this is a total process count

Completion checklist

Event Timeline

Is this a sub-task of T406848?

Ah! Yes, I have marked it as such.

Jdforrester-WMF renamed this task from Count all running subtasks, not just those that contain "wasm" to Count all running subtasks of the evaluator when monitoring for process issues, not just those that contain "wasm".Tue, Dec 2, 3:42 PM