RAM Load Check Reference

All configuration fields, sampling parameters, and alert thresholds for the RAM Load check in octoja.

Written By Stefan Steuer

Last updated 28 days ago

Configuration options and output metrics for the RAM Load check.

The RAM Load check samples memory usage on the device over a short window and compares the result against percentage thresholds. The agent reports the average, the peak, the number of samples, and the device's total installed memory.

Configuration fields

Field	Type	Required	Default	Description
Sampling duration (seconds)	integer	Yes	5	Total time spent collecting RAM samples on each run. Clamped to 1–60
Sampling interval (ms)	integer	Yes	500	Time between individual RAM readings. Clamped to 100–5000
Evaluate against	choice (Peak / Average)	Yes	Peak	Whether the threshold check compares the peak sample or the average of all samples
Warning (%)	integer	Yes	80	Warning is raised when the selected value is at or above this percentage. Clamped to 0–100
Critical (%)	integer	Yes	95	Critical alert is raised when the selected value is at or above this percentage. Clamped to 0–100

Alert behaviour

Condition	Severity
Selected metric ≥ Critical threshold	Critical
Selected metric ≥ Warning threshold (and below Critical)	Warning
Selected metric below the Warning threshold	OK
No memory samples could be collected during the run	Warning, with the message "Unable to collect RAM samples"
An unexpected error occurred while the check was running	Error, with the error text shown in the check detail view

Metrics collected

Average memory usage over the sampling window (%)
Peak memory usage in any single sample (%)
Number of samples collected
Total installed memory (the check detail view shows it in GB)
The threshold metric used for the alert (Peak or Average)

Platform support

Platform	Supported
Windows	Yes
Linux	Yes
macOS	Yes

The check is available on all platforms and runs anywhere the agent can read memory usage from the operating system.

Notes

The check runs every 5 minutes on the agent. The check interval is not user-configurable.
If you set the Warning threshold higher than the Critical threshold by mistake, the agent automatically swaps them — the lower value is treated as Warning, the higher as Critical.
Total installed memory is reported once per run alongside the usage percentage, so you can see absolute consumption (e.g. 24% of 32 GB) at a glance in the check detail view.
Use the Peak evaluation metric for memory-leak detection — a single spike past the threshold fires the alert. Use Average for workloads that cache aggressively and tolerate brief peaks.

See also: Configure a RAM Load Check