You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Overly large log messages cause the node process to crash with out of memory.
This happens frequently:
logzio-logger error: Error: There was a problem with the request.
Response: 413: 413 - "" Error: There was a problem with the request.
Response: 413: 413 - ""
at /var/app/current/node_modules/logzio-nodejs/lib/logzio-nodejs.js:305:42
at tryCatcher (/var/app/current/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/var/app/current/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/var/app/current/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromise0 (/var/app/current/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/var/app/current/node_modules/bluebird/js/release/promise.js:689:18)
at Async._drainQueue (/var/app/current/node_modules/bluebird/js/release/async.js:133:16)
at Async._drainQueues (/var/app/current/node_modules/bluebird/js/release/async.js:143:10)
at Immediate.Async.drainQueues [as _onImmediate] (/var/app/current/node_modules/bluebird/js/release/async.js:17:14)
at processImmediate (internal/timers.js:439:21)
Then at the end this. Presumably, the failed send is retained for retry which is not appropriate if the message is too large and will not index anyway if it does get through to logz.
Overly large log messages cause the node process to crash with out of memory.
This happens frequently:
Then at the end this. Presumably, the failed send is retained for retry which is not appropriate if the message is too large and will not index anyway if it does get through to logz.
The text was updated successfully, but these errors were encountered: