Skip to content

Latest commit

 

History

History
69 lines (49 loc) · 2.58 KB

GLOSSARY.md

File metadata and controls

69 lines (49 loc) · 2.58 KB

Plesk Scripts

Language for the standalone scripts that back up, clean, scan and monitor Plesk servers, and for how those scripts are released and kept up to date.

Language

Plesk

Subscription: The Plesk unit that owns a set of domains and runs its processes under one system user. It is the unit CPU load is attributed to. Avoid: Website, site, account, customer

Vhosts root: The directory under which Plesk keeps every subscription's files, by default /var/www/vhosts. Avoid: Web root, sites directory

Updating

Self-update: A script replacing itself with a newer published version, on request or automatically. Avoid: Auto-upgrade, patch

Gated update: A self-update that installs only a script published in a release and verified against that release's checksums. If verification fails, the current version is kept. Avoid: Safe update, signed update

Release: A dated, tagged snapshot of every script, published with checksums. It is the only source a self-update installs from. Avoid: Version, build, deploy

Platform parity: Keeping the Windows and Linux versions of a script in step. It applies only to scripts that already ship both versions, and the Windows version may be a documented subset. Avoid: Cross-platform support

Backups and retention

Retention: How long a backup is kept before it becomes eligible for deletion, with a minimum number of the newest backups per domain always kept. Avoid: Expiry, TTL

Dry run: A run that reports what would be deleted without deleting anything. Avoid: Preview mode, simulation

Monitoring

Sustained load: Server load that stays above the load threshold for at least 80% of samples across a 30-minute window. A brief spike is not sustained load. Avoid: High CPU, spike, load average

Load threshold: The load level, scaled by core count, above which a sample counts toward sustained load. Avoid: Limit, cutoff

Offender: An IP address responsible for attack-like traffic against a subscription, either because a fail2ban jail has banned it or because its request pattern looks like a bot scan or attack. Avoid: Attacker, bad IP

Banned offender: An offender currently in the banned list of any fail2ban jail except the SSH jail. Avoid: Blocked IP

Handled attack: An attack where banned offenders account for at least 80% of the attack traffic, so fail2ban is already containing it and no alert is needed. Avoid: Mitigated, resolved

Incident: One continuous period of sustained load, from the moment it is detected until load drops back below the threshold. Avoid: Event, outage