The Disk Management page shows the quota, usage, and fill level of the live log (a column-oriented ClickHouse database) and the signed archive disk separately. A "Recommended Space" card, calculated from your last 7 days' real event rate, lets you spot disk space that will fall short of your retention period before it happens.
Every log is written simultaneously to live storage (a fast-search database, kept for the period you set) and to the archive (a file system); total retention is the larger of the two. Disk Management presents these two areas with separate quota/usage/fill-level gauges.
The required GB is calculated by multiplying your last 7 days' real event rate by your configured retention days and adding a 20% margin; if the allocated space is insufficient, the "Increase Space" button in the cloud takes you to your izgate.com account page.
On İzHost Cloud, you split your total quota between live and archive yourself (default suggestion 30%/70%); the live share must be at least 10 GB.
In an on-premises deployment, the panel shows the fill level of the actual disk paths; separate disks for /log and /archive are required during installation (install.sh stops the install if there isn't a separate disk). Disk growth is not done from the panel; it is performed manually on the server.
Live and archive retention periods are set in parallel and independently of each other in settings. Archive pruning cannot be undone, and only removes segments entirely outside the retention window, older than the cutoff date.
Check the total purchased disk, used space, and fill-level percentage from the cards at the top.
Compare the recommended GB — calculated from the last 7 days' event rate for live and archive — with the allocated space.
In the cloud, insufficient space is grown via "Increase Space" from your izgate.com account page; on-premises, it's grown by adding a new disk to the server.
/log and /archive are required in an on-premises deployment; install.sh stops the installation if it doesn't find a separate disk.Your last 7 days' real event rate is multiplied by your configured retention days, and a 20% margin is added; it's calculated separately for live and archive.
No, no record is deleted because of fill level. Archive pruning only clears segments that have fully exceeded the configured retention period; this action cannot be undone.
No. In an on-premises deployment, disk growth is done manually on the server; in the cloud, the total quota is set by your plan and an increase is requested from your izgate.com account page.
The live log is designed for fast search, while the archive is designed for long-term, Law No. 5651–compliant retention; in an on-premises deployment, /log and /archive must be on separate disks.
Yes, on İzHost Cloud you can split your total quota between live and archive yourself; the default suggestion is 30%/70%, and the live share must be at least 10 GB.
Configure izgate Cloud based on your number of firewall devices and storage needs; no setup, get started in minutes. Call us with any questions.