Gateways
Learn what a Gateway is and how it acts as the high-performance edge proxy for all your telemetry data.
What is a Gateway?
A Gateway is a high-performance, stateless proxy server that you deploy inside your own infrastructure. It acts as the edge ingress point for all of your telemetry data, sitting between your data forwarders (like Vector, FluentBit, or Promtail) and your upstream destinations (like Datadog, Splunk, or Elasticsearch).
Gateways are horizontally scalable and pull their configuration down from the SRVANT Control Plane dynamically. This allows you to update routing logic and processing rules in real-time without ever needing to restart your Gateway instances or drop incoming traffic.
Payload Limits & OOM Protection
To ensure high availability and protect the Gateway from Out-Of-Memory (OOM) crashes, SRVANT imposes a strict 10MB limit on incoming request payloads.
Any HTTP request body exceeding 10MB will be immediately rejected with a 413 Payload Too Large response before any pipeline processing or metrics routing occurs. Please ensure your ingestion agents (e.g., Vector, FluentBit) are configured to batch events within this size constraint.
Parsing Optimization Guarantee
To ensure maximum throughput and perfect byte-for-byte fidelity, the proxy engine intelligently checks your pipeline's processors before unpacking any event frames. If a pipeline only contains read-only rules (e.g. filter_drop or sampling), the gateway skips the JSON or String deserialization and re-encoding steps entirely. It natively evaluates the rules and forwards the raw bytes untouched, achieving zero-overhead data routing.
Cost Reduction at the Edge
By dropping noise and sampling data before it leaves your VPC, the SRVANT Gateway significantly reduces your egress bandwidth and Datadog/Splunk ingestion costs. Customers typically see a 30-40% reduction in observability spend.