Logs & metrics

See what's happening. Kaja gives you logs and metrics for your apps right in the dashboard. No switching to the cluster or running kubectl logs. Open an app, go to Logs or Metrics, and you're there. This page is about what you get and how to use it.

Logs

Where you get logs

Open any container app or Helm app and go to the Logs tab. You get a live stream of logs from that app's pods. You can filter by pod (e.g. one replica) or by container (main app or a sidecar). Start and stop the stream, choose how many lines to load (e.g. last 100), and search or download. All from the same dashboard you use for deploy and config.

Logs aren't available for resources that are already deleted or in the process of being removed—in that case the UI tells you and you can still view other details.

What you can do

• Live stream — See logs as they're written. Follow the stream so new lines keep appearing.
• Filter — Show one pod or one container so you can focus on a single replica or a sidecar.
• Tail — Load only the last N lines so you're not waiting for huge history.
• Search and download — Search in the visible log and download the current content if you need to share or inspect offline.

Logs are read from the cluster when you open them; they're not stored long-term in Kaja. When you leave the page or stop the stream, the connection stops.

Metrics

Where you get metrics

For container apps, open the app and go to the Metrics tab. You see a table of pods with their current CPU and memory usage. If you've set resource requests or limits on the app, the dashboard can show you how usage compares—so you can spot when an app is under- or over-provisioned. Metrics refresh on an interval so the numbers stay current.

Metrics are available when your cluster has a metrics server (many managed Kubernetes offerings include it). If it's not installed, the Metrics tab may be empty or show a short message; the rest of Kaja still works.

Helm apps don't have a Metrics tab in the current UI; you still get status, pods, and logs.

What you see

• Per-pod rows — Each pod (e.g. myapp-abc123-xyz) with its CPU and memory usage.
• Comparison to limits — When you've set requests/limits, you see how usage stacks up so you can tune resources or spot issues.

Metrics are current usage, not long-term history. For long-term or custom metrics you'd use your own observability stack; Kaja focuses on quick, in-dashboard visibility so you can debug and right-size without leaving the app.

Why it matters

• One place — Logs and metrics next to deploy, config, and status. No context switching.
• Self-serve — Any developer with access can open logs and metrics. No need to ask for cluster access or run CLI commands.
• Fast — Open the tab and you're streaming or seeing numbers. Helps you deploy faster and spend less time hunting for information.

Summary

See what's happening. Stay in one place. That's the value.

Next steps

• Environments — Where your apps run; Apps — App features. Spin up and pause envs.
• Helm — Deploy Helm charts and view their logs.
• Sync & agents — How the dashboard and your clusters stay in sync.