Edge Processor helps Splunk customers process data closer to the source: filtering, transforming, masking, and routing data before it reaches its final destination. For many production ingestion paths, especially those using Splunk forwarders, processing flexibility is only half of the story. Customers also need confidence that data has been durably received before it moves on. This is where Splunk-to-Splunk acknowledgement, or S2S ACK, comes in.
S2S ACK is now available in Controlled Availability for Edge Processor-on-Cloud as an opt-in capability for supported Splunk-to-Splunk connections (release note). This applies to all deployment models of Edge Processor with a Cloud control plane (standalone EPs, containerized EPs, K8s-based EPs, hybrid mode). It helps provide at-least-once delivery behavior across forwarding paths that include Edge Processor, giving customers a stronger reliability model for data flows where delivery assurance matters.
Figure 1: S2S Acknowledgements empower you with stronger data path reliability , end-to-end confidence, and the flexibility to enable regardless of which mode your Edge Processor is deployed in.
Why This Matters
Many customers rely on Splunk forwarders for security, compliance, audit, and operational data. In those environments, ingestion reliability is critical. Network interruptions, temporary destination issues, or downstream backpressure can happen, and customers need ingestion architecture that can respond predictably.
With S2S ACK enabled, a sender does not consider a batch delivered until the receiving side confirms receipt. If acknowledgement is not received, the sender can retry. This helps customers preserve familiar Splunk forwarding reliability patterns while introducing Edge Processor into the data path.
For customers adopting Edge Processor in standalone or hybrid deployments, S2S ACK closes an important delivery-guarantee gap for S2S protocol flows.
Figure 2: Enable S2S Acknowledgements within individual Edge Processor S2S destination config modals.
What S2S ACK Enables
With S2S ACK support, customers can:
Configure acknowledgement for supported S2S receiver and exporter flows.
Use Edge Processor in forwarding paths that require stronger delivery assurance.
Preserve at-least-once delivery expectations across supported data paths.
Monitor acknowledgement health, latency, queue growth, and backpressure.
Diagnose whether issues are occurring upstream, inside Edge Processor, or downstream at the destination.
Adopt Edge Processor more confidently in production ingestion architectures.
How It Works
S2S ACK must be enabled across the relevant data path.
For incoming data, upstream forwarding clients must be configured to use ACK in their applicable tcpout settings. Edge Processor then acknowledges data after it has been accepted into the downstream durable path.
For outgoing data, customers can enable Indexer acknowledgement on each applicable S2S destination within the Data Management UI. When enabled, Edge Processor tracks sent batches and waits for acknowledgement from the downstream destination before releasing them from its persistent queue.
This creates a more reliable forwarding path: upstream senders receive acknowledgement only after Edge Processor has durably accepted the data, and Edge Processor retains outbound data until the downstream destination confirms receipt.
How Customers Verify It
After enabling S2S ACK, you can send representative data through the complete path and verify acknowledgement metrics in the _metrics index with the edge-metrics source type.
Useful receiver-side signals include:
ingress_ack_sent_total: confirms ACKs are being sent upstream.
ingress_ack_failed_total: should remain at zero.
ingress_ack_channel_timeout_total: can indicate acknowledgement backpressure.
ingress_ack_pending_backlog: can indicate ACKs are not draining back to the forwarder.
Useful exporter-side signals include:
egress_ack_pending_batches: shows batches awaiting downstream ACK.
egress_ack_latency_seconds: tracks downstream ACK round-trip latency.
egress_ack_dropped_total: should remain at zero.
You can also monitor queue usage by comparing queue_size_bytes with queue_max_bytes. If queue usage approaches capacity, investigate destination availability, ACK latency, and downstream backpressure before the queue fills.
Important Operational Considerations
S2S ACK improves delivery assurance, but it does not remove the need for capacity planning and operational validation.
Because ACK can keep data in flight longer, it can increase memory usage for outbound queues. It can also result in duplicate events if a sender retransmits data that was received but not acknowledged before a timeout, restart, or shutdown-drain window expires. This is consistent with at-least-once delivery behavior: the system prioritizes avoiding data loss, and customers should plan for possible duplicates downstream.
It is also important to understand the ACK boundary. On the receiver side, Edge Processor acknowledgement means the data has been durably accepted by Edge Processor. On the exporter side, ACK means Edge Processor retains data until the downstream destination acknowledges receipt.
While S2S ACK provides at least once delivery on the defined boundary, Edge Processor does not provide exactly once delivery. Edge Processor might occasionally redeliver data resulting in duplicates.
Customers should validate S2S ACK with a representative workload before broad rollout, especially in high-volume environments or ingestion paths with strict reliability requirements.
Getting Started
To get started:
Since this is in controlled availability, reach out to
[email protected] to enable this feature.
After receiving confirmation that the feature is enabled, set useAck=true on upstream forwarding clients.
Enable Indexer acknowledgement for applicable S2S destinations with the Edge Processor / Data Management UI.
Restart changed components (Forwarders, Edge Processors).
Send representative data through the full path.
Verify acknowledgement, latency, and queue metrics.
For detailed setup steps, see the Splunk documentation for configuring Edge Processor to use acknowledgement with Splunk forwarders.
Bottom Line
For teams modernizing Splunk ingestion architecture, this is an important step: Edge Processor can now participate in more reliability-sensitive data paths while giving administrators the metrics and controls they need to operate with confidence.
Want first dibs on fresh content? Follow this quick guide to subscribe and get updates instantly.
... View more