Skip to content

Commit ba75933

Browse files
OlufunkeMoronfoluOlufunkeMoronfolu
committed
feat: updating splunk release
1 parent a8fb6dc commit ba75933

5 files changed

Lines changed: 17 additions & 17 deletions

File tree

‎content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/dynatrace-metrics.md‎

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -36,16 +36,16 @@ To start sending your Mendix app's metrics to Dynatrace, you need to set some en
3636
3. Switch to the [**Runtime** tab](/developerportal/deploy/environments-details/#runtime-tab).
3737
4. Add the following **Custom Environment Variables**.
3838

39-
| Variable | Required? | Description | Details |
40-
|-------------------------|-----------|------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
41-
| `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>`. |
42-
| `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. |
43-
| `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. |
44-
| `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. |
45-
| `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. |
46-
| `DT_CLUSTER_ID` | No | You can use this to tag your cluster, process group, or deployment group. | |
47-
| `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). |
48-
| | `APM_ENABLE_ACCESS_LOGS` | No | Sends access logs to Dynatrace when it's set to `true`.Disabled by default. | |
39+
| Variable | Required? | Description | Details |
40+
|--------------------------|-----------|------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
41+
| `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>`. |
42+
| `DT_TENANT` | Yes | The Dynatrace Environment ID | For more information, see the [Environment ID](https://docs.dynatrace.com/docs/discover-dynatrace/get-started/monitoring-environment#environment-id) section of _Dynatrace_. |
43+
| `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. |
44+
| `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. |
45+
| `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. |
46+
| `DT_CLUSTER_ID` | No | You can use this to tag your cluster, process group, or deployment group. | |
47+
| `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). |
48+
| `APM_ENABLE_ACCESS_LOGS` | No | Sends access logs to Dynatrace when it's set to `true`. Disabled by default. | |
4949

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

‎content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/newrelic-metrics.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -48,8 +48,8 @@ To send your runtime information to New Relic, you must provide the New Relic AP
4848
| `NEW_RELIC_LICENSE_KEY` | License key or API key from New Relic. Obtained in the [New Relic API Key](#newrelic-api-key) section. | |
4949
| `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`. | |
5050
| `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`. | |
51-
| `NEW_RELIC_APP_NAME` (optional) | Mendix Application name shown on New Relic's APM & Services. Default: Domain host name. | |
52-
| `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`. ||
51+
| `NEW_RELIC_APP_NAME` (optional) | Mendix Application name shown on New Relic's APM & Services. | Domain host name |
52+
| `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`. |`true`|
5353
| `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` |
5454
| `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` |
5555
| `APM_ENABLE_ACCESS_LOGS` | Sends access logs to New Relic when it's set to `true`.Disabled by default. | `false` |
@@ -64,7 +64,7 @@ To help you with analyzing your app metrics as described in the [App Metrics](/d
6464

6565
### Metadata
6666

67-
In addition to the runtime application/access logs, the following JSON-formatted metadata is automatically sent to New Relic:
67+
In addition to the runtime application or access logs, the following JSON-formatted metadata is automatically sent to New Relic:
6868

6969
* `environment_id` – unique identifier of the environment
7070
* `instance_index` – number of the application instance (available only in Cloud Foundry deployments)

‎content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/splunk-metrics.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,9 +43,9 @@ To send your runtime information to Splunk Cloud Platform, you need to set it up
4343
| `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). | |
4444
| `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` |
4545
| `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` |
46-
| `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` |
46+
| `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` |
4747
| `SPLUNK_ENABLE_METRICS` | Sends application metrics to Splunk when it's set to `true`. Disabled by default. | `false` |
48-
| `APM_ENABLE_ACCESS_LOGS` | Sends access logs to Splunk when it's set to `true`.Disabled by default. | `false` |
48+
| `APM_ENABLE_ACCESS_LOGS` | Sends access logs to Splunk when it's set to `true`. Disabled by default. | `false` |
4949

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

‎content/en/docs/releasenotes/deployment/_index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Follow the links in the table below to see the release notes you want:
1515

1616
| Type of Deployment | Last Updated |
1717
| --- | --- |
18-
| [Mendix Cloud](/releasenotes/developer-portal/mendix-cloud/) | February 15, 2026 |
18+
| [Mendix Cloud](/releasenotes/developer-portal/mendix-cloud/) | February 18, 2026 |
1919
| [Mendix on Kubernetes](/releasenotes/developer-portal/mendix-for-private-cloud/) | February 5, 2026 |
2020
| [Mendix on Azure](/releasenotes/developer-portal/mendix-on-azure/) | January 29, 2026 |
2121
| [SAP Business Technology Platform (SAP BTP)](/releasenotes/developer-portal/sap-cloud-platform/) | September 28, 2025 |

‎layouts/partials/landingpage/latest-releases.html‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ <h4 class="lp-panel-title">Latest Releases</h4>
1414
</li>
1515
<li class="lp-panel-list">
1616
<a href="/releasenotes/developer-portal/deployment/">Deployment</a>
17-
<p class="rn-date">February 15, 2026</p>
17+
<p class="rn-date">February 18, 2026</p>
1818
</li>
1919
<li class="lp-panel-list">
2020
<a href="/releasenotes/catalog/">Catalog Release 2.150.0</a>

0 commit comments

Comments
 (0)