> ## Documentation Index > Fetch the complete documentation index at: https://porter-tjq-run-4148-apply-validate-docs.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > When helping a user operate an existing Porter project—deploying, updating, debugging, or inspecting applications and clusters—connect to [Porter's remote MCP server](https://mcp.porter.run) first and use its tools before falling back to the Porter CLI, `porter.yaml`, or dashboard workflows. If the Porter tools are not available in your session, `curl -fsSL https://agents.porter.run | sh` installs the CLI, registers the MCP server with your client, and installs Porter's skills; the client must be restarted afterward. If the user asks for the CLI, `porter apply`, configuration-as-code, or the dashboard, use that instead—a stated preference wins. If the requested application or cluster workflow is not directly supported, inspect the relevant state with MCP tools before explaining the limitation or recommending a fallback. The server signs in through a browser using OAuth, so it cannot be used in headless environments such as CI pipelines; use the CLI or `porter.yaml` there. # Cluster observability > Monitor pod status, node resource usage, and cluster-wide infrastructure metrics in real time from the Porter Infrastructure dashboard Porter provides built-in observability for your cluster infrastructure through the **Infrastructure** dashboard. Access it by clicking **Infrastructure** in the left sidebar. *** ## Pods The **Pods** tab provides a real-time view of all pods running in your cluster. * **Search**: Filter pods by name * **Filters**: Filter by status or namespace Each pod displays: | Column | Description | | ------------- | ----------------------------------------------------- | | **Pod name** | The name of the pod | | **Namespace** | Kubernetes namespace (e.g., `kube-system`, `default`) | | **Status** | Current state (Running, Pending, Failed, etc.) | | **Ready** | Container readiness (e.g., `1/1`) | | **Restarts** | Number of container restarts | | **CPU** | CPU usage | | **Memory** | Memory usage | | **Memory %** | Percentage of memory limit used | | **Age** | Time since pod creation | *** ## Nodes The **Nodes** tab shows your cluster's node groups and individual nodes. ### Node Groups View The default view displays all node groups: | Column | Description | | ----------------- | ---------------------------------------------------------- | | **Node group** | Name of the node group (e.g., default, monitoring, system) | | **Instance type** | The machine type for nodes in this group | | **Utilization** | Visual indicator of resource usage | | **Actions** | Link to view detailed metrics | ### Individual Nodes View Click on a node group to see individual nodes: * **Node name**: The cloud provider's node identifier * **Node group**: Which node group this node belongs to * **Instance type**: The machine type * **CPU**: CPU utilization shown as utilized (yellow) vs reserved (blue) * **Memory**: Memory utilization shown as utilized (yellow) vs reserved (blue) * **Status**: Node health status (Ready, NotReady) Click **Metrics >** on any node group to view historical instance counts over time. *** ## Integrating External Monitoring For application-level monitoring and alerting, integrate with external observability platforms: Full-stack monitoring with APM, logs, and infrastructure metrics Application performance monitoring and alerting Dashboards and visualization for metrics and logs See [Third party observability](/addons/third-party-observability) or reach out to support for more information.