Splunk Enterprise can forward events to another syslog server. Neither Splunk Cloud Platform nor the universal forwarder has the capability to forward events to another syslog server. The follow section applies to Splunk Enterprise only. How Splunk Enterprise handles syslog outputs It does, however, prepend a host name and timestamp to the event unless you configure it not to. If you send syslog data over TCP, the platform does not strip priority information from the events. The Splunk platform does not modify Transmission Control Protocol (TCP) network packets in this fashion. When you configure a universal forwarder to send data to Splunk Cloud Platform, Splunk Cloud Platform indexes the fields as it receives them from the universal forwarder. The platform prepends these fields to each event before it indexes them. When you configure a UDP network input to listen to a syslog-standard data stream on Splunk Enterprise or the universal forwarder, any syslog events that arrive through the input receive a timestamp and connected host field. How the Splunk platform handles syslog inputs Splunk Cloud Platform cannot send syslog messages, nor can it move messages from one device to another. Splunk Enterprise can also act as a syslog message sender. Splunk Enterprise indexers can act as syslog servers that handle incoming data streams that comply with the syslog messaging standard. If you run Splunk Cloud Platform, you can configure the Splunk universal forwarder to listen on a User Datagram Protocol (UDP) network port and forward that data to your Splunk Cloud Platform deployment. How the Splunk platform handles syslog data over the UDP network protocol