Skip to content
Klacos
Logs and exports

Export access logs and traffic data to the tools you already use

A dashboard answers the questions its vendor thought of, rarely all of yours. With Klacos, whatever passes in front of your site can leave the console: access logs and metrics in standard formats, CSV exports, a read API, and your old logs imported so you keep your history.

Illustration: a cylindrical storage unit surrounded by clouds.
The problem

Data locked inside a dashboard

Your questions often need more than a dashboard offers: combining traffic with your sales, feeding your monitoring, building a report your own way, or keeping a record of what happened before the tool arrived.

When data stays locked in, figures get copied by hand, reports get rebuilt every month, and your history starts again from zero the day you switch service.

What you should expect: formats your tools already read, a stable API, and a history that doesn’t vanish with your old tool.

Illustration: a server rack surrounded by devices and dials.
What you get

Four ways to take your data with you

Logs and metrics

A JSON access log, to switch on if you process it yourself, and metrics in the standard format monitoring tools read.

CSV exports

A single breakdown of up to 5,000 rows, or the full view with its comparison period and filters.

A read API

The same figures as the console, through a versioned API, read with a narrowly scoped key.

Your history

Import your old nginx, Traefik or Caddy logs into the Traffic view.

If you run Klacos on your own servers, the access log never leaves the machine and your monitoring tools read the metrics right there: the page on running it on your own servers sets out what stays with you.

The API

One API, the same one the console uses

The console reads its figures through the read API, so anything you see on screen can also be read by a program. The API is versioned, so your scripts don’t break every time it changes.

Each API key has a limited scope: reading figures, maintaining your allowlists or labelling visits. Its secret is shown once, and it can be revoked at any time. Who creates keys, and with which rights, follows your team’s roles, covered on the page about sharing and team access.

Illustration: a large checkpoint gantry between two buildings, over an access road.
History

Don’t start from scratch

Klacos counts from the day it goes in front of your site. To keep a record of what came before, import your old web server logs (nginx, Traefik, Caddy and the common log format) into traffic analysis. They fill in the curve of your requests; they don’t enter your human audience, which is measured from the day the service is in place.

Logs and exports are part of the analytics capabilities in Klacos.

Questions

Questions about logs and exports

Can I export raw events?

No. Exports cover aggregated figures, by breakdown or for a full view. The API returns the same aggregates as the console.

Do imported logs count towards my audience figures?

No. They feed the Traffic view. Your human audience is measured from the day the service is in place.

Which formats?

CSV for exports, JSON for the access log and the API, and the standard format of monitoring tools for metrics.

Who can read the API?

A key created for your account, with a limited scope. Its secret is shown once, and it can be revoked at any time.

Opening early 2027

Stay in control of your traffic data

Request early access, or tell us which tools you want to see your traffic in.