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.

Error: Attempt to write logs with no transports

See original GitHub issue

From @dorshay6 on October 11, 2018 13:31

When sending a large log (body of the requestor sql query) I get the following error and there is no way to limit log size from Winston.

[winston] Attempt to write logs with no transports {“message”:“Thu, 11 Oct 2018 13:04:32 GMT uncaughtException: 3 INVALID_ARGUMENT: Log entry with size 318.8K exceeds maximum size of 110.0K, stack: Error: 3 INVALID_ARGUMENT: Log entry with size 318.8K exceeds maximum size of 110.0K\n    at Object.exports.createStatusError (/usr/src/app/node_modules/grpc/src/common.js:87:15)\n    at Object.onReceiveStatus (/usr/src/app/node_modules/grpc/src/client_interceptors.js:1188:28)\n    at InterceptingListener._callNext (/usr/src/app/node_modules/grpc/src/client_interceptors.js:564:42)\n    at InterceptingListener.onReceiveStatus (/usr/src/app/node_modules/grpc/src/client_interceptors.js:614:8)\n    at callback (/usr/src/app/node_modules/grpc/src/client_interceptors.js:841:24)“,”level”:“error”}

Environment details

OS: Docker (node:8.9.4)
Node.js version: 8.9.4
npm version:
@google-cloud/logging-winston version: 0.10.2

Steps to reproduce

Send a log with over 110k size

Copied from original issue: googleapis/nodejs-logging-winston#190

Issue Analytics

State:
Created 5 years ago
Reactions:3
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

DominicKramercommented, Mar 15, 2019

I’ve moved this issue to the nodejs-logging repo since this issue should be handled by the @google-cloud/logging module itself that @google-cloud/logging-winston and @google-cloud/logging-bunyan use.

0reactions

DominicKramercommented, Mar 15, 2019

From @dinvlad on March 11, 2019 0:3

I’d say that splitting messages into multiple lines would be the first and easier way to solve the problem (I’d even guess this covers the majority of setups).

Top Results From Across the Web

Attempt to write logs with no transports - using default logger ...

createLogger . The readme states using "your own logger" as the recommended way. Nevertheless I would rather prefer to use the "default logger" ......

Attempt to write logs with no transports. · Issue #1645 - GitHub

What is the problem? Attempt to write logs with no transports on console. [winston] Attempt to write logs with no transports {"message": ...

How To Log Like A Boss With Node.js | by Eren Yatkin

Winston provides levelled logs such as error , verbose , silly , info , debug . ... [winston] Attempt to write logs with...

Attempt to write logs with no transports – using default logger ...

Best Solution. In winston 3 you need to create a logger object, then add transport s to it.

Winston Attempt to write logs with no transports

Defaults to metadata. fillExcept: An array of keys that should not be added to the metadata object. Winston log error object. A logger...