Open
Bug 1363217
Opened 7 years ago
Updated 4 years ago
Add worker creation time to task logs
Categories
(Taskcluster :: Workers, enhancement)
Taskcluster
Workers
Tracking
(Not tracked)
NEW
People
(Reporter: gps, Unassigned)
Details
Currently, the top of a Windows worker log looks something like this: [taskcluster 2017-05-08T11:53:40.869Z] Worker Type (gecko-3-b-win2012) settings: [taskcluster 2017-05-08T11:53:40.961Z] { [taskcluster 2017-05-08T11:53:40.962Z] "aws": { [taskcluster 2017-05-08T11:53:40.962Z] "ami-id": "ami-1b40dd0d", [taskcluster 2017-05-08T11:53:40.962Z] "availability-zone": "us-east-1e", [taskcluster 2017-05-08T11:53:40.962Z] "instance-id": "i-06ed0316631b69e96", [taskcluster 2017-05-08T11:53:40.962Z] "instance-type": "c4.4xlarge", [taskcluster 2017-05-08T11:53:40.962Z] "local-ipv4": "172.31.60.88", [taskcluster 2017-05-08T11:53:40.962Z] "public-hostname": "ec2-52-91-149-116.compute-1.amazonaws.com", [taskcluster 2017-05-08T11:53:40.962Z] "public-ipv4": "52.91.149.116" [taskcluster 2017-05-08T11:53:40.962Z] }, [taskcluster 2017-05-08T11:53:40.962Z] "config": { [taskcluster 2017-05-08T11:53:40.962Z] "deploymentId": "0cbd955f0361", [taskcluster 2017-05-08T11:53:40.962Z] "runTaskAsCurrentUser": false [taskcluster 2017-05-08T11:53:40.962Z] }, [taskcluster 2017-05-08T11:53:40.962Z] "generic-worker": { [taskcluster 2017-05-08T11:53:40.962Z] "go-arch": "amd64", [taskcluster 2017-05-08T11:53:40.963Z] "go-os": "windows", [taskcluster 2017-05-08T11:53:40.963Z] "go-version": "go1.7.5", [taskcluster 2017-05-08T11:53:40.963Z] "release": "https://github.com/taskcluster/generic-worker/releases/tag/v8.2.0", [taskcluster 2017-05-08T11:53:40.963Z] "version": "8.2.0" [taskcluster 2017-05-08T11:53:40.963Z] }, [taskcluster 2017-05-08T11:53:40.963Z] "machine-setup": { [taskcluster 2017-05-08T11:53:40.963Z] "ami-created": "2017-04-20 14:02:32.816Z", [taskcluster 2017-05-08T11:53:40.963Z] "manifest": "https://github.com/mozilla-releng/OpenCloudConfig/blob/0cbd955f0361935e1361a5e559f0b8522f529dd0/userdata/Manifest/gecko-3-b-win2012.json" [taskcluster 2017-05-08T11:53:40.963Z] } [taskcluster 2017-05-08T11:53:40.963Z] } Would it be possible to get "instance-created" (or similar) added to "machine-setup" so we have a general idea of when the machine was created? That would help us understand if a machine is new versus old, which could help assess certain performance characteristics. Something else that would help is a count of previously executed tasks. This would allow us to bucket new workers from old ones, which again would help us make better decisions around optimizing tasks for new versus old workers.
Updated•6 years ago
|
Assignee: nobody → pmoore
Component: General → Generic-Worker
QA Contact: pmoore
Reporter | ||
Comment 3•6 years ago
|
||
I /think/ this feature is newer than the bug filing date, but run-task maintains files in caches logging which tasks used a cache. We display this list of tasks when the cache is "corrupted" so we can identify "bad" tasks and prevent further corruption. I feel like mentioning that feature because it is in the same vein as this one: having a forensic log of worker activity to debug and better understand the behavior of an individual worker.
Assignee | ||
Updated•5 years ago
|
Component: Generic-Worker → Workers
Updated•5 years ago
|
Assignee: pmoore → nobody
Updated•4 years ago
|
QA Whiteboard: [lang=go]
You need to log in
before you can comment on or make changes to this bug.
Description
•