Logging Options

Logging Options

Centralized Logging

All Turbonomic Server components except for the Operator generate logs that are centralized/sent to the rsyslog pod in the namespace the you have deployed Turbonomic in. To view the rsyslog logs use the command below if you have Turbonomic deployed in the turbonomic namespace (if not just replace turbonomic with the namespace you have Turbonomic deploy in)

for i in `kubectl get pods -n turbonomic | grep rsyslog | awk {'print $1'}`; do kubectl -n turbonomic logs $i; done

Operator logging

The Turbonomic Operator writes it logs to the t8c-operator pod. To view the operator logs you can use the single command below if you have Turbonomic deployed in the turbonomic namespace (if not just replace turbonomic with the namespace you have Turbonomic deploy in):

for i in `kubectl get pods -n turbonomic | grep t8c-operator | awk {'print $1'}`; do kubectl -n turbonomic logs $i; done

Additionally, you can turn down the logging of the operator pod by adding the following argument to the operator.yaml deployment:

containers: 
- name: t8c-operator
  image: icr.io/cpopen/t8c-operator:42.30
  imagePullPolicy: Always
  args:
  - --zap-level=error

Azure Monitor

If your AKS cluster is configured with Azure Monitor to collect and centralize pod logs, you can configure this to include or exclude the Turbonomic namespace as desired. Leverage the “exclude_namespaces” parameter under log-data-collection-settings for log_collection_settings.stdout and log_collection_settings.stderr.

Log forwarding

Contact Turbonomic Support for more information on how to forward the following logs:

• Turbonomic centralized rsyslog log to an external syslog collector
• Turbonomic Audit log forwarding to an external syslog collector