The devDependency tap was updated from 13.1.2 to 13.1.3.

🚨 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 devDependency tap was updated from 14.7.0 to 14.7.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 snyk was updated from 1.246.0 to 1.247.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

Please add TypeScript types to this project. It is written in JavaScript and does not bundle type definitions. If that's not possible, please consider adding types to @types/pino-datadog.

Motivation

I'm working on a project in TypeScript and would like to use this library to stream logs to Datadog.

Example

While I could not find other pino loggers for Datadog, there are a few examples available for Winston that might serve as a starting point:

• datadog-winston: https://www.npmjs.com/package/datadog-winston

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

Using log.debug({ object }, "Debug message"); does not send into Datadog

To Reproduce

Steps to reproduce the behavior:

Paste your code here:

import pino from "pino";
import datadog from "pino-datadog";

const streams = [
  { stream: process.stdout },
  { 
    stream: datadog.createWriteStreamSync({
      apiKey: process.env.DD_API_KEY,
      ddtags: `env:${process.env.NODE_ENV}`,
      eu: true,
    }); 
  }
];

const logger = pino( { level: "debug" }, pino.multistream(streams) );

logger.debug({ foo: "bar" }, "debug message");

Expected behavior

A clear and concise description of what you expected to happen.

Paste the results here:

A message in Datadog with:

{"level":20,"time":1670932284621,"pid":214789,"hostname":"service.host","foo": "bar","msg":"debug message"}

Your Environment

• os: Mac, Windows, Linux
• any other relevant information

The dependency snyk was updated from 1.230.8 to 1.231.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 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 🌴

🚀 Feature Proposal

It would be great if the library logged an error to the console when encountering non-JSON lines.

Motivation

When we first implemented pino-datadog, we had an existing configuration that looked at process.env.NODE_ENV and used pino’s prettyPrint when not in production. Separately, we set the stream to either be process.stdout or pino-datadog's writeStream, depending on the existence of process.env.DD_API_KEY. This led to some confusion + debugging time, as it was failing silently locally (we've since changed our code to base both the log format and stream on process.env.DD_API_KEY).

Considering the library logs errors if the Axios request fails (also useful for debugging), I think it'd also be nice to log when JSON-parsing fails.

Hey,

Just wondering why this function is async?

It makes it so that I can't use this in the top level of my file.

Thanks,
Manthan M

Hello , is multi-stream a requirement in order to setup pino-datadog ?

The CLI documentation states that you have to globally install the package for it to be used in this mode.

If you make the CLI executable (chmod +x src/cli.js) however, the global install requirement is removed and you can install pino-datadog as a normal dependency.

This is similar to how pino-pretty works.

🐛 Bug Report

We use pino-datadog in all our projects and receive this advisory alert on every npm i asaxios is a dependency of pino-datadog.
Please could you release a new version with the new axios version that has already been committed to master by snyk-bot. I'm happy to do it if you share details on how you want it done?

To Reproduce

Steps to reproduce the behaviour:

Paste your code here:

npm install pino-datadog
npm audit

Expected behaviour

Should not have any high severity vulnerabilities (or higher) that have already been resolved by dependency maintainers.

Actual behaviour

Your Environment

• os: Mac
• node: 14.16.0
• npm: 6.14.11

Hi,

You mention that the createWriteStreamAsync() is "async for compatibility reasons". Does this mean it does not use a worker thread?

Thanks!

When including the -e (or --eu) CLI flag I get a status 403:

> node --unhandled-rejections=strict --optimize_for_size --max_old_space_size=115 --gc_interval=100 . | pino-datadog

{"level":30,"time":1574122975941,"pid":91734,"hostname":"[redacted]","msg":"App is running under env 'development', listening on port 8080, and has an available heap size of 113303784 bytes (~0.11GB)","v":1}
The previous log have not been saved
Request failed with status code 403
Error: Request failed with status code 403
    at createError (/Users/devillexio/Developer/devillexio/pino-datadog/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/Users/devillexio/Developer/devillexio/pino-datadog/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/Users/devillexio/Developer/devillexio/pino-datadog/node_modules/axios/lib/adapters/http.js:237:11)
    at IncomingMessage.emit (events.js:215:7)
    at endReadableNT (_stream_readable.js:1183:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)

The same config works when I exclude the flag.

🚀 Feature Proposal

Send log batches after timeout even if the batch is not complete.

Motivation

Services may have non-uniform traffic patterns and as such, it may be the case that some logs take a long time before being submitted.

Example

We could add a new option timeout that default maybe to 30s? This option would mean that every timeout seconds the stream will be flushed even if less than size entries are present.

Currently, having the package included in a project as well as the datadog agent running with log collection enabled in the cluster means that logs are duplicated in the datadog interface, and the duplicated logs are neither tagged nor formatted correctly.

I've created a PR adding a commandline option for this here

The dependency snyk was updated from 1.239.5 to 1.240.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 🌴

Stream with option "size": 10 seems to behave really weird thus it won't send my Logs to the DataDog API but when I remove the options everything works fine.

Is there something broken with the implementation?

Because taken from the docs:

size
Type: String (optional)

The number of log messages to send as a single batch (defaults to 1).

What I would have expected was that if I want to send a single Log to the DataDog API that there shouldnt be a problem.

But as long as I kept that option no Log got through.

Hi,

I am trying to send my pino logs to datadog. I currently use pino like below.. would it be difficult to add pino-datadog on top ?

const config = require('../config')

var getNamespace = require('cls-hooked').getNamespace;


const pino = (config.nodeEnv == 'local') ? require('pino')({
  transport: {
    target: 'pino-pretty',
    options: {
      colorize: true
    },
    messageFormat: "[Request: {requestId}] {msg}",
    ignore: "pid,hostname"

  }
}) : require('pino')(require('pino').destination({ sync: false }));



//decorates with request id, user id and business id
const format = (obj_or_message) => {
  let clsNamespace = getNamespace('app');
  const request_id = clsNamespace.get("request_id")
  const user_id = clsNamespace.get("user_id")
  const business_id = clsNamespace.get("business_id")

  if (typeof obj_or_message == 'object') {
    return Object.assign(obj_or_message, { request_id: request_id, user_id: user_id, business_id: business_id })
  } else {
    return { request_id: request_id, user_id: user_id, business_id: business_id, message: obj_or_message }
  }
}

const wrappedPino = {

  debug: (obj) => {
    pino.debug(format(obj))
  },
  warn: (obj) => {
    pino.warn(format(obj))
  },
  info: (obj) => {
    pino.info(format(obj))
  },
  error: (obj) => {
    pino.error(format(obj))
  },
}


module.exports = wrappedPino;

where do I specify my datadog key?