Closed
Bug 1197812
Opened 9 years ago
Closed 9 years ago
Prefix log lines with taskcuster specific errors/exceptions rather than using the general [taskcluster] prefix
Categories
(Taskcluster :: Workers, defect)
Taskcluster
Workers
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: garndt, Assigned: garndt)
References
Details
Right now all things that the docker-worker inserts into the logs is prefixed as [taskcluster]. To make it easier to designate what's a normal logging statement and an error, we should added error/exception specific prefixes such as [taskcluster-error] and [taskcluster-exception].
Assignee | ||
Comment 1•9 years ago
|
||
Spoke with Jonas and it appears that what would allow us some flexibility in the future is if the taskcluster infrastructure and tools log things such as:
[component:event] message
This would translate into something like this for taskcluster infrastructure errors that docker-worker logs:
[taskcluster:error] Error: Pulling docker image "taskcluster/tester:0.3.6"
Or in the case of tool we develop:
[taskcluster-vcs:error] Unable to extract tar archive
If it's purely an informational message, then the event can be omitted and the log message could be:
[component] message
Assignee | ||
Comment 2•9 years ago
|
||
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Assignee: nobody → garndt
Updated•6 years ago
|
Component: Docker-Worker → Workers
You need to log in
before you can comment on or make changes to this bug.
Description
•