1616931 - support logging plugins to pipe worker logs to various places

Status: NEW

(Taskcluster :: Workers, task)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

We would probably support syslog / event log, as well as stackdriver, papertrail, etc. This would allow configuration of logging destinations at the worker-pool level, rather than baking it into the image. This also includes supporting structured logging, both reading from the worker and writing to log destinations

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

WIP in https://github.com/djmitche/taskcluster/tree/bug1616931

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

https://github.com/taskcluster/taskcluster/pull/2435

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

What remains:

• Support for backends other than stdio
  • syslog, for sending directly to papertrail without involving the system logger (I haven't found a golang library for this yet..)
  • stackdriver? some other structured log aggregator?
• docker-worker support (using the log message type)
• Add structured logs to workers where necessary (@walac maybe the WORKER_METRICS makes sense to do with structured logging?)

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

I'm moving this back to the backlog in https://github.com/orgs/taskcluster/projects/5 as it's not blocking anything right now. The portion I've completed is still likely to be useful on its own, and the previous comment gives next steps.

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

Bug 1436274 requests an event-log backend.

Bug 1529660 is about adding structured logging to workers, but without any particular motivation.