From d6f5b3f03f7a3e4dd83cdc593043d7f5f6d184b2 Mon Sep 17 00:00:00 2001 From: ekremsekerci Date: Wed, 25 Mar 2026 09:41:14 +0100 Subject: [PATCH 1/2] Update on Splunk metrics integration --- .../monitoring-with-apm/splunk-metrics.md | 13 ++++++++++--- .../releasenotes/deployment/mendix-cloud/2026.md | 6 ++++++ 2 files changed, 16 insertions(+), 3 deletions(-) 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 index d9fe0a2df04..187285128b7 100644 --- 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 @@ -43,9 +43,16 @@ To send your runtime information to Splunk Cloud Platform, you need to set it up | `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` | - | `APM_ENABLE_ACCESS_LOGS` | Sends access logs to Splunk when it's set to `true`. Disabled by default. | `false` | + | `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. An additional metrics index is also required as explained in below warning panel. | `false` | + | `APM_ENABLE_ACCESS_LOGS` | Sends access logs to Splunk when it's set to `true`. Disabled by default. | `false` | + + {{% alert color="warning" %}} + Splunk Enterprise supports two types of indexes: + Events indexes. Events indexes impose minimal structure and can accommodate any type of data, including metrics data. Events indexes are the default index type. To get logs, you must use an event index as a default index within your HEC token. + Metrics indexes. Metrics indexes use a highly structured format to handle the higher volume and lower latency demands associated with metrics data. To get metrics, you must create an index called `mxmetrics` and add it into the allowed indexes list within your HEC token. More details on metrics indexes can be seen at [Splunk docs](https://help.splunk.com/en/splunk-cloud-platform/get-data-in/metrics/9.2.2406/introduction-to-metrics/overview-of-metrics). + {{% /alert %}} + 5. Return to the **Environments** page for your app and **Deploy** or **Transport** your app into the selected environment. diff --git a/content/en/docs/releasenotes/deployment/mendix-cloud/2026.md b/content/en/docs/releasenotes/deployment/mendix-cloud/2026.md index 60f0723764e..4df27c8c0de 100644 --- a/content/en/docs/releasenotes/deployment/mendix-cloud/2026.md +++ b/content/en/docs/releasenotes/deployment/mendix-cloud/2026.md @@ -8,6 +8,12 @@ weight: 1 ## March 2026 +### March 24, 2026 + +#### Bug Fixes + +* We fixed an issue where Splunk metrics were not being ingested properly. + ### March 15, 2026 #### Improvements From b6b610f9ef8ed72ac52ac05892fdd52461ece646 Mon Sep 17 00:00:00 2001 From: Olufunke Moronfolu Date: Wed, 25 Mar 2026 15:27:02 +0100 Subject: [PATCH 2/2] TW review: splunk metrics update --- .../monitoring-with-apm/splunk-metrics.md | 17 +++++++++++------ .../en/docs/releasenotes/deployment/_index.md | 2 +- .../deployment/mendix-cloud/2026.md | 2 +- .../partials/landingpage/latest-releases.html | 2 +- 4 files changed, 14 insertions(+), 9 deletions(-) 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 index 187285128b7..feb7e11457c 100644 --- 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 @@ -44,14 +44,19 @@ 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. An additional metrics index is also required as explained in below warning panel. | `false` | + | `SPLUNK_ENABLE_METRICS` | Sends application metrics to Splunk when it's set to `true`. Disabled by default. A metrics index is also required, refer to the [metrics index information](#splunk-metrics-info) below. | `false` | | `APM_ENABLE_ACCESS_LOGS` | Sends access logs to Splunk when it's set to `true`. Disabled by default. | `false` | - {{% alert color="warning" %}} - Splunk Enterprise supports two types of indexes: - Events indexes. Events indexes impose minimal structure and can accommodate any type of data, including metrics data. Events indexes are the default index type. To get logs, you must use an event index as a default index within your HEC token. - Metrics indexes. Metrics indexes use a highly structured format to handle the higher volume and lower latency demands associated with metrics data. To get metrics, you must create an index called `mxmetrics` and add it into the allowed indexes list within your HEC token. More details on metrics indexes can be seen at [Splunk docs](https://help.splunk.com/en/splunk-cloud-platform/get-data-in/metrics/9.2.2406/introduction-to-metrics/overview-of-metrics). - {{% /alert %}} +
+ {{% alert color="info" %}} +**Splunk supports two types of indexes:** + +* **Event indexes**: These are the default index type and impose minimal structure, allowing them to store any kind of data, including metrics. To ingest logs, you must configure an event index as the default index in your HEC token. + +* **Metrics indexes**: These use a highly structured format designed for high-volume, low-latency metrics data. To ingest metrics, create an index named `mxmetrics` and add it to the list of allowed indexes in your HEC token. For more information, refer to the [Splunk documentation](https://help.splunk.com/en/splunk-cloud-platform/get-data-in/metrics/9.2.2406/introduction-to-metrics/overview-of-metrics). + +{{% /alert %}} +
5. Return to the **Environments** page for your app and **Deploy** or **Transport** your app into the selected environment. diff --git a/content/en/docs/releasenotes/deployment/_index.md b/content/en/docs/releasenotes/deployment/_index.md index 2b6eb657c69..eb7918cef23 100644 --- a/content/en/docs/releasenotes/deployment/_index.md +++ b/content/en/docs/releasenotes/deployment/_index.md @@ -15,7 +15,7 @@ Follow the links in the table below to see the release notes you want: | Type of Deployment | Last Updated | | --- | --- | -| [Mendix Cloud](/releasenotes/developer-portal/mendix-cloud/) | March 15, 2026 | +| [Mendix Cloud](/releasenotes/developer-portal/mendix-cloud/) | March 24, 2026 | | [Mendix on Kubernetes](/releasenotes/developer-portal/mendix-for-private-cloud/) | February 5, 2026 | | [Mendix on Azure](/releasenotes/developer-portal/mendix-on-azure/) | January 29, 2026 | | [SAP Business Technology Platform (SAP BTP)](/releasenotes/developer-portal/sap-cloud-platform/) | September 28, 2025 | diff --git a/content/en/docs/releasenotes/deployment/mendix-cloud/2026.md b/content/en/docs/releasenotes/deployment/mendix-cloud/2026.md index 4df27c8c0de..9013ce946ba 100644 --- a/content/en/docs/releasenotes/deployment/mendix-cloud/2026.md +++ b/content/en/docs/releasenotes/deployment/mendix-cloud/2026.md @@ -12,7 +12,7 @@ weight: 1 #### Bug Fixes -* We fixed an issue where Splunk metrics were not being ingested properly. +* We fixed an issue where [Splunk metrics](/developerportal/operate/splunk-metrics/) were not being ingested properly. ### March 15, 2026 diff --git a/layouts/partials/landingpage/latest-releases.html b/layouts/partials/landingpage/latest-releases.html index cb540129a07..88eda18d2ba 100644 --- a/layouts/partials/landingpage/latest-releases.html +++ b/layouts/partials/landingpage/latest-releases.html @@ -14,7 +14,7 @@

Latest Releases

  • Deployment -

    March 15, 2026

    +

    March 24, 2026

  • Catalog Release 2.150.0