Epic: Worker Monitoring
@josephjclark is already working on this.
Since Aug 22, 2024.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
An epic issue to have oversight over monitoring on the worker.
The high level brief is: we need better visibility of what's going on inside the worker, especially when things go wrong.
We should consider metrics tracking, sentry reporting, email notification, grafana, etc.
Related:
#603
#402
Things we want
- When a worker claims something (we do this already in Lightning, but will be useful later to track drift between what lightning thinks and what the worker knows).
- When a worker has to kill a run or job.
- Memory sampling for:
- At least the whole process tree
- engine
- workers? (will need to think about how useful this is on it's own since they are 'disposable processes' and picking them out of a crowd in monitoring may not be that useful).
- CPU usage? (might just be solved by monitoring the pod directly)
We need to figure out the best approach for how to integrate this into prometheus, do we expose an aggregate http service (or use lightning for that) that collects up the metrics?
We probably don't want to use service discovery for monitoring? Do we?
There is an advantage of workers exposing their own /metrics server, makes the worker better for everyone.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.