apm-agent-nodejs
apm-agent-nodejs copied to clipboard
elastic
Elastic APM Node.js Agent
**Describe the bug** I am using the custom transaction api to start a transaction when a 'request' comes in on socket.io. I am able to see the transaction in the...
**Is your feature request related to a problem? Please describe.** When using _apollo-link-batch-http_ more than 1 query is sent to the server in a single request. This causes a single...
**Describe the bug** The agent does capture stack trace but it wrongly claims that the line is 299 when it's 364 actually. I first though it was a source map...
**Describe the bug** The MongoDB span is not always showing the correct command i.e. `find` instead of `findOne` **Expected behavior** To show the same MongoDB command as is being used....
Trace Ids not added on uncaught exceptions? When using ECSFormat with winston I don't have TraceIds (transaction.id e etc...) information in uncaught Exceptions. https://github.com/elastic/ecs-logging-nodejs/issues/124 ``` import { createLogger, format, transports...
Starting with mongoose 5.7.0, it uses "mongodb" (rather than "mongodb-core") as a backend. ### Checklist - [ ] Figure out why no ".find" spans with mongoose >=5.7.0 (see comment below)....
`span.context.http.status_code` was deprecated in favour of `span.context.http.response.status_code` in APM Server 7.7: https://github.com/elastic/apm-server/blob/master/changelogs/7.7.asciidoc#intake-api-changes Now that we have APM Server version sniffing (as of #2546), we should be able to know when...
The Lambda `context.fail(...)` method's `err` argument is optional: https://github.com/aws/aws-lambda-nodejs-runtime-interface-client/blob/c31c41ffe5f2f03ae9e8589b96f3b005e2bb8a4a/src/Runtime/CallbackContext.ts#L108-L114 In our current instrumentation `endAndFlushTransaction` will misinterpret that as a success, and set `trans.result` and `trans.outcome` to success values.
One challenge with understanding performance issues in Elastic APM is that outbound HTTP requests are shown as a simple bar representing start and end time, but that omits many details....
# The Problem ```js const apm = require('elastic-apm-node').start() async function somethingToAwait () { return 42 } async function firstThing () { // await Promise.resolve() const span = apm.startSpan('firstThing') await somethingToAwait()...