The Inspector

View as Markdown

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 or a Resource in the Explorer.

Identity fields

FieldWhat it is
NameThe Resource name. Editable, see Rename
DescriptionA short free-text note describing the Resource’s role
EndpointThe served HTTPS URL, https://<resource>--<project>.hyjal.cloud
StatusServing, or the current deploy state
DigestThe sha256: digest of the live artifact
TagsLabels you attach to the Resource for grouping and filtering
RelationsThe 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 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.

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 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 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. 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:

TabWhat it shows
LogsRequests and log lines in one chronological table. See Logs
StatsRequest counts, compute milliseconds, peak memory. See Stats and metering
ConfigPolicy: public, allowlist, env, runLimitSecs, egress, and Domains
TablesLive Hyjal Tables grids for the Project
ActivityThe history of deploys, rollbacks, and policy changes

Next steps