-
Notifications
You must be signed in to change notification settings - Fork 75
Kubeturbo Logging
Jason Shaw edited this page Aug 3, 2023
·
15 revisions
Kubeturbo sends its log stream to STDERR FD of the container, which is generally available via kubectl logs
or to the logging pipeline if configured within the k8s cluster. Kubeturbo additionally by default writes these logs to a file into the container local storage at /var/log if the location is mounted as writable file system within the container. If /var/log is not writable within the container, then these log files are written to /tmp. You can also adjust Kubeturbo log verbosity for both diagnostics and gathering more environmental details.
For details on how to collect and configure Kubeturbo Logging go here.
Introduction
Kubeturbo Use Cases
Kubeturbo Deployment
Kubeturbo Config Details and Custom Configurations
Actions and how to leverage them
- Overview
-
Resizing or Vertical Scaling of Containerized Workloads
a. DeploymentConfigs with manual triggers in OpenShift Environments - Node Provision and Suspend (Cluster Scaling)
- SLO Horizontal Scaling
- Turbonomic Pod Moves (continuous rescheduling)
-
Pod move action technical details
a. Red Hat Openshift Environments
b. Pods with PVs
IBM Cloud Pak for Data & Kubeturbo:Evaluation Edition
Troubleshooting
- Startup and Connectivity Issues
- KubeTurbo Health Notification
- Logging: kubeturbo log collection and configuration options
- Startup or Validation Issues
- Stitching Issues
- Data Collection Issues
- Collect data for investigating Kubernetes deployment issue
- Changes to Cluster Role Names and Cluster Role Binding Names