Instances & Sources

Learn how to activate Instant Logs, select a storage region, and connect Medianova, Cloudflare, or Akamai log sources.

Each CDN source connected to Instant Logs runs as a separate instance. An organization can run multiple instances, and a single query can include one, several, or all connected sources.

Choosing a Plan and a Region

Before activating Instant Logs, choose a plan and a storage region. These settings determine the available capacity and where your logs are stored.

Plans and the Free Trial

Instant Logs plans differ in:

• Included log storage.

• Log retention period.

• Number of CDN sources you can connect.

• API access availability.

The core Instant Logs capabilities are available across self-service plans, including the explorer, filtering, field statistics, and export.

Self-service plans include a free trial. During the trial, you connect a CDN source, ingest your own logs, and use the available Instant Logs capabilities. A status indicator in the product shows the current trial status. At the end of the trial, you can subscribe to a plan or stop using the service.

Enterprise plans are arranged separately and do not include a dedicated Enterprise trial. You can use a self-service trial to evaluate Instant Logs with your own traffic before moving to an Enterprise plan.

Storage Region

Select a storage region when choosing your plan. The selected region determines where your Instant Logs data is stored and controls data residency for the organization.

The storage region applies at the organization level rather than to individual sources. After the region is selected, all sources added to the organization store their logs in the same region.

Storing one organization's Instant Logs data in multiple regions requires an Enterprise arrangement. Contact Medianova Support if your organization requires multi-region storage.

Activating Instant Logs

Instant Logs is available in the Medianova Control Panel under Edgesight → Instant Logs.

When you open Instant Logs for the first time, the product introduction provides a log preview and an option to choose a plan. After you confirm a plan or start a trial, the activation wizard opens.

The activation wizard contains four stages:

1

Source

Select the CDN provider for the instance:

• Medianova

• Cloudflare

• Akamai

Step 1 of the wizard - choosing which provider this instance will read.

Each instance connects to one CDN source. To connect another source, run the activation wizard again. Connected instances can then be queried together in the explorer.

2

Configure

The required configuration depends on the selected CDN provider. After configuration, supported sources use the same Instant Logs explorer.

Medianova

Select the Medianova organization whose logs you want to ingest, then enter a name for the instance.

The Medianova path: choose an organization, then name the instance.

The instance name defaults to the organization name and is used only to identify the instance. No configuration outside the Medianova Control Panel is required.

Cloudflare

Enter a name for the ingest endpoint.

Naming the Cloudflare ingest endpoint, with the ingest URL previewed below it.

Instant Logs provisions:

• An isolated ingest endpoint.

• A dedicated stream.

• An API token.

Instant Logs then displays the ingest URL. Use this URL when configuring the Cloudflare Logpush job.

Akamai

Enter a name for the ingest endpoint.

The same form for Akamai - only the provider you point it at differs.

Instant Logs provisions the ingest endpoint and provides the ingest URL and API token. The Instant Logs configuration is the same as for Cloudflare; on the provider side, Akamai uses DataStream for log delivery.

For Cloudflare and Akamai, the ingest URL and API token are displayed only during setup. Save both before leaving this stage. If the token is lost, you must create the endpoint again.

3

Deploy

Instant Logs provisions the log pipeline. Deployment usually takes approximately one minute.

The provisioning process includes the following stages:

• Creating instance -- Reserves the workspace.

• Building pipeline -- Prepares log storage.

• Connecting log stream -- Connects CDN logs to the pipeline.

• Finalizing access -- Issues and secures access credentials.

The provisioning timeline mid-flight - completed steps ticked, the current one still running.

The deployment status updates as each stage completes.

If a provisioning stage fails, the deployment status identifies the failed stage and provides Retry and Change plan options. You do not need to restart the activation wizard.

4

First Logs

For Medianova sources, logs begin flowing after the pipeline becomes active.

For Cloudflare and Akamai sources, configure the provider's log delivery service to send logs to the ingest URL provided by Instant Logs. See Connecting a Source That Is Not Medianova.

Setting up the pipeline. The ingest URL and token are shown here for the last time - save them now.

The wizard first completes the pipeline configuration and then starts listening for events. After the endpoint becomes active, incoming events are received whether or not you remain on the activation screen.

Listening for your first event. The endpoint is live; the wizard advances on its own when records arrive.

The ingest URL and API token for Cloudflare and Akamai are displayed for the last time during this stage. Save them before leaving the activation flow.

First logs received: the pipeline is live and the explorer is ready.

When the first records arrive, the wizard automatically confirms receipt and displays the number of records received. You can then open the Instant Logs explorer.

Reading Your First Logs

The Instant Logs explorer opens with the Last 15 minutes time range and no filters applied.

The explorer contains three main areas:

• The Log Volume chart.

• The log table.

• The Available Fields panel.

If these areas contain no data, increase the selected time range before troubleshooting the source connection.

Supported Sources

Instant Logs supports Medianova, Cloudflare, and Akamai as CDN log sources.

Medianova

Medianova CDN traffic uses the reference schema to which the other supported sources are mapped.

• 47 columns

• 47 populated

• Full explorer

No external log delivery configuration is required.

Cloudflare

Cloudflare connects to Instant Logs through a Logpush job.

Cloudflare provides the content_type field, which is not available in the Medianova schema. Medianova-specific topology fields remain empty.

• 48 columns

• 32 populated

• Full explorer

Akamai

Akamai connects to Instant Logs through DataStream. Its log format populates fewer fields in the common schema, including fewer origin-side timing fields.

• 47 columns

• 21 populated

• Full explorer

Use the source selector in the explorer to select one, several, or all connected sources. The selected sources apply to:

• The Log Volume chart.

• The log table.

• Field statistics.

• Export.

When multiple sources are selected, the log table includes an additional column identifying the source of each request.

The number of sources you can connect and the CDN providers available to you depend on your plan. A single query can include up to 10 sources.

Connecting a Source That Is Not Medianova

Cloudflare and Akamai use their existing log delivery services to send logs to Instant Logs. No agent or custom integration is required.

Instant Logs provides an ingest URL and API token during activation. Configure the provider's log delivery service to send logs to that endpoint.

Cloudflare Logpush

1

Open Cloudflare Logpush

In the Cloudflare Dashboard, go to Analytics & Logs → Logs → Logpush jobs.

2

Create a Logpush Job

Create a new job and select HTTP as the destination type.

3

Enter the Destination URL

Paste the Instant Logs ingest URL into the destination URL field.

4

Add the API Token

Configure the following custom header:

apikey: <your token>

The header authenticates log delivery requests sent from Cloudflare to the Instant Logs ingest endpoint.

5

Enable the Logpush Job

Save and enable the job.

Cloudflare begins delivering logs to the Instant Logs endpoint after the job becomes active.

Akamai DataStream

1

Open Akamai DataStream

In the Akamai Control Center, go to Common Services → DataStream.

2

Create a DataStream

Create a new stream and select HTTPS as the delivery method.

3

Enter the Endpoint URL

Paste the Instant Logs ingest URL into the endpoint URL field.

4

Add the API Token

Configure the following custom header:

apikey: <your token>

The header authenticates log delivery requests sent from Akamai to the Instant Logs ingest endpoint.

5

Activate the Stream

Activate the DataStream stream.

Akamai begins delivering logs to the Instant Logs endpoint after the stream becomes active.

In both cases, logs begin arriving within minutes. The Instant Logs activation wizard automatically detects the first event received by the endpoint.

Cloudflare Logpush and Akamai DataStream deliver logs to Instant Logs through an HTTP endpoint. Instant Logs does not require an additional agent between the CDN provider and the ingest endpoint.

Differences Between Providers

CDN providers do not record identical sets of log fields. Instant Logs normalizes supported field names and values into a shared schema so that the same filtering and exploration workflow can be applied across supported sources.

For example, provider-specific cache states are normalized to consistent values such as HIT and MISS.

If a provider does not record a particular field, Instant Logs returns that field without a value rather than removing it from the normalized schema. This keeps records from different sources aligned in the same table.

When multiple sources are selected, field discovery uses the intersection of fields supported by all selected sources. A field that is available only from one provider is therefore removed from the filter and statistics lists when another source that does not support the field is added. The field becomes available again when the applicable source is selected independently.

If a field disappears after you add another source, the underlying log data has not been removed. Instant Logs limits the available filter and statistics fields to those supported across all selected sources so that the same query can be applied consistently.