This article addresses an issue where using an FQDN as the host in the security log configuration prevents logs from being successfully sent to an external syslog server.
> show configuration security logutc-timestamp; mode stream; format sd-syslog; source-interface ge-0/0/1.0; stream sd-cloud-logs { category all; host { <Hostname>----------> hostname causing the issue port 6514; } transport { division line-based; protocol tls; tls-profile syslog-profile; } }
This is a known issue, and the fix is available in the below versions.
Please refer to PR1708116.