> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/logz/instant-logs.md).

# Instant Logs

Learn how Instant Logs provides near-real-time access to CDN request logs for   investigation, filtering, analysis, and export.

**Instant Logs** provides a live, searchable view of CDN request logs. Logs become available within seconds after requests are served, allowing you to investigate traffic by narrowing the time range, filtering by field values, reviewing field distributions, and inspecting individual requests.

Instant Logs supports **Medianova**, **Cloudflare**, and **Akamai** as log sources. Logs from supported providers are normalized to a shared schema and can be explored through the same timeline, table, and filtering workflow.

Instant Logs is available in the [**Medianova Control Panel**](https://cloud.medianova.com) under **Edgesight → Instant Logs**.

## What is Instant Logs?

Instant Logs allows you to investigate CDN request logs directly in the Medianova Control Panel without downloading log files or using a separate query language.

Filters apply consistently across the **Log Volume** chart, log table, and field statistics. This allows you to narrow the same result set by attributes such as status code, country, IP address, request path, and other supported fields.

<figure><img src="https://542970813-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtK7oIwmhUHdEJcaH4Hx8%2Fuploads%2FFc3pMMtXWiVEuXP2W8nz%2Finstant-logs.gif?alt=media&amp;token=9aab4d83-826b-4f85-bae9-d4ebfd31f2a3" alt=""><figcaption></figcaption></figure>

Each CDN provider generates logs in its own format. Instant Logs maps supported fields and values to a shared schema so that supported sources can be queried through the same explorer.

When multiple CDN sources are connected, their normalized logs can appear on the same timeline and in the same table.

## Why Choose Instant Logs

#### See Current CDN Traffic

Logs become available within seconds after requests are served. You can inspect recent traffic without waiting for a batch process or downloading a log file.

#### Explore Multiple CDN Sources

Medianova, Cloudflare, and Akamai logs can be explored through the same interface using normalized field names and values.

#### Filter Without a Query Language

Select values such as a status code, country, or IP address to narrow the current result set. The Log Volume chart, log table, and field statistics update together.

#### Analyze Traffic Volume

The **Log Volume** chart displays request volume over the selected time range. Select a time bucket to narrow the explorer to that interval.

#### Export Filtered Results

Export logs matching the selected sources, filters, and time range in **CSV** or **JSON (NDJSON)** format.

## How It Works

A request becomes searchable in Instant Logs through the following flow:

{% stepper %}
{% step %}
**Request served** -- The CDN edge processes the request.
{% endstep %}

{% step %}
**Log record generated** -- The CDN generates the corresponding log record.
{% endstep %}

{% step %}
**Streamed to your workspace** -- The log record is delivered to the Instant Logs workspace.
{% endstep %}

{% step %}
**Searchable** -- The record becomes available in the explorer.
{% endstep %}
{% endstepper %}

This process typically completes within seconds.

#### No Installation Required for Medianova Sources

Medianova CDN traffic already generates logs at the edge. After Instant Logs is activated, no external log pipeline configuration is required for Medianova sources.

Cloudflare and Akamai sources require a one-time connection using the log delivery mechanism provided by the respective CDN.

#### Isolated Data Storage

Instant Logs stores organization data in a logically isolated database with dedicated credentials.

For externally connected sources, each source receives its own ingest endpoint and stream for log delivery.

#### Retention Based on Your Plan

The period for which logs remain queryable depends on the Instant Logs plan. Queries cannot access logs older than the applicable retention window, even if you select a wider time range.

For detailed query and export limits, see [**Export & Reference**](/products/logz/instant-logs/export-and-reference.md).

## Coming From Raw Logs

{% hint style="info" %}
Raw Logs is deprecated and has been replaced by **Instant Logs**. Existing Raw Logs workflows are available through Instant Logs with an updated interface and additional exploration capabilities.
{% endhint %}

If you previously used Raw Logs, review the following differences before using Instant Logs:

<table><thead><tr><th width="158.333251953125">Capability</th><th width="262">Raw Logs</th><th>Instant Logs</th></tr></thead><tbody><tr><td>Volume over time</td><td>Not available</td><td>Log Volume chart with zoom into individual time buckets</td></tr><tr><td>Filtering</td><td>Filter form applied to the table</td><td>Cross-filtering across the chart, table, and field statistics</td></tr><tr><td>Field discovery</td><td>Column name required</td><td>Available Fields panel with distributions and one-click filtering</td></tr><tr><td>Operators</td><td>Equality</td><td>Ten operators, including contains, LIKE, and numeric comparisons</td></tr><tr><td>Request detail</td><td>Not available</td><td>Request detail view with all captured fields, raw JSON, and copy functionality</td></tr><tr><td>Sources</td><td>Medianova only</td><td>Medianova, Cloudflare, and Akamai on the same timeline</td></tr><tr><td>Export</td><td>CSV of visible records</td><td>CSV or NDJSON of the complete filtered result set, delivered in parts and separated by source</td></tr><tr><td>Column selection</td><td>Edit Columns</td><td>Available Fields panel with column selection, distributions, and filtering</td></tr></tbody></table>

{% hint style="warning" %}
Export behavior has changed. Raw Logs exported the records currently visible in the table. Instant Logs exports the complete result set matching the selected filters and time range, up to the applicable export limit. Exports are delivered in parts of 10,000 rows. Review the match count in the export panel before downloading.
{% endhint %}

{% hint style="info" %}
**Edit Columns** has been replaced by **Available Fields**. In addition to controlling the fields displayed in the table, Available Fields provides field distributions and filtering controls.
{% endhint %}

## Where to Next

* [**Instances & Sources**](/products/logz/instant-logs/manage-raw-logs.md) -- Choose a plan and storage region, activate Instant Logs, and connect Medianova, Cloudflare, or Akamai sources.
* [**Exploring & Discovery**](/products/logz/instant-logs/field-definitions.md) -- Configure time ranges, search and filter requests, inspect field distributions, and analyze Log Volume.
* [**Export & Reference**](/products/logz/instant-logs/export-and-reference.md) -- Export filtered result sets and review query, export, retention, and interface limits.
* [**Edgesight Analytics**](/products/logz/mn-logz-analytics.md) -- Analyze CDN traffic through historical dashboards and longer retention windows.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://clients.medianova.com/products/logz/instant-logs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
