April 17, 2026
7 min read time

Varnish Software and Hydrolix Integration

Building a High-Throughput Observability Pipeline for CDN Traffic

For teams running large-scale CDNs, visibility is just as critical as performance. While Varnish Software Enterprise delivers industry-leading caching and edge acceleration, observability at scale requires a backend capable of ingesting and analyzing massive log streams in real time.

This is where Hydrolix comes in.

Hydrolix is purpose-built for high-cardinality, high-volume event data, making it an ideal match for Varnish-generated logs. Together, they enable a powerful observability pipeline that transforms edge traffic into real-time, actionable insights.

This integration is available for both Varnish Enterprise and Ora Streaming customers:

  • Varnish Enterprise users can follow the step-by-step guide below to deploy and configure the integration.

  • Ora Streaming customers can leverage the same integration capabilities by reaching out to their account manager at Varnish Software or Hydrolix to get started.

The following guide walks through a working implementation and shows how to quickly set up a high-throughput logging and analytics pipeline.

Why This Integration Matters

Dealing with massive scale makes traditional CDN observability challenging. The Varnish Enterprise and Hydrolix integration directly addresses these hurdles, which include:

  • Immense Data Volume: Processing millions of requests per second.

  • High-Cardinality Data: Analyzing fields like IP addresses, ASNs, URLs, and user agents.

  • Need for Speed: Demanding near real-time insights.

Key Benefits of the Integration

The joint solution offers four essential advantages:

Benefit How it helps
Instant Performance Insights Get real-time data on critical metrics like cache hit/miss ratios, latency, and request patterns.
Optimized Log Storage Hydrolix efficiently compresses and stores logs, leading to substantial reductions in traditional logging infrastructure costs.
Powerful High-Cardinality Analysis Perform deep dives and break down traffic by geography, ASN, path, or user agent without performance bottlenecks.
Minimal Data Pipeline Burden Utilize Vector as a lightweight and reliable log forwarder with built-in data transformation, ensuring low overhead.

Architecture Overview

The pipeline looks like this:

VE + Hydrolix Architecture (1200 x 800 px)-1

Step-by-Step Setup

1. Install Varnish Enterprise(if you do not have it up and running already)

To use Varnish Software Enterprise, you need a valid license. If you do not already have one, please contact sales@varnishsoftware.com to request access.

If you already have a license, you can follow the official installation and getting started guide here: docs.varnish-software.com/varnish-enterprise

For this integration to work you would also need to:

1. Install additional VMODs:

sudo apt-get install varnish-plus-vmods-extra

2. Install MMDB databases (GeoIP) before starting Varnish to enable geo-enrichment in logs.

2. Enable Hydrolix-Aware VCL

Your VCL should include:

include "hydrolix.vcl";

This VCL layer enriches logs with metadata such as:

  • Client IP

  • ASN

  • Country and city

  • Edge node information

These fields are later parsed and indexed in Hydrolix.

3. Install Vector

Run the provided install script:

sudo bash ./install-vector.sh

This will:

  • Install Vector

  • Deploy a preconfigured pipeline

  • Set up log ingestion from: /var/log/varnish/varnishncsa.log

4. Configure Structured Logging (varnishncsa)

Start logging using a JSON format:

varnishncsa -f hdx-varnish.txt -bc -w /var/log/varnish/varnishncsa.log

This:

  • Runs varnishncsa as a systemd service

  • Outputs structured JSON logs

  • Uses the hdx-varnish.txt file format which is completely configurable.

To monitor logs:

tail -f /var/log/varnish/varnishncsa.log

5. Start Vector Pipeline

Run vector:

vector --config varnish-hydrolix.toml

What Vector Does

  • Reads log file input

  • Parses JSON

  • Sends output to:

    • stdout (for debugging)

    • Hydrolix (for ingestion)

Vector varnish-hydrolix.toml config is available at this link. You will need to:

  1. Insert the correct ingest URL for Hydrolix, under [sinks.hydrolix]
  2. Insert your Authorization header, under [sinks.hydrolix.request.headers]

All is now setup up and you should see logs flowing into Hydrolix and being available via Grafana, similar to this one:

unnamed-4

 

Scalable, Real-time Observability

With this setup in place, you now have a scalable, real-time observability pipeline for your CDN traffic, combining the performance of Varnish Software with the analytics power of Hydrolix.

If you encounter any challenges, reach out to support@varnish-software.com for technical assistance or sales@varnish-software.com for commercial enablement.