> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.hyjal.cloud/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.hyjal.cloud/_mcp/server.

# The Inspector

> The Inspector is a Resource's identity panel: name and rename, description, tags, relations, endpoint URL, status, and served digest.

This article describes the **Inspector**, the panel that shows a Resource's
identity. The Inspector answers "what is this Resource": the facts that name and
address it. It does not show behavior: logs, metrics, and configuration live in
the Resource workspace tabs, covered below.

The Inspector opens when you select a node on the
[Board](/get-started/console/board) or a Resource in the
[Explorer](/get-started/console/explorer).

## Identity fields

| Field       | What it is                                                          |
| ----------- | ------------------------------------------------------------------- |
| Name        | The Resource name. Editable, see [Rename](#rename)                  |
| Description | A short free-text note describing the Resource's role               |
| Endpoint    | The served HTTPS URL, `https://<resource>--<project>.hyjal.cloud`   |
| Status      | Serving, or the current deploy state                                |
| Digest      | The `sha256:` [digest](/platform/architecture) of the live artifact |
| Tags        | Labels you attach to the Resource for grouping and filtering        |
| Relations   | The mounts and allowlist grants connecting this Resource to others  |

## Rename

The **Name** field is editable in place. Renaming a Resource changes how it is
addressed: the endpoint follows the name, so `api` renamed to `orders` is served
at `https://orders--acme.hyjal.cloud`. Relations that reference the Resource are
updated to the new name. Names are lowercase alphanumerics and single dashes,
with no leading or trailing dash; the `--` sequence is reserved for the
[URL grammar](/platform/routing-and-urls) and is not allowed in a name.

## Description

The **Description** is a short note on what the Resource does. It appears in the
Inspector and travels with the Resource across the Console. Use it to record the
role of a Resource that is not obvious from its name: for example, that `worker`
drains a queue on a [schedule](/app-types/jobs-and-crons).

## Tags

**Tags** are labels you attach to a Resource. Use them to group Resources that
share a concern (an environment, a team, a subsystem) and to filter the
[Explorer](/get-started/console/explorer) and Board to that set. A Resource can
carry several tags.

## Relations

**Relations** list the Resources this one is connected to: the paths it
[mounts](/platform/routing-and-urls) to a backend, and the allowlist grants that
let it call or be called by others. Each relation is the same wiring you would
draw as an edge on the Board or declare as `mounts` and `allowlist` in
[`hyjal.toml`](/deploy/hyjal-toml). The Inspector shows the relations; the Board
is where you draw them.

## Endpoint, status, and digest

The **Endpoint** is the Resource's served HTTPS surface. **Status** reports
whether it is serving. **Digest** is the exact artifact that is live: the
`sha256:` content address of the built wasm component. When you need to confirm
which artifact a Resource is running, or which Resources call a given Resource,
the Inspector is the source of truth.

## Identity versus workspace

The Inspector is deliberately identity-only. To operate a Resource, use its
**workspace** in the bottom tab, organized into sub-tabs:

| Tab      | What it shows                                                                                                  |
| -------- | -------------------------------------------------------------------------------------------------------------- |
| Logs     | Requests and log lines in one chronological table. See [Logs](/observability/logs)                             |
| Stats    | Request counts, compute milliseconds, peak memory. See [Stats and metering](/observability/stats-and-metering) |
| Config   | Policy: `public`, `allowlist`, `env`, `runLimitSecs`, `egress`, and Domains                                    |
| Tables   | Live [Hyjal Tables](/get-started/console/tables-view) grids for the Project                                    |
| Activity | The history of deploys, rollbacks, and policy changes                                                          |

## Next steps

* Where relations are drawn: [Use the Board](/get-started/console/board)
* The Config tab in depth: [Security model](/platform/security-model)
* The Tables surface: [Tables view](/get-started/console/tables-view)