Fortinet Community
HelpSign In
Unlock Exclusive Benefits
Join Our Community Today!
Join our community and post in the forum to earn your exclusive Summer Badge! Become a member today!
LOGIN/REGISTER CONTINUE AS A GUEST
  • Support Forum
  • Knowledge Base
    • Customer Service
    • Internal Article Nominations
    • FortiGate
    • FortiClient
    • FortiADC
    • FortiAIOps
    • FortiAnalyzer
    • FortiAP
    • FortiAuthenticator
    • FortiBridge
    • FortiCache
    • FortiCare Services
    • FortiCarrier
    • FortiCASB
    • FortiConverter
    • FortiCNP
    • FortiDAST
    • FortiData
    • FortiDDoS
    • FortiDB
    • FortiDNS
    • FortiDLP
    • FortiDeceptor
    • FortiDevice
    • FortiDevSec
    • FortiDirector
    • FortiEdgeCloud
    • FortiEDR
    • FortiEndpoint
    • FortiExtender
    • FortiGate Cloud
    • FortiGuard
    • FortiGuest
    • FortiHypervisor
    • FortiInsight
    • FortiIsolator
    • FortiMail
    • FortiManager
    • FortiMonitor
    • FortiNAC
    • FortiNAC-F
    • FortiNDR (on-premise)
    • FortiNDRCloud
    • FortiPAM
    • FortiPhish
    • FortiPortal
    • FortiPresence
    • FortiProxy
    • FortiRecon
    • FortiRecorder
    • FortiSRA
    • FortiSandbox
    • FortiSASE
    • FortiSASE Sovereign
    • FortiScan
    • FortiSIEM
    • FortiSOAR
    • FortiSwitch
    • FortiTester
    • FortiToken
    • FortiVoice
    • FortiWAN
    • FortiWeb
    • FortiAppSec Cloud
    • Lacework
    • Wireless Controller
    • RMA Information and Announcements
    • FortiCloud Products
    • ZTNA
    • 4D Documents
  • Community Groups
    • Agora
    • Engage Services
    • The EPSP Platform
    • The ETSP Platform
    • Finland
    • FortiCare Service Development
      • Discussions
      • Announcements
    • FortiGate-VM on Azure
      • Discussions & Onboarding Information
      • Technical Learning
    • FortiGate-VM on AWS
      • Discussions & Onboarding Information
      • Technical Learning
    • FortiGate CNF (All Marketplaces)
      • Getting Started Resources
      • Technical Learning
    • FortiWeb Cloud (All Marketplaces)
      • Getting Started Resources
      • Technical Learning
    • Fortinet for SAP
      • Discussions
      • Technical Learning
      • Knowledge Base
      • Idea Exchange
      • Events
    • FortiSIEM
      • Discussions
      • Blog
    • FortiSOAR
      • Discussions
      • Announcements
      • Idea Exchange
    • KCS
    • Lacework
      • Live security workshops
    • Super User
  • Blogs
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.
  • Fortinet Community
  • Knowledge Base
  • FortiAnalyzer
  • Technical Tip: How to improve FortiAnalyzer perfor...
Options
  • Subscribe to RSS Feed
  • Mark as New
  • Mark as Read
  • Bookmark
  • Subscribe
  • Printer Friendly Page
  • Report Inappropriate Content
acapalbo
acapalbo Staff
Staff

Created on ‎11-14-2022 05:13 AM Edited on ‎09-23-2025 10:18 PM By Community Manager Anthony_E

Article Id 229794

Technical Tip: How to improve FortiAnalyzer performances when FortiSIEM module is not needed

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:

  • Log View -> Fabric will be unavailable. Administrators will not be able to search logs across different device types.
  • Threat Hunting will be unavailable. Threat Hunting feature location across versions:
    • Version 7.2.x The Threat Hunting located under FortiSOC.

    • Versions 7.4.0 to 7.4.2: The feature was relocated to Incidents & Events.

    • Version 7.4.3 and later: Threat Hunting was moved to Log View -> Fabric.

    • Version 7.6.x Threat Hunting has been placed under Log View -> Logs.

  • Event Handlers using the SIEM logs will not be triggered.
  • Reports using the Normalized Logs type will be empty.
  • The handler and report for DarkSide and SolarWind will function partially.

 

To review the current licenses:

 

diagnose license list


Name Status Expiry Description
---------------------------------------------------------------------
PBDS No License N/A post breach detection
SCPC No License N/A cloud storage service
SOAR No License N/A SOAR and SIEM bundle service
FOAS No License N/A FAZ Outbreak Detection Service
ISSS No License N/A Industrial Security Service
FGSA No License N/A Security Rating Update

 

To verify if the FortiSIEM module is up and running, the following CLI command can be used:

 

diagnose test app siemagentd 2
FAZ SIEM: up [status enabled]
siemagentd:
uptime: 70 day 19:06:45, shm-ver: 247, shm-fazid-max: 6


To disable the FortiSIEM module, the following CLI command can be used:

 

config system global
(global) set disable-module siem
(global) end
DISABLE SIEM module
Do you want to continue? (y/n)y

 

Note:

Consider downtime since the below command will require a reboot.


diagnose siem remove database ALL   <----- Not available in v7.6.
Remove the entire SIEM database has been requested.
This operation will remove all data in the SIEM database and reset the database server.
This operation will reboot the device.
Do you want to continue? (y/n)y

 

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
Technical Tip: Integrate FortiAnalyzer and FortiSIEM

Labels:
  • FortiAnalyzer
  • FortiSIEM
10947
4 Kudos
Suggest New Article
Article Feedback
Contributors
  • acapalbo
    acapalbo
  • vraev
    vraev
  • basicnbb
    basicnbb
  • awasfi_FTNT
    awasfi_FTNT
  • Stephen_G
    Stephen_G
  • Jean-Philippe_P
    Jean-Philippe_P
  • Anthony_E
    Anthony_E
  • Nur
    Nur
  • mdeparisse_FTNT
    mdeparisse_FTNT
  • Melhadidi
    Melhadidi
  • tnesh
    tnesh
  • Chuk23
    Chuk23
  • Murat_Dadasoglu
    Murat_Dadasoglu
  • cmartinez1
    cmartinez1
  • markwarner
    markwarner
  • Debbie_FTNT
    Debbie_FTNT
  • coudard
    coudard
  • jitesh36
    jitesh36
fortinet
Broad. Integrated. Automated.

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.

Social Media
Security Research
  • Threat Research
  • FortiGuard Labs
  • Threat Map
  • Threat Briefs
  • Ransomware
  • Getting Started Resources
Company
  • About Us
  • Security Fabric
  • Exec. Mgmt
  • Careers
  • Certifications
  • Events
  • Industry Awards
  • Social Responsibility
News & Articles
  • News Releases
  • News Articles
  • Trademarks
Contact Us
  • Corporate
  • Community

Copyright 2025 Fortinet, Inc. All Rights Reserved.

  • Terms of Service
  • Privacy Policy
  • GDPR
  • Cookie Settings

You are leaving our website

You are leaving our site and we cannot be held responsible for the content of external websites

Stay Here Continue