zrepl/transport
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
..
fromconfig format source tree using goimports 2019-03-22 19:41:12 +01:00
local Spellcheck all files 2020-02-24 16:06:09 +01:00
ssh Spellcheck all files 2020-02-24 16:06:09 +01:00
tcp rpc: proper handling of context cancellation for transportmux + dataconn 2020-04-25 10:44:17 +02:00
tls fix some typos 2020-02-17 18:02:04 +01:00
transport.go [WIP] add and use tracing API as part of package logging 2020-04-25 11:16:59 +02:00