Anyone's got npm:elastic-apm-node working?

[svenemtell]

I'm trying to use npm:elastic-apm-node but haven't succeeded.
I'm new to both Deno and Elastic, so I might be missing something vital...
This is what I've tried:

// test.ts
import apm from "npm:elastic-apm-node"

apm.start({
  serviceName: "test",
});

% deno run -A test.ts
{"log.level":"info","@timestamp":"2025-04-05T13:36:03.317Z","log.logger":"elastic-apm-node","ecs.version":"8.10.0","agentVersion":"4.11.2","env":{"pid":50117,"proctitle":"deno","os":"darwin 24.4.0","arch":"arm64","host":"Svens-MacBook-Pro.local","timezone":"UTC+0200","runtime":"Node.js v20.11.1"},"config":{"logLevel":{"source":"default","value":"info","commonName":"log_level"},"serverUrl":{"source":"default","value":"http://127.0.0.1:8200/","commonName":"server_url"},"serviceName":{"source":"start","value":"test","commonName":"service_name"},"serviceVersion":{"source":"default","commonName":"service_version"}},"activationMethod":"require","message":"Elastic APM Node.js Agent v4.11.2"}
error: Uncaught (in promise) TypeError: this.loopMonitor.reset is not a function
    at RuntimeCollector.collect (file:///Users/sven/Library/Caches/deno/npm/registry.npmjs.org/elastic-apm-node/4.11.2/lib/metrics/runtime.js:55:22)
    at new RuntimeCollector (file:///Users/sven/Library/Caches/deno/npm/registry.npmjs.org/elastic-apm-node/4.11.2/lib/metrics/runtime.js:41:10)
    at createRuntimeMetrics (file:///Users/sven/Library/Caches/deno/npm/registry.npmjs.org/elastic-apm-node/4.11.2/lib/metrics/runtime.js:71:21)
    at new MetricsRegistry (file:///Users/sven/Library/Caches/deno/npm/registry.npmjs.org/elastic-apm-node/4.11.2/lib/metrics/registry.js:43:7)
    at Metrics.start (file:///Users/sven/Library/Caches/deno/npm/registry.npmjs.org/elastic-apm-node/4.11.2/lib/metrics/index.js:38:28)
    at Agent.start (file:///Users/sven/Library/Caches/deno/npm/registry.npmjs.org/elastic-apm-node/4.11.2/lib/agent.js:376:19)
    at file:///Volumes/source/deno/test.ts:4:5

Any thoughts?

[marvinhagemeister]

Issues are best opened as issues rather than a discussion. Issues can't be solved with arguments or opinions, they are hinting at a bug in the software instead. A good indicator of dealing with an issue is when you're getting an unexpected error. This seems to be the case here.

Opened an issue for it here: #28767

[svenemtell]

Thanks @marvinhagemeister!