
That secret is then provided to the HPCC Systems log access framework as a Kubernetes secret. That Kubernetes secret must be named azure-logaccess and the video goes further into details with what other bits of information must be contained in that secret and walks through just how to do that.
The HPCC Systems Kubernetes secret must contain the Service Principal client ID, the Service Principal secret, the (Azure) Tenant ID, and the Azure LogAnalytics Workspace ID.
The developer then illustrates how to create this Kubernetes Secret for the HPCC Systems, and how to leverage the provided helper utilities. He provides the location of these HPCC Systems provided Azure Log Analytics tools relative to the HPCC-Platform/helm repository path as HPCC-Platform/helm/examples/azure/log-analytics and illustrates accessing and modifying the supplied template files, then running the create-azure-logaccess-secrets.sh script which generates that secret. Once the Kubernetes Secret is successfully created, the developer then shows how to use the provided log mapping values file to target the HPCC Systems log analytics workspace, and route the logging information to HPCC Systems.
© 2023 LexisNexis Risk Solutions