FortiAnalyzer
FortiAnalyzer can receive logs and Windows host events directly from endpoints connected to EMS, and you can use FortiAnalyzer to analyze the logs and run reports.
vraev
Staff
Staff
Article Id 362619
Description

 

This article describes how to review the performance information from CLI, API calls, and GUI from FortiAnalyzer and FortiManager.

 

Scope

 

FortiAnalyzer, FortiManager.

 

Solution

 

The FortiAnalyzer information regarding its performance can be gathered using the CLI, GUI, and API calls which is possible only in the latest versions (v7.6.x and above).

 

To review the performance information from the CLI use the following commands:

 

get system performance

CPU:

Used: 5.81%

Used(Excluded NICE): 5.81%

%used %user %nice %sys %idle %iowait %irq %softirq

CPU0 4.10 3.69 0.00 0.41 95.90 0.00 0.00 0.00

CPU1 3.43 1.61 0.00 1.81 96.57 0.00 0.00 0.00

CPU2 3.64 1.82 0.00 1.62 96.36 0.00 0.00 0.20

CPU3 3.80 1.00 0.00 0.60 96.20 0.00 0.00 2.20

CPU4 7.06 4.12 0.00 2.75 92.94 0.00 0.00 0.20

CPU5 13.03 11.41 0.00 1.63 86.97 0.00 0.00 0.00

Memory:

Total: 65,720,544 KB

Used: 10,745,632 KB 16.4%

Total (Excluding Swap): 32,860,388 KB

Used (Excluding Swap): 10,745,632 KB 32.7%

---------- output is truncated -----------

 

diagnose debug sysinfo

collecting information with interval=3 seconds…

---------- output is truncated -----------


=== resource use information ===

Program uses most memory: [/bin/initXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX], pid 1, size 1251m

Program uses most cpu: [/usr/bin/clickhouse-server], pid 27088, percent 25%

 

diag fortilogd lograte-total

 

Logs per second

Totals Last Hour Day Week

-------------------------------------------------------

: 363.29 360.64 97.54

 

execute top -d 2 -b -n 2 -i

top - 10:06:21 up 1 day, 21:50, 0 user, load average: 0.35, 0.35, 0.30

Tasks: 291 total, 1 running, 289 sleeping, 0 stopped, 1 zombie

%Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st

MiB Mem : 32090.2 total, 1036.0 free, 10453.4 used, 23096.9 buff/cache

MiB Swap: 32090.0 total, 32090.0 free, 0.0 used. 21636.8 avail Mem

 

PID USER PR NI VIRT RES %CPU %MEM TIME+ S COMMAND

16807 root 20 0 0.0m 0.0m 6.7 0.0 0:01.42 I [kworker/u12:4-flush-7:0]


Note: The top command will show twice only the active processes.

 

execute iotop -P -b -n 1

 

Note: iotop will show the processes based on their IO activity.

 

execute iotps -w -t 2


Note: Use this command to list system processes sorted by their read/write system call rate.

 

To review the performance information with an API call (from version 7.6 and above).


The API call:

 

{

"id": "string",

"jsonrpc": "2.0",

"method": "get",

"params": [

{

"apiver": 3,

"url": "/fazsys/monitor/system/performance/status"

}

],

"session": "'$APITOKEN'"

}

 

The API output:

 

{

"jsonrpc": "2.0",

"result": {

"status": {

"code": 0,

"message": "OK"

},

"data": {

"cpu": {

"cores": [

{

"user": 0.540541,

"system": 0.180180,

"nice": 0.000000,

"idle": 99.279279,

"iowait": 0.000000

},

{

"user": 0.713012,

"system": 1.426025,

"nice": 0.000000,

"idle": 97.860963,

"iowait": 0.000000

},

{

"user": 0.359066,

"system": 1.436266,

"nice": 0.000000,

"idle": 98.025135,

"iowait": 0.000000

},

{

"user": 1.610018,

"system": 1.788909,

"nice": 0.000000,

"idle": 96.601073,

"iowait": 0.000000

},

{

"user": 1.431127,

"system": 1.073345,

"nice": 0.000000,

"idle": 97.495528,

"iowait": 0.000000

},

{

"user": 0.713012,

"system": 0.891266,

"nice": 0.000000,

"idle": 98.395722,

"iowait": 0.000000

}

],

"used": 2.000597,

"used-excluded-nice": 2.000597

},

"mem": {

"total": 65720544,

"used": 8923668

},

"disk": {

"hard-disk": {

"total": 7689157108,

"used": 46912132,

"iostat-util": 1.010359

},

"flash-disk": {

"total": 1006252,

"used": 441932,

"iostat-util": 0.168980

}

},

"lograte": {

"last-5sec": 360,

"last-30sec": 360,

"last-60sec": 357

}

}

},

"id": "string"

}


To review the storage information from the GUI:


faz_gui_performance.png

 

faz_gui_performance1better.png

 

Troubleshooting:

 

The following commands can be used on the FortiManager/FortiAnalyzer CLI to debug the API Calls:

 

diagnose debug service httpd 255

diagnose debug service main 255

 

Related articles: