> For the complete documentation index, see [llms.txt](https://docs.controltheory.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.controltheory.com/controltheory-documentation/gonzo-docs/integration-examples/container-environments/kubernetes/stern-integration.md).

# Stern ⛵ Integration

Stream and analyze Kubernetes logs with Gonzo using kubectl and [Stern](https://github.com/stern/stern). Monitor pods, deployments, and entire namespaces with powerful real-time analysis and AI-powered insights.

{% hint style="info" %}
**Prerequisites:** Kubernetes cluster access with kubectl configured. Stern is optional but highly recommended for advanced use cases.
{% endhint %}

### Basic Examples

```bash
# Get logs from all pods, all namespaces
stern . --all-namespaces --output json | gonzo

# Monitor specific namespace
stern . -n kube-system --output json | gonzo

# Get last 100 logs from namespace
stern . -n kube-system --tail 100 --output json | gonzo

# Monitor pods matching pattern
stern "api-*" -n production --output json | gonzo

# Get logs from last hour
stern . -n production --since 1h --output json | gonzo
```

### Key Options

* `--output json` - Preferred for Gonzo compatibility (populating attributes)
* `--tail N` - Limit historical logs
* `--since TIME` - Time-based filtering (1h, 30m, etc.)
* `-n NAMESPACE` - Target specific namespace
* `--all-namespaces` - Monitor all namespaces

### Tips

* Use specific pod patterns instead of `.` for better performance
* Always include `--output json` for proper Gonzo (attribute) processing
* Consider `--tail` to limit log volume for large clusters

### Deep Dive Tutorial

For a comprehensive guide on using Gonzo with Kubernetes: 📖 [**Using Gonzo with k9s and Stern: Supercharge Your Kubernetes Log Tailing**](https://www.controltheory.com/blog/using-gonzo-with-k9s-and-stern-supercharge-your-kubernetes-log-tailing/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.controltheory.com/controltheory-documentation/gonzo-docs/integration-examples/container-environments/kubernetes/stern-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.