From 2dfade9a5ffe5d9fcd457b39eba3a8d004ba6301 Mon Sep 17 00:00:00 2001 From: Jean-Hadrien Chabran Date: Tue, 11 Jul 2023 19:36:53 +0200 Subject: [PATCH] doc: mention json_gcp format for logs (#54793) Mentions the availability of `SRC_LOG_FORMAT=json_gcp` in the admin/observability/logging page. ## Test plan CI. --- doc/admin/observability/logs.md | 1 + 1 file changed, 1 insertion(+) diff --git a/doc/admin/observability/logs.md b/doc/admin/observability/logs.md index f35b1af963d..8b4d5e4b56e 100644 --- a/doc/admin/observability/logs.md +++ b/doc/admin/observability/logs.md @@ -23,6 +23,7 @@ A Sourcegraph service's log output format is configured via the environment vari * `condensed`: Optimized for human readability. * `json`: Machine-readable JSON format. * For certain services and log entries, Sourcegraph exports a [OpenTelemetry-compliant log data model](#opentelemetry). +* `json_gcp`: Machine-readable JSON format, tailored to [GCP cloud-logging expected structure.](https://cloud.google.com/logging/docs/structured-logging#special-payload-fields) * `logfmt`: The [logfmt](https://github.com/kr/logfmt) format. * Note that `logfmt` is no longer supported with [Sourcegraph's new internal logging standards](../../dev/how-to/add_logging.md) - if you need structured logs, we recommend using `json` instead. If set to `logfmt`, log output from new loggers will be in `condensed` format.