Application Instance Details

​

Introduction

The application instance detail page shows the current status, resource utilization, deployment metadata, attached networks and volumes, and configuration for a single application instance. Use it to verify that an instance is online, review its placement and workload settings, and inspect logs and snapshot history.

​

Prerequisites

• You are signed in to Edge Infrastructure Services.
• At least one application instance is deployed and visible in Infrastructure > Workloads > Applications.

​

Open the Detail Page

1. In the sidebar, navigate to Infrastructure > Workloads > Applications.
2. Click the name of the application instance you want to inspect.

The detail page opens. The header shows the current run state, application type, and the name of the hosting node, followed by the instance name and description. A Notifications bell icon in the header shows a color-coded badge when EVE-OS has reported errors, warnings, or notices for this instance. Click the bell to view each notification with its severity, explanation, and suggested fix. If the node reports a CPU placement condition for the instance, a placement status pill appears below the run state, admin state, and last reported values. See CPU placement status.

​

Overview Tab

The Overview tab is the default landing view. It provides a fast operational snapshot of the instance’s health and configuration.

​

Status ribbon

The ribbon across the top of the Overview tab shows six values.

​

Resource utilization

The resource utilization panel shows CPU and memory usage history for the last hour, updated in real time. Use this panel to detect resource contention or unexpected spikes before taking a lifecycle action.

​

Identity at-a-glance

The right side of the Overview tab shows a compact identity card with the following fields: ID, Name, Title (if set), Project, Node (with a pin indicator if the instance is pinned to a cluster node), Node Cluster (if cluster-deployed), Edge App, Version (if set), Tags, Created, and Updated.

​

Resources

A tabbed card below the resource utilization panel shows the instance’s attached resources. Three sub-tabs are available.

• Network Interfaces: lists each attached network interface with its name, network instance, MAC address, and IP address. Up to four interfaces are shown; click View all to open the Interfaces tab.
• Volumes: lists each attached volume with its name, type, and run state. Up to four volumes are shown; click View all to open the Storage tab.
• Custom Configuration: indicates whether custom configuration is defined on the instance. Click to open the Custom Configuration tab.

​

Recent activity

A short event log shows the most recent state report, restart, and creation event. Click View all events to open Monitor > Events filtered to this instance.

​

Containers in this application

For Docker Compose instances, a table at the bottom of the Overview tab lists each container the Compose Runtime reports for this instance. The table does not appear for other application types. Use it to confirm that every container in the compose file is running before you open a remote console or check logs. If Edge Infrastructure Services has not received container details from the node, the table is replaced with the message Container details are not available. Expect this while a newly deployed instance is still starting.

​

Opaque status

The Opaque Status card shows the raw status string reported by the agent running on the node. It appears only when Edge Infrastructure Services has received a value, so a card that is absent is not itself a fault. Values longer than 100 characters are truncated. Click Show more to see the full string, and Show less to collapse it again. Click the copy icon to copy the untruncated value, which is useful when you attach the value to a support case.

​

Details Tab

The Details tab shows the complete set of metadata across three cards, plus a CPU placement card when the instance has a CPU placement policy.

​

Identity & Ownership

This card shows the full identity of the application instance.

​

Placement & Workload

This card shows where the instance runs and how it is configured as a workload.

​

State & Timeline

This card shows the current state and the full history of state changes and timestamps for this instance.

​

CPU placement

For Virtual Machine and Container instances with a CPU placement policy, including legacy CPU pinning, a read-only CPU placement card summarizes the instance policy. The instance policy takes precedence over the app definition. Changes to the definition apply only to new instances. Click View app definition to open the source edge app. Expand CPU policy details to see Core allocation, SMT threads per core, and Disk and device emulation. If the node does not place CPUs, the card shows This node does not place CPUs; the saved CPU placement policy is not enforced on it. For configuration steps, see CPU Placement for Application Instances.

​

CPU placement status

The header shows a placement status pill only when the node reports a placement condition. No pill appears when the instance is placed. Hover over the pill to see the description and retry condition. For Needs repack and Part of a repack, the pill links to the node’s Details tab so you can run a repack there. A repack restarts every app on the node that needs repacking, not just this one. For the other conditions, change the policy, free capacity, or deploy to a different node.

​

Interfaces Tab

The Interfaces tab shows a table of all network interfaces attached to this instance. The table shows each interface’s name, associated network instance (linked to the virtual network detail page), MAC address, and IP address. Interfaces with direct attachment are labelled direct.

​

Edit the interface set

Click Edit App Interfaces to change which interfaces this instance has. The editor covers both the interface list and the firewall rules, because an interface and its access control rules are configured together.

​

Restart instead of purge

Before EVE-OS (Edge Virtualization Engine) 17.3.0 LTS, changing the network interfaces of a deployed instance required a purge, which destroyed and recreated the instance’s volumes. On nodes running EVE-OS 17.3.0 LTS or greater, Edge Infrastructure Services applies an interface change with a restart instead. The node stages the new interface set while the application keeps running, and applies it when the application restarts. The volumes and their data survive the change. Keep the following in mind:

• The restart happens when you save. Any workload running in the instance is interrupted until the application comes back up.
• Virtual interfaces and direct-attach network adapters (Ethernet, WLAN, WWAN, SR-IOV virtual functions) can be added, removed, or swapped this way. Changing a direct-attach interface that is not a network adapter, such as a USB or serial device, still requires a purge.
• Automatically assigned MAC addresses are not guaranteed to stay the same after the interface set changes. If the application identifies an interface by MAC address, set a MAC address on the interface when you deploy the instance. See Interface Ordering for Application Instances.

On nodes running an EVE-OS version earlier than 17.3.0 LTS, the Edit App Interfaces button does not appear. To change the interfaces of an instance on those nodes, use Purge & Update after changing the edge app, or redeploy the instance. See Manage an Application Instance.

​

When the editor is available

The button appears only when all of the following are true:

• The edge app is a VM or container app. For Docker Compose, module, and other app kinds, the Interfaces tab shows only Network Interfaces, and the App Interfaces view and this button are hidden.
• You have update permission for application instances in the instance’s project.
• The node hosting the instance runs EVE-OS 17.3.0 LTS or greater, which supports changing an application instance’s interface set without a purge.
• The project has Interface Ordering enabled. See Interface Ordering for Application Instances.

In the editor, you can do the following:

• Click Add interface to add an interface, or click the X on a card header to remove an Optional interface. Required interfaces cannot be removed.
• Rename an interface. Use up to 32 letters, numbers, dots, dashes, or underscores. Each name must be unique within the instance.
• Switch an interface between Virtual Network and Direct Attach.
• Edit the inbound and outbound access control rules for an interface you added in the current editing session. The rules of an interface that is already deployed are read-only, because they are part of the running application’s firewall. To define new rules, add a new interface.
• Select a Virtual Network for each virtual interface. This is required. Only virtual networks on the node hosting this instance are listed. If the node has no virtual networks, create one before adding a virtual interface.

Whether an interface is Optional or Required is set by the edge app and is shown on the card header. You cannot change it in the editor. Interfaces you add here are always Optional. To apply or discard your changes, do the following:

1. Click Save Interfaces. The button is available only after you make a change.
2. In the Save interface changes? dialog, review the warning. Saving restarts the application, and any workload running in it is interrupted until it comes back up.
3. Click Save and Restart to apply the changes, or close the dialog to keep editing.

To discard your changes, click Cancel in the editor. Saving replaces only the instance’s interface set and leaves the rest of its configuration unchanged. Interfaces that already exist keep their original interface order, even if you remove another interface. New interfaces are ordered after the existing ones.

​

Storage Tab

The Storage tab shows two tables. Volumes: lists each volume attached to this instance with its name (linked to the volume detail page), type, and run state. Application Volume Snapshots: lists any snapshots created for this instance. The table shows the snapshot name, creation date, and status. From this table you can roll back the instance to a snapshot or delete a snapshot. For a full overview of snapshot behavior, see Application Snapshot Overview.

​

Custom Configuration Tab

The Custom Configuration tab shows the custom configuration defined on this instance and its source edge app. It includes the configuration metadata (cloud config flag, config name, override setting, delimiter) and all variable groups with their names, formats, required flags, and values. If no custom configuration is defined, the tab shows a message indicating that no configuration is set.

​

Run States

The run state reflects the current operational condition of the application instance as reported by EVE-OS. The state appears in the page header, the status ribbon, and the State & Timeline card. For guidance on interpreting run states, admin state, and health signals, see Application Instance Status and Health. A newly deployed instance typically progresses from Unprovisioned through Init to Online as EVE-OS receives and applies the configuration. If the instance stays in Provisioned or Init for an extended period, verify that the hosting node is online and reachable.

​

Next Steps