zrepl/daemon/job
Christian Schwarz 1ae087bfcf [WIP] add and use tracing API as part of package logging
- make `logging.GetLogger(ctx, Subsys)` the authoritative `logger.Logger` factory function
    - the context carries a linked list of injected fields which
      `logging.GetLogger` adds to the logger it returns
- introduce the concept of tasks and spans, also tracked as linked list within ctx
    - [ ] TODO automatic logging of span begins and ends, with a unique
      ID stack that makes it easy to follow a series of log entries in
      concurrent code
    - ability to produce a chrome://tracing-compatible trace file,
      either via an env variable or a `zrepl pprof` subcommand
        - this is not a CPU profile, we already have go pprof for that
        - but it is very useful to visually inspect where the
          replication / snapshotter / pruner spends its time
          ( fixes #307 )
2020-04-25 11:16:59 +02:00
..
reset move wakeup subcommand into signal subcommand and add reset subcommand 2018-10-12 20:50:56 +02:00
wakeup move wakup mechanism into separate package 2018-10-12 12:44:40 +02:00
active.go [WIP] add and use tracing API as part of package logging 2020-04-25 11:16:59 +02:00
activesidestate_enumer.go build: drop go Dep, switch to modules, support Go 1.13 2019-09-14 13:36:44 +02:00
build_jobs_test.go new features: {resumable,encrypted,hold-protected} send-recv, last-received-hold 2020-02-14 22:00:13 +01:00
build_jobs.go new features: {resumable,encrypted,hold-protected} send-recv, last-received-hold 2020-02-14 22:00:13 +01:00
job.go [WIP] add and use tracing API as part of package logging 2020-04-25 11:16:59 +02:00
passive.go [WIP] add and use tracing API as part of package logging 2020-04-25 11:16:59 +02:00
snapjob.go [WIP] add and use tracing API as part of package logging 2020-04-25 11:16:59 +02:00