Skip to content

docs: add GCP max log size documentation to guides #360

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
skjolber merged 2 commits into from
Apr 30, 2026
Merged

docs: add GCP max log size documentation to guides #360

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e5b90d1
docs: add max size documentation to guides for PR 359
Copilot Apr 30, 2026
9085f78
Merge branch 'increaseMaxSizeForGcp' into copilot/add-documentation-f…
skjolber Apr 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions guides/gRPC.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,6 +163,15 @@ testImplementation ("no.entur.logging.cloud:request-response-spring-boot-starter
```
</details>

Please note:

* GCP `LogEntry` has a hard size limit of 256 KiB. Request/response bodies are truncated at 224 KiB by default to stay safely within this limit, accounting for headers, MDC fields, and other log-framework overhead. Override the default using:
```
entur.logging.request-response.max-body-size=<bytes>
entur.logging.request-response.max-size=<bytes>
```
See also: [Too long lines](troubleShooting.md#too-long-lines).

Adjust the logger using

```
Expand Down
2 changes: 1 addition & 1 deletion guides/troubleShooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,4 +136,4 @@ Does not always translate into `textPayload`.

> Failed to process request with tag kube_abt-xxx_abt-ccc-79d5974b67-jdsk8_abt-ccc_stdout: rpc error: code = InvalidArgument desc = Log entry with size 278.8K exceeds maximum size of 256.0K

Resolution: Truncate long values.
Resolution: Truncate long values. For request-response logging, the library automatically truncates request/response bodies at 224 KiB by default (GCP `LogEntry` max is 256 KiB). The limit can be lowered further via `entur.logging.request-response.max-body-size`.
6 changes: 6 additions & 0 deletions guides/web.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,6 +130,12 @@ Please note:
* For request-response-logging, this library assumes that locally produced JSON has valid syntax and is without pretty-printing.
* This assumption is made so to avoid the processing overhead of unnecessarily parsing JSON documents known to be valid.
* If this assumption for some reason does not hold, use a BodyFilter to compensate.
* GCP `LogEntry` has a hard size limit of 256 KiB. Request/response bodies are truncated at 224 KiB by default to stay safely within this limit, accounting for headers, MDC fields, and other log-framework overhead. Override the default using:
```
entur.logging.request-response.max-body-size=<bytes>
entur.logging.request-response.max-size=<bytes>
```
See also: [Too long lines](troubleShooting.md#too-long-lines).

Some Logbook excludes ([actuator, openapi](https://github.com/entur/cloud-logging/blob/main/request-response/logbook-spring-boot-autoconfigure/src/main/java/no/entur/logging/cloud/spring/logbook/LogbookLoggingAutoConfiguration.java)) are included by default. Add more using

Expand Down
Loading