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/splunk-metrics.md
+11-6Lines changed: 11 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,14 +44,19 @@ To send your runtime information to Splunk Cloud Platform, you need to set it up
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
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. An additional metrics index is also required as explained in below warning panel. |`false`|
47
+
|`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`|
48
48
|`APM_ENABLE_ACCESS_LOGS`| Sends access logs to Splunk when it's set to `true`. Disabled by default. |`false`|
49
49
50
-
{{% alert color="warning" %}}
51
-
Splunk Enterprise supports two types of indexes:
52
-
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.
53
-
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).
54
-
{{% /alert %}}
50
+
<divid="splunk-metrics-info">
51
+
{{% alert color="info" %}}
52
+
**Splunk supports two types of indexes:**
53
+
54
+
***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.
55
+
56
+
***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).
57
+
58
+
{{% /alert %}}
59
+
</div>
55
60
56
61
57
62
5. Return to the **Environments** page for your app and **Deploy** or **Transport** your app into the selected environment.
0 commit comments