Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

regression on 3.16.0: "ecsFormat is not a function"

See original GitHub issue

Describe the bug

node_modules/elastic-apm-node/lib/logging.js:142
...ecsFormat({ apmIntegration: false })
^

TypeError: ecsFormat is not a function
at Object.createLogger (app/node_modules/elastic-apm-node/lib/logging.js:142:8)
at new Config (app/node_modules/elastic-apm-node/lib/config.js:260:27)
at config (app/node_modules/elastic-apm-node/lib/config.js:222:10)
at Agent._config (app/node_modules/elastic-apm-node/lib/agent.js:145:16)
at new Agent (app/node_modules/elastic-apm-node/lib/agent.js:38:8)
at Object.<anonymous> (app/node_modules/elastic-apm-node/index.js:5:18)

To Reproduce

bumped from 3.15.0 to 3.16.0

Expected behavior

it should not break

Environment (please complete the following information)

OS: [e.g. Linux] linux docker, mac os x
Node.js version: v14.16.1
APM Server version:
Agent version:

How are you starting the agent? (please tick one of the boxes)

Calling agent.start() directly (e.g. require('elastic-apm-node').start(...))
Requiring elastic-apm-node/start from within the source code
Starting node with -r elastic-apm-node/start

Additional context

Agent config options

Click to expand

replace this line with your agent config options

package.json dependencies:

Click to expand

replace this line with your dependencies section from package.json

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

trentmcommented, Jun 15, 2021

Okay, thanks. Let me know if you hit other problems. There is some potentially confusing interplay between elastic-apm-node and @elastic/ecs-pino-format. They both attempt to use the other.

https://github.com/elastic/ecs-logging-nodejs/issues/79 was perhaps the same issue (which was fixed in @elastic/ecs-pino-format@1.1.2).

0reactions

sibeliuscommented, Jun 15, 2021

I think the problem was having 2 versions of elastic apm node in our monorepo, tks

Top Results From Across the Web

elastic/ecs-winston-format - npm

A formatter for the winston logger compatible with Elastic Common Schema.. Latest version: 1.3.1, last published: a year ago.

SweetOps #terraform for December, 2020

The merge function takes an arbitrary number maps or objects, and returns a single map or object that contains a merged set of...

Bug listing with status RESOLVED with resolution TEST ...

Bug:233 - "Emacs segfaults when merged through the sandbox." status:RESOLVED resolution:TEST-REQUEST severity:critical · Bug:3888 - "yenta_socket module not ...

The A3 Method - Journal of Statistical Software

Abstract. The measurement and reporting of model error is of basic importance when construct- ing models. Here, a general method and an R ......

npm group repository fails to display metadata for package

When updating our NPM repository with performance improvements the mechanism to handle the package root json was not properly handling null ...