Skip to main content
asersemis
New Member
February 27, 2026
Solved

Can diagnose debug application output be forwarded externally? (FortiAnalyzer / syslog / API)

  • February 27, 2026
  • 2 replies
  • 306 views

Hi all,

 

We are building an automated pipeline to continuously collect SSL-VPN and IPSec debug logs from our FortiGate 90G devices, using:

diagnose debug application sslvpn -1
diagnose debug application fnbamd 8
diagnose debug enable

 

We specifically need the raw debug output (e.g. "SSL established: TLSv1.3 TLS_AES_256_GCM_SHA384") which is not present in structured logs and therefore not available via FortiAnalyzer or syslog.

 

We have already gone through the following KB articles:
• Continuous debug monitoring with Bash and Crontab:
https://community.fortinet.com/t5/FortiAnalyzer/Technical-Tip-Continuous-debug-monitoring-with-Bash-and-Crontab/ta-p/305973

 

• FortiGate remote monitoring and logging CLI command output into a file:
https://community.fortinet.com/t5/FortiGate/Configuration-Example-FortiGate-remote-monitoring-and-logging/ta-p/189892

 

Based on our research, it appears that the debug subsystem and the structured logging pipeline are architecturally separate, the raw output of diagnose debug application commands streams only to the active CLI session, with no native way to route it to FortiAnalyzer, syslog, or any REST API endpoint.

Our current workaround is an automated SSH capture script, which works but feels like it should not be necessary.

 

Our questions:
1. Is there any supported method in FortiOS (any version) to natively forward diagnose debug output to an external destination?
2. Is there any roadmap for this capability?
3. Has anyone found a more elegant solution than SSH capture?

 

Thanks in advance.

Best answer by akileshc

Hello Asersemis,

 

Currently, FortiOS does not provide a built-in way to forward the raw output of `diagnose debug` commands directly to external systems such as FortiAnalyzer, syslog, or REST API endpoints. Debug output is intended for real-time viewing through the CLI, and there is no native mechanism to redirect it externally.

 

The workaround you are using—an automated SSH capture script—is a commonly adopted approach to collect debug output. While it may feel cumbersome, it remains one of the most effective methods to automate debug log collection.

 

Reference:
[Technical Tip: Debug Flow Tool]
(https://community.fortinet.com/t5/FortiGate/Technical-Tip-Debug-flow-tool/ta-p/213238)

 

Regards,

2 replies

akileshc
Staff
akileshcAnswer
Staff
February 27, 2026

Hello Asersemis,

 

Currently, FortiOS does not provide a built-in way to forward the raw output of `diagnose debug` commands directly to external systems such as FortiAnalyzer, syslog, or REST API endpoints. Debug output is intended for real-time viewing through the CLI, and there is no native mechanism to redirect it externally.

 

The workaround you are using—an automated SSH capture script—is a commonly adopted approach to collect debug output. While it may feel cumbersome, it remains one of the most effective methods to automate debug log collection.

 

Reference:
[Technical Tip: Debug Flow Tool]
(https://community.fortinet.com/t5/FortiGate/Technical-Tip-Debug-flow-tool/ta-p/213238)

 

Regards,

asersemis
asersemisAuthor
New Member
March 2, 2026

Thank you for your response!

Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!