Description
This article will provide ways to review the storage information of FortiAnalyzer from GUI, API, and CLI.
Scope
FortiAnalyzer, FortiManager.
Solution
To review the storage information from the CLI use the following commands:
get system performance
--- partial output ---
Hard Disk:
Total: 81,983,896 KB
Used: 7,828,200 KB 9.5%
Inode-Total: 5,242,880
Inode-Used: 61,034 1.2%
IOStat: tps r_tps w_tps r_kB/s w_kB/s queue wait_ms svc_ms %util sampling_sec
25.8 0.2 25.6 0.9 570.2 0.1 4.5 0.5 1.2 8.75
diagnose system print partitions
major minor #blocks name fstype
--- partial output ---
254 0 4199424 vda
254 1 1048576 vda1 ext3
254 16 83886080 vdb
diagnose system print df -h
Filesystem Size Used Available Use% Mounted on
--- partial output ---
/dev/vda1 982.7M 489.5M 493.2M 50% /data
/dev/mdvg/mdlv 78.2G 7.5G 70.7G 10% /var
/dev/mdvg/mdlv 78.2G 7.5G 70.7G 10% /drive0
/dev/mdvg/mdlv 78.2G 7.5G 70.7G 10% /Storage
diagnose log device
Device Name Device ID Used Space(logs / quarantine / content / IPS) Allocated Space Used%
rhodium-fmgfaz-kvm01 FGVxxx 118.0MB( 118.0MB/ 0.0KB/ 0.0KB/ 0.0KB) unlimited n/a
rhodium-fmgfaz-kvm21 FGVxxx 128.2MB( 128.2MB/ 0.0KB/ 0.0KB/ 0.0KB) unlimited n/a
Total: 2 log devices, used=246.2MB quota=unlimited
AdomName AdomOID Type Logs Database
[Retention Quota Used( logs/quaranti/ content/ IPS) Used%] [Retention Quota Used( SiemDB/ hcache) Used%]
root 3 FSF 365days 15.0GB 246.3MB( 246.3MB/ 0.0KB/ 0.0KB/ 0.0KB) 1.6% 60days 35.0GB 493.3MB( 491.7MB/ 0.0KB) 1.4%
Total usage: 1 ADOMs, logs=246.3MB(246.3MB/0.0KB/0.0KB/0.0KB) database=596.4MB(ADOMs usage:493.3MB(491.7MB, 0.0KB) + Internal Usage:103.1MB)
Total Quota Summary:
Total Quota Allocated Available Allocate%
55.4GB 50.0GB 5.4GB 90.3%
System Storage Summary:
Total Used Available Use%
78.2GB 7.5GB 70.7GB 9.6 %
Reserved space: 22.8GB (29.2% of total space, system reserved: 15.0GB, Fabric Storage pool disk quota: 7.8GB).
VM-specific commands:
execute lvm info
LVM Status: OK
LVM Size: 80GB
File System: ext4 78GB
Disk1 : Used 80GB
Disk2 : Unavailable 0GB
execute lvm extend
execute lvm hwinfo
HW models specific commands:
diagnose system raid cc <rate> <delay>
diagnose system raid hwinfo
diagnose system raid status
diagnose system raid status
Storcli RAID:
RAID Level: Raid-10
RAID Status: OK
RAID Size: 7451GB
File System: ext4 7333GB
Groups: 2
Disk 1: OK 3724GB Group-1
Disk 2: OK 3724GB Group-1
Disk 3: OK 3724GB Group-2
Disk 4: OK 3724GB Group-2
To review the current files on the HDD:
diagnose system disk ?
delete Delete disk file.
usage Display disk usage.
HW models specific options:
attributes Show vendor-specific SMART attributes.
disable Disable SMART support.
enable Enable SMART support.
errors Display SMART error logs.
health Show SMART health status.
info Display SMART info.
To erase a disk:
execute format <disk | disk-ext3 | disk-ext4> <RAID level> deep-erase <erase-times>
To review the storage information with an API call (from version 7.6 and above).
The API call:
{
"jsonrpc": "2.0",
"method": "get",
"params": [
{
"apiver": 3,
"url": "/fazsys/storage-info"
}
],
"session": "'$APITOKEN'"
}
The API output:
{
"jsonrpc": "2.0",
"result": {
"data": [
{
"adomname": "root",
"analytics-actual-days": "2",
"analytics-config-days": "60",
"archive-actual-days": "2",
"archive-config-days": "365",
"max-storage": "53687091200",
"analytics-storage-usage": "499130437",
"analytics-storage-max": "37580963840",
"archive-storage-usage": "331755352",
"archive-storage-max": "16106127360"
},
],
"status": {
"code": 0,
"message": "ok"
}
}
}
To review the use of the storage space during some specific time, use the following API call:
{
"id": "123",
"jsonrpc": "2.0",
"method": "get",
"params": [
{
"apiver": 3,
"time-range": {
"end": "2024-11-15T11:57:03.015Z",
"start": "2024-11-13T11:57:03.015Z"
},
"url": "/fazsys/adom/root/storage-info-history"
}
],
"session": "'$APITOKEN'"
}
The output from the API call:
{
"jsonrpc": "2.0",
"result": {
"data": [
{
"adomname": "root",
"timestamp": "1731495600",
"analytics-actual-days": "0",
"analytics-config-days": "60",
"archive-actual-days": "0",
"archive-config-days": "365",
"max-storage": "53687091200",
"analytics-storage-usage": "7819795",
"analytics-storage-max": "37580963840",
"archive-storage-usage": "7383985",
"archive-storage-max": "16106127360"
},
---------- output is truncated -----------
{
"adomname": "root",
"timestamp": "1731585600",
"analytics-actual-days": "1",
"analytics-config-days": "60",
"archive-actual-days": "1",
"archive-config-days": "365",
"max-storage": "53687091200",
"analytics-storage-usage": "272392671",
"analytics-storage-max": "37580963840",
"archive-storage-usage": "260893416",
"archive-storage-max": "16106127360"
},
---------- output is truncated -----------
{
"adomname": "root",
"timestamp": "1731664800",
"analytics-actual-days": "2",
"analytics-config-days": "60",
"archive-actual-days": "2",
"archive-config-days": "365",
"max-storage": "53687091200",
"analytics-storage-usage": "499130437",
"analytics-storage-max": "37580963840",
"archive-storage-usage": "331755352",
"archive-storage-max": "16106127360"
}
],
"status": {
"code": 0,
"message": "ok"
}
},
"id": "123"
}
Note: The output is in bytes.
To review the storage information from the GUI:
Note: If the RAID setting is changed, all data will be deleted!
Related articles:
Technical Tip: How to estimate disk space needed for Archive and Analytics logs
Technical Tip: Extending disk space in FortiAnalyzer-VM/FortiManager-VM
Technical Tip: Adding/extending additional disk under a KVM/QEMU environment to FortiManager and For...
Technical Tip: Performance info from CLI, GUI and API call of FortiAnalyzer and FortiManager
