Announcing Truncated Traces for Node.js

We’re happy to announce truncated trace support for our Node.js stack just in time for the holidays 🎄

Truncated traces example

A trace is anything we measure as part of the request/response life-cycle - database queries, calls to external API’s etc.

Previsouly only traces that ends before a request finishes would be included and shown in the performance breakdown chart. With this update we will also collect and show traces that continues past the end of the transaction. We call these “Truncated Traces”.

Truncated traces are shown with an arrow at the end of the trace, so it’s easy to distinguish those from regular traces.

Why Truncated Traces?

The reason truncated traces are important, is because those traces would previously be included only in your slower transactions (when they fell within the bounds of the request). They would be completely absent from fast transactions.

A developer unfamiliar with the code-base could wrongly conclude that these traces were the reason those transactions were slow.

By showing them as truncated even in the faster transactions, it’s more obvious that the response isn’t dependent on the result of those traces and hence they are not the culprit of the slow transactions.

Upgrade now

To get truncated traces in your app, make sure you are running version 4.4.0 or higher of the Opbeat Node.js agent. If you still haven’t upgraded to version 4.x, simply follow our upgrade guide.

About the author
Thomas Watson is our Node.js lead, speaker and commited open source contributor.
You can follow him on Twitter or GitHub.