Skip to main content
Glama

get_workload_logs

Read-only

Aggregate and filter logs from all pods of a deployment, statefulset, or daemonset. Automatically collects errors, warnings, and panics across replicas, with optional pattern-based filtering.

Instructions

Get aggregated logs from all pods of a workload (Deployment, StatefulSet, or DaemonSet). Logs are collected from all matching pods concurrently, then server-side filtered to errors, warnings, panics, and stack traces using deterministic regex patterns and deduplicated. Set grep for additional server-side filtering before that summary stage, like kubectl logs | grep PATTERN. More useful than get_pod_logs when you need logs across all replicas of a workload. If the target is a config value, feature flag, CRD field, env ref, or YAML/spec content, use search rather than logs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoworkload kind: deployment, statefulset, or daemonset. Defaults to deployment when omitted.
namespaceYesworkload namespace
nameYesworkload name
containerNospecific container name, defaults to all containers
tail_linesNolines per pod (default 100)
grepNooptional regular expression to keep matching log lines before diagnostic filtering, like kubectl logs | grep PATTERN
sinceNoonly return logs newer than this duration (e.g. 30s, 10m, 1h), like kubectl logs --since
previousNoreturn logs from the previous terminated container instance (e.g. for CrashLoopBackOff diagnosis), like kubectl logs -p

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/skyhook-io/radar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server