---
title: Mendix Cloud Integration
source: https://docs.newrelic.com/docs/infrastructure/other-infrastructure-integrations/mendix-cloud-integration
---

The Mendix Cloud integration collects and sends inventory and metrics from your Mendix Cloud Environment to New Relic so you can monitor its health and performance.

Read on to install the integration, and to see what data we collect.

## Setup [#comp-req]

To make use of New Relic, you need a New Relic API key. To find an existing key or request a new one for your app, follow these steps:

1.  Log in to your New Relic account.
2.  Open the user menu options by clicking your name in the lower-left corner. Then click API Keys.
3.  Copy an existing API key or create a new one. For this purpose, New Relic recommends the `License` type.

> #### ⚠️ IMPORTANT
>
> New Relic logging and application metrics are supported in Mendix 9.7 and above.

## Connecting Your environment to New Relic [#connect]

To send your runtime information to New Relic, you must provide the New Relic API key to your environment.

1.  Go to the **Environment** page of your app in the **Developer Portal**.
2.  Click **Details** on the environment you wish to monitor with New Relic.
3.  Switch to the **Details** tab.
4.  Add the following custom environment variables:
    Variable

    Description



    NEW_RELIC_LICENSE_KEY

    New Relic License key.


    NEW_RELIC_LOGS_URI

    URI for the New Relic’s Logs API. For more information, consult New Relic Regions. For valid values, see Send your logging data with our log API
    Example: https://log-api.eu.newrelic.com/log/v1 (EU), https://log-api.jp.nr-data.net/log/v1 (Japan)


    NEW_RELIC_METRICS_URI

    URI for the New Relic’s Metrics API. For more information, consult New Relic Regions. For valid values, see Report metrics via the metric API.
    Example: https://metric-api.eu.newrelic.com/metric/v1 (EU), https://metric-api.jp.nr-data.net/metric/v1 (Japan).


    NEW_RELIC_APP_NAME
    (optional)

    Mendix application name shown on New Relic’s APM & Services page. Default: Domain host name.


    LOGS_REDACTION
    (optional)

    Email addresses are automatically redacted before log entries are sent to New Relic. To disable this redaction, set LOGS_REDACTION to false. Default: true.



5.  Return to the **Environments** page for your app and **Deploy** or **Transport** your app into the selected environment.

> #### ⚠️ IMPORTANT
>
> To start sending data to New Relic, you must redeploy your app and then restart it. Just restarting the app is not sufficient because additional dependencies need to be included.

## Tagging metrics for New Relic [#tagging]

To help you with analyzing your app metrics as described in the [App Metrics](https://docs.mendix.com/developerportal/operate/monitoring-with-apm/#app-metrics) section of Monitoring Your Mendix Apps with an APM Tool, Mendix adds tags to metrics from microflows and activities when using New Relic.

In addition to the runtime application logs, the following JSON-formatted metadata is automatically sent to New Relic:

-   `environment_id`: Unique identifier of the environment
-   `instance_index`: Number of the application instance
-   `hostname`: Name of the application host
-   `application_name`: Default application name, retrieved from the domain name
-   `model_version`: Model version of the Mendix runtime
-   `runtime_version`: Version of the Mendix runtime

You can filter the data by these fields.

## Custom tags [#custom]

If you use New Relic to monitor more than one app and environment, you will not be able to tell which app or environment these metrics apply to. To identify the metrics for your app and environment in New Relic, you need to add tags for the app name and environment.

Mendix recommends using the following tags:

-   `app:{app_name}` (for example, `app:customermanagement`): This enables you to identify all metrics sent from your app
-   `env:{environment_name}` (for example, \`env:accp\`\`): This enables you to identify metrics sent from a particular environment so you can separate out production metrics from test metrics