Enable logs

Single cluster link

1. Get your current installation Helm values, and save them in a file.

     helm get values gloo-platform -n gloo-mesh -o yaml > gloo-single.yaml
   open gloo-single.yaml
     

2. Add the following configuration to your Helm values file to enable logs for Gloo components.

     
   telemetryCollectorCustomization:
     pipelines: 
       logs/ui: 
         enabled: true
     

3. Upgrade your installation by using your updated values file.

     helm upgrade gloo-platform gloo-platform/gloo-platform \
      --namespace gloo-mesh \
      --version $GLOO_VERSION \
      --values gloo-single.yaml
     

4. Verify that your settings were added to the Gloo telemetry collector configmap.

     kubectl get configmap gloo-telemetry-collector-config -n gloo-mesh -o yaml
     

5. Perform a rollout restart of the telemetry collector daemon set to force your configmap changes to be applied to the telemetry collector agent pod.

     kubectl rollout restart -n gloo-mesh daemonset/gloo-telemetry-collector-agent
     

6. Open the Gloo UI.

     meshctl dashboard
     

7. In the navigation pane, click Observability > Logs. Select the cluster, component, pod, and container for which you want to see the logs.

Multicluster link

1. Get the Helm values files for your current version.

   1. Get your current values for the management cluster.

        helm get values gloo-platform -n gloo-mesh -o yaml --kube-context $MGMT_CONTEXT > mgmt-plane.yaml
      open mgmt-plane.yaml
        

   2. Get your current values for the workload clusters.

        helm get values gloo-platform -n gloo-mesh -o yaml --kube-context $REMOTE_CONTEXT > data-plane.yaml
      open data-plane.yaml
        

2. In the Helm chart for the management cluster, add the following configuration to your Helm values file to enable logs for Gloo components.

     
   telemetryCollectorCustomization:
     pipelines: 
       logs/ui: 
         enabled: true
     

3. In the Helm values file for the workload cluster, add the following configuration to your Helm values file to enable logs for Gloo components. Logs are automatically sent to the telemetry gateway in the management cluster.

     
   telemetryCollectorCustomization:
     pipelines: 
       logs/ui: 
         enabled: true
     

4. Upgrade the Gloo management cluster.

     helm upgrade gloo-platform gloo-platform/gloo-platform \
     --kube-context $MGMT_CONTEXT \
     --namespace gloo-mesh \
     -f mgmt-plane.yaml \
     --version $GLOO_VERSION 
     

5. Verify that your settings are applied in the management cluster.

   1. Verify that your settings were added to the Gloo telemetry gateway configmap.

        kubectl get configmap gloo-telemetry-gateway-config -n gloo-mesh -o yaml --context $MGMT_CONTEXT
        

   2. Perform a rollout restart of the telemetry gateway deployment to force your configmap changes to be applied to the telemetry gateway pod.

        kubectl rollout restart -n gloo-mesh deployment/gloo-telemetry-gateway --context $MGMT_CONTEXT
        

6. Upgrade the Gloo workload cluster.

     helm upgrade gloo-platform gloo-platform/gloo-platform \
     --kube-context $REMOTE_CONTEXT \
     --namespace gloo-mesh \
     -f data-plane.yaml \
     --version $GLOO_VERSION
     

7. Verify that your settings are applied in the workload cluster.

   1. Verify that your settings were added to the Gloo telemetry collector configmap.

        kubectl get configmap gloo-telemetry-gateway-config -n gloo-mesh -o yaml --context $MGMT_CONTEXT
        

   2. Perform a rollout restart of the telemetry collector daemon set to force your configmap changes to be applied to the telemetry collector agent pods.

        kubectl rollout restart -n gloo-mesh deployment/gloo-telemetry-gateway --context $MGMT_CONTEXT
        

8. Open the Gloo UI.

     meshctl dashboard --kubecontext $MGMT_CONTEXT
     

9. In the navigation pane, click Observability > Logs. Select the cluster, component, pod, and container for which you want to see the logs.