scriptworker metrics not found

Open
#404 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
observability

Research direction

Start by reviewing Bugzilla 1587471 and generic-worker's metrics.go, especially the WORKER_METRICS example and its event fields. Then identify which scriptworker events should emit relevant worker metrics; done means those metrics are logged consistently for scriptworkers.

Written by the indexing model from the issue text.

Description

Like in https://bugzilla.mozilla.org/show_bug.cgi?id=1587471, we should log relevant worker metrics from our scriptworkers.

For example generic worker is emitting events like this:

WORKER_METRICS {"eventType":"instanceBoot","instanceType":"c5.2xlarge","region":"us-east-1","timestamp":1572379815,"worker":"generic-worker","workerId":"i-09518db4433b5924e","workerPoolId":"aws-provisioner-v1/gecko-t-win10-64"}

See also:
https://github.com/taskcluster/generic-worker/blob/master/metrics.go#L10

Dominant language
Python
Stars
5
Forks
39
Avg merge
4h 18m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla-releng/scriptworker

All issues in mozilla-releng/scriptworker

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.