zrepl/internal/daemon/main.go

package daemon

import (
	"context"

	"github.com/zrepl/zrepl/internal/cli"
	"github.com/zrepl/zrepl/internal/logger"
)

type Logger = logger.Logger

var DaemonCmd = &cli.Subcommand{
	Use:   "daemon",
	Short: "run the zrepl daemon",
	Run: func(ctx context.Context, subcommand *cli.Subcommand, args []string) error {
		return Run(ctx, subcommand.Config())
	},
}
start implementing new daemon in package daemon 2018-08-27 19:10:55 +02:00			`package daemon`

			`import (`
[#307] add package trace, integrate it with logging, and adopt it throughout zrepl package trace: - introduce the concept of tasks and spans, tracked as linked list within ctx - see package-level docs for an overview of the concepts - main feature 1: unique stack of task and span IDs - makes it easy to follow a series of log entries in concurrent code - main feature 2: 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 ) usage in package daemon/logging: - goal: every log entry should have a trace field with the ID stack from package trace - 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 - `logging.GetLogger` also uses package `trace` to get the task-and-span-stack and injects it into the returned logger's fields 2020-04-11 15:49:41 +02:00			`"context"`

move implementation to `internal/` directory (#828) 2024-10-18 19:21:17 +02:00			`"github.com/zrepl/zrepl/internal/cli"`
			`"github.com/zrepl/zrepl/internal/logger"`
start implementing new daemon in package daemon 2018-08-27 19:10:55 +02:00			`)`

			`type Logger = logger.Logger`
cli: refactor to allow definition of subcommands next to their implementation 2018-10-13 15:07:50 +02:00
format source tree using goimports 2019-03-22 19:41:12 +01:00			`var DaemonCmd = &cli.Subcommand{`
cli: refactor to allow definition of subcommands next to their implementation 2018-10-13 15:07:50 +02:00			`Use: "daemon",`
			`Short: "run the zrepl daemon",`
[#307] add package trace, integrate it with logging, and adopt it throughout zrepl package trace: - introduce the concept of tasks and spans, tracked as linked list within ctx - see package-level docs for an overview of the concepts - main feature 1: unique stack of task and span IDs - makes it easy to follow a series of log entries in concurrent code - main feature 2: 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 ) usage in package daemon/logging: - goal: every log entry should have a trace field with the ID stack from package trace - 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 - `logging.GetLogger` also uses package `trace` to get the task-and-span-stack and injects it into the returned logger's fields 2020-04-11 15:49:41 +02:00			`Run: func(ctx context.Context, subcommand *cli.Subcommand, args []string) error {`
			`return Run(ctx, subcommand.Config())`
cli: refactor to allow definition of subcommands next to their implementation 2018-10-13 15:07:50 +02:00			`},`
			`}`