The devDependency tap was updated from 14.8.0 to 14.8.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tap is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

🐛 Bug Report

toLogEntry is expecting options.prefix and options.labels, but these are not passed to the function internally.

To Reproduce

stackdriver.createWriteStream({ resource: '', prefix: 'hi', labels: [...] })

Expected behavior

Should pass prefix and labels to toLogEntry. Currently it only passes resource and keys.

Workaround

Since all the internal functions are exposed, is possible to do this with custom code:

import {
  parseJsonStream,
  toLogEntryStream,
  toStackdriverStream,
} from 'pino-stackdriver/src/stackdriver.js'
import Pumpify from 'pumpify'

declare type PinoStreamOptions = {
  projectId: string
  credentials?: string
  prefix?: string
  logName?: string
  resource?: string
  keys?: {
    httpRequest?: string
    trace?: string
  }
}

const createWriteStream = (options: PinoStreamOptions) =>
  new Pumpify(
    parseJsonStream(),
    toLogEntryStream(options),
    toStackdriverStream(options)
  )

However, it's a pain to make it work with TypeScript due to the lack of types of the internal functions.

The devDependency tap was updated from 14.10.0 to 14.10.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tap is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency @google-cloud/logging was updated from 5.1.2 to 5.1.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@google-cloud/logging is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency snyk was updated from 1.251.0 to 1.251.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

snyk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

I'd like to use pino with Stackdriver-compatible logging. In many Google Cloud environments, stdout will appear in Stackdriver automatically, so I only need the output in the right format. This would match a major design decision behind pino: That the logging process shouldn't care about the transport.

I propose a way to use pino-stackdriver without making calls to the Stackdriver API (for performance and separation of concerns), and without requireing @google-cloud/logging (for faster startup times).

The dependency snyk was updated from 1.249.0 to 1.249.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

snyk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency snyk was updated from 1.252.0 to 1.253.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

snyk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency @types/node was updated from 12.7.3 to 12.7.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency @google-cloud/logging was updated from 7.1.0 to 7.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@google-cloud/logging is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

🐛 Bug Report

When the CLI program hits a 404 response from the Google Cloud API, it does not show any error, just says "logging".

To Reproduce

Try to log with the CLI program to a non-existing project ID.

$ ./my-program | pino-stackdriver --project bar --credentials foo.json
logging

In the Google Cloud Console I see the corresponding errors in the logging API:

However, pino-stackdriver does not tell me about those.

Expected behavior

The CLI program should inform me about the remote API errors so that they can be fixed.

Your Environment

• os: Ubuntu 20.04

🐛 Bug Report

I have everything setup correctly, secret with credentials etc. No errors are thrown but the actual logs are not showing up inside the stackdriver logging for my kubernetes containers

To Reproduce

Steps to reproduce the behavior:

pinoms({
    streams: [
      {
        stream: stackdriver.createWriteStream({
          logName: "NAME",
          projectId: "PROJECT_ID"
        })
      }
    ]
  });

Expected behavior

I want the logs to show up inside the actual container logs/kubernetes. Can this be a problem with missing labels?

Your Environment

• Google Cloud Kubernetes Engine

The devDependency @types/node was updated from 13.7.2 to 13.7.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency tap was updated from 14.10.3 to 14.10.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tap is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Last release on NPM is 10 months old, update on typescript types were 8 months old. Can you release a new version on NPM? @ovhemert

The devDependency @types/node was updated from 12.12.3 to 12.12.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency tap was updated from 14.5.0 to 14.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tap is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

🐛 Bug Report

I am not sure if this is intentional, but it looks like the CLI version requires credentials while the API version does not.

I am deploying to a cloud run instance and the service account associated with the instance has the necessary permissions to write logs.

To Reproduce

Run CLI without passing credentials or having ENV var set.

Expected behavior

Use CLI without specifying credentials.

Your Environment

• GCP Cloud Run
• Service account has log writer permissions

The dependency snyk was updated from 1.243.0 to 1.244.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

snyk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

🚀 Feature Proposal

Support passing credentials object parameter to Stackdriver lib instead of specifying a key file path.

Motivation

Every GCP Node package, including Stackdriver, allows passing credentials in several ways:

• process.env.GOOGLE_APPLICATION_CREDENTIALS with the path to they key file.
• Passing option { keyFilename: '...' } with the path to they key file.
• Passing option { credentials: { client_email: '...', private_key: '...' } } without any key file in disk.

Only the first way is supported in this library but the other ones come handy in some situations.

Example

https://github.com/googleapis/google-auth-library-nodejs/blob/master/samples/credentials.js#L36

https://github.com/googleapis/nodejs-logging/blob/master/src/index.ts#L206

Other

I think this is not hard to implement with backward support by just assigning the current credentials parameter to process.env.GOOGLE_APPLICATION_CREDENTIALS if typeof credentials === 'string', or passing the whole thing to Logging constructor otherwise (and updating the .d.ts file).

🐛 Bug Report

My app can't start because of type error. I'm using it with nestjs pino logger

To Reproduce

Paste your code here:

    LoggerModule.forRoot({
      pinoHttp: [
        {
          name: 'add some name to every JSON line',
          level: 'debug',
          prettyPrint: false,
          useLevelLabels: true,
          // and all the others...
        },
        stackdriver.createWriteStream({
          logName: 'pino-nest',
          projectId: 'yosh-bot-gateway',
        }),
      ],
    }),

Expected behavior

Just work :)

Paste the results here:

(node:28720) UnhandledPromiseRejectionWarning: TypeError: log[chunk.meta.severity] is not a function
    at Writable.write [as _write] (C:\Projects\bot-gateway\node_modules\pino-stackdriver\src\stackdriver.js:84:31)
    at doWrite (_stream_writable.js:415:12)

Your Environment

• os: Windows

The dependency snyk was updated from 1.247.1 to 1.248.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

snyk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency @types/node was updated from 12.12.5 to 12.12.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

🚀 Feature Proposal

This is rather a question, to understand if providing Typescript types are part of this module's path.

Motivation

Leverage this module to be used on Typescript projects.

The devDependency @types/node was updated from 12.0.12 to 12.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I'm trying to integrate this library into a project and although I'm seeing the logs show up with the proper levels in Stackdriver, I'm noticing that I'm missing most of the jsonPayload key/values that I would normally expect such as hostname, pid, and any other items I set up from Pino's base option. This is also true for any custom object I send for the log itself.

const stackdriver = require('pino-stackdriver');
const pino = require('pino');

const credentials = process.env.GOOGLE_APPLICATION_CREDENTIALS;
const projectId = 'xxxxx';
let writeStream;

if (credentials) {
  writeStream = stackdriver.createWriteStream({
    credentials,
    projectId,
  });
}
const logger = pino(
  {
    level: 'trace',
  },
  writeStream || process.stdout
);

const child = logger.child({ childProperty: 'property' });
child.info({ prop: 'something' }, 'PINO this is an info log from child 1!');

All I seeing in Stackdriver logs are:

{
 insertId:  "..........44gwuhZIKBPA_UhWeVQvNxw"  
 jsonPayload: {
  message:  "PINO this is an info log from child 1!"   
 }
 logName:  "projects/xxxxx/logs/pino_log"  
 receiveTimestamp:  "2018-12-22T21:56:44.243763581Z"  
 resource: {
  labels: {
   project_id:  "xxxxx"    
  }
  type:  "global"   
 }
 severity:  "INFO"  
 timestamp:  "2018-12-22T21:56:41.496000051Z"  
}

Notice that jsonPayload is only showing a message key/value. What I'm unsure of is if this is a limitation with pino-stackdriver or a configuration issue on my end.

When I view the Pino log output without writing to this stackdriver stream, I see all the key/values as expected.

{
  "level": 30,
  "time": 1545517082929,
  "msg": "PINO this is an info log from child 1!",
  "pid": 65250,
  "hostname": "xxxxx",
  "childProperty": "property",
  "prop": "something",
  "v": 1
}

When I try other logging solutions such as Bunyan with bunyan-stackdriver, all the necessary key/values get populated.

Before you submit an issue we recommend you first check if an existing issue does not already exist.

Please read this entire template before posting any issue. If you ignore these instructions
and post an issue here that does not follow the instructions, your issue might be closed.

🐛 Bug Report

I am trying to use the credentials as an object, which was added in the new release and the functionality does not appear, installing the package from npm version 2.1.1

To Reproduce

Steps to reproduce the behavior:

• install package
• check the CLI documentation, it is incomplete or does not correspond to the last commit

npm i pino-stackdriver

Expected behavior

be able to use the latest version with the latest changes shown on github

Your Environment

• os: Mac

🐛 Bug Report

The main guide does not work.

To Reproduce

Steps to reproduce the behavior:

const writeStream = stackdriver.createWriteStream({ credentials, projectId })
const logger = pinoms({ streams: [writeStream] })

Expected behavior

I got an error from TypeScript:

$ tsc --build tsconfig.json 
index.ts:53:53 - error TS2741: Property 'stream' is missing in type 'WritableStream' but required in type '{ stream: WritableStream | DestinationStream; level?: "error" | "debug" | "fatal" | "warn" | "info" | "trace" | undefined; }'.

53     const logger = pinoms({ streams: [writeStream] })

Your Environment

• os: Linux
• pino-stackdriver: 2.1.0

https://github.com/ovhemert/pino-stackdriver/blob/master/src/cli.js
It looks like CLI support only "project" and "credentials"

The devDependency @types/node was updated from 12.12.11 to 12.12.12.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @types/node was updated from 13.1.6 to 13.1.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @types/node was updated from 12.0.11 to 12.0.12.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency @google-cloud/logging was updated from 5.2.1 to 5.2.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@google-cloud/logging is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency tap was updated from 14.2.4 to 14.2.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tap is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency @types/node was updated from 12.0.0 to 12.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency snyk was updated from 1.240.3 to 1.241.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

snyk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency @google-cloud/logging was updated from 5.1.3 to 5.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@google-cloud/logging is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency @types/node was updated from 12.0.8 to 12.0.9.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency tap was updated from 13.1.9 to 13.1.10.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tap is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency @google-cloud/logging was updated from 5.2.2 to 5.3.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@google-cloud/logging is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Should logger.error() events be recognized by Error Reporting? I see them show up as expected in Logging.

As per this article, it sounds like logs should automatically be captured in Error Reporting if they follow a certain format (which I think they do?), and if I am using Compute Engine (which I am)
https://cloud.google.com/error-reporting/docs/setup/compute-engine?hl=en_US

Sorry if this is a dumb question, very new to all this...Thanks!

The devDependency sinon was updated from 7.4.1 to 7.4.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

🐛 Bug Report

It currently waits a log line is uploaded and it does not perform batching but uploads one at a time.
Reference from the issue:
pinojs/pino#1064
Currently, it's near impossible to use pino-stackdriver + fastify in the production with this bug. ...

Your Environment

• os: Ubuntu 20.04