Kubernetes Clusters - Object Logs

Available in PagerDuty Runbook Automation Commercial products.

Overview

This plugin retrieves logs from a specific object within a Kubernetes cluster. Since this is a node-step plugin, multiple Kubernetes clusters or namespaces can be targeted within a single Job.

The types of objects that can be viewed logs from within a Kubernetes cluster include:

• Pods

Configuration

Prerequisites

Before configuring the Kubernetes Object Logs plugin, the target clusters must be added to the Runbook Automation instance and the authentication method must be configured. This is done by following the steps outlined in the Kubernetes Plugins Overview.

Add Kubernetes Object Logs Step

When building a Job, add the Kubernetes / Clusters / Object Logs node step:

Configure the following fields:

• Name: The name of the object to view logs from, such as Pod name.
• Container: Specify a particular container to view logs from within the object.
• Number of Log Lines: The number of log lines to retrieve. Default is 50.
• Time-span (seconds): A relative time in seconds before the current time from which to show logs.
• Follow Logs: If selected, the plugin will follow the log output. Note that the Job may continue to run until manually stopped.

Invocation Output

The output of the step will be the logs from the object in the Kubernetes cluster:

Notes

• When using the "Follow Logs" option, be aware that the Job will continue running until it's manually stopped.
• The Time-span option allows you to view logs from a specific point in time, which can be useful for troubleshooting recent issues.