Skip to main content

​
Overview

Resource Viewer is Metoro’s K9s-style interface for exploring Kubernetes resources. It gives you a fast way to move between resource kinds, drill into details, and inspect what was happening in your cluster at a specific point in time. Open it from the main navigation at /resource-viewer.

​
Time-Travel Resource State

Resource Viewer is designed for historical analysis, not just “what is live right now.” The list and detail views are anchored to your selected time range, so you can:
  • See cluster state during an incident window
  • Compare resource state before and after a rollout
  • Reconstruct what changed when debugging failures
For relative time ranges, you can keep the view live with autorefresh. For fixed absolute time ranges, Resource Viewer stays pinned to that historical window.

​
How You Use It

At a high level, the workflow is:
  1. Choose a resource kind (Pod, Node, Deployment, Service, and others)
  2. Narrow the scope with namespace and search filters
  3. Open a resource to inspect its state and context
  4. Move between views to understand behavior and changes over time
This gives you a K9s-like “scan -> focus -> drill down” loop directly in the Metoro UI.

​
What You Can Inspect

Depending on the resource kind, you can inspect:
  • Overview: summary fields and health context
  • YAML: point-in-time manifest snapshot
  • Events: lifecycle and warning events around the selected window
  • Related telemetry: logs, metrics, pods, and request-level context where applicable

​
Common Use Cases

  • Incident reconstruction: what did this resource look like when the incident started?
  • Change verification: did a deployment, scaling action, or config update produce expected state?
  • Lifecycle debugging: when did warnings, restarts, or readiness issues first appear?
  • Cross-resource exploration: pivot quickly across pods, nodes, workloads, and services in one place.

​
How It Fits With Other Views

  • Use Resource Viewer for cluster-wide resource exploration over time.
  • Use the Service pages for service-scoped operational workflows.
  • Use the Infrastructure page for node-centric analysis with Resource Viewer embedded for node drill-down.
For additional context, see Kubernetes Resources and Kubernetes Events.