Send to the systems you need
CyberStitch implements HTTP, syslog, Kafka, Amazon S3, Azure Blob Storage, Azure Event Hubs, Google Cloud Storage, SSH/SFTP, local file, and CyberStitch-to-CyberStitch destinations.
Splunk is an example of a downstream HTTP integration, not a separate native sink. A Splunk HEC deployment requires compatible payload formatting and authentication; validate the chosen configuration before relying on it.
Choose the records that leave
An output stream selects records for delivery. Configure the destination, credentials, format, and egress policy to match the intended workflow. Keep sensitive data local unless you explicitly intend to send it.
Track delivery and backlogs
Records spool durably and are delivered in batches. Retry and overflow policies make unavailable destinations visible to operators.
Delivery guarantees depend on the destination and policy. UDP syslog, for example, cannot provide the same acknowledgments as an authenticated record transfer. Choose those tradeoffs deliberately.
Complete the operational loop
Inspect delivery status and execution history instead of assuming that a configured destination received its data. Use downstream systems for the workflows they already serve.