Bug 1616931 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

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?)
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?)
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?)
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?)
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?)
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?)

Back to Bug 1616931 Comment 3