Unable to flush; exceeding quota

Environment details

• OS: Linux
• Node.js version: 10.16
• npm version: 6.9.0
• @google-cloud/logging version:^5.1.0

Steps to reproduce

1. Do async logging
2. Observe no async callback messages untill app is closed

So if you’re writing a lot of logs, and want to space them out in time to avoid exceeding the quota, it is not clear how to do this. A search for ‘flush’ in the repo returns empty.

ERROR: { Error: Bandwidth exhausted
    at Http2CallStream.call.on (/x/node_modules/@grpc/grpc-js/build/src/client.js:101:45)
    at Http2CallStream.emit (events.js:203:15)
    at process.nextTick (/x/node_modules/@grpc/grpc-js/build/src/call-stream.js:71:22)
    at process._tickCallback (internal/process/next_tick.js:61:11)
  code: 8,
  details: 'Bandwidth exhausted',
  metadata: Metadata { options: undefined, internalRepr: Map {} },
  note:
   'Exception occurred in retry method that was not classified as transient' }

[alexander-fenster]

@stephenplusplus This gist https://gist.github.com/alexander-fenster/883347a958d529c5b8a5289132b92e45 shows how to override default batching settings.

[stephenplusplus]

Yeah, that would be great, just to help anyone who stops by. Sorry I missed the other sample.