> ## Documentation Index
> Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL.
> Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other.
> Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking.
> Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify.

# Monitoring, Logs, Events, Reports, and Jobs

> View application logs, review platform events, analyze capacity and performance reports, and track alerts plus Edge AI and cloud jobs in one place.

## Introduction

The Monitor and Operations sections of Edge Infrastructure Services consolidate the operational surfaces you use to verify current state, diagnose failures, and confirm that actions completed successfully. Logs, Events, and Reports are in the **Monitor** section. Alerts and Jobs are in the **Operations** section.

## Logs

**Path:** Infrastructure > Monitor > Logs

The Logs page shows container log output (stdout and stderr) forwarded by EVE-OS (Edge Virtualization Engine) from edge application instances. Logs are available for application instances where **Enable Logs Access** is turned on. You can enable this setting when deploying an application instance or in the **General Settings** dialog on an existing instance.

To view logs for an application instance:

1. Open **Infrastructure > Monitor > Logs**.
2. (Optional) In the **Status** dropdown, select a run state (for example, **Online** or **Error**) to limit the application list to instances in that state. The default is **All statuses**. Changing the status clears the selected application.
3. In the **Application** dropdown, select the instance whose logs you want to view.
4. Use the **Time range** selector to choose the log window: 1 hour, 6 hours, 24 hours, or 7 days. To choose a specific window, select **Custom**, then set the **From (local time)** and **To (local time)** values. The end time must be after the start time and no later than now.
5. Logs stream in the viewer panel. Use the scroll bar or wait for real-time output to append.
6. Click **Download** to save the loaded log output as a text file. The file name includes the start and end of the loaded time window.
7. Click **Refresh** to re-fetch logs.

If no logs appear, confirm that **Enable Logs Access** is set to **Yes** on the application instance. See [Application Instance Details](https://zededa.mintlify.site/new-ui/infrastructure-services/applications/app-instance-details.md) for the field location.

## Events

**Path:** Infrastructure > Monitor > Events

The Events page shows a centralized log of state-change events across all objects in your enterprise, including nodes, application instances, virtual networks, volumes, and projects. Each event includes a severity level, timestamp, affected object, and a human-readable description.

Use Events to understand what changed in your environment and when. Common use cases include tracing unexpected application restarts, reviewing node state transitions, and auditing configuration changes.

The event list supports:

* **Search** by event message or object name.
* **Filter by severity** to narrow results to errors, warnings, or informational events.
* **Filter by object type** to view events for a specific resource category.
* **Time range selection** to limit results to a recent window.

Click any event row to expand the full event details.

You can also access events scoped to a single object from that object's detail page. On an application instance detail page, for example, click **View all events** in the Recent Activity section to open Events pre-filtered to that instance.

## Reports

**Path:** Infrastructure > Monitor > Reports

The Reports page shows organization-wide resource totals, current resource capacity, performance of a single resource over time, and archived nodes. It has four tabs: **Summary**, **Capacity**, **Performance**, and **Archived**. The page opens on the Summary tab. Access follows your organization and project permissions.

The first time you open Reports, an **Introducing Reports** dialog describes each tab. To reopen it later, click **How it works** in the page header.

> [!NOTE]
>
> Links to earlier versions of the Reports page still work. A link that points to a specific node or application instance opens the Performance tab, and a link to the former fleet-wide Utilization view opens the Capacity tab.

### Summary tab

The Summary tab shows organization-wide totals for the resources you can access, across all projects.

**Nodes** shows the total node count and a state distribution bar. The bar breaks the total into **Online**, **Suspect**, **Provisioned**, and **Error** nodes, plus **Other states** for the remaining nodes. A count shows **Not reported** or **Unavailable** when Edge Infrastructure Services did not return it. These values are not zero.

**Resources** shows one card per resource type.

| Card | Description |
| - | - |
| Applications | Deployed application instances. |
| Edge Apps | Application definitions. |
| App Images | Application artifacts. |
| Projects | Deployment groups. |
| Networks | Network configurations. |
| Virtual Networks | Virtual networks on edge nodes. |
| Volumes | Volume instances. |
| Datastores | Image and volume sources. |

To export a snapshot of the summary, click the **Export summary** icon and select one of the following options:

* **Download CSV**: saves the counts as a CSV file.
* **Export PDF**: opens your browser's print dialog. Choose **Save as PDF** to save the file.

### Capacity tab

The Capacity tab lists nodes or application instances with their current reported CPU, memory, and storage values, so you can compare resources side by side.

Use the following controls to filter the list:

* **Search**: filter by resource name.
* **Project**: limit the list to one project, or show all projects.
* **Resource type**: choose **Nodes** or **Applications**.
* **Status**: limit the list to one run state. Each option shows the number of matching resources.

Each row shows the resource name, project, state, and the **CPU**, **Memory**, and **Storage** values. Use the row actions to do the following:

* Click the details icon to open the **Capacity details** dialog, where you can inspect and copy every reported value for the resource.
* Click **View performance** to open the resource on the Performance tab.

### Performance tab

The Performance tab shows how one node or application instance performed over a time window.

1. Select the **Project**, **Resource type**, and (optional) **Status** to narrow the resource list.
2. Select a node or application in the **Node** or **Application** picker.
3. Select a **Time range**: **Last 1 hour**, **Last 6 hours**, **Last 12 hours**, **Last 24 hours** (default), **Last 7 days**, or **Last 30 days**. To choose a specific window, select **Custom period**, then set **From (local time)** and **To (local time)**.

The time window in use, with your time zone, appears below the controls. Click it to copy it.

The tab shows the selected resource's current state and last report time, and the following charts:

* **CPU usage**.
* **Memory** (node memory or application memory).
* **Storage**.
* **Interface throughput**: receive and transmit rates for each reported interface. Click an interface to include it in or exclude it from the chart.

Charts show averages over time intervals, and throughput is a calculated rate. Edge Infrastructure Services can fill missing intervals, so a zero or continuous line does not confirm uninterrupted reporting. Each chart shows its latest returned timestamp.

For a node, the tab also lists **Applications on this node**, so you can open the performance view of each application instance it hosts. For an application instance, click **View host performance** to open the node that runs it. Click **Events in this period** to open the Events page filtered to the resource and time window.

### Archived tab

The Archived tab lists nodes that have been deregistered from Edge Infrastructure Services across your organization. The table includes the node **Name**, **Serial number**, and **ID**. The list loads more rows as you scroll.

To export the list, click **Export archived nodes**. You can choose the columns to include and export the list as CSV, JSON, or Markdown.

Use this tab to confirm that deregistered nodes are no longer active, or to retrieve identifying information for a decommissioned device.

## Alerts

**Path:** Infrastructure > Operations > Alerts

> [!NOTE]
>
> The Alerts page is not yet available. The sidebar item and route are currently disabled. This section documents the intended behavior and will be updated when the feature is enabled.

Alerts notify you of conditions that require attention, such as nodes going offline, application instances entering an error state, or EVE-OS version policy violations. Configure alert rules at the enterprise level. Active alerts appear on the Alerts page with their severity, affected object, and trigger time.

## Jobs

The Jobs page has two views: **Edge AI jobs** and **Cloud jobs**. Access each view from a different sidebar entry. Both views share the same page but show different data.

### Edge AI jobs

**Path:** Inference > Monitor > Jobs

The Edge AI Jobs view shows model import and inference jobs from AI model providers. Each job row shows:

| Column | Description |
| - | - |
| Job ID | A unique identifier for the job, displayed in monospace. Click to open the job detail page. |
| Provider | The source provider (for example, HuggingFace, S3, NGC, MLflow, Azure). |
| Type | The job type (for example, Import). |
| Model | The model name or identifier. |
| Org | The organization the job belongs to. |
| Status | Current job state: Pending, Running, Completed, Failed, or Cancelled. |
| Created | The date and time the job was created. |
| Duration | How long the job ran. |

Use the **Status** filter to narrow results. Click any row to open the job detail page.

### Cloud jobs

**Path:** Infrastructure > Operations > Jobs

The Cloud Jobs view shows bulk and long-running platform operations, such as EVE-OS updates, application deployments, policy changes, and tag updates applied across multiple nodes.

Each job row shows:

| Column | Description |
| - | - |
| Name | The job name. |
| Job | The action type (for example, Create, Delete, Update, Deploy, Purge, Reboot, Apply). |
| Type | The object type the job acted on (for example, Application, Node, Virtual Network, Volume). |
| Object | The specific resource the job operated on. |
| Status | Current state badge. |
| Tasks | A summary of per-task results within the job. |
| Created | When the job was created. |
| Finished | When the job completed. |
| Duration | Total job duration. |
| Created By | The user who triggered the job. |

Click any row to open the cloud job detail page, which shows the full task breakdown with per-task status (Accepted, Completed, Error, or No Action Required).

Use the **Status** and **Type** filters to narrow results, or search by name or object.

## Next Steps

> [card] [Application Instance Details](https://zededa.mintlify.site/new-ui/infrastructure-services/applications/app-instance-details.md)
>
> Enable logs access on an application instance.

> [card] [Node Details](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/node-details.md)
>
> View per-node resource utilization and recent events.

> [card] [Manage an Application Instance](https://zededa.mintlify.site/new-ui/infrastructure-services/applications/manage-an-application-instance.md)
>
> Trigger operations that appear in Cloud Jobs.
