Folder Size Check Reference

All parameters, thresholds, and configuration options for the folder size check in octoja.

Written By Erdinc Akay

Last updated About 2 months ago

Folder Size Check Reference

The Folder Size Check measures the total size of specific directories and alerts when the size reaches or exceeds the configured thresholds.

Configuration fields

FieldTypeRequiredDefaultDescription
Folders to monitorListYesOne or more directories, each with path and thresholds
— Folder pathStringYesAbsolute directory path
— Warning threshold (GB)NumberNo50Size in GB that triggers a warning
— Critical threshold (GB)NumberNo100Size in GB that triggers a critical result
Include subdirectoriesBooleanNoYesInclude all files in subdirectories

Execution cadence

The check runs every 60 minutes (hourly). The cadence is declared by the check itself and is not exposed as a per-instance configuration field.

Collected metrics

  • Size per monitored folder (GB and bytes) — there is no aggregate total across folders
  • File count per folder
  • Per-folder count of files that could not be read (access denied) — surfaced in the result detail as "N files inaccessible (access denied)"
  • Per-folder result status and any error message recorded while scanning

Result statuses

Each folder is evaluated on its own; the overall check result is the worst per-folder result.

SituationPer-folder result
Size below the warning thresholdOK
Size reaches or exceeds the warning / critical thresholdWarning / Critical
Folder path does not existCritical, with the error "Directory not found" (dir-not-found)
No file in the folder could be readThe error "Access denied to all files" (access-denied) is recorded; the measured size is 0, so the result follows the thresholds (usually OK)
Unexpected error while scanningFailure

Platform support

PlatformSupported
WindowsYes
LinuxYes
macOSYes

Notes

  • The check calculates the size by summing all file sizes in the directory tree. For directories with millions of files, execution may be slower.
  • The agent process must have read permission for the directory and its contents.
  • If the warning threshold is set higher than the critical threshold, the agent silently swaps the two values before evaluating — a misconfigured pair still produces useful results, but the configuration screen is the source of truth, not the alert payload.
  • If no folders are configured, the check reports Warning (not Failure and not OK) to surface the empty configuration without raising an incident.
  • Symbolic-link traversal follows .NET DirectoryInfo defaults and is not explicitly enabled or disabled by the check. Behaviour can differ between Windows, Linux, and macOS — if symlinks under a monitored path may point to large external directories, validate the resulting total against your expectation.

See also: Configure a Folder Size Check