Skip to main content
Talk to SalesGet Started
Talk to Sales
Get Started

[Edgesight · Logpush]

Your CDN logs,in your storage.

Real-Time Logpush delivers every request your Medianova CDN serves to Stook, Amazon S3, S3-compatible storage, Elasticsearch or an HTTP/S endpoint, compressed, every five minutes. No manual exports.

Talk to salesSee how it works
Source
Medianova CDN
Logpush
batch · compress · deliver
Stook
Amazon S3
S3-compatible
Elasticsearch
HTTP/S

Logpush in numbers

Batch window: a batch leaves every five minutes, or sooner at the size limit
5 min
Destination types: Stook, Amazon S3, S3-compatible, Elasticsearch and HTTP/S
5
Batch size limit for storage destinations; 5 MB for HTTP delivery
50 MB
One JSON record per line, Gzip-compressed (.txt.gz)
JSONL

FEATURES

Logs leave the edge and land where you keep them

For teams who already have a bucket, a cluster or an endpoint, and want their CDN logs there without exporting them by hand.

FULL LOGS

Every request the CDN serves

Each HTTP request and response, with its request, cache and network metrics. The complete record, not a summary.

AUTOMATED

Pushed, not downloaded

Once a job is set up, batches keep arriving on their own. No manual exports, no files to fetch at the end of the day.

BATCHED

Every five minutes, or sooner

A batch leaves every five minutes or as soon as it reaches the size limit: 5 MB for HTTP delivery, 50 MB for storage. Near real time, without a request per log line.

COMPACT

JSON Lines, Gzip-compressed

One JSON record per line, compressed as .txt.gz. Easy to parse, small to store, quick to move.

DESTINATIONS

Five places a job can land

The destinations the docs list today. You verify the connection before the job is created.

Stook

Medianova’s own object storage.

Amazon S3

Deliver batches to an Amazon S3 bucket.

S3-compatible

Any storage service that speaks the S3 API.

Elasticsearch

Index logs straight into an Elasticsearch index.

HTTP/S

POST batched logs to an HTTP or HTTPS endpoint.

Read the docs

USE CASES

What teams do with their logs

Once the logs are in your own storage, they work with the tools you already run.

  • Performance monitoring

    Spot latency issues, cache misses and traffic spikes as the batches arrive.

  • Security auditing

    Track suspicious requests, referrers and unauthorized access attempts.

  • Business analytics

    Feed your BI platform and chart how your content is used.

  • Data archiving

    Keep compressed logs for long-term retention and compliance.

HOW IT WORKS

From a name to a live job

Medianova Sales turns Logpush on for your account; then every job takes the same four steps. Filters are optional: with none, every record is pushed.

01

Name the job

Pick the organization and its CDN resources, or take every resource in that organization.

02

Choose fields

Keep the columns you want on the stream. The ones you leave out stay behind.

03

Filter, if you need to

Narrow the stream before it leaves. Skip this step and every record is pushed.

04

Connect and verify

Point the job at Stook, Amazon S3, S3-compatible storage, Elasticsearch or HTTP/S, then confirm the connection.

Turn on Logpush for your account

Medianova Sales enables Logpush and can adjust your delivery limits.

Talk to sales