The metric summary is sent to the service along with the span/trace and is displayed as an emitted metric.
The metric itself did not leave a trace on Relay, or storage.
The metric and the metric summary on the span are sent with different requests, more specifically the metric itself may be sent in a delayed manner. If e.g. the process is shutdown using Ctrl-C, this could cause the metric to not be sent at all if there is no graceful shutdown.
The hypothesis is therefore that the NodeJS SDK is not finishing up gracefully and sending metrics when it shuts down, causing some of these missing messages.
Sentry Feedback: JAVASCRIPT-2TCF
While testing Metrics on a node.js application, I noticed that the metrics were registered - https://prithvi-0c.sentry.io/performance/trace/bb7d30ac44d736458771daf104a6bf8e/?node=txn-ae8be857d56847c4bc5ea4ee592de3df&statsPeriod=1h×tamp=1717076023
But it did not show up on the UI - https://prithvi-0c.sentry.io/metrics/?interval=1d&project=6307748&statsPeriod=30d