Add structured logging infrastructure (#246)
New global flags:
* `--log-file FILE`: can be literal `stdout`, `stderr`, or a file name (default `stderr`)
* `--log-level LEVEL`: can be `error`, `warn`, `info`, `debug`, `trace`, or `disabled` (default `disabled`)
* `--log-format TYPE`: can be `text` or `json` (default `text`)
New functions in the `log` package take a `context.Context` and retrieve
the logger from said context.
Because we carry the logger in a context, adding
[attributes](https://pkg.go.dev/golang.org/x/exp/slog#hdr-Attrs_and_Values)
to the logger can be done as follows:
```go
ctx = log.NewContext(ctx, log.GetLogger(ctx).With("foo", "bar"))
```
2023-03-16 13:46:53 +00:00
|
|
|
package root
|
|
|
|
|
|
|
|
import (
|
|
|
|
"context"
|
|
|
|
"fmt"
|
2023-03-21 16:05:04 +00:00
|
|
|
"os"
|
Add structured logging infrastructure (#246)
New global flags:
* `--log-file FILE`: can be literal `stdout`, `stderr`, or a file name (default `stderr`)
* `--log-level LEVEL`: can be `error`, `warn`, `info`, `debug`, `trace`, or `disabled` (default `disabled`)
* `--log-format TYPE`: can be `text` or `json` (default `text`)
New functions in the `log` package take a `context.Context` and retrieve
the logger from said context.
Because we carry the logger in a context, adding
[attributes](https://pkg.go.dev/golang.org/x/exp/slog#hdr-Attrs_and_Values)
to the logger can be done as follows:
```go
ctx = log.NewContext(ctx, log.GetLogger(ctx).With("foo", "bar"))
```
2023-03-16 13:46:53 +00:00
|
|
|
|
|
|
|
"github.com/databricks/bricks/libs/flags"
|
|
|
|
"github.com/databricks/bricks/libs/log"
|
|
|
|
"golang.org/x/exp/slog"
|
|
|
|
)
|
|
|
|
|
2023-03-21 16:05:04 +00:00
|
|
|
const (
|
|
|
|
envBricksLogFile = "BRICKS_LOG_FILE"
|
|
|
|
envBricksLogLevel = "BRICKS_LOG_LEVEL"
|
|
|
|
envBricksLogFormat = "BRICKS_LOG_FORMAT"
|
|
|
|
)
|
|
|
|
|
2023-03-29 12:58:09 +00:00
|
|
|
func initializeLogger(ctx context.Context) (context.Context, error) {
|
Add structured logging infrastructure (#246)
New global flags:
* `--log-file FILE`: can be literal `stdout`, `stderr`, or a file name (default `stderr`)
* `--log-level LEVEL`: can be `error`, `warn`, `info`, `debug`, `trace`, or `disabled` (default `disabled`)
* `--log-format TYPE`: can be `text` or `json` (default `text`)
New functions in the `log` package take a `context.Context` and retrieve
the logger from said context.
Because we carry the logger in a context, adding
[attributes](https://pkg.go.dev/golang.org/x/exp/slog#hdr-Attrs_and_Values)
to the logger can be done as follows:
```go
ctx = log.NewContext(ctx, log.GetLogger(ctx).With("foo", "bar"))
```
2023-03-16 13:46:53 +00:00
|
|
|
opts := slog.HandlerOptions{}
|
|
|
|
opts.Level = logLevel.Level()
|
|
|
|
opts.AddSource = true
|
2023-03-23 07:56:39 +00:00
|
|
|
opts.ReplaceAttr = log.ReplaceAttrFunctions{
|
|
|
|
log.ReplaceLevelAttr,
|
|
|
|
log.ReplaceSourceAttr,
|
|
|
|
}.ReplaceAttr
|
Add structured logging infrastructure (#246)
New global flags:
* `--log-file FILE`: can be literal `stdout`, `stderr`, or a file name (default `stderr`)
* `--log-level LEVEL`: can be `error`, `warn`, `info`, `debug`, `trace`, or `disabled` (default `disabled`)
* `--log-format TYPE`: can be `text` or `json` (default `text`)
New functions in the `log` package take a `context.Context` and retrieve
the logger from said context.
Because we carry the logger in a context, adding
[attributes](https://pkg.go.dev/golang.org/x/exp/slog#hdr-Attrs_and_Values)
to the logger can be done as follows:
```go
ctx = log.NewContext(ctx, log.GetLogger(ctx).With("foo", "bar"))
```
2023-03-16 13:46:53 +00:00
|
|
|
|
|
|
|
// Open the underlying log file if the user configured an actual file to log to.
|
|
|
|
err := logFile.Open()
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
var handler slog.Handler
|
|
|
|
switch logOutput {
|
|
|
|
case flags.OutputJSON:
|
|
|
|
handler = opts.NewJSONHandler(logFile.Writer())
|
|
|
|
case flags.OutputText:
|
|
|
|
handler = opts.NewTextHandler(logFile.Writer())
|
|
|
|
default:
|
|
|
|
return nil, fmt.Errorf("invalid log output: %s", logOutput)
|
|
|
|
}
|
|
|
|
|
|
|
|
slog.SetDefault(slog.New(handler))
|
|
|
|
return log.NewContext(ctx, slog.Default()), nil
|
|
|
|
}
|
|
|
|
|
|
|
|
var logFile = flags.NewLogFileFlag()
|
|
|
|
var logLevel = flags.NewLogLevelFlag()
|
|
|
|
var logOutput = flags.OutputText
|
|
|
|
|
|
|
|
func init() {
|
2023-03-21 16:05:04 +00:00
|
|
|
// Configure defaults from environment, if applicable.
|
|
|
|
// If the provided value is invalid it is ignored.
|
|
|
|
if v, ok := os.LookupEnv(envBricksLogFile); ok {
|
|
|
|
logFile.Set(v)
|
|
|
|
}
|
|
|
|
if v, ok := os.LookupEnv(envBricksLogLevel); ok {
|
|
|
|
logLevel.Set(v)
|
|
|
|
}
|
|
|
|
if v, ok := os.LookupEnv(envBricksLogFormat); ok {
|
|
|
|
logOutput.Set(v)
|
|
|
|
}
|
|
|
|
|
Add structured logging infrastructure (#246)
New global flags:
* `--log-file FILE`: can be literal `stdout`, `stderr`, or a file name (default `stderr`)
* `--log-level LEVEL`: can be `error`, `warn`, `info`, `debug`, `trace`, or `disabled` (default `disabled`)
* `--log-format TYPE`: can be `text` or `json` (default `text`)
New functions in the `log` package take a `context.Context` and retrieve
the logger from said context.
Because we carry the logger in a context, adding
[attributes](https://pkg.go.dev/golang.org/x/exp/slog#hdr-Attrs_and_Values)
to the logger can be done as follows:
```go
ctx = log.NewContext(ctx, log.GetLogger(ctx).With("foo", "bar"))
```
2023-03-16 13:46:53 +00:00
|
|
|
RootCmd.PersistentFlags().Var(&logFile, "log-file", "file to write logs to")
|
|
|
|
RootCmd.PersistentFlags().Var(&logLevel, "log-level", "log level")
|
|
|
|
RootCmd.PersistentFlags().Var(&logOutput, "log-format", "log output format (text or json)")
|
|
|
|
RootCmd.RegisterFlagCompletionFunc("log-file", logFile.Complete)
|
|
|
|
RootCmd.RegisterFlagCompletionFunc("log-level", logLevel.Complete)
|
|
|
|
RootCmd.RegisterFlagCompletionFunc("log-format", logOutput.Complete)
|
|
|
|
}
|