Skip to content
Investigate

Metrics & performance

Use telemetry to find slow requests and inspect changes over time.

Choose the right view

ViewWhen to use it
Nodes and telemetryCheck which runtime is reporting and whether its recent activity is healthy.
MetricsInspect a focused time series or request-performance change.
AnalyticsCompare broader workspace trends over the available time ranges.
ProfilesInspect runtime activity associated with sampled transactions, when enabled.

Enable backend performance capture

Errors and transactions have separate sample rates. sampleRate controls errors; tracesSampleRate controls performance transactions. Backend tracing is off by default. Set a transaction sample above zero in Node.js or Go, then verify transactions arrive before enabling profiling.

Investigate a change

Sampling and plan retention affect how much evidence is available. Check the event's release and full commit before associating a performance change with a particular build.

  1. Start with an affected node, environment, and time range.

  2. Look for a latency or volume change around a deployment.

  3. Open the corresponding transaction or timeline and inspect the operations that took time.

  4. Use an available profile for a closer view, then compare the result with your application logs and code.