losalex

Results 11 issues of losalex

In few cases when we retrieve the package version by calling [getNodejsLibraryVersion](https://github.com/googleapis/nodejs-logging/blob/42859ab634721cb57ca76960f8a8aa5f6dd3a987/src/utils/instrumentation.ts#L168) the content from package.json is returned. This fix tries to retrieve version from JSON and returns 'unknown' value...

api: logging
size: s

`Log` supports maxEntrySize and truncate functionality is not supported in LogSync - we should add support in maxEntrySize for consistency

type: feature request
api: logging
priority: p3
logging-resilience

**Is your feature request related to a problem? Please describe.** Today some requests might contain oversized log entries which cause entire write request to be dropped instead just of oversized...

priority: p3
type: feature request
api: logging
logging-resilience

Discovered in [732](https://github.com/googleapis/nodejs-logging-winston/issues/732).

type: bug
priority: p2
api: logging

**Is your feature request related to a problem? Please describe.** Today some requests might contain oversized log entries which cause entire write request to be dropped instead just of oversized...

priority: p3
type: feature request
api: logging
logging-resilience

1) Is this a client library issue or a product issue? When running locally on my MAC, I got too many errors: `(node:11479) UnhandledPromiseRejectionWarning: Error: Unable to detect a Project...

type: bug
priority: p3
api: logging
lang: nodejs

Today we print `timestamp` in `nanos` and `seconds` format (see [imestamp-processing](https://cloud.google.com/logging/docs/agent/logging/configuration#timestamp-processing) for more info). However, this format is less readable especially for output printed to `stdout`, so it might be...

type: feature request
api: logging
priority: p3

Update to latest `nodejs-logging` which contains a [1352](https://github.com/googleapis/nodejs-logging/issues/1352) fix.

type: bug
priority: p2
api: logging
logging-resilience

Add support for automatic log splitting per [LogSplit](https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry#LogSplit)

type: feature request
api: logging
priority: p3

As raised in [732](https://github.com/googleapis/nodejs-logging-winston/issues/732), there is a problem with handling invalid payload in [client-interceptors.ts](https://github.com/grpc/grpc-node/blob/6764dcc79602faee5457243629da520ba08b726f/packages/grpc-js/src/client-interceptors.ts#L373): 1. When `latency` contains a [Duration](https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry#HttpRequest) as string (e.g. "1s"), the following failure occurs: **google.logging.type.HttpRequest.latency: object...

priority: p2
type: bug