Skip to content

Add access logs support to Splunk, New Relic and Dynatrace integrations. #10780

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ekremsekerci wants to merge 1 commit into
base: development
Choose a base branch
from
Open

Add access logs support to Splunk, New Relic and Dynatrace integrations. #10780

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 10 additions & 9 deletions ...en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/dynatrace-metrics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,15 +36,16 @@ To start sending your Mendix app's metrics to Dynatrace, you need to set some en
3. Switch to the [**Runtime** tab](/developerportal/deploy/environments-details/#runtime-tab).
4. Add the following **Custom Environment Variables**.

| Variable | Required? | Description | Details |
| --- |-----------| --- | --- |
| `DT_SAAS_URL` | Yes | The URL of Dynatrace environment | The format when using the Dynatrace SaaS environment is similar to `https://<your-environment-id>.live.dynatrace.com`. If you are using a Dynatrace managed environment, just provide the full URL of the Dynatrace domain, like `https://<your-dynatrace-domain>`. |
| `DT_TENANT` | Yes | The Dynatrace Environment ID | For more information, see the [Environment ID](https://www.dynatrace.com/support/help/get-started/monitoring-environment/environment-id) Dynatrace documentation. |
| `DT_PAAS_TOKEN` | Yes | The access token for integrating your Mendix app with Dynatrace | Create this on the Dynatrace environment. For more information, see [Generate an Access Token](https://www.dynatrace.com/support/help/get-started/access-tokens#create-api-token). The token must include the `PaaS integration - Installer download` and `Ingest metrics` scopes. For logging integration, `Ingest logs` scope is also required. |
| `DT_ENABLE_LOGS` | No | Set this to `true` to enable logging | Only supported for Dynatrace SaaS. `Ingest logs` scope is required to be included in the access token. |
| `DT_IS_MANAGED` | No | Set this to `true` if you are using Dynatrace Managed. The default is assumed to be Dynatrace SaaS and set to `false`. | This variable is only needed for custom application metrics ingestion. |
| `DT_CLUSTER_ID` | No | You can use this to tag your cluster, process group, or deployment group. | |
| `DT_CUSTOM_PROP` | No | This can be used to provide metadata for your process group. | For more information, see [Define Your Own Process Group Metadata](https://www.dynatrace.com/support/help/platform-modules/infrastructure-monitoring/process-groups/configuration/define-your-own-process-group-metadata). |
| Variable | Required? | Description | Details |
|-------------------------|-----------|------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `DT_SAAS_URL` | Yes | The URL of Dynatrace environment | The format when using the Dynatrace SaaS environment is similar to `https://<your-environment-id>.live.dynatrace.com`. If you are using a Dynatrace managed environment, just provide the full URL of the Dynatrace domain, like `https://<your-dynatrace-domain>`. |
| `DT_TENANT` | Yes | The Dynatrace Environment ID | For more information, see the [Environment ID](https://www.dynatrace.com/support/help/get-started/monitoring-environment/environment-id) Dynatrace documentation. |
| `DT_PAAS_TOKEN` | Yes | The access token for integrating your Mendix app with Dynatrace | Create this on the Dynatrace environment. For more information, see [Generate an Access Token](https://www.dynatrace.com/support/help/get-started/access-tokens#create-api-token). The token must include the `PaaS integration - Installer download` and `Ingest metrics` scopes. For logging integration, `Ingest logs` scope is also required. |
| `DT_ENABLE_LOGS` | No | Set this to `true` to enable logging | Only supported for Dynatrace SaaS. `Ingest logs` scope is required to be included in the access token. |
| `DT_IS_MANAGED` | No | Set this to `true` if you are using Dynatrace Managed. The default is assumed to be Dynatrace SaaS and set to `false`. | This variable is only needed for custom application metrics ingestion. |
| `DT_CLUSTER_ID` | No | You can use this to tag your cluster, process group, or deployment group. | |
| `DT_CUSTOM_PROP` | No | This can be used to provide metadata for your process group. | For more information, see [Define Your Own Process Group Metadata](https://www.dynatrace.com/support/help/platform-modules/infrastructure-monitoring/process-groups/configuration/define-your-own-process-group-metadata). |
| | `APM_ENABLE_ACCESS_LOGS` | No | Sends access logs to Dynatrace when it's set to `true`.Disabled by default. | |

5. Return to the **General** tab and restart your environment.

Expand Down
22 changes: 12 additions & 10 deletions .../en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/newrelic-metrics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,15 +43,16 @@ To send your runtime information to New Relic, you must provide the New Relic AP
1. Switch to the **Runtime** tab.
1. Add the following **Custom Environment Variables**:

| Variable | Description | Default |
| --- | --- | --- |
| `NEW_RELIC_LICENSE_KEY` | License key or API key from New Relic. Obtained in the [New Relic API Key](#newrelic-api-key) section. | |
| `NEW_RELIC_LOGS_URI` | URI for the New Relic's Logs API. For more information, consult [New Relic Regions](#uri-regions). Example: `https://log-api.eu.newrelic.com/log/v1`. | |
| `NEW_RELIC_METRICS_URI` | URI for the New Relic's Metrics API. For more information, consult [New Relic Regions](#uri-regions). Example: `https://metric-api.eu.newrelic.com/metric/v1`. | |
| `NEW_RELIC_APP_NAME` (optional) | Mendix Application name shown on New Relic's APM & Services. 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`. ||
| `FLUENTBIT_LOGS_BUFFER_SIZE` | Sets the maximum amount of data (in KB) that the TCP input plugin reads from the socket per read operation. Increasing this value can help to get rid of data flow delay, and errors related to queue buffer overflow. | `128` |
| `FLUENTBIT_LOGS_MEM_BUF_LIMIT` | Defines the maximum total memory an input plugin can use for buffering log records before they are processed or flushed to storage/output. Limits memory which can be consumed by the Fluentbit agent | `50MB` |
| Variable | Description | Default |
| --- |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| --- |
| `NEW_RELIC_LICENSE_KEY` | License key or API key from New Relic. Obtained in the [New Relic API Key](#newrelic-api-key) section. | |
| `NEW_RELIC_LOGS_URI` | URI for the New Relic's Logs API. For more information, consult [New Relic Regions](#uri-regions). Example: `https://log-api.eu.newrelic.com/log/v1`. | |
| `NEW_RELIC_METRICS_URI` | URI for the New Relic's Metrics API. For more information, consult [New Relic Regions](#uri-regions). Example: `https://metric-api.eu.newrelic.com/metric/v1`. | |
| `NEW_RELIC_APP_NAME` (optional) | Mendix Application name shown on New Relic's APM & Services. 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`. ||
| `FLUENTBIT_LOGS_BUFFER_SIZE` | Sets the maximum amount of data (in KB) that the TCP input plugin reads from the socket per read operation. Increasing this value can help to get rid of data flow delay, and errors related to queue buffer overflow. | `128` |
| `FLUENTBIT_LOGS_MEM_BUF_LIMIT` | Defines the maximum total memory an input plugin can use for buffering log records before they are processed or flushed to storage/output. Limits memory which can be consumed by the Fluentbit agent | `50MB` |
| `APM_ENABLE_ACCESS_LOGS` | Sends access logs to New Relic when it's set to `true`.Disabled by default. | `false` |

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

Expand All @@ -63,7 +64,7 @@ To help you with analyzing your app metrics as described in the [App Metrics](/d

### Metadata

In addition to the runtime application logs, the following JSON-formatted metadata is automatically sent to New Relic:
In addition to the runtime application/access 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 (available only in Cloud Foundry deployments)
Expand All @@ -72,6 +73,7 @@ In addition to the runtime application logs, the following JSON-formatted metada
* `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
* `log_type` – type of the log, which can be `mx.applicationlogs` or `mx.accesslogs`

You can filter the data by these fields.

Expand Down
6 changes: 4 additions & 2 deletions ...nt/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/splunk-metrics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ description: "How to configure Mendix Cloud to send your runtime application log

## Introduction

[Splunk Cloud Platform](https://www.splunk.com/en_us/products/splunk-cloud-platform.html) is a monitoring and analysis tool for cloud applications. This document explains how to configure your Mendix Cloud application to send runtime application logs and metrics to Splunk Cloud Platform to provide additional search, analysis, and visualization of your runtime application logs and metrics.
[Splunk Cloud Platform](https://www.splunk.com/en_us/products/splunk-cloud-platform.html) is a monitoring and analysis tool for cloud applications. This document explains how to configure your Mendix Cloud application to send runtime application logs, access logs and metrics to Splunk Cloud Platform to provide additional search, analysis, and visualization of your runtime application logs and metrics.

Mendix provides integration with Splunk Cloud Platform; it does not currently integrate with other Splunk monitoring products.

Expand Down Expand Up @@ -44,7 +44,8 @@ To send your runtime information to Splunk Cloud Platform, you need to set it up
| `LOGS_REDACTION` | Email addresses are automatically redacted before log entries are sent to Splunk Cloud Platform. To disable this redaction, set `LOGS_REDACTION` to `false`. The environment variable `SPLUNK_LOGS_REDACTION` is now deprecated in Cloud Foundry and is not supported for apps with Kubernetes deployment. Its use is not recommended. | `true` |
| `FLUENTBIT_LOGS_BUFFER_SIZE` | Sets the maximum amount of data (in KB) that the TCP input plugin reads from the socket per read operation. Increasing this value can help to get rid of data flow delay, and errors related to queue buffer overflow. | `128` |
| `FLUENTBIT_LOGS_MEM_BUF_LIMIT` | Defines the maximum total memory an input plugin can use for buffering log records before they are processed or flushed to storage/output. Limits memory which can be consumed by the Fluentbit agent | `50MB` |
| `SPLUNK_ENABLE_METRICS` | Sends application metrics to Splunk when it's set to `true`. Disabled by default. | `false` |
| `SPLUNK_ENABLE_METRICS` | Sends application metrics to Splunk when it's set to `true`. Disabled by default. | `false` |
| `APM_ENABLE_ACCESS_LOGS` | Sends access logs to Splunk when it's set to `true`.Disabled by default. | `false` |

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

Expand All @@ -61,6 +62,7 @@ In addition to the runtime application logs, the following JSON-formatted metada
* `application_name` – default application name, retrieved from domain name
* `model_version` – model version of the Mendix runtime
* `runtime_version` – version of the Mendix runtime
* `log_type` – type of the log, which can be `mx.applicationlogs` or `mx.accesslogs`

You can filter the data by these fields.

Expand Down
6 changes: 6 additions & 0 deletions content/en/docs/releasenotes/deployment/mendix-cloud/2026.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,12 @@ weight: 1

## February 2026

### February 18, 2026

#### New Features

* We added support for access logs to Splunk, New Relic and Dynatrace integrations.

### February 15, 2026

#### Bug Fixes
Expand Down