Resource Monitoring

MyOsicam collects resource readings from each managed server — CPU usage (%), memory consumption (MB), and disk usage (MB) — directly via the local agent. Readings are stored as timestamped snapshots so you can see whether a server is under stress at a glance. No external monitoring service is required.

What is measured

The agent reads the following metrics from the server OS on each collection cycle:

Metric	Source	Unit
CPU usage	/proc/{pid}/stat (OScam process)	Percentage (%)
RAM consumption	/proc/{pid}/status (OScam process)	Megabytes (MB)
Disk usage	OScam instance base directory	Megabytes (MB)

Readings are collected periodically by the agent and stored as timestamped snapshots on the panel’s resource_readings table.

Note

Resource readings require a running agent on the server. If the agent is stopped or the server is unreachable, new readings will not be collected until the agent reconnects and sends a heartbeat.

Viewing resource readings

Resource readings are displayed per install within the fleet view. To view them:

1. Log in to the panel.
2. In the left sidebar, click OSCam Installs.
3. Open the detail view for the install you want to inspect.

The readings panel shows the most recent values for CPU, RAM, and disk usage, along with a history of previous snapshots so you can spot trends over time.

Understanding the readings

CPU usage

CPU percentage represents the share of CPU time that the OScam process consumed during the measurement window. A value near 100% on a single-core VPS means OScam is consuming almost all available CPU. On a multi-core host, OScam can exceed 100% if it is using more than one core.

Tip

A consistently high CPU reading may indicate an unusual card-sharing load or a runaway OScam process. If CPU stays elevated and you are not under a known-high-traffic period, check your OScam logs for excessive connection attempts.

RAM consumption

RAM is shown in megabytes. OScam’s memory footprint is typically modest (tens of MB for most deployments), but can grow with large user and reader lists. The reading reflects the OScam process’s resident set size.

Disk usage

Disk usage reflects the size of the OScam instance’s base directory in megabytes. Unlike CPU and RAM, disk is collected regardless of whether the OScam process is running — a stopped install still reports its disk footprint. A growing disk reading over time can indicate accumulating log files in the base directory.

Agent requirements for monitoring

Resource monitoring is only available for installs managed by the Go agent. The agent must be:

• Installed and running as the myosicam-agent systemd service.
• Successfully registered with the panel.
• Sending regular heartbeats (visible as Online status in the fleet view).

If a server shows Unreachable, it means the agent has not sent a heartbeat recently and no fresh readings are available. See Troubleshooting / FAQ for steps to diagnose an unreachable agent.

Data retention

Resource readings are retained for at least 30 days. The panel’s audit-retention cron job prunes snapshots older than that automatically. See Operational Monitoring for full details on the retention policy and how to verify it in your panel’s cron log.

Related pages

• Install the Agent — required for resource monitoring to work.
• Fleet View — overview of all installs and their runtime status.
• Troubleshooting / FAQ — diagnose unreachable agents and connectivity issues.