> For the complete documentation index, see [llms.txt](https://docs.kinesis.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kinesis.network/getting-started/running-llms-with-kinesis-network/monitoring-apps.md).

# Monitor and troubleshoot

Read status, choose the right logs and investigate deployment or runtime failures.

Open an app to inspect its status, endpoints and operational tabs. Image pulls, builds and machine provisioning can take time; use the reported state to decide what to inspect next.

| Tab             | Use it for                                                              |
| --------------- | ----------------------------------------------------------------------- |
| **Logs**        | Container output, separated by server when there are multiple instances |
| **Terminal**    | An interactive shell in a running container                             |
| **Metrics**     | CPU, GPU, memory and other usage over time                              |
| **History**     | App actions and platform events affecting placement or execution        |
| **Deployments** | Repository import, image-build progress and builder logs                |
| **Config**      | Source, runtime, network, execution and resource settings               |

## Follow deployment state

| State or symptom              | What to inspect                                         |
| ----------------------------- | ------------------------------------------------------- |
| Building                      | Deployment step and builder logs                        |
| Downloading or starting       | Image size, pull progress and startup behavior          |
| Provisioning                  | Grid capacity, servers and pending orders               |
| Start blocked                 | Runtime errors, balance and placement requirements      |
| Error or repeated exits       | Runtime logs, command, environment and restart policy   |
| Stopped with a running target | Matching capacity, placement filters and runtime errors |
| Queued on a shared grid       | Fair-share position and available capacity              |

## App runs but the endpoint does not respond

Check that the service binds to `0.0.0.0`, uses the configured container port and supports the selected protocol. Use the endpoint Kinesis returns: some protocols allocate a public port different from the container's port. In API status, an endpoint with a null address is not wired yet.

## Build fails before the app starts

Read builder logs rather than runtime logs. Confirm the image's base tag, package installation steps, build context and Dockerfile path. For repository apps, correct the source settings or Dockerfile, then trigger a new build. A successful image build is followed by deployment; continue checking app status afterward.

## App stops or loses capacity

Inspect runtime errors and History. Repeated startup failures, an idle-reclaim policy, a fair-share turn ending or a manual stop can produce different outcomes. A grid may still be filling even while another instance of the app is running.

## Automate inspection

Use REST status, logs and usage endpoints, or MCP `get_app_status`, `get_app_logs` and `get_app_usage`. Runtime logs and build logs require `monitoring:read` in addition to any resource-specific scope listed in the reference. App-usage queries support ranges of at most 30 days.

See the [Apps reference](/api/apps.md), [Builds reference](/api/builds.md) and [agent workflows](/mcp/workflows.md).

When asking [support](/support.md) for help, include the project/app ID, time of the failure, request ID and a short log excerpt with secrets removed.


---

# 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.kinesis.network/getting-started/running-llms-with-kinesis-network/monitoring-apps.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.