You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/dynatrace-metrics.md
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,15 +36,16 @@ To start sending your Mendix app's metrics to Dynatrace, you need to set some en
36
36
3. Switch to the [**Runtime** tab](/developerportal/deploy/environments-details/#runtime-tab).
37
37
4. Add the following **Custom Environment Variables**.
38
38
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). |
|`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. ||
48
49
49
50
5. Return to the **General** tab and restart your environment.
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/newrelic-metrics.md
+12-10Lines changed: 12 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,15 +43,16 @@ To send your runtime information to New Relic, you must provide the New Relic AP
43
43
1. Switch to the **Runtime** tab.
44
44
1. Add the following **Custom Environment Variables**:
45
45
46
-
| Variable | Description | Default |
47
-
| --- | --- | --- |
48
-
|`NEW_RELIC_LICENSE_KEY`| License key or API key from New Relic. Obtained in the [New Relic API Key](#newrelic-api-key) section. ||
49
-
|`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`. ||
50
-
|`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`. ||
53
-
|`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`|
54
-
|`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`|
|`NEW_RELIC_LICENSE_KEY`| License key or API key from New Relic. Obtained in the [New Relic API Key](#newrelic-api-key) section. ||
49
+
|`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`. ||
50
+
|`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. | 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`|
53
+
|`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`|
54
+
|`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`|
55
+
|`APM_ENABLE_ACCESS_LOGS`| Sends access logs to New Relic when it's set to `true`.Disabled by default. |`false`|
55
56
56
57
1. Return to the **Environments** page for your app and **Deploy** or **Transport** your app into the selected environment.
57
58
@@ -63,7 +64,7 @@ To help you with analyzing your app metrics as described in the [App Metrics](/d
63
64
64
65
### Metadata
65
66
66
-
In addition to the runtime application 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:
67
68
68
69
*`environment_id` – unique identifier of the environment
69
70
*`instance_index` – number of the application instance (available only in Cloud Foundry deployments)
@@ -72,6 +73,7 @@ In addition to the runtime application logs, the following JSON-formatted metada
72
73
*`application_name` – default application name, retrieved from the domain name
73
74
*`model_version` – model version of the Mendix runtime
74
75
*`runtime_version` – version of the Mendix runtime
76
+
*`log_type` – type of the log, which can be `mx.applicationlogs` or `mx.accesslogs`
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/splunk-metrics.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ description: "How to configure Mendix Cloud to send your runtime application log
9
9
10
10
## Introduction
11
11
12
-
[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.
12
+
[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.
13
13
14
14
Mendix provides integration with Splunk Cloud Platform; it does not currently integrate with other Splunk monitoring products.
15
15
@@ -43,8 +43,9 @@ To send your runtime information to Splunk Cloud Platform, you need to set it up
43
43
|`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). ||
44
44
|`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`|
45
45
|`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`|
47
-
|`SPLUNK_ENABLE_METRICS`| Sends application metrics to Splunk when it's set to `true`. Disabled by default. |`false`|
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`|
47
+
|`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
49
49
50
5. Return to the **Environments** page for your app and **Deploy** or **Transport** your app into the selected environment.
50
51
@@ -61,6 +62,7 @@ In addition to the runtime application logs, the following JSON-formatted metada
61
62
*`application_name` – default application name, retrieved from domain name
62
63
*`model_version` – model version of the Mendix runtime
63
64
*`runtime_version` – version of the Mendix runtime
65
+
*`log_type` – type of the log, which can be `mx.applicationlogs` or `mx.accesslogs`
0 commit comments