Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

#98 Error: 3 INVALID_ARGUMENT: Log entry with size 6.23M exceeds maximum size of 256.0K

See original GitHub issue

Environment details

OS: Ubuntu Xenial
Node.js version: v8.11.2
@google-cloud/logging-bunyan version: 0.9.5

Steps to reproduce

Create a big object bigger than 256ko
logger.info(object, message);

It throws an error when it’s happening and sometimes stop my node process

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:9 (4 by maintainers)

Top GitHub Comments

5reactions

mike-luabasecommented, Jun 11, 2022

Truncate your objects to 256 kb before sending

how did you do this? we’re sending a JSON, so you can’t really truncate it (will invalidate the JSON)

3reactions

alexander-fenstercommented, Jul 15, 2019

This is not coming from grpc-js, but from the logging server. This page says that, regardless of the batch size limit, the size of each entry cannot exceed 256K. This looks like the stackdriver API limitation, not a client library issue.

I’ll close this for now, feel free to reopen if you have any questions! Thanks 😃