Description | This article describes how to mitigate the FortiAnalyzer high CPU usage when the FortiSIEM module is enabled but not used. |
Scope | FortiAnalyzer v6.4+. |
Solution |
In v6.4, the FortiSIEM database is introduced, and it consumes resources that may affect performance (i.e. CPU usage can significantly increase when the FortiSIEM module feature is enabled). It is also necessary to adjust the resources based on MEA accordingly if required: Management extension applications To improve FortiAnalyzer performance, it is recommended to disable the FortiSIEM module, keeping in mind that if disabled:
To review the current licenses:
diagnose license list
To verify if the FortiSIEM module is up and running, the following CLI command can be used:
diagnose test app siemagentd 2
config system global
Note: Consider downtime since the below command will require a reboot.
The following command can be used to enable/disable the FortiSIEM module in hardware models:
diagnose siem module-ctrl {enable | disable}
The following command can be used to start/stop the FortiSIEM module in VM-based units:
diagnose siem service {start | stop}
To stop the daemon process of FortiSIEM:
diagnose test application siemagentd 99 diagnose test application siemdbd 99
FortiAnalyzer's SIEM module-related CLI reference: FortiAnalyzer 7.6.0 CLI Reference SIEM.
Note: As prompted above, FortiAnalyzer must be reloaded to make the change effective.
Related articles: Technical Tip: How to gather information and fix high CPU and Mem utilization conditions Technical Tip: Backup and restore of FortiAnalyzer settings, logs and reports |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.