New Relic

Monitor and observe your SDK with New Relic.

New Relic supports different languages, frameworks, and platforms to retrieve metrics and traces.

Java SDK


Include the New Relic middleware in the Java SDK

The Java SDK integrates with New Relic through the commercetools-monitoring-newrelic module.

After adding commercetools-monitoring-newrelic as a dependency in your application, add the New Relic middleware to your SDK using the .withTelemetryMiddleware() method.

ApiHttpClient apiHttpClient = ApiRootBuilder
.withTelemetryMiddleware(new NewRelicTelemetryMiddleware())

NewRelicTelemetryMiddleware reads NewRelicContext from the request, restores the transaction context, and logs request-response details to New Relic as external calls.

To create a trace per web request, such as in a Spring boot application, create a client with the New Relic transaction. You can achieve this by using the SDK's ContextClient.

ContextApiHttpClient contextClient = ContextApiHttpClient.of(
false // don't close the ApiHttpClient
ProjectApiRoot apiRoot = ProjectApiRoot.fromClient(projectKey, contextClient);

The ContextClient adds the NewRelicContext object to every API request to ensure that even asynchronous calls in different threads are instrumented.

To adhere to best practices, the API Client should be reused across the application lifetime. You should also ensure the ContextClient is configured to leave the inner client open, even if the ContextClient itself is closed.

For an example of integrating New Relic with the Java SDK, refer to the Spring Boot New Relic example application.

TypeScript SDK


The TypeScript SDK uses the @commercetools/ts-sdk-apm package and the withTelemetryMiddleware() middleware builder method to integrate with New Relic and OpenTelemetry. This setup allows for the collection and uploading of metrics and trace data to New Relic, enhancing monitoring capabilities.

See the NewRelic Express example application for a demonstration of using New Relic with the TypeScript SDK.

Include the monitoring package in the TypeScript SDK

The following code example demonstrates how to set up your SDK client for using New Relic monitoring.

// Import the @commercetools/ts-sdk-apm package
import { createTelemetryMiddleware } from '@commercetools/ts-sdk-apm'
import { ClientBuilder } from '@commercetools/sdk-client-v2'
// Configure the telemetry options
const telemetryOptions = {
apm: () => require('newrelic'),
userAgent: 'typescript-sdk-middleware-newrelic',
// Create the client with the withTelemetryMiddleware() middleware
const client = new ClientBuilder()
.withTelemetryMiddleware(telemetryOptions) // telemetry middleware

Add the New Relic agent configuration

Once the New Relic agent is installed, create a file named newrelic.js in your project root and copy the following code into it. You should modify app_name and license_key to match your New Relic profile.

('use strict');
* New Relic agent configuration.
* See lib/config/default.js in the agent distribution for a more complete
* description of configuration variables and their potential values.
exports.config = {
* Array of application names.
app_name: [process.env.NEW_RELIC_APP_NAME],
* Your New Relic license key.
license_key: process.env.NEW_RELIC_LICENSE_KEY,
logging: {
* Level at which to log. 'trace' is most useful to New Relic when diagnosing
* issues with the agent, 'info', and higher will impose the least overhead on
* production applications.
level: 'info',
* When true, all request headers except for those listed in attributes.exclude
* will be captured for all traces, unless otherwise specified in a destination's
* attributes include/exclude lists.
allow_all_headers: true,
attributes: {
* Prefix of attributes to exclude from all destinations. Allows * as wildcard
* at end.
* NOTE: If excluding headers, they must be in camelCase form to be filtered.
exclude: [

An example newrelic.js file is also available in the NewRelic Express example application. You can view the default New Relic agent configurations for all the possible and implementable configurations here.

You should require the configuration file during application launch either by adding it at the first line of the application entry module/file or as a command-line argument. Both approaches produce the same result.

Require the New Agent configuration filetypescript
// app.js
require('./path/to/newrelic.js') // require the nodejs New relic agent configuration here
import express from 'express'
const app = express()
app.listen('8000', function() {
console.log(`server listening on port ${8000}`)
Command for requiring the New Agent configuration filejson
"script": {
"start": "node -r ./path/to/newrelic.js app.js"

An example of the command-line configuration can be found in the NewRelic Express example application.



Include the monitoring package in the PHP SDK

The New Relic PHP Agent supports the Guzzle HTTP client, so each API call can be monitored by New Relic without extra configuration in the SDK Client.

The Symfony demo app demonstrates how to include New Relic in the PHP SDK using a Docker environment.


Include the monitoring package in the .NET SDK

The New Relic agent supports the monitoring of async methods. The API calls can be traced by New Relic without extra configuration, using auto instrumentation.

The NewRelicExample App demonstrates how to profile applications using New Relic.

Using the New Relic dashboard

You can now send requests in your application to commercetools Composable Commerce through your SDK and monitor the reported data dashboard, telemetry, and performance statistics in New Relic.

For more information on using the New Relic dashboard, consult Understand your system with the New Relic entity explorer, Lookout, and Navigator and other New Relic documentation.