Open the right stream#

  1. Open a Pod, or a workload that exposes the Logs tab.
  2. Select the pod and container when the viewer offers multiple choices. Include the relevant init or application container for the issue you are investigating.
  3. Choose the historical tail size. The current selector offers 50, 100, 200, 500, 1000 or All.
  4. Wait for the connection status to show that the stream is connected, then follow incoming output. Changing the container or stream options reconnects the viewer.

Use the viewer controls#

ControlHow to use it
Show TimestampsEnable when correlating output with events or another system.
Previous ContainerUse for the previous terminated instance of the selected container, when Kubernetes still has those logs.
Word WrapWrap long lines rather than scrolling horizontally; Alt/Option+Z toggles wrapping.
FindUse Ctrl/Cmd+F in the log editor to find text in the displayed output.
DownloadExports the buffered text to a pod/container-specific text file. It does not query an external logging archive.
Display settingsAdjust font size and available presentation settings to make long sessions readable.
The Logs tab provides the pod selection and stream controls. This demonstration container has no log lines at capture time.
The Logs tab provides the pod selection and stream controls. This demonstration container has no log lines at capture time. View full size ↗

Investigate a restarting container#

  1. Check the pod’s restart count and current state.
  2. Select the failing container and enable Previous Container.
  3. Look near the end of the output for the failure, then compare its timestamp with the pod Events tab.
  4. Switch back to the current instance to see whether the same failure is repeating.

When logs are missing#

  • An empty result can mean the container has not written output, the previous instance has no retained logs, or your selected container is incorrect.
  • A disconnected WebSocket can be caused by an expired session or a proxy that does not pass WebSocket upgrades.
  • Access to a pod list does not automatically grant access to pod logs. Check the log permission and Kubernetes connection permissions.
  • For long-term retention and cross-system searching, use your logging system; this viewer is a live Kubernetes log interface.