1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
|
# `clog/gcp`: structured logging for Google Cloud using [`slog`](https://pkg.go.dev/log/slog)
Contrary to the
[documented "standard" approach for logging](https://cloud.google.com/logging/docs/setup/go),
this doesn't use any third-party logging package for logging.
Instead, it relies on Google Cloud's support for ingesting structured logs by
simply printing JSON to stderr.
This method of emitting structured logs is supported by:
- [Cloud Run](https://cloud.google.com/run/docs/logging#using-json)
- [Kubernetes Engine](https://cloud.google.com/logging/docs/structured-logging#special-payload-fields)
- [Cloud Functions](https://cloud.google.com/functions/docs/monitoring/logging#writing_structured_logs)
- [App Engine](https://cloud.google.com/logging/docs/structured-logging#special-payload-fields)
(standard and flexible)
- and in other products, using the
[Cloud Logging agent](https://cloud.google.com/logging/docs/agent/logging) and
[Ops agent](https://cloud.google.com/logging/docs/agent/ops-agent).
## Basic Usage
To use this, underscore-import `gcp/init`, which will configure `slog` to use
the GCP-optimized JSON handler for all log messages:
Then when you use `slog`, all log messages will be output in JSON format to
standard error, which is automatically ingested by Cloud Logging.
```go
import _ "github.com/chainguard-dev/clog/gcp/init"
...
http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
slog.InfoContext(r.Context(), "my message",
"mycount", 42,
"mystring", "myvalue",
)
})
```
This logs the message, with the additional structured logging fields in Cloud
Logging:
<table><tr><td><img src="basic.png" width=50%/></td></tr></table>
## Correlating Logs with Requests
You can also use this to correlate log lines with the request that generated
them, by associating the log message with the request's trace context header.
```go
import "github.com/chainguard-dev/clog/gcp"
...
http.Handle("/", gcp.WithCloudTraceContext(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
slog.InfoContext(r.Context(), "my message",
"mycount", 42,
"mystring", "myvalue",
)
})))
```
This logs the message, associated with the request's trace, in Cloud Logging:
<table><tr><td><img src="correlated.png" width=50%/></td></tr></table>
Other logs with the same `trace` attribute are generated by the same incoming
request.
See https://cloud.google.com/trace/docs/trace-log-integration for more
information.
## Critical Logging
Cloud Logging supports a **CRITICAL** logging level, which doesn't map cleanly
to `slog`'s built-in levels.
To log at this level:
```go
slog.Log(ctx, gcp.LevelCritical, "I have a bad feeling about this...")
```
See `./cmd/example` for a deployable example.
---
This repo is forked from https://github.com/remko/cloudrun-slog, which
originated this idea and implementation.
|
