A collector with high cpu usage. It's reporting, procs are up.. the stop start seems to be very short in duration what is it actually doing?
Thanks
Solved! Go to Solution.
Hi @KarlH,
We've seen this behavior on Collectors that have not enough resources for the amount of logs. In case of a VM, try to give it more RAM, CPU or a better drive (SSD, in case you're using HDD). Or use multiple Collectors instead of a single one to distribute the load.
Best,
Christian
Hi @KarlH ,
Looks like the processes are crashing and recovering on its own.
You would need to check which process #phstatus and probe further on the error. Especially check for unknown events and events with large length/volume.
Ok thank you Prem!
Hi @KarlH,
We've seen this behavior on Collectors that have not enough resources for the amount of logs. In case of a VM, try to give it more RAM, CPU or a better drive (SSD, in case you're using HDD). Or use multiple Collectors instead of a single one to distribute the load.
Best,
Christian
Will do thank you Christian!
Welcome to your new Fortinet Community!
You'll find your previous forum posts under "Forums"
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.