4.2. Applications
The full list of monitored applications, and detailed observability data for each one.

Overview
The Applications menu shows every application OPENMARU Observability monitors, on one screen. An application is the basic unit of monitoring; in a Kubernetes environment that means a workload such as a Deployment, StatefulSet or DaemonSet.
Read each application's current state and headline metrics quickly, then click one to see its tabs — SLOs (service level objectives), CPU, memory, logs, distributed traces, profiling and more.
Click Applications in the left sidebar to reach this screen.
The application list
Screen layout
The top of the list screen carries the filters, the view toggle and the status legend, with the application list below.
| Area | Description |
|---|---|
| Top header | Page title, application filters (namespace, category, search) |
| View toggle | Switches between list view and card view |
| Status legend | Shows the application count per state, and filters by it |
| List area | List view: a table. Card view: a grid of cards |
| Pagination | Items per page (10, 20, 50, 100, All) and page navigation |
Status legend

The status legend in the toolbar at the top summarises every application by state.
| State | Meaning |
|---|---|
| SLO violation | The application has passed an SLO threshold. It needs immediate action. |
| Warning | The application is in a warning state and needs attention |
| Errors in logs | An error pattern was detected in the application's logs |
| Security threats | An attack pattern was detected against the application |
| Integration required | No agent connection, so no data is being collected for the application |
| OK | The application is running normally |
Click an entry in the status legend to filter down to applications in that state. Several states can be selected at once; the selected entries are highlighted and the rest dim. Click again to clear the filter.
Tip: check the count of applications in an SLO violation or warning state first, then click that state to concentrate on the ones with problems.
Main features
Filters
Use the filters at the top right to narrow the list by namespace, category and application name. Combine conditions to show only the applications you want.
Hiding applications
Temporary applications that appeared briefly through a misconfiguration (unknown_service, say), or applications you no longer want to see, can be hidden globally (a soft hide) to clear noise from the list and the topology map. A hidden application is not deleted; it is gathered on the Hidden applications screen and can be shown again at any time.
Node.js apps that PM2 runs (host mode)
On a VM, each Node.js app that PM2 runs shows as a separate application. This is true also when one PM2 daemon runs many apps.
- The application name has the format
<systemd unit>-<PM2 app name>. Example:pm2-ginet-cu119NEXT - CPU and memory limits do not show for each app. These values apply to the full systemd unit, so they show only on the PM2 daemon application.
- The node agent environment variable
TRACK_PM2_APPSturns this function on or off. The defaultautoturns it on for a VM and off for a Kubernetes pod. You can also settrueorfalse. - To exclude a systemd unit from the split, put the unit name in
PM2_SPLIT_DENYLIST. Use commas between names. Example:pm2-ginet.service
List view

Click the list icon in the view toggle at the left of the toolbar to switch to List view, which suits comparing many applications at once.
Click a column header to sort by it, and click several columns in turn to sort by more than one.
The main columns in list view are as follows.
| Column | Description |
|---|---|
| Application | The name and namespace. Click it to open the detail page. |
| Kind | The Kubernetes workload kind (Deployment, StatefulSet, DaemonSet and so on) |
| Type | The application's technology stack (Java, Python, Redis, Kafka, vLLM and so on) |
| Errors | The error rate against the SLO |
| Latency | The response time against the SLO. For a vLLM application, the value uses the time to first token (TTFT). Move the pointer onto the cell to see the tooltip "Based on time to first token (TTFT) p95" |
| Upstreams | How many upstream services this application calls |
| Instances | How many instances are running |
| Restarts | How many times instances have restarted |
| CPU | CPU usage |
| Memory | Memory usage |
| Disk I/O load | Disk I/O load |
| Disk usage | Disk usage |
| Network | Network state |
| DNS | DNS query state |
| Security | The number of attack types (SQLi, XSS and so on) that are detected now. It shows with a shield icon. Click it to go to the security tab of the detail page. If nothing is detected, the cell shows |