From 66cdf5ce71863442e1c5a536ce7ab48fc92515e7 Mon Sep 17 00:00:00 2001 From: Rodrigo Pastrana Date: Wed, 28 Aug 2024 16:06:59 -0400 Subject: [PATCH] HPCC-32699 Encode all ALA response data - Encodes all response log data from ALA Signed-off-by: Rodrigo Pastrana --- helm/managed/logging/loki-stack/README.md | 21 +++++++++++++++++++ .../grafana-hpcc-logaccess-baremetal.xml | 18 ++++++++++++++++ 2 files changed, 39 insertions(+) create mode 100644 helm/managed/logging/loki-stack/grafana-hpcc-logaccess-baremetal.xml diff --git a/helm/managed/logging/loki-stack/README.md b/helm/managed/logging/loki-stack/README.md index e50a0437444..8d2af452a8d 100644 --- a/helm/managed/logging/loki-stack/README.md +++ b/helm/managed/logging/loki-stack/README.md @@ -200,3 +200,24 @@ Example use: logFormat: type: "json" ``` +#### Baremetal configuration + +LogAccess can be configured on baremetal systems as well. It is not a common scenario because baremetal logs continue to be persisted on the local filesystem. Enabling LogAccess on a baremetal system would allow users to fetch remotely stored HPCC logs (not likely related to the host HPCC Systems deployment). To enable, inject a logAccess block with all configuration values properly filled in. The logAccess block can be injected within the Software element in the active environment.xml or within the global element on the esp.xml. + +For example: + +``` + + + + + + + + + + + + + + ``` \ No newline at end of file diff --git a/helm/managed/logging/loki-stack/grafana-hpcc-logaccess-baremetal.xml b/helm/managed/logging/loki-stack/grafana-hpcc-logaccess-baremetal.xml new file mode 100644 index 00000000000..2f4c073ce1e --- /dev/null +++ b/helm/managed/logging/loki-stack/grafana-hpcc-logaccess-baremetal.xml @@ -0,0 +1,18 @@ + + + + + + + + + + + + + + + + + + \ No newline at end of file