Merge pull request #10621 from ekremsekerci/metrics_to_splunk

OlufunkeMoronfolu · web-flow · commit 4b170182e9ec · 2026-01-20T11:41:11.000+01:00
Update Splunk integration documentation.
diff --git a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/splunk-metrics.md b/content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/splunk-metrics.md
@@ -9,9 +9,9 @@ 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 app to send the runtime application logs to Splunk Cloud Platform to provide additional search, analysis, and visualization of your runtime application logs.
+[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.
 
-Mendix provides integration with Splunk Cloud Platform; it does not currently integrate with other Splunk monitoring products. Mendix sends only the runtime application logs to Splunk.
+Mendix provides integration with Splunk Cloud Platform; it does not currently integrate with other Splunk monitoring products.
 
 {{% alert color="info" %}}
 For support on other cloud deployment options, such as Mendix on Kubernetes, refer to their dedicated documentation. For deployment on Kubernetes, for example, see [Monitoring Environments in Mendix on Kubernetes](/developerportal/deploy/private-cloud-monitor/).
@@ -32,24 +32,25 @@ To use the Splunk Cloud Platform and send data to Splunk Cloud Platform from you
 To send your runtime information to Splunk Cloud Platform, you need to set it up using environment variables in the Mendix Portal.
 
 1. From [Apps](https://sprintr.home.mendix.com), go to the **Environments** page of your app.
-1. Click **Details** on the environment you wish to monitor with Splunk Cloud Platform.
-1. Switch to the [**Runtime** tab](/developerportal/deploy/environments-details/#runtime-tab).
-1. Add the following **Custom Environment Variables**.
-
-    | Variable | Description | Default |
-    | --- | --- | --- |
-    | `SPLUNK_HOST` | The hostname or the IP address of the Splunk Cloud Platform Controller without the scheme (protocol). An example is `test.splunkcloud.com`. | |
-    | `SPLUNK_PORT` | The HTTP (or HTTPS) port of the Splunk Cloud Platform Controller. | `8088` |
-    | `SPLUNK_TOKEN` | An access token to the Splunk Cloud Platform. To create a new token on the Splunk Cloud dashboard, open the Splunk Cloud dashboard in a browser, go to **Settings** > **Data Input** > **HTTP Event Collector**, and click **New Token** (on the upper-right corner of the page). | |
-    | `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` |
-
-1. Return to the **Environments** page for your app and **Deploy** or **Transport** your app into the selected environment.
+2. Click **Details** on the environment you wish to monitor with Splunk Cloud Platform.
+3. Switch to the [**Runtime** tab](/developerportal/deploy/environments-details/#runtime-tab).
+4. Add the following **Custom Environment Variables**.
+
+    | Variable                       | Description                                                                                                                                                                                                                                                                                                                            | Default |
+    |--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+    | `SPLUNK_HOST`                  | The hostname or the IP address of the Splunk Cloud Platform Controller without the scheme (protocol). An example is `test.splunkcloud.com`.                                                                                                                                                                                            |         |
+    | `SPLUNK_PORT`                  | The HTTP (or HTTPS) port of the Splunk Cloud Platform Controller.                                                                                                                                                                                                                                                                      | `8088`  |
+    | `SPLUNK_TOKEN`                 | An access token to the Splunk Cloud Platform. To create a new token on the Splunk Cloud dashboard, open the Splunk Cloud dashboard in a browser, go to **Settings** > **Data Input** > **HTTP Event Collector**, and click **New Token** (on the upper-right corner of the page).                                                      |         |
+    | `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` |
+
+5. Return to the **Environments** page for your app and **Deploy** or **Transport** your app into the selected environment.
 
     {{% alert color="warning" %}}The first time you set up the Splunk Cloud Platform integration, you must redeploy your app and then restart it. Just restarting the app is not sufficient because additional dependencies need to be included.{{% /alert %}}
 
-### Metadata
+### Metadata for Logs
 
 In addition to the runtime application logs, the following JSON-formatted metadata is automatically sent to the Splunk Cloud Platform:
 
@@ -63,7 +64,16 @@ In addition to the runtime application logs, the following JSON-formatted metada
 
 You can filter the data by these fields.
 
-### Custom tags
+### Metadata for Metrics
+
+In addition to the runtime application logs, the following JSON-formatted metadata is automatically sent to the Splunk Cloud Platform:
+
+* `environment_id` – unique identifier of the environment
+* `pod_name` – name of the application pod (available only in Kubernetes deployments)
+
+You can filter the data by these fields.
+
+### Custom Tags
 
 You can also set up custom tags in the format `key:value`. Mendix recommends adding the following custom tags:
 
diff --git a/content/en/docs/releasenotes/deployment/mendix-cloud/2026.md b/content/en/docs/releasenotes/deployment/mendix-cloud/2026.md
@@ -14,6 +14,12 @@ weight: 1
 
 * We have added support for centralized certificate management. Through the updated [Custom Domains](/developerportal/deploy/environments/#custom-domains) tab on the **Cloud Settings** page, Technical Contacts can now centrally manage custom domain certificates rather than only at the application level. They can also check whether a certificate is managed locally at the app level or centrally.
 
+### January 16, 2026
+
+#### New Features
+
+* We have added metrics support to [Splunk Cloud Platform integration](/developerportal/operate/splunk-metrics/).
+
 ### January 11, 2026
 
 #### Improvements
