Apache / Nginx support via the Vector agent
LogLens now ingests from any Linux web server running Apache or Nginx via the open-source Vector agent. Pick the platform in onboarding, get a pre-filled vector.yaml, install and you're done in under ten minutes.
Until today LogLens ingested via CloudFront, Cloudflare and Vercel — fine if you're behind a CDN, useless if you run a traditional VPS or dedicated box.
That changes today. Apache and Nginx are now first-class ingest sources using the open-source Vector agent from Datadog.
How it works on your side:
1. In the dashboard, add a new website and pick Apache / Nginx (Vector). 2. Choose nginx or apache, paste your access log path (we default to the usual place), click Generate config. 3. Run the install one-liner: curl --proto '=https' --tlsv1.2 -sSfL https://sh.vector.dev | bash. 4. Drop the downloaded vector.yaml into /etc/vector/ and sudo systemctl enable --now vector. 5. Click Test connection in the dashboard — events should appear within 30 seconds.
What you get:
- Real-time ingestion (5-second batches by default, configurable).
- Disk-buffered so a brief network blip or LogLens outage won't lose events — Vector queues to disk and flushes when we're back.
- Gzipped NDJSON to keep your bandwidth bill negligible.
- Per-site bearer token, generated once and revocable from the dashboard. Distinct from your read API key — a leaked ingest token can only write events for one site.
The same dashboard, alerts, SEO insights, AI helper and exports as every other source. Once events arrive past the ingest layer they're indistinguishable from CloudFront or Vercel traffic.
Full setup walkthrough and troubleshooting matrix at /help.html#apache-nginx-setup.